Community
Participate
Working Groups
Unfortunately we are victim of a CDT problem (Bug 315632), where the include paths returned from the project description provider are all returned using the path format of the local machine. This really screws things up when your local machine is windows and the remote machine is *NIX. The preprocessor on the remote system gets some paths containing backslashes, and since backslash is a valid filename character, it treats it as such and looks for a big long filename full of backslashes, which of course it doesn't find. It's not a real solution, but a temporary hack-fix is to convert all backslashes to slashes before sending the paths to the remote system. This way at least the main RDT use cases of Windows->*NIX and *NIX->*NIX will work. Unfortunately, using Windows as a remote system will be busted until we have a real fix for this.
Created attachment 171112 [details] proposed patch Attached proposed patch.
I agree it's a hack, but it seems ok until someone wants to use Windows as a backend. We should specify which backend systems are supported somewhere if we don't already.
BTW this also means that using backslshes in your filenames won't work either. Thankfully, most people have the sense not to do that though.
This was committed to HEAD.
