Looks like platform 4.5 now depends on
org.eclipse.e4.core.di.annotations and some others
Change-Id: Ic7ecde8e52c825a563956ffeb1b56407f6d98325
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
(cherry picked from commit 0434220f80)
- Add a note about turning pre-processor off so edits made as part of
the tutorial are not overwritten
- Add missing ConfinedToDsfExecutor for Exercise 4
- Fix typo
Change-Id: I790fc2e3f640510a665a9a29a04f20502af7c710
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
When creating BP with dialog, make sure it starts out as
not-relocated.
Change-Id: Ia5b703315ce4a6ea55bac584097b255f08b19b17
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
The cause of the different output is a change in o.e.core.resources
where the order of visiting a project has changed to become
alphabetical. See
http://eclip.se/461838
Therefore, our benchmark files must also have the output of
subdirectories in alphabetical order.
Change-Id: I3331649cf516adbe3b453b11f1ed6733a007ce4d
or have other errors, causes several error dialogs to pop up.
Change-Id: Id5b56c2696e4911143a4daeb93cc8a442b3ebe33
Signed-off-by: Rob Stryker <rob.stryker@jboss.com>
- launch bar launch config was not handling add of another launch config
correctly - it was just resetting itself to handle new LC. This cannot
really be done because this dialog is bound to launch group and new lc
may not be part of it and may not even support the mode current dialog
is in. Also that make missyncronization between LC stored in parent and
LC stored in getTabViewer which can cause other nasty problems.
So let parent handle adding (which only handles locatio change) and for
duplication we just open a new dialog and close current one.
Change-Id: I2dde5c3af26d901d1f4b18cad84a83a9857a6ca9
Currently, CDT does not ask GDB for the value of the variables it
believes to be of complex types, such as structures. However, as
described in the bug, it assumes that a typedefed pointer is a complex
structure. Because of that, it displays a value of "{...}" for it
instead of the pointer value.
By asking GDB for the value of the variable even if it's of a complex
type, CDT will always display the right thing for the value. This will
cause a few more -var-evaluate-expression calls, but their number is
still limited to what is visible in the variables view. So the impact
should be negligible.
Screenshot of before/after:
http://i.imgur.com/Sx5ZPfO.png
It is still impossible to edit the value, but this would be addressed in
another patch.
Change-Id: I92e6ead6351677e098a56d4af5bdb85fc61df080
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
This could happen if a project was selected before creating the launch
and the project was missing a project description. For example, if the
.cproject was missing.
Change-Id: I3ecea6c4ee3cd3939c07ade361b2180fd86e6949
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Turns out to be pretty easy, just check the config for each launch
and stop the ones that match the active config.
Change-Id: Ib74a31405382b2d1996b257f7e8ad1d85a23e6c6
The TestsRunner Run launch automatically inherits the Run launch from
CDT but specifies the tabs itself. Now that we modernized the CDT Run
launch and use CMainTab2, we should do the same for TestsRunner.
Also, remove the source tab for the TestsRunner Run launch; that tab is
only for debugging.
Change-Id: I4d412787f4e937ae776f01470f4c63746589ef75
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
