Hi,
On Mon, May 17, 2010 at 03:37:37PM -0700, Natalie Tasman wrote:
> 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 directi
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-com
On Sat, May 15, 2010 at 5:26 AM, Simon Richter wrote:
> It's more related to autoconf than to automake.
Oops :)
Sorry for replying too quickly on the autoconf list :(
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
I'm working on a build system with autotools. I'd like to cross-compile,
building a mingw/windows executable from linux. So far, my system works
well with the --host option (and appropriate cross tools installed, from the
mingw-cross-env project.)
I have one target which is actually a utility us
