summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 5d35141)
raw | patch | inline | side by side (parent: 5d35141)
author | Thomas Vander Stichele <thomas@apestaart.org> | |
Thu, 24 Apr 2003 09:23:33 +0000 (09:23 +0000) | ||
committer | Thomas Vander Stichele <thomas@apestaart.org> | |
Thu, 24 Apr 2003 09:23:33 +0000 (09:23 +0000) |
Original commit message from CVS:
adding a q&a
adding a q&a
docs/faq/Makefile.am | patch | blob | history | |
docs/faq/developing.xml | patch | blob | history | |
docs/faq/gstreamer-faq.xml | patch | blob | history |
diff --git a/docs/faq/Makefile.am b/docs/faq/Makefile.am
index 0af304a08b35387df7e9fedab631371c653f97e7..ea06c1460933c314dfd3afdd2ea1ff4f898fcf8b 100644 (file)
--- a/docs/faq/Makefile.am
+++ b/docs/faq/Makefile.am
perl -i -p -e's@href="index\.html@href="index.php@' $$a; \
perl -i -p -e's@href="(ar.*)\.html@href="$$1.php@' $$a; \
done
-
-check:
- xmllint -noout -valid $(MAIN)
-
index 459c613bc07e97bfca9d216ae022c739369167f1..c64d730afe4b6e88ac2c2a520d0e27aa213fa946 100644 (file)
--- a/docs/faq/developing.xml
+++ b/docs/faq/developing.xml
</answer>
</qandaentry>
+ <qandaentry>
+ <question id="developing-uninstalled-gstreamer">
+ <para>How do I develop against an uninstalled GStreamer copy ?</para>
+ </question>
+
+ <answer>
+ <para>
+It is possible to develop and compile against an uninstalled copy of
+gstreamer and gst-plugins (for example, against CVS copies).
+The easiest way to do this is to use a script like this (for bash):
+
+<programlisting>
+#!/bin/bash -i
+# set up environment to use and develop gstreamer from uninstalled
+# this is run -i so that PS1 doesn't get cleared
+
+# extract version from $0
+# gst-cvs -> cvs
+VERSION=`echo $0 | sed s/.*gst-//g`
+echo $VERSION
+
+# base path under which dirs are installed
+GST=~/gst/$VERSION
+if test ! -e $GST; then
+ echo "$GST does not exist !"
+ exit
+fi
+
+# set up a bunch of paths
+PATH=$GST/gstreamer/tools:$GST/gst-plugins/tools:$PATH
+export PKG_CONFIG_PATH=$GST/gstreamer/pkgconfig:$GST/gst-plugins/pkgconfig
+export GST_PLUGIN_PATH=$GST/gstreamer:$GST/gst-plugins
+
+# set up prompt to help us remember we're in a subshell and start bash
+PS1="[gst-$VERSION] $PS1" bash
+</programlisting>
+If you put this script in your path, and symlink it to gst-cvs (if you want
+to develop against cvs HEAD) or to gst-0.6 (if you want to develop against the
+0.6 branch), it will automatically use the uninstalled version from that
+directory.
+ </para>
+ <para>
+This requires you to have put your checkouts of gstreamer and gst-plugins
+under ~/gst/cvs (for the HEAD version). The program is easily modifiable
+if this isn't the case.
+ </para>
+ <para>
+After running this script, you'll be in an environment where you can
+use the uninstalled tools, and where gst-register registers the uninstalled
+plugins by default. Also, pkg-config wil detect the uninstalled copies
+before any installed copies.
+ </para>
+ </answer>
+ </qandaentry>
+
+
<qandaentry>
<question id="developing-gconf">
<para>How can I use GConf to get the system-wide defaults ?</para>
index a1ce0bb003ddf274e91eaef9d092f27d4f55a86a..fcd4167ba76b80eb54d7ca7b75f3770615126b28 100644 (file)
<revhistory>
<revision>
- <revnumber>0.1</revnumber>
+ <revnumber>0.1.1</revnumber>
+ <date>2003-04-24</date>
+ <revremark>Added Q&A about developing with uninstalled copy.</revremark>
+ </revision>
+
+ <revision>
+ <revnumber>0.1.0</revnumber>
<date>2002-10-01</date>
<revremark>Initial conversion from FAQ database.</revremark>
</revision>