I've been frustrated by this as well, especially during development of
the Network kit (which seemed especially sensitive to compiler versions
for some unknown reason). When I first started with the project I had
to drill through the newsletters archive to find out what was required
for OBOS development (issue 13, "So, you wanna be an OBOS developer",
IIRC). IM[not so]HO, it would behoove us to document a set of minimum
requirements for the toolchain somewhere on our site and in a more
prominent place, maybe on the "Dev Central" page. Better yet, perhaps
we could include a download link on said page for the complete
toolchain (including the updated cvs, ld, and jam stuff), that way
we're all using the same set of development tools (?). Standards are a
good thing sometimes. :-)
For whatever it's worth I've been using the BeOS Max 3 beta 2 and am
quite happy with it. Vasper has done a really good job in maintaining
this distro.
Just my two bits, not trying to stir up trouble.
Cheers, Scott
On Fri, 22 Aug 2003 21:23:44 -0400 EDT "Jared Eldredge" <jared@xxxxxx> wrote:David
i believe that gcc 2.95.3 is the right compiler. OBOS uses JAM for its
build system and you should probably have some software for that as
well.
No,
Please do not use gcc 2.95.3. It seems you are looking at an older version
of BeOS MAX since they have (AFAIK) corrected this oversight in the
current version. Use either the gcc included in R5 (from 1999) or the
geekgadgets gcc. (from 2000, version 2.9-beos-000224) If they still have
not fixed the BeOS MAX "distro" then you can still install it and install
one of the working compilers over it. (or just switch to the other
compiler if it turns out to be bundled with it as well)
could someone with more experience please reply for David with a list of the software tools required/useful for diving into the code base?
As it was mentioned earlier, you can find all of the open-beos specific
tools at this page: http://open-beos.sourceforge.net/dev.php
Please note that you will have to remake the jam from cvs after you do
a checkout. You can do this by running the web jam in the tools subdir.
Andrew
