Ralf Corsepius wrote:
> On Thu, 2004-01-15 at 12:41, Warren Turkal wrote:
>> This assumes that something sets those variables still (autoconf).
>
> Just add something similar to this
> CC_FOR_BUILD=${CC_FOR_BUILD-${CC})
> or
> AS_IF([$build != $host],
> [CC_FOR_BUILD=${CC_FOR_BUILD-cc],
> [CC_FOR_BUILD=$CC])
> to your configure.ac.
Then you are still manually setting up this stuff.
> If you additionally split build-compiled tools into a separate directory
> + Makefile.am which contains CC = @CC_FOR_BUILD@ you can use
> automake-generated rules there.
>
> If you want a clean way, you'd have to split buildtools and
> host-packages into separate (sub) packages and write a costomized
> toplevel configure-script to parse and set the configure options for
> build- and host- compile packages.
This is just a hack. I have seen this solution proposed before. It is not
conceptually another package. Why treat it that way? I would like to have
one configure script per package.
> automake isn't the actual problem. The actual problem is autoconf
> support for build-compilation, because supporting build- and host-
> compilation/checks would require to duplicate almost all autoconf
> checks/variables etc.
Automake is part of the problem.
wt
--
Warren Turkal
President, GOLUM, Inc.
http://www.golum.org
