mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-21 13:42:30 +02:00
0568568c33
The maintenance of having a streamlined standalone debugger that starts as fast as possible is no longer possible. See for example #591 - therefore when using standalone debugger, use the same sets of plug-ins/features as the product it is installed in uses. The side effect is that the standalone debugger in this use case will start slower and extra "stuff" will be present in this UI. For people just building the standalone debugger, provide a minimum feature set. This will be many more bundles than before, but should still provide a reasonably small set that starts well. This simplification also includes removing the the duplicates set of CDT docs (debug/org.eclipse.cdt.debug.application.doc). These provided a simplified version of CDT's documentation targetted at just standalone debugger. However there are a few problems related to this duplication: - The two sets of docs were not kept in sync - The standalone docs appear in the online help, leading to duplicated entries - With the config.ini changes above, there is no way to exclude the main docs in the standalone case, so remove the duplicate A number of directly related clean-ups are included too: - Remove the `ConfigGenerator.java` that stopped being referenced in PR #761 - Complete the removal of `build-standalone-debugger-rcp` profile that was started in #761. There is a small drawback to not having this profile, the standalone debugger is very slow to build compared to the rest of CDT. If this becomes a problem, restoring this profile along with the changes made in #761 is reasonable. - bring debug.product's licenses up to date - modernize command line args to eclipse when using debug.product Fixes #781 |
||
|---|---|---|
| .. | ||
| .settings | ||
| .project | ||
| debug.product | ||
| pom.xml | ||
| README | ||
This product is based on the CDT Stand-alone Debugger application found in org.eclipse.cdt.debug.application. This product can be built on its own, without the rest of the C/C++ package which makes it much smaller. It also makes it easier to use because the user only has to launch the executable after extracting the product. For example the product can be launched by simply running: ./cdtdebug -e ~/myproject/bin/a.out arg1 arg2 You can find more information about command-line options in org.eclipse.cdt.debug.application/scripts/README. Note that this product is currently only built for the more popular architecture x86_64 on Linux, Windows and Mac and aarch64 on Linux.