[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: cross compiling in general
- From: Rory Toma <rory@...>
- Date: Thu, 04 Mar 2010 16:48:38 -0800
And don't forget things like EXTRA_CFLAGS and the ilk. I'm shoe-horning
this into an OpenWRT-based distro. And, to be fair, it's not just lua. I
can't tell you how many times I run across the follwing in a gnu
if "cross-compile" = "yes"
> 2) Makefiles often have things like CFLAGS and CC hardcoded
Having been into make lately, it would seems that there a lot of
confusion about make (or GNU make anyway) defaults.
1. methinks CPPFLAGS and CFLAGS separation is helpful (never happens)
On 5/3/2010 11:18 AM, Rory Toma wrote:
On Thu, 04 Mar 2010 14:35:45 -0800
Rory Toma<firstname.lastname@example.org> wrote:
I notice that every package that I cross compile, I have to, at a
minimum, rewrite the configure scripts and often the Makefiles. What
is the standard lua way of building for cross-compile?
/path/to/your/cross-compiler -Isrc etc/all.c -o lua
Is one approach.
It's not that, it's that all the support scripts seem to be standardized
in a way which
1) wants to call the local lua on the build machine to get installation
2) Makefiles often have things like CFLAGS and CC hardcoded
3) There is usually no support for things like $(DESTDIR)
Each set of files looks similar enough that they probably are based on
the same original set, yet each is different enough that they have to be
tweaked by hand.