Torbjörn Svensson 5654112209 Bug 572759: Allow debugging binaries with project relative path ... In some situations, it makes sense to have a build structure parallel with the source tree, and it this case, the build results may not be part of the resources visible in the Eclipse workspace. Current implementation allows absolute paths to the binary to debug. While it works, it's a cumbersome way to handle the above situation. By resolving the relative path outside of Eclipse scope allows to point to files that are not part of the Eclipse workspace, allthough the path is relative to a project in the workspace. Contributed by STMicroelectronics Change-Id: I284a5dad61e692dae4029e5f142d23d8cda98ed0 Signed-off-by: Torbjörn Svensson <torbjorn.svensson@st.com>		2021-04-11 16:07:16 +02:00
..
org.eclipse.cdt.docker.launcher	Bug 572552 - CDT releng: update versions to 10.3.0	2021-04-04 16:17:25 -04:00
org.eclipse.cdt.docker.launcher-feature	Bug 572552 - CDT releng: update versions to 10.3.0	2021-04-04 16:17:25 -04:00
org.eclipse.cdt.flatpak.launcher	[releng] Fix case where copyright year end == start	2021-01-15 21:52:03 -05:00
org.eclipse.cdt.flatpak.launcher-feature	Bug 572552 - CDT releng: update versions to 10.3.0	2021-04-04 16:17:25 -04:00
org.eclipse.cdt.launch	Bug 572759: Allow debugging binaries with project relative path	2021-04-11 16:07:16 +02:00
pom.xml	Bug 572552 - CDT releng: update versions to 10.3.0	2021-04-04 16:17:25 -04:00