Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

2016-08-16 Thread Elizabeth A. Fischer
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 wil

Re: [CMake] Private dependencies of static libraries exported as targets

2016-08-16 Thread Nicholas Braden
Ah, I misunderstood what you were asking about. It would be pretty weird if CMake didn't know that static libraries always need all their dependencies linked regardless of privacy, but I agree it should at least be mentioned somewhere. My bad. As for include path bloat, I cannot replicate this in

Re: [CMake] Private dependencies of static libraries exported as targets

2016-08-16 Thread Ivan Shapovalov
TBH, I do not see the "PRIVATE dependencies are made PUBLIC for the purposes of linking when the dependent is static library" there. --  Ivan Shapovalov / intelfx / On 2016-08-16 at 02:35 -0500, Nicholas Braden wrote: > Yes, the behavior is documented in several places, the most prominent > bein

Re: [CMake] Need ideas/opinions on third party library management

2016-08-16 Thread Daniel Schepler
For what it's worth, what I've done here is to create binary packages of each third-party library for each supported platform (i.e. .deb packages for Ubuntu, .rpm packages for RHEL/CentOS, Chocolatey packages for Windows). Except for cases where the system already provided sufficient versions o

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

2016-08-16 Thread Ruslan Baratov via CMake
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 u

Re: [CMake] Need ideas/opinions on third party library management

2016-08-16 Thread Ruslan Baratov via CMake
On 13-Aug-16 03:12, Elizabeth A. Fischer wrote: I don't think CMake is the best place to do it, for a number of reasons. I would not try to re-invent the wheel here. Can you provide any details? I personally think that CMake is a natural and the only place where it should be done. On 16-Au

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

2016-08-16 Thread Ruslan Baratov via CMake
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 platform has a different CPU target

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

2016-08-16 Thread Ruslan Baratov via CMake
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,

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

2016-08-16 Thread Elizabeth A. Fischer
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 requir

Re: [CMake] [cmake-developers] Need ideas/opinions on third party library management

2016-08-16 Thread Benjamin Ballet via CMake
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 things...

Re: [CMake] Private dependencies of static libraries exported as targets

2016-08-16 Thread Nicholas Braden
Yes, the behavior is documented in several places, the most prominent being here: https://cmake.org/cmake/help/latest/manual/cmake-buildsystem.7.html#transitive-usage-requirements On Mon, Aug 15, 2016 at 9:22 PM, Ivan Shapovalov wrote: > On 2016-08-15 at 21:46 -0400, Guillaume Dumont wrote: >> A