[haiku-development] OS & WebKit builds
- From: David Himelright <david.himelright@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 2 Jun 2009 00:27:20 -0400
Hi, I'm a curious newbie who's just set about getting cross-compilation set
up on ubuntu jaunty with gcc4. I had really hoped to get a dogfood
development rig set up but this is a small machine and there seems to be a
hefty memory requirement for self-hosting system builds. At this point I
have a few questions.
1) What's a likely safe minimum memory for building haiku with gcc4 under
haiku?
a) and is the filesystem driver the memory hog?
b) and what sorts of profiling tools are Haiku developers using?
2) Is there a roadmap doc for the binary compatibility situation? I've read
that Haiku R1 is intended to be more or less binary compatible with BeOS R5,
and that Haiku R2 will break binary compatibility by transitioning to gcc4
for new development. Has any kind of universal binary package format
situation seen any consideration by planners?
3) To Ryan regarding WebKit: I've downloaded the old WebKit dependencies
files from the article on haiku-os.org, and I'm checking out from your svn
server (sorry I didn't email and introduce myself first). I'm only just
getting the hang of using jam, so I'm not quite sure if I've made some
configuration missteps or if the build is busted for gcc4, or both. I
assumed you're now possibly waiting for upstream changes in the tool chain
to settle down.
4) Any suggestions about an oss IDE for applications development that runs
under a gcc4 build?
Any help appreciated. So development is pretty painless and gives me lots of
reason to be optimistic about Haiku.
Thanks,
~David
Other related posts:
