Re: [jamboost] bjam v1 doing actions twice caused by stage rule

From: Jeff Holle (jeff.holle_at_[hidden])
Date: 2004-02-03 16:12:33

bjam version is Version 3.1.9. OS=LINUX.
output of bjam -a -an is:
...found 642 targets...
...updating 5 targets...
gcc-C++-action bin/cppParser/cppParser/gcc/release/cppParser.o

set -e
g++ -c -Wall -ftemplate-depth-100 -DNDEBUG -DNDEBUG -O3 
-finline-functions -Wno-inline -I"bin/cppParser" 
-I"/home/jholle/boost_CVS/boost" -o 
"bin/cppParser/cppParser/gcc/release/cppParser.o" "cppParser.cpp"

gcc-Link-action bin/cppParser/cppParser/gcc/release/cppParser

LD_LIBRARY_PATH=/home/jholle/boost_CVS/boost/boost/build/bin-stage:$LD_LIBRARY_PATH 

export LD_LIBRARY_PATH
g++ -s -o "bin/cppParser/cppParser/gcc/release/cppParser" 
-L"/home/jholle/boost_CVS/boost/boost/build/bin-stage" 
"bin/cppParser/cppParser/gcc/release/cppParser.o" -Wl,-rpath-link,.

Chmod1 bin/cppParser/cppParser/gcc/release/cppParser

chmod 711 "bin/cppParser/cppParser/gcc/release/cppParser"

FileClone install/cppParser

cp -fpd "bin/cppParser/cppParser/gcc/release/cppParser" "install/cppParser"

gcc-C++-action bin/cppParser/cppParser/gcc/release/cppParser.o

set -e
g++ -c -Wall -ftemplate-depth-100 -DNDEBUG -DNDEBUG -O3 
-finline-functions -Wno-inline -I"bin/cppParser" 
-I"/home/jholle/boost_CVS/boost" -o 
"bin/cppParser/cppParser/gcc/release/cppParser.o" "cppParser.cpp"

gcc-Link-action bin/cppParser/cppParser/gcc/release/cppParser

LD_LIBRARY_PATH=/home/jholle/boost_CVS/boost/boost/build/bin-stage:$LD_LIBRARY_PATH 

export LD_LIBRARY_PATH
g++ -s -o "bin/cppParser/cppParser/gcc/release/cppParser" 
-L"/home/jholle/boost_CVS/boost/boost/build/bin-stage" 
"bin/cppParser/cppParser/gcc/release/cppParser.o" -Wl,-rpath-link,.

Chmod1 bin/cppParser/cppParser/gcc/release/cppParser

chmod 711 "bin/cppParser/cppParser/gcc/release/cppParser"

...updated 5 targets...

Rene Rivera wrote:

> Jeff Holle wrote:
>
> > I have a simple Jamfile in which I added a stage rule so the executable
> > is placed in my
> > ./Install directory.
> >
> > It is:
> > project-root ;
> > SEARCH on python.jam = $(BOOST_BUILD_PATH) ;
> >
> > stage install : <exe>cppParser : <locate>. : release ;
> >
> > exe cppParser
> > : # sources
> > cppParser.cpp
> > : # requirements
> > <include>/home/jholle/boost_CVS/boost
> > # library path required for linking to boost_python shared lib.
> > <library-path>$(BOOST_ROOT)/boost/build/bin-stage
> > :
> > release
> > ;
> >
> > While the stage rule does what I wanted it to, it also causes all
> > actions to be taken twice. Is this normal? Can I avoid it while still
> > copying the the actions to ./Install?
>
> Could you send me a log of the build? -- Done with "bjam -n -a". -- 
> I'd like
> to see which actions it's repeating.
>
> And.. Which version of Boost are you using?
>
>
> -- 
> -- Grafik - Don't Assume Anything
> -- Redshift Software, Inc. - http://redshift-software.com
> -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
>
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
>
> * To visit your group on the web, go to:
> http://groups.yahoo.com/group/jamboost/
> * To unsubscribe from this group, send an email to:
> jamboost-unsubscribe_at_[hidden]
> <mailto:jamboost-unsubscribe_at_[hidden]?subject=Unsubscribe>
> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service <http://docs.yahoo.com/info/terms/>.
>
>