From: Eric Woodruff (eric.woodruff_at_[hidden])
Date: 2008-08-19 12:41:10
Can someone please comment on my question below?
Eric Woodruff wrote:
> I'm working on a set of Jam rules to build an RPM. I'm using stage.jam
> to install files into a buildroot directory, and a scanner to analyze
> the dependencies of the RPM spec file. The goal of the build system is
> to only build dependencies of an RPM when one is being built. At this
> point everything seems to be working fine except for the behavior of the
> install rule.
> When install is run, it builds all of its sources and runs the virtual
> targets that install the sources into <location>. The behavior I need is
> that files not listed in the RPM spec file should not be built or
> staged. So I'm looking for a way to extend install () or modify it with
> a build requirement such that install () doesn't actually construct
> anything, but instead only registers the virtual targets for each
> element that has the potential to be staged. This way the stage targets
> can still be found as dependencies of the RPM spec file, and are only
> run in that case rather than unconditionally.
> Does anyone have any advice on how this might be enhanced? I've been
> looking at the install-target-class, but the solution hasn't made itself
> apparent to me yet.
> Unsubscribe & other changes:
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