Re: [Boost-users] [bcp] [shared_ptr] [wave] Extracting subsetofboostforshared_ptr - 3.2MB?

From: Nat Goodspeed (ngoodspeed_at_[hidden])
Date: 2006-02-19 08:06:47

> -----Original Message-----
> From: boost-users-bounces_at_[hidden] [mailto:boost-users-
> bounces_at_[hidden]] On Behalf Of David Abrahams
> Sent: Saturday, February 18, 2006 1:42 PM
> To: boost-users_at_[hidden]
> Subject: Re: [Boost-users] [bcp] [shared_ptr] [wave] Extracting
> subsetofboostforshared_ptr - 3.2MB?
> 
> > Wouldn't it
> > work just to point bcp to the compiler of interest -- by giving it
the
> > name of one of a set of small prepackaged files that #defines the
> > vendor-specific compiler-predefined macros that Boost cares about --
> 
> Also, there are macros introduced by Jamfiles and configuration macros
> set by users in their own Jam/Make/whateverfiles.  Unless you know
> what their values will be ahead of time, you may leave out some files
> the user will need.

[Nat] Okay. But the reason I suggested capturing a compiler's typical
#defines in a config file was to enable a user to create a custom one
containing their own #defines as well. Heh, the custom config file
wouldn't need to *clone* the generic one packaged with bcp: it could
#include the generic one and then add to it.