Ulrich Weigand <[EMAIL PROTECTED]> writes:
> Well, the IMO most important configure checks are CPU architecture
> and OS specific (e.g. location of system headers / libraries and the
> like). While there are of course also compiler / toolchain dependent
> checks, those should matter only to the build process itself, and not
> the header files.
I disagree; the important configure checks are the ones that matter to
the build process. configure is very useful to determine headers
location, which libraries contain which symbols etc. and this is what
it should be used for. Architecture differences do not need configure
checks, all the #defines we need are already part of the compilation
environment (__i386__, __sparc__ etc.)
> Cross compilation doesn't work anyway, and it does not appear easy
> to set up the build process for it. Why do you think it important?
Cross compilation can be useful in many cases, especially for embedded
systems, and is actually quite easy to support if we do things
right. The main obstacle is that our tools (winebuild, wrc) should not
use #ifdefs but run-time checks instead. But that shouldn't be too
hard to fix.
--
Alexandre Julliard
[EMAIL PROTECTED]
