If this is Windows specific, it can be inside ifeq ($(OS),WNT)

This also prevents a weird problem I see when cross-compiling in one tree (but
not in other trees for other cross-compilation targets).

Change-Id: I102e652c259a66ea124b344bd229e8988801ac58
Need more modules when cross-compiling to a desktop platform

Because gengal.

Change-Id: I679177b8bade42787dc921a500679c53278029d1
Export CROSS_COMPILING=YES, if set, while running the configure script

It can thus be used in a pkg-config replacement wrapper that makes pkg-config
look in an appropriate place, which typically is needed when not using a
proper cross-compilation toolchain. (Such would come with an own copy of
pkg-config.)

Change-Id: I4c746206cc67ed7a428833f03b9d3aad250d31e1