[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

different hosts in subprojects

From: Ineiev
Subject: different hosts in subprojects
Date: Tue, 18 Mar 2008 07:48:45 +0000 (GMT)

I try to mount my project on Autoconf.
it has very heterogeneous software parts, e.g.

(1) fat POSIX host (typically HOST=BUILD=`config.guess')
(2) ARM-based microcontroller without external memory
 (I am used to build tools with arm-elf- prefix)
(3) little AVR appendices.

(2) and (3) are written in C and need configuration,
but they are not portable and the host needs to be forced.

So I split the whole tree into several several subprojects.

I am quite new to Autotools and I am not sure this
was the right way. there are a lot of readings on Autoconf available,
but I could not find a ready solution.

The only that come into my head was to invoke 'configure'
of subprojects recursively, like this:

if test "z$arm_recursion_trigger" != ztriggered;then
 export arm_recursion_trigger=triggered
 #forcing HOST=arm-elf should not imply BUILD=HOST
 config_guessed=$($(echo ${0} | sed "s/configure$/config.guess/"))
 case $# in
  0) ${0} --build=${config_guessed} --host=arm-elf;;
 #if --build is set it should override the guessed value
  *) ${0} --build=${config_guessed} $@ --host=arm-elf;;
 exit $?

This does not work when included in
just after AC_INIT invocation (at least, with Autoconf-2.61),
though the info tells it should. AFAIU from this list,
this is an Autoconf-2.61 AC_INIT bug, although self-made
arguments parsing is deprecated.

Also, I am afraid that recursion may trigger some issues
of caching and regenerating configure scripts.

What is the right way to autoconfiscate such projects?


Rise to the challenge for Sport Relief with Yahoo! For Good

reply via email to

[Prev in Thread] Current Thread [Next in Thread]