|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]||[ Search: ]|
Written by Vincent Knecht email@example.com. Last updated 19 March 2006.
It is possible to build Crystal Space RPM's. This is useful if you want to distribute pre-built Crystal Space packages, or if you want to install Crystal Space on your machine using the normal package management facilities of your host. For this purpose, ‘CS/scripts/rpm/cs.spec’ file is provided with Crystal Space.
Building RPM packages involves a few settings, which are covered at the following page:
Once you've set your system to build RPM packages as a regular user, perform the following steps:
cd /home/user/rpm/SPECS tar xvjf /home/user/rpm/SOURCES/cs-current-snapshot.tar.bz2 \ CS/scripts/rpm/cs.spec mv CS/scripts/rpm/cs.spec /home/user/rpm/SPECS rm -rf CS
rpmwon't be able to do his job.
rpmbuild -bb cs.spec
rpmbuild -ba cs.spec
Build options are specified by using
--with switch. The following
values are supported:
--with perlto build with Perl support.
--with debugto build with debugging support.
--with sharedto build with shared libraries.
So, to build all packages, with Perl support, use:
rpmbuild -ba cs.spec --with perl
The binary RPM's should be under ‘rpm/RPMS/’, and the source RPM in ‘rpm/SRPMS/’.
The process creates four Crystal Space binary RPM packages:
|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
This document was generated using texi2html 1.76.