Re: [boost] [beast] Request for Discussion

Subject: Re: [boost] [beast] Request for Discussion
From: Edward Diener (eldiener_at_[hidden])
Date: 2016-10-02 20:38:29

On 10/2/2016 7:55 PM, Paul Fultz II wrote:
>
>> On Oct 2, 2016, at 12:01 PM, Edward Diener <eldiener_at_[hidden]> wrote:
>>
>> On 10/1/2016 8:58 PM, Paul Fultz II wrote:
>>>
>>>> On Oct 1, 2016, at 7:39 PM, Vinnie Falco <vinnie.falco_at_[hidden]> wrote:
>>>>
>>>> On Sat, Oct 1, 2016 at 8:20 PM, Paul Fultz II <pfultz2_at_[hidden]> wrote:
>>>>> The library looks nice
>>>>
>>>> Thanks!
>>>>
>>>>> I tried to run the tests and install it using cmake and it both failed.
>>>>
>>>> If you could please be so kind as to create an issue on the Beast
>>>> GitHub repository page with the details, I will try to address it
>>>> right away:
>>>> https://github.com/vinniefalco/Beast/issues
>>>
>>> Ok, will do.
>>>
>>>>
>>>>> Also, looking at the cmake, it looks like you use coroutines.
>>>>
>>>> Beast is header-only, the Jamfile and CMakeLists.txt are only for
>>>> building the unit tests and the examples.
>>>
>>> Well, cmake should install the library, even its header-only.
>>
>> Why should CMake "install" a header-only library ?
>
> There are a lot of reasons for this:
>
> 1) Cmake can install configured headers in the library(such as a version or config header).
>
> 2) Cmake can install packaging information to make it easier to use and link the library. Just because it is header-only doesn’t mean it doesn’t need to link against other libraries.
>

Whatever CMake can or cannot do, Boost should not require its use for 
anything right now since their is no official support for it.

>> Boost does not use CMake and header-only libraries do not need to be "installed”.
>
> Boost.Hana does use cmake and is header-only that is installed with cmake.

Boost.Hana is part of Boost now and is "installed" when you install 
Boost. In Github Boost Hana is installed when I get the Hana submodule. 
If Boost Hana needs CMake in order to be installed or in order to work 
that is news to me, and I am sure it would also be news to other Boost 
developers.

I have no official stake in whatever debate may exist regarding Boost 
Build and CMake but I think that, even if you favor CMake, you should 
not be saying that CMake is necessary for Boost when it is not.