mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-30 05:31:15 +00:00
adding a q&a
Original commit message from CVS: adding a q&a
This commit is contained in:
parent
5d35141256
commit
29d011a8e2
3 changed files with 63 additions and 5 deletions
|
@ -35,7 +35,3 @@ www-faq: gstreamer-faq
|
||||||
perl -i -p -e's@href="index\.html@href="index.php@' $$a; \
|
perl -i -p -e's@href="index\.html@href="index.php@' $$a; \
|
||||||
perl -i -p -e's@href="(ar.*)\.html@href="$$1.php@' $$a; \
|
perl -i -p -e's@href="(ar.*)\.html@href="$$1.php@' $$a; \
|
||||||
done
|
done
|
||||||
|
|
||||||
check:
|
|
||||||
xmllint -noout -valid $(MAIN)
|
|
||||||
|
|
||||||
|
|
|
@ -37,6 +37,62 @@ or integrate with autoconf using the pkg.m4 macro.
|
||||||
</answer>
|
</answer>
|
||||||
</qandaentry>
|
</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>
|
<qandaentry>
|
||||||
<question id="developing-gconf">
|
<question id="developing-gconf">
|
||||||
<para>How can I use GConf to get the system-wide defaults ?</para>
|
<para>How can I use GConf to get the system-wide defaults ?</para>
|
||||||
|
|
|
@ -28,7 +28,13 @@
|
||||||
|
|
||||||
<revhistory>
|
<revhistory>
|
||||||
<revision>
|
<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>
|
<date>2002-10-01</date>
|
||||||
<revremark>Initial conversion from FAQ database.</revremark>
|
<revremark>Initial conversion from FAQ database.</revremark>
|
||||||
</revision>
|
</revision>
|
||||||
|
|
Loading…
Reference in a new issue