[haiku-development] Re: GCC 2 x GCC 4.
- From: Alexandre Deckner <alex@xxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 13 Aug 2008 16:34:04 +0200
Bruno Albuquerque wrote:
Alexandre Deckner wrote:
I for one, never tried either the gcc4 or hybrid build, so from my
point of view this still looks experimental and not mandatory for the
first alpha, but please prove me wrong :-)
It is definitely not mandatory, but it is also that I would like to do
sooner than later. The point is that the first developer-oriented
release is the best release to do this as we will have mostly
developers using it. Later revisions, specially if this one is a
success, will result inmore users than developers and then it gets
complicated.
Besides, supposing that the gcc4 hybrid works perfectly, alpha
testers error reporting is gonna be more complex since we will have
to account for compiler/library combinations that would be implicit
otherwise.
This is for developers after all and we *WILL* have to do this at some
point in time. We will on;y be supporting the apps we shipe anyway and
we will know how they were compiled. Other apps (that the user
download, for exmaple), will mostly like be GCC2. In the end, we can
always include a small tool that is able to tell which GCC version was
used for a specific program.
This might be ok for haiku developers, but a new developer is also a
general user and thus could still be confused by that. But you're right
that it *WILL* happen and doing it sooner has it's advantages.
Wait for what? To get clueless users using the system and then do
this? :)
Well, i'm just prudent, i mean, wait for our primary goals to be
completed and somewhat stable. This looks more like a new feature to me
and not something high on the priorities. But don't take me wrong, i'd
really like to see this happen, it just doesn't look that harmless to me
(for users/new-devs and haiku devs) at this point :-)
One could even argue this isn't an R1 goal, more of a R1.x when we
start throwing the legacy and transition to the real future, aka R2 ;-)
This would be true if it was not already done. Also the goal of being
R5 compatible is not broken by this.
Yeah, i know it's done and probably working like a charm, but it just
looked to me like noone really tested it, but maybe i'm alone :-)
Regards,
Alex
Other related posts:
