From: jrsr01801 (jrsr369shop_at_[hidden])
Date: 2004-01-28 12:29:28
Thanks for the help. I took your suggestion creating a new target
type, and it worked wonderfully.
--- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
> jrsr01801 wrote:
> > Hi,
> Hi Jordan,
> > Here are a couple of specific questions:
> > 1) I wrap some code I will be using in many subprojects into a rule
> > which is defined in project-root.jam. However, to get things to
> > work I had to make the rule "operate" in the caller's module. Is
> > this the correct way to do this?
> That's fine. Of course, you can create main target class... but for
> you have that's too complex solution. There are no problems with the
> you've written.
> > 2) The libraries I use in my rule had to be defined in the top
> > project Jamfile, because I got errors when I tried to put this code
> > into project-root.jam. Is there a better way to do this?
> Again, what you do is quite reasonable. You can put targets into
> project-root.jam, or any other module as described in
> (that should work in project-root.jam), but there's no need.
> > 3) Finally, my files require a custom suffix; in particular, my
> > shared libraries should not use .so as its suffix, but a different
> > custom suffix. I used type.set-generated-target-suffix to change
> > this, but was not sure if this was the correct way to do it.
> Depends. This will change suffix for all libraries Boost.Build creates.
> If that's fine with you, then it's fine. Otherwise, you can create a
> target type derived from SHARED_LIB and change suffix on it only.
> Example can be found at
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