Re: [jamboost] Pitfall -- environment variables

From: Richard Hadsell (hadsell_at_[hidden])
Date: 2002-03-28 12:06:10

David Abrahams wrote:
> 
> We're going to stop relying on environment variables for
> boost.build-specific configuration (except for BOOST_BUILD_PATH, which
> will be optional), so there will be no need for BOOST_xxx or JAM_xxx.
> For more details, www.boost.org/tools/build/architecture.html.
> 
> We're never going to stop responding to "standard" environment variables
> such as $(OS) when they can be used to generate a correct configuration
> without user intervention on 99% of all systems. However, as I said,
> we'll provide a way for users to override those settings by supplying
> explicit configuration (in a configuration file).

I didn't know that OS has a standard value for various platforms. I was only
aware that we set it on all of our Unix systems in a script that everyone runs
at start-up. Can you point me to a list of standard values? I'd like to know
what to watch out for in the future.

It would still be very helpful to list up front in the build docs OS and any
other environment variables that don't have a BOOST_ or JAM_ name but affect the
build.

-- 
Dick Hadsell	914-259-6320 Fax: [phone]
Reply-to:	hadsell_at_[hidden]
Blue Sky Studios http://www.blueskystudios.com
44 South Broadway, White Plains, NY 10601