Re: [jamboost] Introduction & small patch & question

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-01-21 02:33:08

Hi Niklaus,

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

Welcome here!

> 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]

Does not work for me :-( On x86 os.uname()[4] returns "i686". I've put the 
following extra logic:

cpu = os.uname()[4]
if re.match("i.86", cpu):
jam_build_dir = "bin.linuxx86";
else:
jam_build_dir = "bin.linux" + os.uname()[4]

and committed this version. Thanks!

> Would somebody be interested in modifications/extensions to boost.jam to
> support cross-compiling for vxWorks?

Definitely. Cross-compiling is a thing we always wanted to implement, but 
nobody pushed us hard enough to get this done. Since you're doing 
cross-compiling on regular basics, I think you can easily outline the areas 
where changes are needed.

- Volodya