[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnash-commit] gnash ChangeLog doc/C/Makefile.am doc/C/refmanu...
|
From: |
Rob Savoye |
|
Subject: |
[Gnash-commit] gnash ChangeLog doc/C/Makefile.am doc/C/refmanu... |
|
Date: |
Sun, 02 Mar 2008 17:49:18 +0000 |
CVSROOT: /sources/gnash
Module name: gnash
Changes by: Rob Savoye <rsavoye> 08/03/02 17:49:18
Modified files:
. : ChangeLog
doc/C : Makefile.am
doc/C/refmanual: internals.xml
doc/C/refmanual/extensions: extensions.xml
Log message:
* doc/C/Makefile.am: Furthur tweaking of the .xml.texi rule so
it
works with versions to correctly produce both info files. On
Fedora, it kept only creating gnash_user.info
* doc/C/refmanual/internals.xml: Use <emphasis> instead of
<code>,
as <code> doesn't appear to be supported on Fedora.
* doc/C/refmanual/extensions/extensions.xml: Use <emphasis>
instead of <code>, as <code> doesn't appear to be supported on
Fedora.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnash/ChangeLog?cvsroot=gnash&r1=1.5774&r2=1.5775
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/Makefile.am?cvsroot=gnash&r1=1.59&r2=1.60
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/internals.xml?cvsroot=gnash&r1=1.4&r2=1.5
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/refmanual/extensions/extensions.xml?cvsroot=gnash&r1=1.2&r2=1.3
Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnash/gnash/ChangeLog,v
retrieving revision 1.5774
retrieving revision 1.5775
diff -u -b -r1.5774 -r1.5775
--- ChangeLog 2 Mar 2008 16:32:20 -0000 1.5774
+++ ChangeLog 2 Mar 2008 17:49:17 -0000 1.5775
@@ -1,5 +1,18 @@
2008-03-02 Rob Savoye <address@hidden>
+ * doc/C/Makefile.am: Furthur tweaking of the .xml.texi rule so it
+ works with versions to correctly produce both info files. On
+ Fedora, it kept only creating gnash_user.info
+ * doc/C/refmanual/internals.xml: Use <emphasis> instead of <code>,
+ as <code> doesn't appear to be supported on Fedora.
+ * doc/C/refmanual/extensions/extensions.xml: Use <emphasis>
+ instead of <code>, as <code> doesn't appear to be supported on
+ Fedora.
+
+ * doc/C/Makefile.am: For the perl based version of the docbook
+ tools, pipe directly through makeinfo to avoid file name
+ transformation problems.
+
* doc/C/Makefile.am: Print warning when linking to preformatted
versions that they may be out of date. Change path to preformatted
versions.
Index: doc/C/Makefile.am
===================================================================
RCS file: /sources/gnash/gnash/doc/C/Makefile.am,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -b -r1.59 -r1.60
--- doc/C/Makefile.am 2 Mar 2008 16:53:46 -0000 1.59
+++ doc/C/Makefile.am 2 Mar 2008 17:49:18 -0000 1.60
@@ -151,11 +151,15 @@
fi
endif
-# basefile=$(notdir $(basename $<));
+# The first test seems to be the default for Fedora/Redhat/Centos based
distributions,
+# which use a wrapper script for jade.
+# Ubuntu/Debian uses a real perl script that actually does the real work
.xml.texi:
if ENABLE_TEXI
address@hidden test x$(DB2X_TEXI) != x; then \
- $(DB2X_TEXI) --encoding=us-ascii//TRANSLIT --string-param
directory-description="Gnash" $< ; \
+ out=`echo $* | sed -e 's:gnash:gnash_:'`; \
+ $(DB2X_TEXI) --encoding=us-ascii//TRANSLIT --string-param
directory-description="Gnash" --string-param output-file=$${out} $<; \
+ $(MAKEINFO) --force $${out}.texi; \
else \
basefile="$*"; \
$(DB2X_XSLTPROC) -s texi $< --output $${basefile}.txml; \
Index: doc/C/refmanual/internals.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/internals.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- doc/C/refmanual/internals.xml 2 Mar 2008 16:28:29 -0000 1.4
+++ doc/C/refmanual/internals.xml 2 Mar 2008 17:49:18 -0000 1.5
@@ -31,7 +31,6 @@
are freed up automatically by the interpreter. Both STL and
Boost smart pointers are used.
</para>
-
</sect3>
<sect3 id="libgnashgeo">
@@ -40,7 +39,6 @@
<para>
Libgnashgeo contains code for device independent graphics routines.
</para>
-
</sect3>
<sect3 id="libgnashgui">
@@ -50,7 +48,6 @@
Libgnashgui contains code for a portable GUI class that
supports using GTK2, a framebuffer, SDL, or KDE, FLTK, or Aqua.
</para>
-
</sect3>
<sect3 id="libgnashserver">
@@ -90,23 +87,22 @@
code that glues this display to the Gnash. Supported
rendering backends are OpenGL, Cairo, and AGG.
</para>
-
</sect3>
+
<sect3 id="libgnashpluin">
<title>libgnashplugin</title>
<para>
Libgnashplugin is the Mozilla/Firefox plugin.
</para>
-
</sect3>
+
<sect3 id="libklashpart">
<title>libklashpart</title>
<para>
Libklashpart is the Konqueror plugin.
</para>
-
</sect3>
</sect2>
@@ -717,7 +713,6 @@
This will print a summary of tests run, and should be
called as the last step in your SWF generator.
-
</programlisting>
</para>
@@ -736,10 +731,7 @@
See section <link linkend="writing_test_runners">Writing Test
Runners</link>
for information about writing SWF test runners.
</para>
-
-
</sect3>
-
</sect2>
<sect2 id="writing_dejagnu_so_tests">
@@ -753,20 +745,20 @@
</para>
<para>
- The loadable module is called <code>Dejagnu.swf</code> and is built
during
- <code>make check</code> under testsuite/misc-ming.all. In order to use
it
+ The loadable module is called <emphasis>Dejagnu.swf</emphasis> and is
built during
+ <emphasis>make check</emphasis> under testsuite/misc-ming.all. In order
to use it
you will need to load it into your SWF. We currently load it with an
IMPORT
tag for our ActionScript based test cases, but you can probably also use
loadMovie or whatever works in the target SWF you're generating. Just
make
sure that the module is initialized before using it. You can check this
by
- inspecting the <code>dejagnu_module_initialized</code> variable, which
will
+ inspecting the <emphasis>dejagnu_module_initialized</emphasis>
variable, which will
be set to 'true' when all initialization actions contained in the
- <code>Dejagnu.swf</code> file are executed.
+ <emphasis>Dejagnu.swf</emphasis> file are executed.
</para>
<para>
Once the module is loaded you will be able to invoke the following
functions,
- all registered against the <code>_root</code> sprite (effects of
<code>_lockroot</code>
+ all registered against the <emphasis>_root</emphasis> sprite (effects
of <emphasis>_lockroot</emphasis>
untested):
<programlisting>
@@ -810,11 +802,14 @@
</para>
<para>
- Visual traces are lines of text pushed to a textarea defined by the
<code>Dejagnu.swf</code> module.
- The textarea is initially placed at <code>0, 50</code> and is
<code>600x800</code> in size.
- You can resize/move the clip after loading it.
- Also, you can completely make the clip invisible if that bothers you.
The important thing is the
- <emphasis>debugging</emphasis> trace (call to the trace function). The
latter will be used by the testing framework.
+ Visual traces are lines of text pushed to a textarea defined
+ by the <emphasis>Dejagnu.swf</emphasis> module. The textarea is
+ initially placed at <emphasis>0, 50</emphasis> and is
+ <emphasis>600x800</emphasis> in size. You can resize/move the clip
+ after loading it. Also, you can completely make the clip
+ invisible if that bothers you. The important thing is the
+ <emphasis>debugging</emphasis> trace (call to the trace
+ function). The latter will be used by the testing framework.
</para>
<para>
@@ -973,14 +968,14 @@
<para>
A generator for simple test runners can be found in
- <code>testsuite/generic-testrunner.sh</code>.
- The script can be invoked by passing it <code>$(top_builddir)</code>
+ <emphasis>testsuite/generic-testrunner.sh</emphasis>.
+ The script can be invoked by passing it
<emphasis>$(top_builddir)</emphasis>
as the first argument and the name of the SWF file (without the path)
as the second argument. This will create a specific runner for your
test in the current build directory.
A simple Makefile.am rule for doing this follows:
<programlisting>
-MyTest-Runner: $(srcdir)/../generic-testrunner.sh MyTest.swf
+ MyTest-Runner: $(srcdir)/../generic-testrunner.sh MyTest.swf
sh $(srcdir)/../generic-testrunner.sh $(top_builddir) MyTest.swf > $@
chmod +x $@
</programlisting>
@@ -993,7 +988,7 @@
to the generic-testrunner.sh call. The following will create a runner
playing the movie twice:
<programlisting>
-MyTest-Runner: $(srcdir)/../generic-testrunner.sh MyTest.swf
+ MyTest-Runner: $(srcdir)/../generic-testrunner.sh MyTest.swf
sh $(srcdir)/../generic-testrunner.sh -r2 $(top_builddir) MyTest.swf >
$@
chmod +x $@
</programlisting>
@@ -1004,7 +999,7 @@
exact number of times to call the frame advancement routine, you can
use the
-f switch to control that.
<programlisting>
-MyTest-Runner: $(srcdir)/../generic-testrunner.sh MyTest.swf
+ MyTest-Runner: $(srcdir)/../generic-testrunner.sh MyTest.swf
sh $(srcdir)/../generic-testrunner.sh -f10 $(top_builddir) MyTest.swf
> $@
chmod +x $@
</programlisting>
@@ -1064,6 +1059,5 @@
&newasclass;
-
</chapter>
Index: doc/C/refmanual/extensions/extensions.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/refmanual/extensions/extensions.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- doc/C/refmanual/extensions/extensions.xml 1 Mar 2008 21:14:07 -0000
1.2
+++ doc/C/refmanual/extensions/extensions.xml 2 Mar 2008 17:49:18 -0000
1.3
@@ -57,7 +57,7 @@
<para>
Each new extension should live in it's own directory. The
extensions included in Gnash are all in the
- <code>gnash/extensions</code> directory. Creating an extension
+ <emphasis>gnash/extensions</emphasis> directory. Creating an extension
requires a Makefile.am,
</para>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gnash-commit] gnash ChangeLog doc/C/Makefile.am doc/C/refmanu...,
Rob Savoye <=