Subject: Re: [Boost-build] How to run python test's explicitly ?
From: å×ÇÅÎÉÊ ûÕÂÉÎ (shubin_evgeniy_at_[hidden])
Date: 2010-05-05 06:40:21
I have this rule in Jamroot (on top of projects) :
constant JAMROOT : $(__name__) ;
sed "s_at_PREFIX@$(INSTALL_PATH)@g" $(>) | sed "s_at_NAME@$(DAEMON_NAME)@g" > $(<)
chmod a+x $(<)
cp $(>) $(<)
rule your-install ( DAEMON_NAME2 )
install install-bin : $(DAEMON_NAME) : <location>$(INSTALL_PATH)/bin ;
make $(INSTALL_PATH)/conf/$(DAEMON_NAME).conf.sample : ../../conf/$(DAEMON_NAME).conf : @$(JAMROOT).transform-conf ;
make $(INSTALL_PATH)/scripts/$(DAEMON_NAME).sample : ../../scripts/rc_script.freebsd : @$(JAMROOT).transform-script ;
Also I have rule invocation in Jamfile of subproject search_retriever:
modules.poke $(JAMROOT) : DAEMON_NAME : search_retriever ;
your-install search_retriever2 ;
explicit search_retriever2 ;
When I execute command "bjam" in directory search_retriever (I want only compilation, not installing),
the installation also take place.
If I comment lines
#modules.poke $(JAMROOT) : DAEMON_NAME : search_retriever ;
#your-install search_retriever2 ;
#explicit search_retriever2 ;
and run bjam my subproject search_retriever is only compiled without invocation of your-install rule.
Fri, 23 Apr 2010 12:11:04 +0400 ÐÉÓØÍÏ ÏÔ Vladimir Prus <ghost_at_[hidden]>:
> å×ÇÅÎÉÊ ûÕÂÉÎ wrote:
> >>> There is one more question: how to run rules explicitly (not to run on any other target)?
> >> Exactly as Steven said. If you use:
> >> bjam <other options> ecf
> >> then only ecf target is requested. Of course, if it depends on other targets those
> >> will be made as well, but no independent targets will be built.
> >> Does this answer the question?
> >> - Volodya
> > If there is any over target (for example: exe some_exe) in Jamfile.
> > And I call "bjam some_exe" the rule ecf is also called.
> Can you provide a minimal example reproducing this behaviour?
> - Volodya
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk