From: Phillip Seaver (phil_at_[hidden])
Date: 2007-04-25 15:10:50
My mistake. Sorry. "requirements" and "usage-requirements" are the
I would have thought what you had would have worked. You should try
what Johan suggested in his reply.
Phillip (who clearly needs more sleep and/or caffeine)
DrAnonymous wrote, on 4/25/2007 2:26 PM:
> Phillip -
> I tried to use buld-requirements and it gave the following error:
> error: Invalid project attribute 'build-requirements' specified for
> project at '.'
> I tried to search the .jam files to see if build-requirements was
> listed, and it didn't find it.
> Aaron R>
> On 4/25/07, *Phillip Seaver* <phil_at_[hidden] <mailto:phil_at_[hidden]>>
> DrAnonymous wrote, on 4/25/2007 1:21 PM:
> > I can't figure out how to alter Jamroot to include the includes
> > directory for all the subprojects. I tried:
> > project myTools : requirements <source>./includes ;
> > and
> > project myTools : requirements <include>includes ;
> > Neither works and the first one has an error.
> > Can someone please help me get this working?
> > Thanks,
> > Aaron R>
> > PS - Should my Jamfiles always have a project entry in them? In the
> > above source tree I used only a lib target in one and an exe
> target in
> > the other.
> You probably want "project myTools : build-requirements
> <include>includes ;". That will affect your sub-projects' builds.
> "requirements <include>includes" affects everything that *uses*
> the project.
> You don't have to. Many of mine don't. I mainly use it when I
> want to
> apply a build or usage requirement to all of the targets in the
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