Subject: Re: [Boost-build] feature detection
From: alainm (alain.miniussi_at_[hidden])
Date: 2016-10-25 06:38:14
Forgot to mention: once the flag detected, is there some
support/standard way to put it in a config header file ?
(something similar to configure_file in cmake).
I need to detected some feature/characteristic to decide if I can
install/build some part of a lib.
But then I need to remember that choice for the library users who
probably wont use b2 to build theirs code.
So I need to provide a header file with :
#define FEATURE 1
Sorry if it's already in the doc.
On 25/10/2016 11:37, Vladimir Prus wrote:
> On 25-Oct-16 12:16 PM, Dominique Devienne wrote:
>> On Tue, Oct 25, 2016 at 10:56 AM, Vladimir Prus <vladimir.prus_at_[hidden]
>> <mailto:vladimir.prus_at_[hidden]>> wrote:
>> [...] I've put together an example, here:
>> It sets a macro based on compilability of a C++ source file,
>> which seems
>> like what you're after. [...]
>> I've seen the term 'feature' being used several times in the BB threads.
>> But is it an abstract concept with no concrete representation in the
>> Jam/BB language?
>> Or is feature somehow a keyword too?
> it is not a keyword, but it's not an abstract concept either.
> The introduction into features can be found at
> and the src/build/feature.jam module has functions to define a feature,
> specifying its properties.
>> For a BB novice like me, it's unclear reading your example.
>> If 'feature' is just a name in that example, a different less-generic
>> might clear up that confusion IMHO. My $0.02. --DD
> The use of 'feature' in example was unfortunate, I've pushed a commit
> to rename it.
> Hope this helps,
-- Alain Miniussi Pole Génie Logiciel Scientifique Observatoire de la Côte d'Azur Blv de l'Observatoire, Nice
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk