public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marty Plummer <netz.kernel@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] mingw-w64 crossdev prefix?
Date: Wed, 17 May 2017 23:52:41 -0500	[thread overview]
Message-ID: <20170518045240.bezemjns376zeovp@tha-monstah.mydomain> (raw)
In-Reply-To: <988123b7-f442-277a-6009-a788f6ed73a3@gentoo.org>

On Thu, May 18, 2017 at 12:42:09AM -0400, Ian Stakenvicius wrote:
> On 18/05/17 12:08 AM, Marty Plummer wrote:
> > On Thu, May 18, 2017 at 06:46:24AM +0300, Alon Bar-Lev wrote:
> >> Hi,
> >> You can emerge crossdev and then run crossdev -t x86_64-w64-mingw32 or
> >> crossdev -t i686-w64-mingw32
> >> Alon
> >>
> > I'm aware of that, using it. Its simply the fact that its fairly broken
> > for mingw-w64, and requires quite a lot of hackage to get going.
> > 
> > What I'm suggesting is the creation of a profile that should handle this
> > sort of thing for you semi-automatically. Something like the
> > prefix/windows, but meant more for toolchains. it seems that beber's
> > portage tree at git.meleeweb.net/gentoo/portage.git already has a setup
> > similar to what I envision already.
> > 
> 
> There isn't a whole lot that's broken about it actually -- the main
> issue is that the default 'embedded' profile doesn't allow all of the
> variable overrides in it that are necessary for the crossdev to work
> properly.  See bug http://bugs.gentoo.org/487310
> 
> The crossdev that's created will provide all the necessary profile
> overrides to allow you to emerge the things you want, and of course
> compile your own things as well.  There's no need for a special prefix
> (or 'prefix/*' profile) in order to support this, IMO, once the
> embedded profile permits the overrides necessary to the ARCH, ELIBC,
> and KERNEL variables that the crossdev tool already sets.
>

There's also a host of packages that are pulled in by default which are
simply uneeded for this sort of setup, such as coreutils, sed, file,
debianutils which have to be manually package.provided away by end
users. I'm simply suggesting we should make this a bit more easy for
everyone involved, as it could ease use and possibly cut down on
spurious bug reports if there was a standardized way of doing things.

This is a common enough use case that it should be handled upstream
imho. I'm more than willing to help in this matter, but I don't want to
be spitting into the wind if nothing will actually come of it.


  reply	other threads:[~2017-05-18  4:50 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 [this message]
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=20170518045240.bezemjns376zeovp@tha-monstah.mydomain \
    --to=netz.kernel@gmail.com \
    --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