On Thu, Jun 13, 2019 at 09:19:34PM +0200, Stefan Weil wrote:
> recent versions of pkg-config fail to work in cross builds targetting Windows,
> so such cross builds no longer work for many users.
> 
> Error message when calling i686-w64-mingw32-pkg-config or 
> x86_64-w64-mingw32-pkg-config:
> 
>     Please install dpkg-dev to use pkg-config when cross-building
> 
> A simple fix just removes the problematic lines (which I think were 
> introduced recently):

I guess I'm responsible for this. Removing the lines makes the user
experience bad when dpkg-dev is not installed.

> A better fix would skip the multiarch check for *-w64-mingw32 as I don't 
> expect

Why do you think so? The cross wrapper is intended to be used with
Debian architectures. Using it beyond that way is out of scope. I argue
that placing a symlink i686-w64-mingw32-pkg-config -> crosswrapper is a
bug in itself. A different cross wrapper should be used for things that
are not Debian architectures. As such I propose reassigning the bug to
mingw-w64-tools. Any objections to doing so?

> that Debian will add multiarch support for *-w64-mingw32 in the near future.

I actually looked into this and attempted doing it (though I couldn't
figure out how to make the toolchain bootstrap work similar enough to
Linux). I think that doing so would be a very good idea, because it
simplifies cross building in a number of ways: The current way we do
mingw in Debian is repeating the ia32-libs mess. Every package that is
needed for mingw incurs a new binary package (and a trip through NEW).
Instead, we could have a Debian architecture (which would never be a
"full" or release architecture) and cross build packages for that
architecture. Doing so could get us rid of a pile of packages (such as
libz-mingw-w64*, libgpg-error-mingw-w64*, libgcrypt-mingw-w64*, ...) and
provide lots of libraries at once instead. If you are interested in
pursuing this, contact debian-cross@l.d.o.

Helmut

Reply via email to