[lateralorange]

Great, just tried your solution, works just as you said. Thanks!

Good to know about the #error directive for printing the command line invocation, I’ll keep that in mind. I normally add:

SET(CMAKE_EXPORT_COMPILE_COMMANDS 1)

Which creates compile_commands.json, and has a list of every single gcc invocation, and can be used with other stuff like SourceTrail.

Anyways, thanks for the support, really enjoying VisualGDB 🙂

[lateralorange]

Look at the path strings. It’s complaining about \U, which appears in the second path in the screenshot. Note that the path above it is using forward slashes for the path. You just need to change your paths so that they use the forward slashes instead.

This is common with MSYS(2)/Cygwin interoperability. It’s like a hybrid between posix and Windows

[Author]

Posts