Subject: Re: [boost] Switch to CMake -- Analysis
From: Florent Castelli (florent.castelli_at_[hidden])
Date: 2017-07-27 14:24:12
On 25/07/2017 09:06, Norbert Wenzel via Boost wrote:
> On 07/21/2017 10:28 PM, Florent Castelli via Boost wrote:
>> On 21/07/2017 22:22, Andrey Semashev via Boost wrote:
>>> On 07/21/17 22:30, Alain Miniussi wrote:
>>>> On 21/07/2017 19:24, Andrey Semashev via Boost wrote:
>>>>> Actually, as a user I do care and not in favor of CMake because
>>>>> there is always a possibility that Boost requires a newer CMake
>>>>> version that is not available on my platform.
>>>> We could embed the required CMake distribution in boost, compile it,
>>>> and use it to build boost ?
>>> There's the build dependencies of cmake on Ubuntu: [...]
>>>
>>> Are you going to include those as well?
>> All the required dependencies (beside OpenSSL for cURL) are included
>> with the CMake sources and it will optionally use those.
> We had problems with using the CMake versions of eg. cURL in our company
> and switched to using the system libraries. I think this might have to
> do with missing OpenSSL but cURL without TLS support is pretty useless
> today. So we were not able to build our own (usable) CMake without using
> system libraries.
>
> _______________________________________________
> Unsubscribe & other changes: http://listarchives.boost.org/mailman/listinfo.cgi/boost
It depends on the context. Will Boost's CMake reference anything over
HTTPS or will it be self-contained? Probably self contained, so that
wouldn't be a problem.
If you require a full version of CMake, it is possible to build it using
your system cURL, which isn't too difficult to build either.