List Info

Thread: Problems running CW tests on Darwin




Problems running CW tests on Darwin
user name
2006-02-23 03:56:03
Hi,

So I managed to get a snapshot of CVS onto my test machine
and followed 
the instructions for configuring the v2 tests.  Here's the
output from 
the command.

[~/Projects/boost/status] Noel% ~/bin/bjam --v2 -n
warning: toolset cw initialization: can't find tool
mwcc.exe
warning: initialized from
Building Boost.Regex with the optional Unicode/ICU support
disabled.
Please refer to the Boost.Regex documentation for more
information
(and if you don't know what ICU is then you probably don't
need it).
error: Unable to find file or target named
error:     '/python//python_for_extensions'
error: referred from project at
error:     '../libs/python/test'

And here is the environment, bjam version, the lines I added
to 
user-config.jam.  Anyone know what's wrong?

[~/Projects/boost/status] Noel% echo $BOOST_BUILD_PATH
/Users/Noel/Projects/boost/tools/build/v2
[~/Projects/boost/status] Noel% ~/bin/bjam -v
Boost.Jam  Version 3.1.12. OS=MACOSX.
    Copyright 1993-2002 Christopher Seiwald and Perforce
Software, Inc.
    Copyright 2001 David Turner.
    Copyright 2001-2004 David Abrahams.
    Copyright 2002-2005 Rene Rivera.
    Copyright 2003-2005 Vladimir Prus.

[~/Projects/boost/status] Noel% more
../tools/build/v2/user-config.jam
#  Copyright (C) Vladimir Prus 2003. Permission to copy,
use, modify, 
sell and
#  distribute this software is granted provided this
copyright notice 
appears in
#  all copies. This software is provided "as is"
without express or 
implied
#  warranty, and with no claim as to its suitability for any
purpose.

[ snip ]

import toolset : using ;

# CodeWarrior configuration

using cw ;

using python : 2.4 : /usr ;

-- Noel


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
Problems running CW tests on Darwin
user name
2006-02-23 05:42:04
On Feb 22, 2006, at 8:56 PM, Noel Belcourt wrote:

> Hi,
>
> So I managed to get a snapshot of CVS onto my test
machine and followed
> the instructions for configuring the v2 tests.  Here's
the output from
> the command.
>
> [~/Projects/boost/status] Noel% ~/bin/bjam --v2 -n
> warning: toolset cw initialization: can't find tool
mwcc.exe
> warning: initialized from
> Building Boost.Regex with the optional Unicode/ICU
support disabled.
> Please refer to the Boost.Regex documentation for more
information
> (and if you don't know what ICU is then you probably
don't need it).
> error: Unable to find file or target named
> error:     '/python//python_for_extensions'
> error: referred from project at
> error:     '../libs/python/test'

Ignore this, I've just answered my own question.

The changes are attached although I'm not sure they should
be committed 
just yet.  I'm still pretty new to boost build syntax and
coding style.

Thanks,

-- Noel


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
Outputting build summaries instead of details
user name
2006-02-25 05:12:38
We'd like to control what information our customers see on
stdout when 
they run our product's installer (bjam) at their sites.

For example, when we deliver them software, we setup bjam to
build in a 
bootstrapping mode to build as much of our code base as it
can.  The 
problem is that we have about 100 libraries to build
containing some 
30000 source files, about 50 executables to link and lots of
tests to 
run sprinkled throughout the build process.  The amount of
information 
output to stdout by bjam is overwhelming to our customers
and is really 
only useful to us.  That's why we'd like all the normal
bjam output 
redirected to a file that, ideally, we can name with a
property in the 
Jamroot.

Instead of the detailed bjam output to stdout, we'd rather
have a 
summary line output for each lib, exe and test target as it
is built 
and run.  This summary information would be much more
manageable for 
our customers and, because the summary line is output as the
target is 
built, it would provide temporal feedback to the customer
about the 
build/run time required for each target.  If our code
doesn't compile 
cleanly or a test fails, we'd like the summary to count the
number of 
warnings and errors (or the number of files generating these
messages) 
and output this information to the summary line as well. 
Naturally, if 
the customer has build or test problems, we could have them
send us the 
summary and detailed output for us to look at.

A representative summary line for three library targets.

Building netcdf 3.6.0, 3 warnings, 0 errors finished.
Building exodus 4.15, 1 warnings, 0 errors finished.
Building nemesis 3.03, 7 warnings, 2 errors not finished.

Has anyone done something like this or know how to?  I'm
willing to do 
it but I don't know how to get  a count of the compile
warnings and 
errors for starters, much less where I'd have to hook the
build process 
to output this following completion of each target.  (The
temporal 
feedback is important to us so we'd like to output the
"Building .." 
just prior to building the target and output the summary
just following 
it's completion.)

Any ideas?

-- Noel


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
Problems running CW tests on Darwin
user name
2006-02-26 16:18:17
On Thursday 23 February 2006 08:42, Noel Belcourt wrote:

> > [~/Projects/boost/status] Noel% ~/bin/bjam --v2 -n
> > warning: toolset cw initialization: can't find
tool mwcc.exe
> > warning: initialized from
> > Building Boost.Regex with the optional Unicode/ICU
support disabled.
> > Please refer to the Boost.Regex documentation for
more information
> > (and if you don't know what ICU is then you
probably don't need it).
> > error: Unable to find file or target named
> > error:     '/python//python_for_extensions'
> > error: referred from project at
> > error:     '../libs/python/test'
>
> Ignore this, I've just answered my own question.
>
> The changes are attached although I'm not sure they
should be committed
> just yet.  I'm still pretty new to boost build syntax
and coding style.

The changes look fine, I've comitted them. Thanks!

Are there any other showstopper issues on Darwin that I can
help to fix?

- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
[1-4]

about | contact  Other archives ( Real Estate discussion Medical topics )