cdt/debug/org.eclipse.cdt.debug.dap/BuildDebugServers.xml

<?xml version="1.0" encoding="UTF-8"?>
<project default="BuildDebugServers">
	<!-- Wrap running yarn in an ant task so that we don't have to specify absolute path to yarn in external tool builder. -->
	<target name="BuildDebugServers" description="Build the Node Debug Servers with yarn">
		<!-- Don't upgrade on each build - TODO determine better way to keep this bundle up to date, in the meantime
			the upgrading is a manual process when and if needed, and is
			part of https://github.com/eclipse-cdt/cdt-infra/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Aendgame
		-->
		<!-- <exec executable="yarn" dir="./debug-servers" failifexecutionfails="true">
			<arg value="upgrade"/>
			<arg value="cdt-gdb-adapter"/>
		</exec> -->
		<exec executable="yarn" dir="./debug-servers" failifexecutionfails="true" />
	</target>
</project>
Bug 542488: Initial/rudimentary version of DAP integration README: Create a C/C++ Application launch as normal, and in the Launch Configuration dialog click "Select other..." at the bottom/center and selecting GDB (DAP) Debug Process Launcher (you can't do this in the LaunchBar's dialog as it does not support changing the launcher). Then debug as you normally do (with less features so far :-) Change-Id: Ia36acedf064b3774c6ac2a863880eaf7efe9c399 2019-01-04 12:49:36 +00:00			`<?xml version="1.0" encoding="UTF-8"?>`
			`<project default="BuildDebugServers">`
			`<!-- Wrap running yarn in an ant task so that we don't have to specify absolute path to yarn in external tool builder. -->`
			`<target name="BuildDebugServers" description="Build the Node Debug Servers with yarn">`
[releng] Manually upgrade cdt-gdb-adapter from now on The upgrade is one of the steps of the endgame plan, or it can be done manually when needed. Change-Id: I9ec83b65015474a08099e294bd168105a5bdcbe7 2020-01-06 20:48:20 -05:00			`<!-- Don't upgrade on each build - TODO determine better way to keep this bundle up to date, in the meantime`
			`the upgrading is a manual process when and if needed, and is`
			`part of https://github.com/eclipse-cdt/cdt-infra/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Aendgame`
			`-->`
			`<!-- <exec executable="yarn" dir="./debug-servers" failifexecutionfails="true">`
Bug 542488: JTAG debug support based on DAP remote debugging Change-Id: I035ca6341b8e1dc7273f53da80eb281d7b5e59d4 2019-08-03 11:17:58 -04:00			`<arg value="upgrade"/>`
			`<arg value="cdt-gdb-adapter"/>`
[releng] Manually upgrade cdt-gdb-adapter from now on The upgrade is one of the steps of the endgame plan, or it can be done manually when needed. Change-Id: I9ec83b65015474a08099e294bd168105a5bdcbe7 2020-01-06 20:48:20 -05:00			`</exec> -->`
Bug 542488: Initial/rudimentary version of DAP integration README: Create a C/C++ Application launch as normal, and in the Launch Configuration dialog click "Select other..." at the bottom/center and selecting GDB (DAP) Debug Process Launcher (you can't do this in the LaunchBar's dialog as it does not support changing the launcher). Then debug as you normally do (with less features so far :-) Change-Id: Ia36acedf064b3774c6ac2a863880eaf7efe9c399 2019-01-04 12:49:36 +00:00			`<exec executable="yarn" dir="./debug-servers" failifexecutionfails="true" />`
			`</target>`
			`</project>`