Re: [Mingw-cross-env-list] Cross-compile detection

[Volker Grabsch]

Tony Theodore <address@hidden> schrieb:
> I was curious about the wine cross-compile detection and thought I'd
> do a quick check of the logs after a successful build with wine
> installed. Attached is just a naive grep 'cross compiling... no'
> log/20101006_061553/* and there are just over a hundred packages. I
> removed the native builds, and a similar check without wine only has a
> handful of native builds. The full directory is too large to attach
> [1].
> 
> Surely these can't be all be silently failing?

Well, we _could_ try to fix that for every single package. But I
thought it would be better to only on demand.

Note that a wrong "cross compiling... no" detection is irrelevant
to most packages. It causes only problems for packages whose
./configure performs runtime tests (instead of compile-only tests),
and for packages which compile a code generator.

Nevertheless, a central solution would be nice, something like
disabling wine in the main Makefile. However, this has multiple
pitfalls. First, this is not as easy as it may sound, because
executing .exe files though Wine doesn't happen explicitly, but
implicitly by some "magic" deep in the system. Second, even if
we could successfully do that, nobody could try out the build
scripts by hand anymore. This would be very bad, because at least
for me it is very practical to be able to "cd" to the failed build
directory and run configure/make commands by hand there.

But if you think you have a solution, feel free to propose it.
Until then, let's better add the Wine hack only on demand.


Greets,
Volker

-- 
Volker Grabsch
---<<(())>>---