From: Vladimir Prus (ghost_at_[hidden])
Date: 2001-11-23 09:19:25
David Abrahams wrote:
> ----- Original Message -----
> From: "Vladimir Prus" <ghost_at_[hidden]>
> > Toon Knapen wrote:
> > > As for windows, I'm only an occasional windows user so I guess others
> > > are in a better position to provide the windows jam exe.
> > Well, jam.exe is no problem. boost-build.exe can be. I've written a C
> > code which forwards to jam.exe with all the paths guessed from argv.
> > The
> > other option would be to append the path setting to autoexec.bat. (Shell
> > can't be used for forwarding due to problem with spaces in parameters;
> > console programs simply can't access registry).
> > Is the following procedure acceptable:
> > 1. Zip is unpacked somewhere
> > 2. boost-build.exe --install
> > is run, and adjusts autoexec.bat
> > 3. autoexec.bat is reread (after reboot?)
> > 4. commands boost-build and jam became available.
> What is boost-build.exe? I guess the point is to automatically find the
> boost installation and set up the neccessary environment before invoking
Yep. My package for RedHat does the same trick.
> I have a few reactions, all at once:
> 1. Wow, that's a neat idea
> 2. The name is kinda long
Not sure. I type this name several types a day but isn't bored yet.
> 3. Is running jam with jam -sBOOST_ROOT="..." really too much to ask of
I think it's too much even for developers. I think that for users which just
want to build some program, this is surely overkill. They'll need to type as
few command as possible.
> 4. Should we do this on the jamboost list?
Already here :-)
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