On 17-Aug-16 04:29, Florent Castelli wrote:
The Boost source download is cached outside of the build directory
in a unique folder.
So it’s effectively only done once for all platforms and then reused.
This is true for local machines and for custom build servers like
your personal Jenkins.
On 17-Aug-16 08:36, Elizabeth A. Fischer wrote:
> > I don't think CMake is the best place to do it,
> Can you provide any details? I personally think that CMake is a
> natural and the only place where it should be done.
The most important reason here is because there are combinatorially
many
Well, I tried upstreaming the new build scripts to some projects and it
didn’t go well.
Some of the reasons I’ve heard of:
> I installed CMake 2.8.6 five years ago and I don’t want to update yet
> again! People relying on old versions is quite common and any attempt
> to raise the min version
On 16-Aug-16 16:37, Florent Castelli wrote:
Well, I tried upstreaming the new build scripts to some projects and
it didn’t go well.
Some of the reasons I’ve heard of:
- Windows developpers don’t use CMake, they have project files on the
repository.
The CMake files for Windows will never be
On 16-Aug-16 17:04, Florent Castelli wrote:
On 16 Aug 2016, at 15:29, Ruslan Baratov > wrote:
On 16-Aug-16 13:52, Florent Castelli wrote:
For example, Boost is used by 5 platforms: Windows, OSX, Linux,
Android and iOS.
Each
On 16-Aug-16 13:52, Florent Castelli wrote:
For example, Boost is used by 5 platforms: Windows, OSX, Linux, Android and iOS.
Each platform has a different CPU target (or many 32/64bit, x86/ARM).
Each platform has many compilers.
Some platforms have instrumentation options (Debug / Release, ASan,
CMake builds for existing libraries are certainly an interesting and useful
thing, and deserve to be posted in a GitHub repo somewhere. They should
also serve as the basis of a campaign to get the library authors to
incorporate the CMake build directly in their repos.
But any approach that
Very interesting discussion, we have the same issues here.
Florent Castelli, how many third parties libraries do you use ? I think a
super build can be a very good solution but I'm wondering how much third
party code you have to build. Here we use OpenCV, with, boost, and poco,
and other