From: Timo Mueller
The title of a pdf document is part of the image used on the title
page. Thus the title defined (e.g. bookinfo.title) in a document
should never be used when creating title pages for pdf documents. As
other output formats may use the title information to create metadata
the tit
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
Furthermore supporting new output formats can now be achieved by
creating a new customization file containi
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
Additional paramet
From: Timo Mueller
Hi,
this patch series was put on hold until the successful release of yocto 1.3.
This is a rebase of the original patch series that now applies to the current
master of the project.
Cheers,
Timo
The original cover letter of the patch:
Hi,
this is a rework of
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |6 +-
.../dev-manual/dev-manual-customizati
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/adt-manual/adt-manual.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/adt-manual/adt-manual.xml
b/documentation/adt-manua
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../dev-manual
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the adt-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |9 +
From: Timo Mueller
This target will generate eclipse help for the dev-manual using
the dev-manual-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile | 10 ++
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the dev-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |7 ---
1
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |6 +-
.../bsp-guide/bsp-guide-customization
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../bsp-guide/
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/bsp-guide/bsp-guide.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/bsp-guide/bsp-guide.xml
b/documentation/bsp-guide/bsp
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the bsp-guide. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |7 ---
1 f
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the kernel-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |8 +---
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/dev-manual/dev-manual.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/dev-manual/dev-manual.xml
b/documentation/dev-manua
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../kernel-man
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/kernel-manual/kernel-manual.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/kernel-manual/kernel-manual.xml
b/documentati
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../poky-ref-m
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/poky-ref-manual/poky-ref-manual.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/poky-ref-manual/poky-ref-manual.xml
b/doc
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |7 +--
.../kernel-manual/kernel-manual-cust
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |7 +--
.../poky-ref-manual-customization.xs
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |3 +--
.../yocto-project-qs-customization.xsl
From: Timo Mueller
This target will generate eclipse help for the yocto-project-qs using
the yocto-project-qs-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile |
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the yocto-project-qs. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |9 +
From: Timo Mueller
This target will generate eclipse help for the poky-ref-manual using
the poky-ref-manual-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile |
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the poky-ref-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |6 +++---
From: Timo Mueller
This target will generate eclipse help for the adt-manual using
the adt-manual-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile | 23 ++
From: Timo Mueller
The script tools/eclipse-help.sed is used to convert links that
point to other documentation parts. This avoids having to leave
the eclipse help center when clicking these links.
---
documentation/Makefile | 18 --
1 files changed, 16 insertions(+), 2 deletio
From: Timo Mueller
This target will generate eclipse help for the kernel-manual using
the kernel-manual-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile |4
From: Timo Mueller
The fake title section is converted into a docbook
article.articleinfo. If used with a custom title page this will lead
to the excapt same output. But I will enable the creation of metadata
from this title information.
---
.../yocto-project-qs/yocto-project-qs.xml |
From: Timo Mueller
---
documentation/Makefile | 16
1 files changed, 4 insertions(+), 12 deletions(-)
diff --git a/documentation/Makefile b/documentation/Makefile
index 785c065..7da14a4 100644
--- a/documentation/Makefile
+++ b/documentation/Makefile
@@ -11,6 +11,8 @@
#
From: Timo Mueller
The file is used when creating eclipse help html files. It processes
all html files and converts links so that the user can navigate
between different docuementation parts without leaving the eclipse
help center.
---
documentation/tools/eclipse-help.sed | 18
From: Timo Mueller
This target will generate eclipse help for the bsp-guide using
the bsp-guide-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile |4 +++-
1
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../yocto-proj
From: Timo Mueller
Hi,
if you build eclipse-poky with the provided build script it will always use
the upstream version of the IDE.
During development I wanted to use my local repository to make sure that my
changes don't break the build system. Therefor I added an option to the build
script to
From: Timo Mueller
If USE_LOCAL_GIT_REPO is set to 1 the build scripts uses the local
repository of the eclipse poky project for building instead of the
upstream project. The local repository is derived from the location
for the build script.
---
scripts/build.sh |8
1 files changed
From: Timo Mueller
If the script is called with the -l option the local git repository is
used instead of the upstream repository.
---
scripts/build.sh |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/scripts/build.sh b/scripts/build.sh
index 2d4452e..5dbdd4a 100755
From: Timo Mueller
Calling the build script with the -h option will now show the usage.
The cmdline parsing can be extended to add new options in the future.
---
scripts/build.sh | 18 ++
1 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/scripts/build.sh b/scripts
From: Atanas Gegov
Adds a method to create a YoctoUIElement that contains the content of
the yocto settings stored in the plugin's default preference store.
---
.../src/org/yocto/sdk/ide/YoctoSDKUtils.java | 25
1 files changed, 25 insertions(+), 0 deletions(-)
diff
From: Timo Mueller
Hi,
changing the yocto settings of a project is currently achieved through
a separate dialog. This dialog can be opened via the eclipse menu bar
(project -> change yocto project settings). Typically all project
related settings in eclipse are located in the project properties
From: Atanas Gegov
Removes the error prone method of using the fControls array and uses
the new YoctoUIElement interface.
Improved method of setting default preferences (globally)
---
.../ide/preferences/YoctoSDKPreferencePage.java| 51 +--
1 files changed, 3 insertions(+)
From: Atanas Gegov
Currently a YoctoUIElement is used to create a YoctoUISetting
widget. It is also possible to retrieve a YoctoUIElement containing
the current input of the widget. This patch adds the capability to
also set the input of the widget using a YoctoUIElement. Instead of
using the fCo
From: Atanas Gegov
The setCurrentInput method replaces the functionality that was
provided by the fControl array.
---
.../src/org/yocto/sdk/ide/YoctoUISetting.java | 14 --
1 files changed, 0 insertions(+), 14 deletions(-)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto
From: Timo Mueller
The yocto property page in a project's properties dialog will now show
the yocto settings that are also used in the global yocto preferences
dialog. On save the defined values will be stored to the project's
environment.
---
.../preferences/YoctoSDKProjectPropertyPage.java
From: Timo Mueller
Saving yocto project settings is currently only used by the "Change
Yocto Project Settings" command. To allow other UI elements
(e.g. project property pages) to modify the yocto settings of a
project the functionality has been extraced to a separate method and
moved to the util
From: Timo Mueller
Adds an empty preference page to projects with the YoctoSDKNature. This
preference page is shown in the standard project properties dialog and
will later allow modifying the yocto settings of the project.
---
.../OSGI-INF/l10n/bundle.properties|1 +
plugins
From: Timo Mueller
As the yocto settings can now be set via the project's property pages,
the "Change Yocto Project Settings" will now open the property page
instead of showing the a standalone dialog.
---
.../yocto/sdk/ide/actions/ReconfigYoctoAction.java | 29 ++
.../yocto/sdk/ide/action
From: Timo Mueller
Hi,
these are some minor fixes for the eclipse help generation currently located
in the timo branch of the yocto-docs repository.
1: Fixes an issue with the figures folder when eclipse target was called
consecutively without cleaning in between
2: Whitespace fix
3: Enable chu
From: Timo Mueller
When calling the eclipse target twice without calling clean in between
the figures folder was copied as a subfolder of the existing figures
folder. This patch fixes the copy command to correctly copy the
figures folder.
---
documentation/Makefile |2 +-
1 files changed, 1
From: Timo Mueller
---
documentation/tools/eclipse-help.sed |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/tools/eclipse-help.sed
b/documentation/tools/eclipse-help.sed
index 71d3395..38690bc 100644
--- a/documentation/tools/eclipse-help.sed
+++ b/docu
From: Timo Mueller
The chunk.quietly option disables the output of the docbook
chunker. Creation of a new html file is now longer printed to the
console. This provides a much cleaner output of the eclipse makefile
target.
---
.../adt-manual-eclipse-customization.xsl |1 +
.../bsp-g
From: Timo Mueller
Adds yocto specific eclipse help to the plugin. The help is currently
empty but will contain the official yocto documentation later.
---
.../META-INF/MANIFEST.MF |3 ++-
.../org.yocto.sdk.ide.doc.user/build.properties|7 +--
plugins/or
From: Timo Mueller
Hi,
since the last proposal some things have changed:
1. Eclipse help generation is now part of the yocto-docs project
(currently available in the origin/timo branch)
2. We agreed that the plugin should be licensed under the EPL v1.0
instead of having a separate documentation
From: Timo Mueller
The separate yocto manuals are added to the table of contents to
prepare their inclusion into the plugin.
---
plugins/org.yocto.sdk.ide.doc.user/plugin.xml | 24
plugins/org.yocto.sdk.ide.doc.user/toc.xml| 18 ++
2 files changed
From: Timo Mueller
This script will checkout the yocto-docs project containing the
official yocto documentation. After successful checkout the eclipse
help is generated and the about.html file of the doc.user plugin is
created.
---
scripts/generate_doc.sh | 84 +
From: Timo Mueller
As documentation is licensed under CCA-SA 2.0 UK and the plugin itself
is licensed under EPL v1.0 an about file needs to be added to the
plugin identifying the third party content.
---
plugins/org.yocto.sdk.ide.doc.user/about.html.in | 166
.../org.yoct
From: Timo Mueller
After successful generation the eclipse help files and the table of
contents of each manual are copied to the user.doc plugin.
---
scripts/generate_doc.sh |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/scripts/generate_doc.sh b/scripts/generate_doc.s
From: Timo Mueller
When building the plugin the matching documentation is automatically
generated and added to the user.doc plugin prior to the plugin build.
---
scripts/build.sh |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/scripts/build.sh b/scripts/build.sh
in
From: Timo Mueller
As the eclipse generation is currently not part of the master the generation is
always using the origin/timo branch to generate the eclipse help. This patch is
added for testing purposes only.
DO NOT MERGE THIS PATCH UPSTREAM - ONLY APPLY LOCALLY FOR TESTING
---
scripts/gen
From: Timo Mueller
Calling the build script with the -h option will now show the usage.
The cmdline parsing can be extended to add new options in the future.
---
scripts/build.sh | 18 ++
1 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/scripts/build.sh b/scripts
From: Timo Mueller
If the script is called with the -l option the local git repository is
used instead of the upstream repository.
---
scripts/build.sh |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/scripts/build.sh b/scripts/build.sh
index 693dcf7..54081d5 100755
From: Timo Mueller
Hi,
I've rebased the patch series. It should now apply to the current master.
Best regards,
Timo
>From the original cover letter:
if you build eclipse-poky with the provided build script it will always use
the upstream version of the IDE.
During development I wante
From: Timo Mueller
If USE_LOCAL_GIT_REPO is set to 1 the build scripts uses the local
repository of the eclipse poky project for building instead of the
upstream project. The local repository is derived from the location
for the build script.
---
scripts/build.sh |8
1 files changed
From: Timo Mueller
If USE_LOCAL_GIT_REPO is set to 1 the build scripts uses the local
repository of the eclipse poky project for building instead of the
upstream project. The local repository is derived from the location
for the build script.
Signed-off-by: Timo Mueller
---
scripts/build.sh |
From: Timo Mueller
Calling the build script with the -h option will now show the usage.
The cmdline parsing can be extended to add new options in the future.
Signed-off-by: Timo Mueller
---
scripts/build.sh | 18 ++
1 files changed, 14 insertions(+), 4 deletions(-)
diff --gi
From: Timo Mueller
Hi,
as Paul requested I've signed-off the patches. Other than that it's still
the rebased patch series from PATCHv2.
Best regards,
Timo
>From the original cover letter:
if you build eclipse-poky with the provided build script it will always use
the upstream version
From: Timo Mueller
If the script is called with the -l option the local git repository is
used instead of the upstream repository.
Signed-off-by: Timo Mueller
---
scripts/build.sh |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/scripts/build.sh b/scripts/build.sh
From: Timo Mueller
This currently empty plugin will in the future contain the
documentation of the yocto project converted to the eclipse help
format.
---
plugins/org.yocto.sdk.doc.user/.classpath |6
plugins/org.yocto.sdk.doc.user/.project| 28 +++
From: Timo Mueller
This is the preparation needed for adding documentation from the yocto
project later on.
---
.../org.yocto.sdk.doc.user/META-INF/MANIFEST.MF|1 +
plugins/org.yocto.sdk.doc.user/build.properties|2 ++
plugins/org.yocto.sdk.doc.user/plugin.xml |7 +++
From: Timo Mueller
Hi,
the documentation of the yocto project can currently be viewed online
or as a separate pdf. When using the eclipse ide to develop software
on base of a yocto sysroot and toolchain it would be convenient to
access the relevant parts of the documentation from within the ide.
From: Timo Mueller
The added plugin will contain the official documentation of the yocto
project.
---
features/org.yocto.sdk.doc/feature.xml |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/features/org.yocto.sdk.doc/feature.xml
b/features/org.yocto.sdk.doc/featur
From: Timo Mueller
The project documentation of yocto is licensed under the Create
Commons Attribution Share Alike 2.0 (CCA-SA). Because the plugins
containing this documentation cannot be licensed under the Eclipse
Public License 1.0, as it is not compatible to the CCA-SA, this
feature will cont
From: Timo Mueller
The feature is added to the yocto main feature so it will be part of
the build. Also when installing the documentation feature will also be
installed.
To be able to install the documentation feature is has to be available
via an eclipse update site. It is currently not part of
From: Timo Mueller
Using the update site the user is able to install the documentation
feature. As it is required by yocto's main feature it will be
automatically installed during the main features installation.
---
features/org.yocto.sdk.site/category.xml |6 ++
features/org.yocto.sdk.
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
Furthermore supporting new output formats can now be achieved by
creating a new customization file containi
From: Timo Mueller
Hi,
before my vacation I've submitted a patch to the eclipse-poky project
integrating the documentation into the eclipse IDE. To enable the integration
into eclipse I've manually generated eclipse help from the documentation
using the eclipse stylesheet provided by docbook.
I
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../adt-manual
From: Timo Mueller
This target will generate eclipse help for the adt-manual using
the adt-manual-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile | 20 ++
From: Timo Mueller
The title of a pdf document is part of the image used on the title
page. Thus the title defined (e.g. bookinfo.title) in a document
should never be used when creating title pages for pdf documents. As
other output formats may use the title information to create metadata
the tit
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the adt-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |9 +
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/adt-manual/adt-manual.xml |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/documentation/adt-manual/adt-manual.xml
b/documentation/adt-manu
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../dev-manual
From: Timo Mueller
This target will generate eclipse help for the dev-manual using
the dev-manual-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile | 10 ++
From: Timo Mueller
---
documentation/Makefile |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/Makefile b/documentation/Makefile
index 0537c22..005d670 100644
--- a/documentation/Makefile
+++ b/documentation/Makefile
@@ -295,13 +295,13 @@ ifneq ($(DOC
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |6 +-
.../dev-manual/dev-manual-customizati
From: Timo Mueller
Hi,
I've recently submitted a proof of concept showing how eclipse help files
can be generated from the adt-manual using the docbook eclipse3.xsl
stylesheet. These patches are currently in the temporary branch 'timo'
in the yocto-docs git.
This patch series fixes a small bug
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../bsp-guide/
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/dev-manual/dev-manual.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/dev-manual/dev-manual.xml
b/documentation/dev-manua
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the dev-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile | 13 ---
From: Timo Mueller
This target will generate eclipse help for the bsp-guide using
the bsp-guide-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile |4 +++-
1
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |6 +-
.../bsp-guide/bsp-guide-customization
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the bsp-guide. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |7 ---
1 f
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/bsp-guide/bsp-guide.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/bsp-guide/bsp-guide.xml
b/documentation/bsp-guide/bsp
From: Timo Mueller
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
---
documentation/Makefile |7 +--
.../kernel-manual/kernel-manual-cust
From: Timo Mueller
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
---
.../kernel-man
From: Timo Mueller
This target will generate eclipse help for the kernel-manual using
the kernel-manual-eclipse-customization.xsl stylesheet.
The output will be generated to a separate directory which can be used
for integrating the documentation into eclipse.
---
documentation/Makefile |4
From: Timo Mueller
The title of the document used to create metadata for output formats
such as eclipse help.
---
documentation/kernel-manual/kernel-manual.xml |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/documentation/kernel-manual/kernel-manual.xml
b/documentati
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the kernel-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |8 +---
From: Timo Mueller
Eclipse help documents are now created when calling the 'make all'
target on the poky-ref-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
---
documentation/Makefile |6 +++---
1 - 100 of 178 matches
Mail list logo
