![]() That said, I don’t think ROS should support two parallel build systems - the maintenance burden of two build systems in an open source ecosystem that already struggles to find enough maintainers would be too high (e.g. To fully achieve the benefits we had to write bazel build rules for all our dependencies too. But it was a massive undertaking, and my experience was that bazel does not play nicely with other build and packaging systems at all. The benefits of reproducibility are huge, and cloud based build execution/caching led to an order of magnitude improvement in developer productivity. I’m a big fan of bazel - at Cruise we completely replaced catkin+cmake with bazel. One critical point I see is the additional maintenance burden for repo maintainers, since they would have to maintain the build configuration twice, once for CMake and once for Bazel. Those designs are potentially in opposition to solutions currently in place in the ROS ecosystem Some other topics require a careful design that will support those goals (repo setup, message generation, ament plugin magic).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |