public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthias Maier <tamiko@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] mingw-w64 crossdev prefix?
Date: Wed, 17 May 2017 22:46:50 -0500	[thread overview]
Message-ID: <87wp9e25ed.fsf@kestrel.kyomu.43-1.org> (raw)
In-Reply-To: <20170517222548.d75vcbnrid5bn7qb@tha-monstah.mydomain> (Marty Plummer's message of "Wed, 17 May 2017 17:25:48 -0500")

[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]

Hi there,

On Wed, May 17, 2017, at 17:25 CDT, Marty Plummer <netz.kernel@gmail.com> wrote:

> Greetings,
>
> So, I'm a relatively new gentoo user (as of 2016-12) coming from arch,
> and  one thing I've noticed is the relative difficulty of setting up a
> mingw-w64 cross-compile toolchain and libraries.
>
> I'm considering the idea of setting up a sort of prefix specifically
> with the intent of being used on a 'normal' gentoo system with the sole
> purpose of creating 'normal' windows binaries; does anyone have
> suggestions/objections about the idea?
>
> As it currently stands I have to use an archlinux chroot to do my
> cross-compiling, and I'd really enjoy to be able to do this sort of
> thing without depending on an auxiliary distro.

You can find some information on the wiki [1] (warning: I might be a bit
outdated).

But anyway, just check it for you (I haven't set up a cross compilation
toolchain for windows for the last ~7 years): From a plain amd64 stage-3
setting up a mingw-264 environment via:

  # emerge crossdev
  # crossdev [...] -t x86_64-w64-mingw32

still works with a minor complication [2]. Please verify that this works
and open a bug report for the libsanitizer issue mentioning the
workaround [2,3].

After that you end up with a cross-compiler toolchain

  x86_64-w64-mingw32-*

and necessary runtime somewhere in /usr/x86_64-w64-mingw32.

You can also use $ x86_64-w64-mingw32-emerge to cross compile
libraries/packages for mingw.


Keep in mind that a cross compilation toolchain is a bit of a rocky
journey. You might have to pin certain versions of libraries/programs,
and or manually patch some stuff.

Best,
Matthias


[1] https://wiki.gentoo.org/wiki/Mingw

[2] I had to manually disable libsanitizer for gcc-6.3.0. Just set
    EXTRA_ECONF="--disable-libsanitizer" via env/package.env for the
    cross-x86_64-w64-mingw32/gcc package.

[3] https://bugs.gentoo.org/buglist.cgi?quicksearch=mingw&list_id=3536150

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 850 bytes --]

  parent reply	other threads:[~2017-05-18  3:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 22:25 [gentoo-dev] mingw-w64 crossdev prefix? Marty Plummer
2017-05-18  3:46 ` Alon Bar-Lev
2017-05-18  4:08   ` Marty Plummer
2017-05-18  4:42     ` Ian Stakenvicius
2017-05-18  4:52       ` Marty Plummer
2017-05-19  4:46       ` Marty Plummer
2017-05-18  3:46 ` Matthias Maier [this message]
2017-05-18  3:53   ` Alon Bar-Lev
2017-05-18  4:25     ` Matthias Maier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wp9e25ed.fsf@kestrel.kyomu.43-1.org \
    --to=tamiko@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox