Re: [gentoo-dev] mingw-w64 crossdev prefix?

[Marty Plummer <netz.kernel@gmail.com>]

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.
> 
>
So why do we not just fix the embedded profile? crossdev sets it
automatically, and then sets those variables, but the profile itself
won't let that work? seems like a bad idea to have an official tool use
an official profile which officially is not allowed to work like that.