Author: fernando
Date: Tue Oct 15 04:23:47 2013
New Revision: 11979
Log:
Rephrase tests intructions for dbus-1.6.16.
Modified:
trunk/BOOK/general/sysutils/dbus.xml
Modified: trunk/BOOK/general/sysutils/dbus.xml
==============================================================================
--- trunk/BOOK/general/sysutils/dbus.xml Tue Oct 15 02:43:51 2013
(r11978)
+++ trunk/BOOK/general/sysutils/dbus.xml Tue Oct 15 04:23:47 2013
(r11979)
@@ -94,7 +94,8 @@
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="dbus-glib"/> (to run tests),
- <xref linkend="dbus-python"/> (to run tests) and
+ <xref linkend="python2"/> (to run tests),
+ <xref linkend="dbus-python"/> (to run tests), and
<xref linkend="doxygen"/> (to generate the API documentation)
</para>
@@ -162,11 +163,15 @@
<para>
The dbus tests cannot be run until after <xref linkend="dbus-glib"/>
- has been installed. The tests require passing additional parameters to
- <command>configure</command> and exposing additional functionality in the
- binaries. These interfaces are not intended to be used in a production
- build of <application>D-Bus</application>. If you would like to run the
- unit tests, issue the following commands:
+ has been installed. If you want to run only the unit tests, replace,
+ below, <parameter>--enable-tests</parameter> by
+ <parameter>--enable-embedded-tests</parameter>, otherwise,
+ <xref linkend="dbus-python"/> has to be installed, before.
+ The tests require passing additional parameters to
+ <command>configure</command> and exposing additional functionality in
+ the binaries. These interfaces are not intended to be used in a
+ production build of <application>D-Bus</application>. If you would
+ like to run the tests, issue the following commands:
</para>
<screen><userinput>make distclean &&
@@ -176,8 +181,8 @@
make distclean</userinput></screen>
<para>
- If run-test.sh fails, it can be disabled with the following sed, before
- running the commands for the tests:
+ If <command>run-test.sh</command> fails, it can be disabled with the
+ following sed, before running the commands for the tests:
</para>
<screen><userinput>sed -i -e 's:run-test.sh:$(NULL):g'
test/name-test/Makefile.in</userinput></screen>
@@ -215,7 +220,14 @@
<para>
<parameter>--enable-tests</parameter>: Build extra parts of the code to
- support testing. Configure will end with a NOTE warning about this.
+ support all tests. Configure will end with a NOTE warning about increased
+ size of libraries and decreased security.
+ </para>
+
+ <para>
+ <parameter>--enable-embedded-tests</parameter>: Build extra parts of the
+ code to support only unit tests. Configure will end with a NOTE warning
+ about increased size of libraries and decreased security.
</para>
<para>
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
