With this option, the build implicitly verifies that it would also
be possible to install the product (and its plugins) from that
repository.
This means that it provides some basic sanity check for plugin
dependencies.
For example, this would have uncovered the missing dependency to
launchbar.core fixed here: https://git.eclipse.org/r/65572
See
https://eclipse.org/tycho/sitedocs/tycho-p2/tycho-p2-director-plugin/materialize-products-mojo.html#source
Change-Id: I77382bb99b95784b18892cabe545c039d568ff01
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
The RCP stand-alone debugger does not have the multicore visualizer
plugins but does have the visualizer plugins. That means a user can
open the Visualizer view but nothing will display.
We could either add the multicore visualizer plugins or remove the
visualizer plugins. To follow what the stand-alone script does, this
patch removes the visualizer plugins.
Change-Id: I90075c7fc5c87f21c0b697f81c45abf1d0395218
Add Error view to both the rcp and the script.
Also update the script to include com.google.gson which is required by
cdt.core.
Change-Id: I3975420cff8c912c07949384226bfa655a1a10e3
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
This change will make it work when launching from Eclipse
This is not necessary when building as tycho resolves the dependecies
Change-Id: I914405e3a1fc43238717fd05b872584fc0c1c561
This patch creates a product so that the stand-alone can be downloaded
without
the rest of the C/C++ EPP. It also makes it easier to use because the
user only
has to launch the executable, just like a regular Eclipse instead of
finding
the script.
To try the RCP:
mvn clean package -Pbuild-standalone-debugger-rcp
The result (tar.gz) is available under
debug/org.eclipse.cdt.debug.application.product/target/products
Once extracted, it can be started just like the normal script:
./cdtdebug -e myexecutable
Change-Id: Ifb849af8a8f2ec03abcae57cf43d57cde2333759
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
