[Top][All Lists]

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

Re: [Mingw-cross-env-list] Wine cross-compilation detection - wxwidgets

From: Volker Grabsch
Subject: Re: [Mingw-cross-env-list] Wine cross-compilation detection - wxwidgets
Date: Wed, 26 May 2010 02:52:34 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

Tony Theodore <address@hidden> schrieb:
> So it seems wxwidgets wasn't being affected by pthreads, but by wine.
> Attached is just the standard $(SED) replacement.
> --- a/src/wxwidgets.mk        Fri May 21 03:37:31 2010 +0200
> +++ b/src/wxwidgets.mk        Fri May 21 17:24:09 2010 +1000
> +    # wine confuses the cross-compiling detection, so set it explicitly
> +    $(SED) -i 's,cross_compiling=no,cross_compiling=yes,' '$(1)/configure'
> +    # wine confuses the cross-compiling detection, so set it explicitly
> +    $(SED) -i 's,cross_compiling=no,cross_compiling=yes,' 
> '$(1)/$(wxwidgets_SUBDIR)/configure'

Included. Thanks!

> Out of curiosity, since I'm seeing this more often, I tried:
> $ grep 'checking whether we are cross compiling... no' log/* | uniq
> and came up with over 80 packages (below). Of course, some of those
> are native stages of builds, but I was surprised by the number.

The cross-compiling detection is only important for more involved
builds, i.e. if there are code generators to be compiled and used,
or if there are checks which would try to run a cross-compiled
program when in non-cross mode.

That's why it doesn't really matter for the majority of packages.

> Is this likely to be an issue, or would we have already noticed it?

You can't overlook such issues, so I don't think this a problem.

However, feel free to provide a patch that adds our Wine hack
to all packages which are affected - but only to their cross
builds, not their native builds!


Volker Grabsch
NotJustHosting GbR

reply via email to

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