Re: [Boost-build] Generating CMake package files using Boost.Build

Subject: Re: [Boost-build] Generating CMake package files using Boost.Build
From: Stephen Kelly (hello_at_[hidden])
Date: 2016-05-12 14:42:01

Raffi Enficiaud wrote:

> Le 12/05/16 à 10:42, Stephen Kelly a écrit :
>> Raffi Enficiaud wrote:
>>
>>> What does in my sentence make you believe that I did not understand what
>>> cmake packages are supposed to cover?
>>
>> Too many reasons. Look again at how you brought NSIS and .deb into the
>> discussion and then mentioned binary packages several more times.
> 
> I was stressing the fact that "package" may mean a lot of different
> things. 

I pointed out that 'package config files' are part of cmake and your 
response was 'I am more interested in building than packaging'. 'package 
config files' is very specific - it does not mean lots of different things, 
and it doesn't mean 'packaging'.

> Creating .deb file using cmake is "packaging with cmake" as
> well. There is a problem in the terminology.

I was specifically not talking about that.

Anyway, we can drop this point. I think it's a miscommunication/diversion 
which we would not have if we had this conversation in person. The important 
point is what you said:

> I do little know about this package producer/consumer feature.

>> I think you're just missing some base understanding. I can't tell if you
>> read the documentation I pointed you too.
> 
> I already did, thanks.

Great!

> This is indeed going nowhere, at least for me. Your initial message was
> posted almost 6 months ago and no replies until mine, I let the
> conclusions on your side.

Yes, and thanks again for your interest. The silence in the last 6 months 
led me to already believe that no one in the boost community (at least the 
people who tend to steer the ship) knows enough about cmake to understand 
config files, so I gave up long before you responded :).

I'm just waiting for someone to come along who does understand the benefits, 
and then...

>> ... we can work on the 'what will they contain' and the 'how will we
>> make them', instead of the 'why' and the 'what is this?'.

> I disagree with your approach, and I asked a fair amount of questions
> about the "how".

My reference to 'how will we make the files' is about designing, coding and 
integrating a solution. We are not at that point.

Thanks for your interest and responses!

Steve.