[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: cross compiling in general
- From: Rory Toma <rory@...>
- Date: Thu, 04 Mar 2010 16:46:46 -0800
As for ignoring those, six of one, half dozen of the other. I hard-code
my lua info (which the configure tries to get) into the script, then I
don't have to change the other stuff as much. Seems like the work is
about the same, just different ways to go about it.
Thanks for the input, just checking to see if I was missing something.
I assume you're building an embedded system when you talked about
cross-compile. And my experience is to ignore those configure scripts
I include those modules simply by add the source files directly into
my project. and so far so good.
The only thing I need to do is do a native-compile in pc and check
what -D definitions or other gcc argument should be given when
compiling those modules.
As for ./configure, it has built-in support for cross-compile but many
source code cannot work with it. You should use ./configure to
cross-compile the standard gnu tools. But for most lua modules this is
an unecessary overhead.
On Fri, Mar 5, 2010 at 6:35 AM, 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?