From: Miguel A Sepulveda (ironphase_at_[hidden])
Date: 2006-12-07 08:19:41
This brings another issue which I have not been able
to resolved so far. Say that I have a DLL target build
but I want it installed in some location with a
different extension name, some the target built is
myPlugin.dll and the installation should deploy
myPlugin.xll, How can I do that with the latest bjam?
--- Phillip Seaver <phil_at_[hidden]> wrote:
> Deane Yang wrote, on 12/6/2006 12:36 PM:
> > I'd like to use the install rule with an
> executable and shared libraries
> > that it depends on. If I include, in the list of
> targets in the install
> > rule, the target that creates a shared library,
> then it installs both
> > the DLL and the stub LIB file. Worse, if I follow
> the advice on the
> > install documentation for automatically installing
> dependencies with
> > "<install-type>LIB", all the static libraries that
> were used to build
> > the DLL are also installed, too.
> > How do I install the executable and DLL's only?
> > (Again, I apologize if this is documented
> somewhere. I have a lot of
> > difficulty locating the relevant information in
> the boost documentation.)
> Try "<install-type>SHARED_LIB".
> Unsubscribe & other changes:
Want to start your own business?
Learn how on Yahoo! Small Business.
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