At Saturday 2004-10-02 03:11, you wrote:
Hmmm, I hadn't realized John was going to change it (we went to all the trouble of checking for the environment variable just so we COULD keep the original path)
John, I think looking in the registry is a BAD idea... the Environment variables are readily visible to users, the registry is NOT
Just to be clear here - I haven't changed anything yet - or even experimented with such a change, more like thinking out loud.
It was to THIS change I referred when I said: "John was going to change" no change should have been necessary......................... T:\Projects\boost\tools\build\v1>cvs log vc8.0-tools.jam RCS file: /cvsroot/boost/boost/tools/build/v1/vc8.0-tools.jam,v Working file: vc8.0-tools.jam head: 1.4 branch: locks: strict access list: symbolic names: keyword substitution: kv total revisions: 4; selected revisions: 4 description: ---------------------------- revision 1.4 date: 2004/10/01 10:39:16; author: johnmaddock; state: Exp; lines: +2 -1 Updated default install path to reflect current Beta. ----------------------------
However if a particular toolset readily identifies itself in the registry, that seems to be a lot more reliable than messing with environment variables that the user has to type in every time they want to use Boost.
I didn't suggest that the user type in anything, I suggested we use the environment variable(s) which are put there by the install process.
BTW the Metrowerks jam-toolset already works this apparently.
John. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"