Re: cross-compiling but keeping one target native

[Natalie Tasman]

Hello Simon,

I've created a separate configure.ac and Makefile.in for the "native"
project.  However, when invoking configuration from the top-level
(cross-compiled) project, AC_CONFIG_SUBDIRS passes various options,
including directives to use the top-level cache as well as the "--host"
cross-compile directive.

Do you know how to cause the subproject to be ./configured as a truly
independent project, without passing cached config data as well as options
from the top level?

BTW, the autoconf list bounced me back here :)

Thanks,

-Natalie

On Sat, May 15, 2010 at 2:26 AM, Simon Richter <address@hidden>wrote:

> Hi,
>
> On Fri, May 14, 2010 at 03:53:29PM -0700, Natalie Tasman 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?
>
> Not directly. The trick is to have a separate configure script for that
> tool, and have a mechanism in place to configure it differently, usually
> from the toplevel Makefile.
>
> I agree that it would be nice to have a readymade way for doing that.
>
> > (I'm new to the list; please let me know if this is more appropriate on
> the
> > autoconf list).
>
> It's more related to autoconf than to automake.
>
>   Simon
>