* timer.t: Added task-based timer information including the
new directives rtems_timer_initiate(), rtems_timer_server_fire_after(),
and rtems_timer_server_fire_when().
* SUPPORT, LICENSE: New files.
* Numerous files touched as part of merging the 4.5 branch
onto the mainline development trunk and ensuring that the
script that cuts snapshots and releases works on the documentation.
<corsepiu@faw.uni-ulm.de> which:
* should fix the building rtemsdoc outside of the sourcetree with
relative srcdir issue
* adds --enable-papersize=[letter|a4|]
<corsepiu@faw.uni-ulm.de> that makes the following changes:
* Don't use a temporary file for ch19.texi anymore
* pass all files to be handled by summarize as commandline arguments
* Remove a dangling empty first line in posix1003_1.texi (texi2html
(!) expects \input texinfo on the first line)
which splits the current monolithic specs files into a sequence of
subparts. These can be concatenated togather to make a the whole .spec
file. This cleans up the maintenance problem of having "all languages"
and a "C/C++ only" gccnewlib spec files. Plus it should make it easier
to produce variants like the gdb-m68k-bdm which require special hackery. :)
Ralf's comments:
It addresses the way *.spec.in get composed inside of the source
tree.
Changes:
* Each spec.in is broken into several files (*.add), one *.add file
per sub-package.
* Each Makefile.am composes spec.ins from the *.add files
* Removal of redundant automake support files.
* Default value for BuildRoot changed to /tmp/<spec-file-name>
* %clean stage added to *specs
Advantages (IMHO).
* The *.add files are easier to adminstrate and more flexible in
comparison to the former *.specs.ins.
* gccnewlib_c_only.spec.in now is composed from the same sources as
gccnewlib.spec.in (less errors)
* If using the default BuildRoot --clean now deletes all files that
were generated while building.
Notes:
* rtems.spec.in has not yet been adapted to the scheme used for the
other *spec.ins
* Except for cosmetical changes the internals of the *.spec files
should not have changed.
To Apply:
cvs rm -f scripts/binutils/binutils.spec.in
cvs rm -f scripts/gccnewlib/gccnewlib.spec.in
cvs rm -f scripts/gccnewlib/gccnewlib_c_only.spec.in
cvs rm -f scripts/gdb/gdb.spec.in
cvs rm -f scripts/config.sub
cvs rm -f scripts/config.guess
cvs rm -f scripts/install-sh
cvs rm -f scripts/mkinstalldirs
cvs rm -f scripts/missing
patch -p1 < rtems-rc-4.5.0-21.diff
cvs add scripts/*/*.add
cvs add scripts/*/README
This patch changes the installation directory of the supplements to
supplements/<cpu>.
This allows browsing the html files inside of the source tree,
because after having applied this patch, the structure of the html
installation directory hierarchy is the same as the directory
structure of the source tree.
Ralf's comments follow:
Changes:
* Enhanced versioning:
- Addition of automake's version.texi support
- Replacement of rtemsdoc's former versioning support by automake's
versioning support (Abandoning RTEMS-UPDATE-* etc.)
- Abandoning setup.texi.in
- Add EDITION to each documents Makefile.am
- version.texi support in project.am
- Addition of maintainer mode (currently only used to prevent incorrectly
updating timestamps when users touch automake's version.texi timestamp
files (stamp-vti)).
* Fixing info dir support
- Use texinfo's @dircategory and @direntry instead of infos *-DIR-ENTRY
- $(infodir)/dir is now correctly set up
* Avoid using temporary files
- Pipe texts through REPLACE2 into BMENU2 instead of using temporary files.
- Abandon using bmenu in favor of bmenu2 (bmenu could be removed now)
* Prepare Makefile.ams for building in a separate buildtree
- prefix files with $(srcdir) in Makefile.am for files which must be
generated inside of the source tree
Notes:
* rtemsdoc can not yet be build in a separate source-tree, but we
are very close to it.
* You as the maintainer of this package now should always use
--enable-maintainer-mode to configure rtemsdoc.
Adds a -I <path> option to texi2www. This option is supposed to
compatible to the option of the same name in makeinfo, texi2dvi etc.
[This patch actually is kind of a hack, but it works :]
the bug-texinfo mailing list:
There is also a bug in the PDF outline: Any outline item containing an
underscore shows up as a bunch of texinfo codes ("@unhbox @kern.06em
@vbox{..."). This bug was remedied by the following addition to
\pdfmakeoutlines.
