From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-06-02 10:00:19
On Thursday 02 June 2005 18:48, João Abecasis wrote:
> Vladimir Prus wrote:
> > On Wednesday 01 June 2005 21:29, Eric Niebler wrote:
> >>David Abrahams wrote:
> >>>You really think it's likely that they've set up HOME and yet have
> >>>installed a user-config.jam that they don't want bjam to use in
> >>>%HOMEDRIVE%%HOMEPATH%? I don't.
> >>Haha, ok. You're right. But as it so happens, this was exactly the case
> >>on my machine. I struggled to get bjam working the first time, and in
> >>the process, I scattered user-config.jam all over the place. I ended up
> >>with one in %HOME% and a turd user-config.jam in %HOMEDRIVE%%HOMEPATH%
> >>(which I just deleted to be safe).
> > Not sure how much of a help that would be, but I've added a logic to
> > print the locations of site-config.jam and user-config.jam when the
> > --debug-configuration
> > option is specified. Probably that would help the next time somebody has
> > the same problem.
> Nice feature! I just used it to track a duplicate toolset configuration
> which surfaced after the changes to the user-config.jam lookup rules.
> One suggestion for improvement...
> Instead of printing "loaded site/user-config from ..." after the fact, I
> think it would be better to print "loading ..." before entering these
Well, it's a bit harder to implement ;-) We don't know the module location
until we call modules.load
I'll see if I can implement the desired behaviour with some tricks.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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