On Fri, Apr 13, 2018, 2:44 PM Trevor Bramwell
wrote:
...
> I noticed you started a bit
> of this work[2]
Also, that's no longer experimental; OpenOCF now uses Bazel exclusively for
building. It uses autoconf for source config. This works quite nicely. For
example it means we can configure (inc
On Fri, Apr 13, 2018, 2:59 PM Gregg Reynolds wrote:
>
> Not that a Bazel
>
Make that "Note that "
___
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
On Fri, Apr 13, 2018, 2:44 PM Trevor Bramwell
wrote:
> 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.
Thought you might like that bit.
And t
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 p
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 r
