Re: cross-compiling question: static libraries and binaries to different places?

[Dan Kegel]

You'd think so, but playing games like that might really
confuse libtool.

What I'd like to see is a fully-worked out example of how
to use libtool, with both static and shared libraries,
in a cross-compile situation, without the static libraries
leaking out onto the target system.  We may need to split
--libdir into --libdir and --buildlibdir, or something
awful like that?

Thinking about libtool and cross-compiling is giving me
serious heartburn.
- Dan

Guido Draheim wrote:
> 
> --bindir vs. --libdir ?
> 
> Es schrieb Dan Kegel:
> >
> > I'm cross-developing.  I want to build a package
> > that has both static libraries and binaries.
> > The binaries should go to the target system;
> > the libraries should stay on the build system.
> > What do I pass to configure and to make?
> >
> > If I do
> > configure --build=pentium-unknown-linux address@hidden@-unknown-linux
> > --disable-shared --with-gnu-ld --prefix=/usr
> > make -C @IXIA_PORTARCH@/src/lib DESTDIR=$(DEST) install
> >
> > the library ends up in the right place (DEST/usr/lib)
> > but the binary ends up in the wrong place (DEST/usr/bin).
> >
> > If instead I do
> >
> > make -C @IXIA_PORTARCH@/src/lib DESTDIR=$(DEST)/fsimg install
> > the library ends up in the wrong place (DEST/fsimg/usr/lib)
> > but the binary ends up in the right place (DEST/fsimg/usr/bin).
> >
> > What to do?  In cross-development environments, is it not
> > supported to have static libraries go to the build system,
> > but binaries go to the target?
> >
> > - Dan