-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Jennings schreef:
| On Tuesday, 18 March 2008, at 08:52:12 (+0100),
| Lars Munch wrote:
|
|> The attached patch fixes expedite cross build. Without this patch it
|> will look in /usr/include for include files when cross building.
|
| So could someone please explain to those of us who don't do
| cross-compiling why $(includedir) would/should not be redefined when
| cross-compiling? Please note that $(includedir) is not guaranteed to
| be /usr/include or any other directory used by default, so being able
| to ensure that headers in $(includedir) are found, particularly on
| non-Linux systems, is of value.
It's not about redefining $(includedir), it's about this situation:
arm-angstrom-linuxgnueabi-gcc something-doing-math.c -I/usr/include
- -I/data/cross/arm/usr/include -o foo
something-doing-math.c looks something like:
..
#include <optimized-header.h>
..
The build will pick up the mmx version of the header from /usr/include
(assuming you build on an intel system) and the compiler will choke on
strange asm and datasizes.
Or if you are want to build against freetype 2.0 and your host has
freetype 2.4
Things get even worse if you are cross-compiling to *bsd, aros, wince, etc.
Redefining ${includedir} won't help, since you want the software to end
up in $[{prefix} on the target when installing the package.
Hopefully this clears things up a bit
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH4ACXMkyGM64RGpERAg9RAJ0ZgVtglcFmIbPVpgMbiKcqE3tBlwCgkOmr
bZ0aYYrAKyIqODhTLdaM+KY=
=m7cc
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
