Hey Gregg, IoTivity immediately came to mind first time I heard of Bazel. The remote caching would be a huge win as hopefully it would bring out build times back down to <15 minutes for Linux. And the way they do external dependency[1] management I expect would save developers a lot of time, and provide a much more stable environment.
Obviously one of the major blockers to using it is time and effort to convert the build system over from Scons. I noticed you started a bit of this work[2] (Thank you!) and I'm going to poke it a bit in the next couple weeks to see if I can't wrap my head around Bazel as well. Regards, Trevor Bramwell [1] https://docs.bazel.build/versions/master/external.html#external-packages [2] https://github.com/OpenOCF/iochibity/tree/bazel On Sat, Apr 07, 2018 at 08:03:55PM +0000, Gregg Reynolds wrote: > A while back I mooted the possibility of moving iotivity to Bazel. FWIW > I've been using Bazel for OpenOCF for months, and imho it beats the snot > out of Scons, especially wrt cross-compiles. I'll save the details for > another msg; for now I just want to draw your attention to 2 features: > > - Bazel's remote caching ( > https://docs.bazel.build/versions/master/remote-caching.html). This seems > like a huge win for CI. > > - Android support is extraordinarily good: see > https://blog.bazel.build/2018/02/28/incremental-dexing.html and > https://docs.bazel.build/versions/master/mobile-install.html > > Note that Bazel supports Java/Android builds natively. No need for Gradle > etc. One build system for all languages. > > Gregg > _______________________________________________ > iotivity-dev mailing list > iotivity-dev@lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
signature.asc
Description: PGP signature
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
