From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-07-04 07:07:35
> In fact I found some spare time to give it a try. I did not have
> chance to plug it in real project, just compiled bjam and examples.
> Everything worked fine for me.
Ok, I'll release M5 then. If any problems turn out later, M5.1 can always be
> Few moments:
> 1. The problem we dicussed some time ago with bad bison in path still
> there. Well the problem is not that build fails, after all detecting
> wether bison works or not is probably a little bit too much, the
> problem is that after bjam build fails because of wrong bison, simply
> adding valid bison to path will not make build happy, it tries to
> remove already removed jamgram.c and fails. Starting over with fresh
> copy of jam sources fixes the problem.
Hmm... I though Rene has fixed this issue. However, I was able to reproduce
this problem. It now filed at
Rene, care to take a look?
> 2. Msvc link command does not have -nologo switch.
> 3. customization is a nice example, however it fails to run on windows
> (from windows shell) because shell is so dumb that it can't execute
> ./inline_file.py, however it is capable of executing "./inline_file.py"
> This will make example run on windows system with windows version of
> python installed. However it still will not run on windows systems
> with cygwin python from windows shell even if cygwin python is in the
> path (python ./inline_file.py will work in this case).
OTOH, the windows box I used to V2 testing does not have python in path. I
have a feeling that most windows users don't have python in path, since .py
files are executed anyway.
I've added quotes and instructions for Cygwin Python to the example.
> I have not tested getext, and qt examples due to lack of required
In fact, I don't know if gettext even exists for windows.
Thanks for your testing!
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