From 49749466639aae446e159f9e7e3fcf80eea1adf7 Mon Sep 17 00:00:00 2001 From: Darren Salt Date: Sat, 15 Oct 2005 13:41:27 +0000 Subject: Add a small section on building .debs. Mention -dev/-devel packages in the front-end build problems section. Mention why the name of the "gnome-xine" CVS module. CVS patchset: 7760 CVS date: 2005/10/15 13:41:27 --- doc/faq/faq.sgml | 56 ++++++++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 48 insertions(+), 8 deletions(-) diff --git a/doc/faq/faq.sgml b/doc/faq/faq.sgml index 273aa305e..8fe44d01a 100644 --- a/doc/faq/faq.sgml +++ b/doc/faq/faq.sgml @@ -75,7 +75,7 @@ - What are those xine-lib, xine-ui, gxine, ... modules in cvs for? + What are those xine-lib, xine-ui, gnome-xine, ... modules in cvs for? Some time ago xine just became too complex to be just one big program. Therefore it was split into two major parts. @@ -122,18 +122,26 @@ Then, to check out individual modules (e.g. xine-lib, - gxine or xine-ui): + gnome-xine or xine-ui):    cvs -d :pserver:anonymous@cvs.xine.sf.net:/cvsroot/xine co <modulename> + + Why is gxine's CVS module named "gnome-xine"? + + Historical reasons: gxine was originally named gnome-xine. + + + Where can I find pre-compiled binaries, e.g. RPMs? The xine project does not provide pre-compiled binaries for legal reasons (some parts of xine may be covered by patents in some countries). Some OS projects/vendors (e.g. debian, freebsd, ...) offer binaries - for their distributions - please contact them for further info. + for their distributions - please contact them or use their package search + tools for further info. You can also find links to third parties providing xine RPMs on the xine homepage at http://xinehq.de/index.php/releases. @@ -168,7 +176,7 @@ Frontends might need additional libraries, e.g. for gxine you'll need to have - GTK installed. Make sure you have not only the shared libraries themselves + GTK2 installed. Make sure you have not only the shared libraries themselves but also the header files (often packaged seperately as so-called -dev packages) on your system. @@ -250,7 +258,7 @@ - Making your own RPM packages (xine-lib, xine-ui) + Making your own RPM packages (xine-lib, xine-ui, gxine) Basically you will only have to issue one command, if you have just downloaded a source tarball from our web site: @@ -268,7 +276,7 @@ In case that you have a fresh CVS checkout, you will need to do the following first in order to get a tarball release out of it which you can later use with the rpmbuild -ta command above: -    ./autogen.sh && make clean && make dist +    ./autogen.sh && make clean && make dist In any case, please keep in mind that you have to build and install @@ -276,6 +284,36 @@ + + Making your own .deb packages (xine-lib, xine-ui; gxine CVS) + + First, make sure that the "devscripts" package is installed. You'll + then need the following commands: + +   tar xzf <PACKAGE-VER.tar.gz> +   cd <PACKAGE-VER> +   ./autogen.sh noconfig +   debuild binary + + (If debuild complains about unmet dependencies, then + - as root - install them using + aptitude install <PACKAGES> then re-run + debuild binary. + + + Once the build has been successfully completed, you'll have some new .debs. + +   cd .. +   ls *.deb +   su - -c 'cd '"`pwd`"' && dpkg -i <DEB_PACKAGES>' + + + + In any case, please keep in mind that you have to build and install + xine-lib first before you can proceed with xine-ui or gxine. + + + Can I provide additional CFLAGS for compilation? @@ -390,8 +428,10 @@ have $prefix/bin in your path and that your linker is able to find libraries installed in $prefix/lib By the way, $prefix is where you installed your xine-lib to earlier - (yes, installing xine-lib with make install would be a good - idea before trying to compile the frontend ;) ). + (yes, installing xine-lib with make install or + installing the corresponding distribution-provided -dev or -devel + package would be a good idea before trying to compile the frontend ;) + ). -- cgit v1.2.3