public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alon Bar-Lev <alonbl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] mingw-w64 crossdev prefix?
Date: Thu, 18 May 2017 06:46:24 +0300	[thread overview]
Message-ID: <CAOazyz2-Yw9HtxDayqJeq7DUapNeJrE89jB6=4wHtVAcCcQ5hQ@mail.gmail.com> (raw)
In-Reply-To: <20170517222548.d75vcbnrid5bn7qb@tha-monstah.mydomain>

Hi,
You can emerge crossdev and then run crossdev -t x86_64-w64-mingw32 or
crossdev -t i686-w64-mingw32
Alon

On 18 May 2017 at 01:25, 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.
>
> Marty.
>


  reply	other threads:[~2017-05-18  3:46 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 [this message]
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
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='CAOazyz2-Yw9HtxDayqJeq7DUapNeJrE89jB6=4wHtVAcCcQ5hQ@mail.gmail.com' \
    --to=alonbl@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