Introduction & small patch & question

From: Niklaus Giger (NiklausGiger_at_[hidden])
Date: 2005-01-20 15:40:49

Hi everybody

I am a software engineer at Netstal Machinery, a manufacturer of plastic 
injection modules, where we run our own control SW.

Among other things I maintain our build infrastructure. About 4 years ago we 
dipped Make in favor of Perforce Jam and were quite happy with its 
capability.

Lately the complexity increased as we integrated more third party software 
modules (in source code), introduced unittest running under MinGW, etc. Also 
I looked for a way to test our build system. Therefore we are considering a 
switch to boost-jam (or parts of it). Probably several weeks of work.

We cross-develop under Windows/XP for a PowerPC target running vxWorks. As I 
get my salary, I have to accept two unfree OS at work. But at least one of 
them works reliably. Runnning the unittests under cygwin resulted in a few 
errors. I will probably discuss them in a later email.

Therefore I decided to run first the tests on my personal PowerBook running 
Debian/GNU Linux. After compiling from source, etc calling
python test_all.py gave me the following warning 
Note: skipping extra tests
unit_tests : Cannot find built Boost.Jam
Traceback (most recent call last):
File "test_all.py", line 149, in ?
run_tests(critical_tests, tests)
File "test_all.py", line 34, in run_tests
__import__(i)
File "/mnt/data.ng/boost/tools/build/v2/test/unit_tests.py", line 5, in ?
t = Tester(pass_toolset=0)
File "/mnt/data.ng/boost/tools/build/v2/test/BoostBuild.py", line 137, in 
__init__
os.exit(1)

The following patch (my first Python code!) fixed the problem. Could somebody 
please review and apply it? 

diff -r1.65 BoostBuild.py
96c96
< jam_build_dir = "bin.linuxx86"
---
> jam_build_dir = "bin.linux"+os.uname()[4]
Would somebody be interested in modifications/extensions to boost.jam to 
support cross-compiling for vxWorks? 
Best regards
-- 
Niklaus Giger
Wieshoschet 6
CH-8753 Mollis