From: Timo Mueller
In case cmake reported an error during project configuration the
resulting error dialog showed a generic 'build failed' message. The
specific error message which can help the user find the problem was
hidden in cmake console.
Along with logging the cmake er
From: Timo Mueller
Until now the stream pipe was connecting one input stream with one
output stream. This for example allowed showing the output of a process
in an eclipse console. If the output is required elsewhere, e.g. in a
message dialog, the only possiblity was to read out the whole
From: Timo Mueller
This enables logging the process output to something other than a
eclipse console. e.g. a log file or string that can be reused for
dialogs and messages.
Signed-off-by: Timo Mueller
---
.../src/org/yocto/cmake/managedbuilder/job/ExecuteConfigureJob.java| 3 ++-
1 file
From: Timo Mueller
The sysroots provided by the toolchain were not added to the
CMAKE_FIND_ROOT_PATH variable. This resolved into CMake searching on the
host system breaking cross-compilation in some cases.
With the addition of the sysroot environment variables provided by
oecore, we make sure
From: Timo Mueller
Hi,
we were not considering the oecore sysroot variables provided by the
environment script when constructing the CMAKE_FIND_ROOT_PATH in the
toolchain cmake. As the other used variables do not necessarily
contain values the CMAKE_FIND_ROOT_PATH can be empty. This can lead to
From: Timo Mueller
Adding new environment variables to the list of variables that
contribute to the the CMAKE_FIND_ROOT_PATH involved manually appending
to the value string and also adding a whitespace to separate values.
The construction of the CMAKE_FIND_ROOT_PATH value is extracted to a
From: Timo Mueller
The error reported by CMake was logged to the console but not used in
any error dialog shown to the user so far.
By capturing the error in a separate stream we can use it when reproting
the error to the user.
Signed-off-by: Timo Mueller
---
.../cmake/managedbuilder/util
From: Timo Mueller
Hi,
when problems occured during configuring the project with CMake we
showed a messge dialog with a generic 'build failed' method. In
parallel the reason for the error was captured in the configuration
console. But as the dialog did not contain any note on the ex
From: Timo Mueller
CDT sets default include paths when a defined toolchain does not provide
include paths of its own. The default include paths point to the host
system which does not make sense for cross compiled projects.
Instead of using the default include paths we provide our own path that
From: Timo Mueller
The command can be used in a radio group to switch the target profile
of a selected project.
Radio items should call this command handing over the name of the
target profile as the command's parameter.
Signed-off-by: Timo Mueller
---
.../OSGI-INF/l10n/bundle.prope
From: Timo Mueller
If a project with a yocto nature is selected, the toolbar will show a
target profile menu which allows the user to switch the used target
profile of the project.
The content of this menu is dynamically created using the list of
globally defined target profiles. Additionally
From: Timo Mueller
If a project with a yocto nature is selected, the project menu will
show a target profile menu which allows the user to switch the used
target profile of the project.
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/plugin.xml | 25 +
1 file
From: Timo Mueller
Through the context of the ProjectPreferenceUtil class we can infer
that all methods act on project preferences. Having this context
information duplicated in the method name is not needed anymore and
can be removed to get a cleaner API.
Signed-off-by: Timo Mueller
From: Timo Mueller
Project specific util methods are moved to a separate util class. This
way the general util class will get more concise and other project
specific methods can be move to this new util class later.
Signed-off-by: Timo Mueller
---
.../natures
From: Timo Mueller
Move project specific methods to the new util class to allow public
usage of theses methods.
Signed-off-by: Timo Mueller
---
.../preferences/YoctoSDKProjectPropertyPage.java | 119 ++---
.../sdk/ide/utils/ProjectPreferenceUtils.java | 102
From: Timo Mueller
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java
b/plugins/org.yocto.sdk.ide/src/org
From: Timo Mueller
Hi,
Changes in v4:
- Rebase of patch series
Changes in v3:
- Only grey out project specific profile if not configured.
- Fix Bug where multiple menu item could be selected at the same time
Changes in v2:
Handle error when project specific profile is not configure more
From: Timo Mueller
On initial setup the profile form is populated with the values from
the previously selected target profile. This allows the user to
quickly make project specific adaptions of an existing profile.
Signed-off-by: Timo Mueller
---
.../sdk/ide/preferences
From: Timo Mueller
Move project specific methods to the new util class to allow public
usage of theses methods.
Signed-off-by: Timo Mueller
---
.../preferences/YoctoSDKProjectPropertyPage.java | 121 ++---
.../sdk/ide/utils/ProjectPreferenceUtils.java | 102
From: Timo Mueller
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/.options| 2 ++
.../org/yocto/sdk/ide/TargetProfileContributionItem.java | 15 ++-
2 files changed, 16 insertions(+), 1 deletion(-)
create mode 100644 plugins/org.yocto.sdk.ide
From: Timo Mueller
If a project with a yocto nature is selected, the project menu will
show a target profile menu which allows the user to switch the used
target profile of the project.
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/plugin.xml | 25 +
1 file
From: Timo Mueller
Project specific util methods are moved to a separate util class. This
way the general util class will get more concise and other project
specific methods can be move to this new util class later.
Signed-off-by: Timo Mueller
---
.../natures
From: Timo Mueller
If a project with a yocto nature is selected, the toolbar will show a
target profile menu which allows the user to switch the used target
profile of the project.
The content of this menu is dynamically created using the list of
globally defined target profiles. Additionally
From: Timo Mueller
The command can be used in a radio group to switch the target profile
of a selected project.
Radio items should call this command handing over the name of the
target profile as the command's parameter.
Signed-off-by: Timo Mueller
---
.../OSGI-INF/l10n/bundle.prope
From: Timo Mueller
Hi,
in conclusion to the previous discussion, we've agreed that the quick
switch menu will enable the user to select only configured profiles.
An unconfigured project specific profile will be shown as a greyed out
option in the menu.
There also has been a bug wher
From: Timo Mueller
Through the context of the ProjectPreferenceUtil class we can infer
that all methods act on project preferences. Having this context
information duplicated in the method name is not needed anymore and
can be removed to get a cleaner API.
Signed-off-by: Timo Mueller
From: Timo Mueller
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java
b/plugins/org.yocto.sdk.ide/src/org
From: Timo Mueller
On initial setup the profile form is populated with the values from
the previously selected target profile. This allows the user to
quickly make project specific adaptions of an existing profile.
If a project specific profile is already defined the form will show the
values
le bit more of different
> setting selections via different approaches, some of the inconsistent
> behavior can get user lost.
>
> Thanks, Jessica -Original Message- From:
> yocto-boun...@yoctoproject.org
> [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Timo Mueller
&
From: Timo Mueller
If a project with a yocto nature is selected, the toolbar will show a
target profile menu which allows the user to switch the used target
profile of the project.
The content of this menu is dynamically created using the list of
globally defined target profiles. Additionally
From: Timo Mueller
The command can be used in a radio group to switch the target profile
of a selected project.
Radio items should call this command handing over the name of the
target profile as the command's parameter.
Signed-off-by: Timo Mueller
---
.../OSGI-INF/l10n/bundle.prope
From: Timo Mueller
Move project specific methods to the new util class to allow public
usage of theses methods.
Signed-off-by: Timo Mueller
---
.../preferences/YoctoSDKProjectPropertyPage.java | 121 ++---
.../sdk/ide/utils/ProjectPreferenceUtils.java | 102
From: Timo Mueller
This changes the behaviour of the project specific profile button. If
the project specific profile is not yet defined for the selected
project, the list will contain a button to open the project
preferences instead of the greying out the button.
Signed-off-by: Timo Mueller
From: Timo Mueller
If a project with a yocto nature is selected, the project menu will
show a target profile menu which allows the user to switch the used
target profile of the project.
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/plugin.xml | 25 +
1 file
From: Timo Mueller
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java
b/plugins/org.yocto.sdk.ide/src
From: Timo Mueller
Through the context of the ProjectPreferenceUtil class we can infer
that all methods act on project preferences. Having this context
information duplicated in the method name is not needed anymore and
can be removed to get a cleaner API.
Signed-off-by: Timo Mueller
From: Timo Mueller
Changes in v2:
Handle error when project specific profile is not configured more
gracefully. Instead of showing an error message the button is now
greyed out.
Patches 01..07 contain the implementation with the greyed out menu
button.
After playing around with the two options
From: Timo Mueller
Project specific util methods are moved to a separate util class. This
way the general util class will get more concise and other project
specific methods can be move to this new util class later.
Signed-off-by: Timo Mueller
---
.../natures
From: Timo Mueller
Project specific util methods are moved to a separate util class. This
way the general util class will get more concise and other project
specific methods can be move to this new util class later.
Signed-off-by: Timo Mueller
---
.../natures
From: Timo Mueller
If a project with a yocto nature is selected, the toolbar will show a
target profile menu which allows the user to switch the used target
profile of the project.
The content of this menu is dynamically created using the list of
globally defined target profiles.
Signed-off-by
From: Timo Mueller
Move project specific methods to the new util class to allow public
usage of theses methods.
Signed-off-by: Timo Mueller
---
.../preferences/YoctoSDKProjectPropertyPage.java | 121 ++---
.../sdk/ide/utils/ProjectPreferenceUtils.java | 102
From: Timo Mueller
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java
b/plugins/org.yocto.sdk.ide/src
From: Timo Mueller
Hi,
if a user wants to change the used target profile of a project he
currently has to open the project preferences. This can be tedious if
he has to switch the profile often.
This is a small addition which allows the user to quickly switch the
used target profile of a
From: Timo Mueller
If a project with a yocto nature is selected, the project menu will
show a target profile menu which allows the user to switch the used
target profile of the project.
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/plugin.xml | 30 ++
1
From: Timo Mueller
Through the context of the ProjectPreferenceUtil class we can infer
that all methods act on project preferences. Having this context
information duplicated in the method name is not needed anymore and
can be removed to get a cleaner API.
Signed-off-by: Timo Mueller
From: Timo Mueller
The command can be used in a radio group to switch the target profile
of a selected project.
Radio items should call this command handing over the name of the
target profile as the command's parameter.
Signed-off-by: Timo Mueller
---
.../OSGI-INF/l10n/bundle.prope
From: Timo Mueller
This fixes a regression where the default profile was not changed if
the content of the UI settings were identical.
The regression was introduced with
f93aabf17df2c9a8971c4b428f67a9273c011233
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/preferences
Hi Atanas,
Am 05.03.2013 17:51, schrieb Atanas Gegov:
From: Atanas Gegov
Hi,
This patch series does some refactoring in the org.yocto.sdk.ide plugin.
The natures and the utils get their own packages. Some methods and members were
also moved to suitable classes.
What are you trying to improv
From: Timo Mueller
If the last validation resulted in an error and the user made changes
to the settings the error message is replaced by a message asking the
user to revalidate.
Signed-off-by: Timo Mueller
---
.../org/yocto/sdk/ide/YoctoSDKMessages.properties | 1 +
.../src/org/yocto/sdk
From: Timo Mueller
If the content of the YoctoUISettings changes, because a contained
widget reports a modify or selection event, an corresponding event is
triggered on the parent composite. UI elements containing the
YoctoUISettings can now register listeners and be notified when the
content
From: Timo Mueller
The layout of the parent composite is set in every yocto settings
element. Depending on the order in which the elements are added to the
composite this may lead to different layouts being used.
Layout of the composite is now set in the preference/property pages
instead of
From: Timo Mueller
If the toolchain location contains environment scripts but no target
architecture is selected show an appropriate error message.
Signed-off-by: Timo Mueller
---
.../org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoSDKChecker.java| 6 ++
.../src/org/yocto/sdk/ide
From: Timo Mueller
Hi,
these are some minor changes to improve the display of the SDK check
error messages on the property and preference pages.
The 'lifetime' of the error messages has been changed slightly. If an
SDK check failed the error message will now only be shown unti
From: Timo Mueller
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoSDKMessages.properties | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoSDKMessages.properties
b/plugins
From: Timo Mueller
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoUISetting.java| 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java
b/plugins/org.yocto.sdk.ide
From: Timo Mueller
If settings made by the user do not pass the SDK check the error
message was not shown in eclipse but was printed to system out which
was never visible by the user.
The error is now shown in the message area of the property or preference
page if the check fails.
Signed-off
From: Timo Mueller
The result of the validation did not affect the behaviour of the
method. Also an error is not reported back to the caller or the
user. Validation of the setting should be handled before setting the
input or on save.
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide
From: Timo Mueller
The message keys are now stored with the enum values simplifying the
construction of error messages.
Error messages have also been split up into a one line error message
and an advice. The one line error message can for example be used in
UI Parts with limited space (e.g
From: Timo Mueller
The class YoctoSDKChecker provided some unused code for checking a
Yocto SDK configuration. Checking of the SDK was done in
YoctoSDKUtils. An enum for results was provided in both classes (under
the same name) but contained different possible values.
To avoid confusion
From: Timo Mueller
Hi,
I tried to display the messages resulting from validating the
YoctoUISettings in the message area of the properties/preference pages
instead of showing a dialog. This led to some refactoring of the
validation functionality and also the messages.
If for example the user
From: Timo Mueller
The project property page for yocto project settings contains the same
edit buttons as the preference page. As editing profiles is not
allowed in the property page these buttons have been permanently
disabled.
This removes them completely from the property page. The remaining
From: Timo Mueller
If a cross development profile is changed that is used by projects,
the user will be warned that these projects will also be changed. If
the user accepts the affected projects are updated and are marked
"dirty". Next time the projects are built a reconfigure wi
From: Timo Mueller
Hi,
this implements two of Jessica's comments regarding the target
profiles that have been introduced recently.
01..02: Small cleanup work
03: Changes the name of target profiles to cross development
profiles
04..05: If a global profile is updated this will
From: Timo Mueller
This adds hashCode and equals methods generated by Eclipse to allow
comparison of two UIElements.
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoUIElement.java | 58 ++
1 file changed, 58 insertions(+)
diff --git
a/plugins
From: Timo Mueller
Signed-off-by: Timo Mueller
---
.gitignore | 1 +
1 file changed, 1 insertion(+)
create mode 100644 .gitignore
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000..ba077a4
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+bin
--
1.7.11.7
From: Timo Mueller
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java
b/plugins/org.yocto.sdk.ide/src
From: Timo Mueller
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoSDKMessages.properties | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoSDKMessages.properties
b/plugins
From: Timo Mueller
UI elements are added to the project properties in order to use
profile capabilites with a project.
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoProfileSetting.java | 3 +
.../yocto/sdk/ide/YoctoProjectSpecificSetting.java | 9 +++
.../preferences
From: Timo Mueller
If a target profile is modified, renamed or deleted globally the
projects using this profile are updated accordingly.
On deletion of a target profile the affected projects will set use the
standard target profile.
Signed-off-by: Timo Mueller
---
.../org/yocto/sdk/ide
From: Timo Mueller
Until now only global target profiles could be used to configure a
project. Now a project can have its own specific settings which are
not affected by global changes to the profile.
Signed-off-by: Timo Mueller
---
.../yocto/sdk/ide/YoctoProjectSpecificSetting.java | 80
From: Timo Mueller
The added functions allow storing the yocto settings in the
preferences store of a project. Project-specific yocto settings as
well as the used profiles can be stored.
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoSDKUtils.java | 110
From: Timo Mueller
Signed-off-by: Timo Mueller
---
.../org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoSDKProjectNature.java | 1 +
1 file changed, 1 insertion(+)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoSDKProjectNature.java
b/plugins/org.yocto.sdk.ide/src/org
From: Timo Mueller
Hi,
this patch set enables projects to make use of the target profiles
proposed in "[RFC v4 00/17][eclipse-poky] Storing yocto settings as
target profiles".
Currently the target profiles are only used to determine the
default settings when creating a new project
From: Timo Mueller
The preference page is now aware of profiles. By default the standard
profile is used and the values are stored to its preference store. If
a different profile is selected it's preferences store is used
instead.
Signed-off-by: Timo Mueller
---
.../ide/prefer
From: Timo Mueller
Adds the UI elements that allow managing profiles to the preference
page.
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/preferences/YoctoSDKPreferencePage.java | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
a/plugins/org.yocto.sdk.ide
From: Timo Mueller
Deletion of a profile currently has no effects on the preference
page.
Signed-off-by: Timo Mueller
---
.../org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoProfileSetting.java | 4
1 file changed, 4 insertions(+)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk
From: Timo Mueller
When renaming a profile the current values are stored in the profile's
new preference store.
Signed-off-by: Timo Mueller
---
.../org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoProfileSetting.java | 4
1 file changed, 4 insertions(+)
diff --git
a/pl
From: Timo Mueller
A profile is removed from the list, when the delete button is
clicked. The deletion has to be confirmed by the user. Deleting the
standard profile is not allowed.
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoProfileSetting.java | 34
From: Timo Mueller
When switching profile the values of the profile are retrieved from
the preference store. The UI is updated using the retrieved values.
Signed-off-by: Timo Mueller
---
.../org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoProfileSetting.java | 4
1 file changed, 4
From: Timo Mueller
When the rename button is clicked a dialog shows up and the user has
to provide the new name for the profile. The validity of the name is
checked during input. If the name is valid and the users confirms the
profile is renamed. Renaming the standard profile is not allowed
From: Timo Mueller
YoctoUIElement should always be the first element, e.g. as in
saveElemToStore().
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoSDKUtils.java | 2 +-
.../src/org/yocto/sdk/ide/preferences/YoctoSDKProjectPropertyPage.java | 2 +-
2
From: Timo Mueller
When the save as button is clicked a dialog shows up and the user has
to provide the name of the new profile. The validity of the name is
checked during input. If the name is valid and the users confirms the
new profile is created from the current input of the yocto settings
From: Timo Mueller
Yocto preferences are now stored using a user-defined name that
identifies a target profile. To store these preferences eclipse'
scoped preferences provider is used. The filename in the eclipse
configuration area is derived from the unique target profile name.
Signed-o
From: Timo Mueller
The added method calls the performOK method on the provided preference
page to store the current content of the page.
This callback is needed so the profile UI is able to propagate changes
to the preference page it is part of.
Signed-off-by: Timo Mueller
---
.../src/org
From: Atanas Gegov
A target profile is a combination of yocto settings identified by a
user-defined name. This UI element allows the user to add new profiles
and to rename or delete existing ones.
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoProfileElement.java | 104
From: Timo Mueller
When a profile is selected through the combo box the value of the
profileElement changed to contain the selected profile.
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoProfileSetting.java | 23 ++
1 file changed, 23 insertions(+)
diff
From: Atanas Gegov
The value of the target array set in the constructor is now also
affected when the input of the element is changed.
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java | 2 ++
1 file changed, 2 insertions(+)
diff --git
a
From: Atanas Gegov
The YoctoUISetting form as a whole can be disabled and enabled using
this method. A disabled form can for example show a read-only yocto
configuration.
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoUISetting.java | 44 ++
1 file
From: Timo Mueller
Hi,
I removed the last patch that was moving the "Save as ..." button to
the bottom. So now it is located beneath the dropdown box. I also
changed the message in the profile deletion dialog to only ask if the
user really wants to delete the profile.
>From RFC
From: Atanas Gegov
Extracting the labels as private members allows the modification of
the label settings after creation. This is will allow disabling and
enabling the labels after creation of the form.
Signed-off-by: Timo Mueller
---
.../src/org/yocto/sdk/ide/YoctoUISetting.java
From: Timo Mueller
The dialog has been merged with the project settings. Therefor the
message is no longer needed.
Signed-off-by: Timo Mueller
---
.../org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoSDKMessages.properties | 1 -
1 file changed, 1 deletion(-)
diff --git
a/plugins
From: Timo Mueller
The separate yocto manuals are added to the table of contents to
prepare their inclusion into the plugin.
Signed-off-by: Timo Mueller
---
plugins/org.yocto.doc.user/plugin.xml | 28
plugins/org.yocto.doc.user/toc.xml| 21
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.
Signed-off-by: Timo Mueller
---
scripts/generate-doc.sh | 85
From: Timo Mueller
Signed-off-by: Timo Mueller
---
scripts/build.sh | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/scripts/build.sh b/scripts/build.sh
index e1ec5fc..73bf889 100755
--- a/scripts/build.sh
+++ b/scripts/build.sh
@@ -132,10 +132,14 @@ cd ${TOP
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.
Signed-off-by: Timo Mueller
---
scripts/build.sh | 7 +++
1 file changed, 7 insertions(+)
diff --git a/scripts/build.sh b/scripts
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.
Signed-off-by: Timo Mueller
---
scripts/generate-doc.sh | 2 ++
1 file changed, 2 insertions(+)
diff --git a/scripts/generate-doc.sh b/scripts
From: Timo Mueller
Signed-off-by: Timo Mueller
---
features/org.yocto.doc.headless.build/.project | 11 +
.../org.yocto.doc.headless.build/build.properties | 262 +
.../org.yocto.doc.headless.build/customTargets.xml | 212 +
3 files changed, 485
From: Timo Mueller
Signed-off-by: Timo Mueller
---
features/org.yocto.doc/.project | 17
features/org.yocto.doc/build.properties | 3 +
features/org.yocto.doc/feature.properties | 163 ++
features/org.yocto.doc/feature.xml| 35
From: Timo Mueller
Signed-off-by: Timo Mueller
---
features/org.yocto.sdk.site/category.xml | 4
features/org.yocto.sdk.site/site.xml | 4
2 files changed, 8 insertions(+)
diff --git a/features/org.yocto.sdk.site/category.xml
b/features/org.yocto.sdk.site/category.xml
index
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.
Signed-off-by: Timo Mueller
---
plugins/org.yocto.doc.user/about.html.in| 189
1 - 100 of 202 matches
Mail list logo
