Re: [idea] Build GIL stand-alone

Subject: Re: [idea] Build GIL stand-alone
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2018-06-21 17:14:42

On 21 June 2018 at 02:27, Stefan Seefeld <stefan_at_[hidden]> wrote:
> On 2018-06-20 04:43 PM, Mateusz Loskot wrote:
>>
>> Stefan, in your comment to PR [1], you shared this wish:
>>
>> "I'd really like to be able to build Boost.GIL stand-alone,
>> but that ain't possible with Boost.Build anyhow..."
>>
>> This sounds like an interesting idea and I guess it may be possible
>>
>> Could you elaborate what you have in mind and
>> what specific obstacles do you see?
>
>
> Well, the use-case I have in mind is the same I keep repeating on the Boost
> mailing list, as well as on the Boost.Build list, with respect to all Boost
> libraries:
>
> Improve the build system such that any Boost library can be built not
> in-tree with the entire Boost superproject checked out, but only with in its
> own stand-alone repo, where any references to prerequisite Boost libraries
> are met from externally installed Boost libraries.

That's one of major motivations I added and maintain the CMake setup

I have filled the Development [1] section in the contributors guide
explaining in details how to use CMake in both, the super-project
modes and the lightweight stand-alone mode.

[1] https://github.com/boostorg/gil/blob/develop/CONTRIBUTING.md#development

> I understand that Boost.Build currently doesn't support that, but I have
> managed to do exactly that with Boost.Python, using faber
> (https://stefanseefeld.github.io/faber), and I have indeed started work on
> doing the same with Boost.GIL (see for example
> https://github.com/boostorg/gil/blob/develop/fabscript).

Good. I've added "Using Faber" section for you :-)

[2] https://github.com/boostorg/gil/blob/develop/CONTRIBUTING.md#using-faber

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net