| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Building your own RPMs is probably the best option. This way you won't have to find distribution specific package, and you'll be able to set building options. For this purpose, `CS/scripts/rpm/cs.spec' file is provided with Crystal Space.
Building RPMs packages involves a few settings, which are covered in the following page: http://qa.mandrakesoft.com/twiki/bin/view/Main/RpmHowTo#Preliminary_tasks
Once you've set your system to build RPM packages as a regular user:
cd /home/user/rpm/SPECS
tar xvjf /home/user/rpm/SOURCES/cs98_003.tar.bz2 \
CS/scripts/rpm/cs.spec
mv CS/scripts/rpm/cs.spec /home/user/rpm/SPECS
rm -rf CS/
|
rpm won't be able to do his job.
rpm -bb cs.spec
rpm -ba cs.spec
Build options are specified by using --with switch. The following
values are supported:
--with newrenderer to build with New Renderer support.
--with perl to build with Perl support.
--with debug. This option may be useless since rpm
strips files before packaging.
So, to build all packages, with New Renderer and Perl support, use:
rpm -ba cs.spec --with newrenderer --with perl
The binary RPMs should be under `rpm/RPMS/', and the source RPM in `rpm/SRPMS/'.
The process builds three Crystal Space binary RPMs packages :
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |