|
Boost Testing : |
From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-02-17 19:45:15
Stephen W. Carson wrote:
I finally have some time again to work on this..
> Rene says the fix for this is checked in. I just ran again yesterday and
> the CMD problems haven't gone away.
Darn :-(
> I guess this is what I would do if I understood JAM and the source
> control system that y'all use:
> -Verify that Rene's change indeed prevents references to CMD files on
> the Mac platform.
You can do this quickly with the aid of the boost sources by:
1. cd [boost-root]/tools/build/v1/example/lib_use
2. bjam -n -sTOOLS=cw -a
And look at the output to see if there are any "@"'s in the commands.
THe "-n" "-a" combination causes all to build and only outputs the
commands without running them.
> -Verify that Rene's change is ending up in the tarball.
I could verify part of that.. Where is the tarball obtained from? (I'll
see if I can figure this out by myself) So I can download it directly
and see what it has. I it has the correct content then I can MD5 it so
you can check if it's the same tarball you have.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq