When you switch to bazel, someone would have a very hard time (the one person who is doing the transition). Infrastructure task that would taken multiple team collaboration from all the team in the company and few month of painful transition were done by a single team without cooperation or disrupting other teams.ĭo not listen to all these guys here advising for sticking to cmake.
#Bazel clion how to#
We change logging system of the whole company without developers even noticing that the change happened. How to read the tensorflow source code with clion's bazel plugin, how to import and build, I can read an navigate inside the code base.This problem has been bothering me for a week. With cmake, this wouldn't even have been possible. We created a memory allocation for part of entire stack and it just took a week to migrate. Result after switching, we could do stuff in a week that with cmake, we never even attempted. I made a bunch of script to reduce the number of tedious jobs. Once you do it for a few, the others are relatively easy to do. It was a fairly large project and over 100's of different libraries, and 10's of custom asset generation/compiling rules for many of them, I made a bazel build file personally. I paid the personal price for it with lots and lots of late nights session trying to make everything works. It was definitely hard, specially since bazel we started with was on version 0.xx. We switched to Bazel in my company from make and cmake. Not familiar with meson but very familiar with cmake and make.
0 kommentar(er)
