cubepilot_cubeorange does not configure & build properly in VSCode GUI

[Ionstream]

When selecting build targets in VSCode GUI, cubepilot_cubeorange target points to cubepilot_cubeorange_test. Current workaround is to call make cubepilot_cubeorange directly in terminal.

[hamishwillee]

FYI, when this get fixed we can remove the note I put in for tracking in PX4/PX4-user_guide@9775c2c

[dagar]

This is because cubepilot_cubeorange_test includes the serial console which many people use while debugging.

You can change this to cubepilot_cubeorange_default if that's what you prefer.

cubepilot_cubeorange_test = cubepilot_cubeorange_default + serial console + test material

[Ionstream]

Ah, that explains it. The orange cube does not expose it's debug port without some disassembly and a special cable, so I guess that's where my efforts went wrong. Thanks for the clarification!

That said, I do have trouble with the build configuration when attempting to build cubepilot_cubeorange_test. Is there anything I'm missing here?

[cmake] Configuring incomplete, errors occurred!
[cms-driver] Error during CMake configure: 
	Error: Configuration failed.
	at CMakeServerClient._onMessage (/home/ionstream/.vscode/extensions/ms-vscode.cmake-tools-1.7.3/dist/main.js:44271:33)
	at CMakeServerClient._onMoreData (/home/ionstream/.vscode/extensions/ms-vscode.cmake-tools-1.7.3/dist/main.js:44244:18)
	at Socket.emit (events.js:315:20)
	at addChunk (internal/streams/readable.js:309:12)
	at readableAddChunk (internal/streams/readable.js:284:9)
	at Socket.Readable.push (internal/streams/readable.js:223:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)

[dagar]

I don't think that error means much. Try wiping the build directory (or make distclean), then freshly open vscode and click on the cubepilot variant (on the blue bar) to initiate the cmake configure.