|
|
发表于 2004-2-23 19:05:23
|
显示全部楼层
OpenBeOS Howto
Basic information on how to install and build OpenBeOS sources from CVS.
It seems the one thing the OpenBeOS project forgot to do was to supply a simple instruction page for people who want to install and build from CVS. So here it is:
0. You must install onto vanilla BeOS 5.0.3 to build this code. If you are running BeOS 5.0.3 Personal Edition you will also need to install the R5 Development Tools. Do NOT install any other packages such as the mediaupdate, Bone-7a, OpenGL, 3Dkit or anything which could modify the system. If any of these have been installed already, remove them first or do a completely fresh installation.
1. Download copies of CVS, JAM and the PDF library (see the links below) and install them under the /boot/home/config tree in appropriate locations. The PDF library shouldn't be necessary but it is for now, evidently.
2. Install ld_switch and set it so that the new linker is in use. If you have a totally unmodified BeOS 5.0.3 system, simply installing the new ld into /boot/home/config/bin is sufficient.
3. Create a directory called /boot/home/obos or something similar to receive the files. The name and location isn't important, but it should be somewhere in your home tree.
4. Open a terminal and change to the directory created in (3) above.
5. Type the following:
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/open-beos login
(Hit the Enter key when asked for a password)
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/open-beos co current
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/open-beos logout
You should soon have all the sourcecode under a new subdirectory called `current'.
6. Type `cd current' to get into that directory.
6a. Type `chmod -x * -R' to fix source code erroneously marked as executable. You should only need to do this at the first checkout.
7. Type `./configure'
8. Type `jam'
You should now be seeing the build in progress, and with any luck there shouldn't be any major problems from here. There will be a few new libraries popping up in /boot/home/config/lib (which could be improved, since the build really should stay independent of the host) but otherwise your system will remain as it was.
Once the build finishes you can browse the source tree and look over the fine work of the developers, hack a bit of code and/or find some bugs to fix/report.
To update the code you should create a shell script so you can forget about the complexities of CVS itself. Here's the one I use, which I call `update':
---8<---snip---
#! /bin/sh
# Script to update OpenBeOS sources from SourceForge
echo No password, hit Enter
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/open-beos login
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/open-beos update
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/open-beos logout
---8<--snip---
Assuming you created the directory suggested in (3) above, this script should live in /boot/home/obos
An-Dee <an-dee@beos.hu> has also pointed out that you can simply cd to /boot/home/obos/current and type `cvs up' although this doesn't allow you to specify the -z3 for compressed downloads.
A tip to speed up subsequent builds by an hour or more (depending on processor speed) follows:
Edit src/Jamfile and change the following lines thus ...
# SubInclude OBOS_TOP src tests ;
# SubInclude OBOS_TOP src tools ;
You're unlikely to need these rebuilt in a hurry.
Go to it!! |
|
IP卡
狗仔卡
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
显身卡
楼主
发表于 2004-2-21 03:02:12