From: Pedro Ferreira (pedro.ferreira_at_[hidden])
Date: 2004-01-30 06:56:32
> > A possible approach would be to pass to the ui compiler the path to the
> > directory
> > where the plugin is built. The problem is that the plugin depends on a
> > of libraries
> > which must be on the path...
> I think there's a solution to this. When building a target, the internal
> 'xdll-path' properties contains paths to all dependent libraries. We can
> convert them to -L flags to uic.
> Can you try the attached patch? Running modified Boost.Build on
> I get all the necessary -L options. Since I've no experience with uic
> I can't tell if it works in real life, though.
> There are other possible solutions, but let me know what you think about
> one, first.
I haven't yet had the opportunity to thoroughly test your patch but, at
a couple of projects, works like a charm.
Many thanks for your help,
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