Subject: Re: [boost] Cmake
From: Gary Furnish (gfurnish_at_[hidden])
Date: 2017-06-24 22:45:41
This is a pretty well known race condition that I haven't seen a fix
for yet. The workaround is multiple src directories if you might call
cmake in parallel after doing something that will trigger a rebuild.
Even I think this is a poor solution and I like CMAKE. I like the
idea of B2, it just doesn't support a bunch of things I would like to
support all that easily.
On Sat, Jun 24, 2017 at 4:10 PM, Niall Douglas via Boost
>> One of the issues that I've seen is that the generated project files are
>> just shells around cmake invocations of all kinds. As opposed to direct
>> project declarations. Which means that they are susceptible to parallel
>> build bugs in cmake and make it awkward to deal with them past just
> The project files generated by cmake are native to that build system.
> cmake injects a prebuild call to cmake to check if any cmake files have
> been changed, if so it rebuilds the build system and rebootstraps the build.
> ned Productions Limited Consulting
> http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost