| 1 |
On Sat, 30 Nov 2002 00:22:17 +0100 |
| 2 |
Per Wigren <wigren@××××.se> wrote: |
| 3 |
|
| 4 |
> Agreed. But I still think gobo should be an exception.. 3 hours on my |
| 5 |
> pretty fast machine vs a minute using tcc is a HUGE win! The Gobo tools |
| 6 |
> are only used when compiling other Eiffel-packages anyway.. It contains |
| 7 |
> Eiffel-replacements for C-stuff like flex, bison/yacc, cpp |
| 8 |
> (preprocessor) and more.. It's not used at runtime.. |
| 9 |
|
| 10 |
Given the size of tcc itself, the huge win we can observe with gobo, and |
| 11 |
the fact that gobo/eiffel is pretty esoteric even in Gentoo circles, I |
| 12 |
think we should default to DEPEND="dev-lang/tcc-<version>" for now. |
| 13 |
|
| 14 |
Eventually, it would be nice to have a tcc useflag, but if it's in reality |
| 15 |
only applicable for this one package, there will be little use for it. As |
| 16 |
tcc starts being able to compile other packages _AND_ those packages |
| 17 |
exhibit a noticeable improvement in compilation time, I suggest we |
| 18 |
introduce the useflag. |
| 19 |
|
| 20 |
In the meantime, we should just make it easy for people to modify the |
| 21 |
ebuild to not avail itself of tcc, for the people who feel a strong |
| 22 |
loyalty towards gcc ;) |
| 23 |
|
| 24 |
In time, it would of course be really, really sweet to have |
| 25 |
package-specific useflags and package-specific default useflag settings, |
| 26 |
so that we could do something like: |
| 27 |
|
| 28 |
# emerge --show-options gobo |
| 29 |
Useflag (default setting): |
| 30 |
tcc (on) |
| 31 |
whatever (off) |
| 32 |
... |
| 33 |
|
| 34 |
# USE="+tcc" emerge gobo |
| 35 |
|
| 36 |
But that's for another time. |
| 37 |
|
| 38 |
|
| 39 |
Kind regards, |
| 40 |
|
| 41 |
Karl T |
| 42 |
|
| 43 |
-- |
| 44 |
gentoo-dev@g.o mailing list |
Archives