[haiku-development] hybrid questions -- not "how" to build, but why?

  • From: Stéphane Charette <stephanecharette@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Mon, 28 Dec 2009 03:24:58 -0800

This e-mail is about the "why" behind hybrid builds.  (I'll start a
different e-mail thread to handle my questions regarding "how".)  I've make
some newbie assumptions:

ASSUMPTION #1:  gcc 2.95.3 is solely for people with old BeOS apps hanging
around

ASSUMPTION #2:  gcc 4 is almost ten years older then gcc 2, contains a
truckload of fixes and new stuff, and thus must be better than gcc 2 at many
things (remember, gross newbie assumptions here!)

Here are my questions:

QUESTION #1:  Without starting a flame war over semantics or
code/implementation/theory details, are assumptions #1 and #2 valid?

QUESTION #2:  As a new developer to Haiku, with no old BeOS software hanging
around on my shelves, should I want a hybrid build, or should I just build
with gcc4?

QUESTION #3:  What is the difference between the two hybrid flavours, GCC2/4
and GCC4/2?

QUESTION #4:  If the answer to question #2 is that I should use a hybrid,
how do I know if I should use GCC2/4 or GCC4/2?

I spent a large part of tonight reading though several dozen past postings
to the mailing list as well as the wiki...and while I understand most of
what I'm reading, I'm still left wanting a clear and concise "getting
started" build guide.  I wont promise the moon, but I've documented what
I've learned up to now, and will summarize the answers to my questions for
future new Haiku developers here:
http://charette.no-ip.com:81/haiku/#Your_First_Hybrid_Build

Best regards,

Stéphane Charette

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 12-2009