[haiku-development] Re: my build environment problems
- From: "Michael Berg" <mike@xxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 15 Jun 2007 07:29:06 -0400
On 6/15/07, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote:
"Michael Berg" <mike@xxxxxxxxxxx> wrote:
> On R5 I try for R5 and Dano for Dano. I can't build Haiku I've only
> got 256
> RAM right now. I have seperate trees at the moment. I did install
> the
> complete gcc package, replaced the headers and library.
You may not be able to compile some stuff for R5 or Dano because we
don't do that that often, depending on the maintainer. But most stuff
should build just fine (like Tracker and Deskbar) on all platforms.
Also, I'm building Haiku with only 256 MB on some machines, too. When
building the whole tree you may quit everything except the Terminal to
make it work, but Jam will use less memory when there are less targets
to be built; IOW you can make iterative builds until you can build the
whole thing (ie. build libbe.so separately).
HTH
Bye,
Axel.
From here on out R5 will mean R5 and Dano unless stated otherwise :)
I am able to build quite a few things
in R5. I'm wondering if I should go back and "fix" the stuff that
doesn't. For
example last night I started looking at cortex, since it doesn't compile. I
found that most of the problems were with missing class references. I fixed
them, now it is hitting me with some real errors. Do I fix these and submit
a patch or is it unnecessary for some apps to compile under R5. I guess
what it boils down to is does the project want someone to be testing and
fixing these old targets. If R5 binary compatibility is a goal of R1
shouldn't these builds be maintained?
Other related posts: