[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cross-compiling but keeping one target native
|
From: |
Keith Marshall |
|
Subject: |
Re: cross-compiling but keeping one target native |
|
Date: |
Tue, 18 May 2010 13:05:06 +0100 |
|
User-agent: |
KMail/1.9.10 |
On Monday 17 May 2010 23:55:10 Ben Pfaff wrote:
> > I have one target which is actually a utility used during
> > *build* time. Is it possible to specify one target which should
> > *not* be built with the cross-compiler, but natively instead?
>
> I find that the easiest way to deal with this problem is to avoid
> it, by writing build-time tools in a language such as shell,
> Python, Perl, or awk that doesn't need to be compiled at all. If
> the utility is simple, so that you could easily rewrite it in a
> different language, then you might consider that solution.
That's fine, when you are writing an application from scratch; when
porting an existing application, that may entail more effort than
you are willing to invest. Additionally, adoption of some of those
alternative languages may introduce portability issues of their own.
--
Regards,
Keith.