Request for "--config-file=FILE" to override user-config.jam/site-config.jam

I have been working on updating the Unix-like configure
script to  
work with BBv2. This has become rather more important
recently with  
the new Getting Started guide recommending the use of
"configure".

With BBv1, the configure script just built up a big command
line to  
pass to bjam with all of the configuration parameters.

With BBv2, the configure script needs to generate either a
user- 
config.jam or a site-config.jam. The problem is, we don't
want to  
overwrite the user's existing configuration, the site
configuration,  
or the sample configurations that are a part of bjam.

One hack I can think of would be to create a
test-config.jam, but  
that's just a hack. I think the right way to handle this
would be for  
BBv2 to support a new command-line option,
--config-file=FILE, that  
allows the user to provide the name of an alternate
configuration  
file.  Unfortunately, I've been staring at build-system.jam,
which  
looks like the place to do it, and I don't understand how we
can make  
this happen?

Do we want this feature?
Could someone give me a hint as to how to do this,
or---better  
yet---"make it so"?

	Cheers,
	Doug
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Wednesday 13 December 2006 01:22, Doug Gregor wrote:
> I have been working on updating the Unix-like configure
script to  
> work with BBv2. This has become rather more important
recently with  
> the new Getting Started guide recommending the use of
"configure".
> 
> With BBv1, the configure script just built up a big
command line to  
> pass to bjam with all of the configuration parameters.
> 
> With BBv2, the configure script needs to generate
either a user- 
> config.jam or a site-config.jam. The problem is, we
don't want to  
> overwrite the user's existing configuration, the site
configuration,  
> or the sample configurations that are a part of bjam.
> 
> One hack I can think of would be to create a
test-config.jam, but  
> that's just a hack. I think the right way to handle
this would be for  
> BBv2 to support a new command-line option,
--config-file=FILE, that  
> allows the user to provide the name of an alternate
configuration  
> file.  Unfortunately, I've been staring at
build-system.jam, which  
> looks like the place to do it, and I don't understand
how we can make  
> this happen?
> 
> Do we want this feature?
> Could someone give me a hint as to how to do this,
or---better  
> yet---"make it so"?

Doug,
on HEAD and RC_1_34_0 as of few minutes ago, you should be
able to use:

	--user-config=/tmp/user-config.jam

This option overrides just user-config.jam, I'm not sure if
overriding site-config.jam is
needed or not, but it's anyway empty in default Boost.Build
install.

HTH,
Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Dec 18, 2006, at 8:33 AM, Vladimir Prus wrote:
> Doug,
> on HEAD and RC_1_34_0 as of few minutes ago, you should
be able to  
> use:
>
> 	--user-config=/tmp/user-config.jam
>
> This option overrides just user-config.jam, I'm not
sure if  
> overriding site-config.jam is
> needed or not, but it's anyway empty in default
Boost.Build install.

Thanks! Everything seems to be working well, now; the
updated  
configure script will be available on HEAD and RC_1_34_0 in
the next  
hour or two.

	Cheers,
	Doug
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build