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

[Earnie Boyd]

I've always done this with a two stage build.  Stage 1 is for the build
system, Stage 2 is for the targeted host system.  If my host name is foo
and the targeted host is bar then I would do:
  configure --prefix=/usr --host=foo --build=foo --target=bar
  make && make install && make clean
  rm config.cache
  configure --prefix=/usr --host=bar --build=foo --target=bar
  make && make install DESTDIR=/depot

The standards for configure and make are such that this is the only way
to accomplish what you want, AFAICS.

Earnie.

Dan Kegel wrote:
> 
> 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

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com