Also fix version numbers in all bundles who's binary contents have
changed despite no change in the source of the bundle.
Change-Id: Ic67b79aafa801c7ce96c5e52843ad5c881827d84
The previous alignment of all the warnings/ignores
led to too many warnings that weren't there before. This
commit relaxes them a bit.
The core/org.eclipse.cdt.core/.settings/org.eclipse.jdt.core.prefs
is still the "master" copy, with
releng/scripts/check_code_cleanliness.sh containing the
exceptions that apply to test plug-ins.
Change-Id: Ibd4e31ade0b42b31e7cbe5a94f06c6fc15183a56
The releng/scripts/apply_jdt_prefs_to_all_projects.sh was run to
copy standard settings to all other projects.
Change-Id: I4436c947d7f0142f56b709e661379c3eb54f666b
There is also a new script to verify completeness of .gitattributes:
releng/scripts/verify_gitattributes.sh
Change-Id: I2ce270852ab54b66b6c474a6ec94203fe5bba78b
I used a simple script:
for every file name of a given extension {
grep for the file name usage
if no result {
delete it!
}
}
I only deleted things under the documentation plugins, to be safe.
This results in about 8MB of deleted images.
Change-Id: I566b8b1ff396b67689d273fc6e827dd3a02ad991
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
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>
Building documentation can take several minutes and is often not necessary.
I suggest that we leave it on by default so that people building locally
still get a full, consistent build of CDT but that it should be possible to
skip it on demand.
My build time went from 4:14s to 1:45s (without running tests).
Change-Id: Ic7c4535f3faf82080534d39ccbe6f452d8b52317
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
- allow pid to be specified following -a option for Standalone debugger
- if pid is specified, use it to set the ATTR_ATTACH_PROCESS_ID
setting for the launch configuration
- setting the pid will cause the process dialog not to appear and
the debugger will attempt to debug the given process
- an invalid pid will result in in the dialog being opened
- the pid is not used with the -r option and is ignored
- updated the README file and docs
Change-Id: I5a1d39f97285ad41dcb986dfb4692f9d808bafeb
Change-Id: Ifcbfd598d90305ac24bddf96893d4170201858c9
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/36700
Tested-by: Hudson CI
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
Tested-by: Jeff Johnston <jjohnstn@redhat.com>
Change-Id: I8cda245f8bc34b21e3088de561442982b86f05ef
Reviewed-on: https://git.eclipse.org/r/30540
Tested-by: Hudson CI
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
Tested-by: Jeff Johnston <jjohnstn@redhat.com>
- add org.eclipse.cdt.debug.application plugin which supports running
CDT debugger as Eclipse application
- add org.eclipse.cdt.debug.application.docs plugin which is the
modified
CDT docs
- add org.eclipse.cdt.debug.standalone-feature which bundles the
two aforementioned plugins
- add org.eclipse.cdt.debug.standlone.source-feature
Change-Id: I1a1ae855ab3912e678b7d9e3465e2fbbfe949e13
Reviewed-on: https://git.eclipse.org/r/25845
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
Tested-by: Jeff Johnston <jjohnstn@redhat.com>
