Hello Robert, * Robert Woodworth wrote on Fri, Nov 12, 2010 at 06:48:33PM CET: > http://lists.gnu.org/archive/html/autoconf/2010-01/msg00039.html > > I also want to use autoconf for an embedded system code base and I want to > force my configure script to set the cross compile environment correctly. So, you can do it exactly as suggested in the mail you cite. > I'm trying to get a team to adopt autotools for a rather large embedded > project, but I need to make sure the default execution of 'configure' does > the right thing without forcing the setting of 'CC' and --host and a few > other defaults. Well, if you absolutely have to, then put the : ${host_alias="mips-elf"} line in configure.ac right after AC_INIT. That will relieve your cow-orkers from creating a config.site file, but of course also make your package building for mips-elf rather than native by default. I do suggest you get acquainted with 'info Autoconf "Site Defaults"' however and reconsider this decision. > I have set the following in my 'configure.ac': > > <snip> > host=mips-elf > host_alias=mips-elf > ac_tool_prefix=mips-elf- > cross_compiling=yes The others here are not needed, as they should get set accordingly by the configure code. Hope that helps. Cheers, Ralf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
