[gentoo-dev] [RFC] New category for xmingw cross compile toolchain

[gentoo-dev] [RFC] New category for xmingw cross compile toolchain

[Stefan Jones]

Hi all,

I am just wondering about people's option about making a new category, 
called something like dev-xmingw or similar.

At the moment we have in portage:

dev-util/xmingw-binutils  dev-util/xmingw-runtime
dev-util/xmingw-gcc       dev-util/xmingw-w32api

Which gives a usable W32 toolchain on gentoo using just standard W32 
libraries.

But every so often people submit ebuild for other libraries for use with 
this toolchain
( eg. http://bugs.gentoo.org/show_bug.cgi?id=101468 )

I have not added them up to now as it would, in my opinion, just clutter 
things.

The other option is to make an external non-official tree that people 
could use as an overlay.

Opinions?

Stefan
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] [RFC] New category for xmingw cross compile toolchain

[Dave Nebinger]

Just a few opinions from the outside looking in...

On Thursday 13 October 2005 12:25 pm, Stefan Jones wrote:
> I am just wondering about people's option about making a new category,
> called something like dev-xmingw or similar.

Wouldn't set a precident for dev-gcc, dev-icc, dev-[enter alternate toolchain 
here]?

> The other option is to make an external non-official tree that people
> could use as an overlay.

Personally I don't like that idea either.  To me, external overlays are 
'tainted' because they are not blessed enough to be part of the default 
gentoo tree.  I therefore don't trust them and don't use them.  Obviously 
that means I don't get the latest cutting edge stuff, but to have a stable 
gentoo environment I'm willing to make that sacrafice.

Relegating these mingw stuff to an external overlay would carry the same 
'taint' with it.

And the fact that external non-official overlays are not really given much 
representation in the doco, most users looking for something like this would 
not have any idea that the external overlay existed and they could get the 
packages they're looking for from there.

Like I said, just comments from an outsider...
 
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] [RFC] New category for xmingw cross compile toolchain

[Mike Frysinger]

On Thursday 13 October 2005 12:25 pm, Stefan Jones wrote:
> dev-util/xmingw-binutils  dev-util/xmingw-runtime
> dev-util/xmingw-gcc       dev-util/xmingw-w32api

i'd prefer to see these moved into the normal binutils/gcc ebuilds myself

> But every so often people submit ebuild for other libraries for use with
> this toolchain
> ( eg. http://bugs.gentoo.org/show_bug.cgi?id=101468 )
>
> I have not added them up to now as it would, in my opinion, just clutter
> things.

are these libraries special ?  that is, are these things specific to xmingw ?  
or are they just ebuilds which take normal packages and force them to be 
compiled with the xmingw toolchain ?

if they are xmingw-specific, then they should be added to the tree as sep 
packages, but if they are normal packages and these ebuilds are special hacks 
to cross compile them with xmingw, then they have no business in the tree
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] [RFC] New category for xmingw cross compile toolchain

[Stefan Jones]

Mike Frysinger wrote:

>On Thursday 13 October 2005 12:25 pm, Stefan Jones wrote:
>  
>
>>dev-util/xmingw-binutils  dev-util/xmingw-runtime
>>dev-util/xmingw-gcc       dev-util/xmingw-w32api
>>    
>>
>
>i'd prefer to see these moved into the normal binutils/gcc ebuilds myself
>
>  
>
I do not think that would ever work well; the bootstrap method is a bit 
to out of sync with the GNU/Linux target
Plus it would mean I would step on the gcc maintainers toes alot.

[ xmingw cross compiled libraries]

>are these libraries special ?  that is, are these things specific to xmingw ?  
>or are they just ebuilds which take normal packages and force them to be 
>compiled with the xmingw toolchain ?
>
>  
>
About half (guess) are xmingw spercific; will not compile in GNU/Linux.

Others are normal libraries which work on Linux but need special tricks 
to get working with the crosscompiler.

>if they are xmingw-specific, then they should be added to the tree as sep 
>packages, but if they are normal packages and these ebuilds are special hacks 
>to cross compile them with xmingw, then they have no business in the tree
>  
>
But what is the difference in effect? Both are libraries for the xmingw 
toolchain, but a line would need to be drawn otherwise I might as well 
port the entire cygwin distribution!

Out of tree collection looks good; but I doubt anyone will find it and I 
do not really use xmingw!

Stefan
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] [RFC] New category for xmingw cross compile toolchain

[Mike Frysinger]

On Thursday 13 October 2005 08:16 pm, Stefan Jones wrote:
> Mike Frysinger wrote:
> >On Thursday 13 October 2005 12:25 pm, Stefan Jones wrote:
> >>dev-util/xmingw-binutils  dev-util/xmingw-runtime
> >>dev-util/xmingw-gcc       dev-util/xmingw-w32api
> >
> >i'd prefer to see these moved into the normal binutils/gcc ebuilds myself
>
> I do not think that would ever work well; the bootstrap method is a bit
> to out of sync with the GNU/Linux target

glanced in the ebuilds and they dont look too bad to me ... this is how we do 
avr after all ... we punted the avr gcc/binutils ebuilds and now people have 
to `emerge crossdev && crossdev avr`

> Plus it would mean I would step on the gcc maintainers toes alot.

err, you mean me ? :)
i dont think the other toolchain guys would care too much

> [ xmingw cross compiled libraries]
>
> >are these libraries special ?  that is, are these things specific to
> > xmingw ? or are they just ebuilds which take normal packages and force
> > them to be compiled with the xmingw toolchain ?
>
> About half (guess) are xmingw spercific; will not compile in GNU/Linux.

these are OK then imho

> Others are normal libraries which work on Linux but need special tricks
> to get working with the crosscompiler.

these are not valid then as sep packages

> >if they are xmingw-specific, then they should be added to the tree as sep
> >packages, but if they are normal packages and these ebuilds are special
> > hacks to cross compile them with xmingw, then they have no business in
> > the tree
>
> But what is the difference in effect? Both are libraries for the xmingw
> toolchain, but a line would need to be drawn otherwise I might as well
> port the entire cygwin distribution!

i thought the line i drew was pretty clear ;)
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] [RFC] New category for xmingw cross compile toolchain

[Stefan Jones]

Mike Frysinger wrote:

>glanced in the ebuilds and they dont look too bad to me ... this is how we do 
>avr after all ... we punted the avr gcc/binutils ebuilds and now people have 
>to `emerge crossdev && crossdev avr`
>  
>
Ok, many thanks Mike for the input.
I guess I better get on with it!

Stefan

-- 
gentoo-dev@gentoo.org mailing list