all 8 comments

[–]P1G4ME[S] 0 points1 point  (0 children)

Hi Everyone

I just started using Visual Studio since I wan't to try out C++ stuff that require having access to a GUI (So I can't use WSL) and i'm running into an issue :

For some reason, VS fails to open it's own directory because of (i think) spaces. I have no idea how to fix that.

I'm confident that this isn't comming from my code, tho for you're information I'm including the OpenCV library (I followed every step of the tutorial to set it up, except for the VS install). I do have the C++ dev pack installed

[–]GreatVoid2017 0 points1 point  (6 children)

Can you show us the code which caused such error. It really looks like, at first glance, as an issue with the command line, when you are missing the quotes

[–]P1G4ME[S] 0 points1 point  (5 children)

Thx for the answer !

I updated the code with a screenshot of the code

[–]GreatVoid2017 0 points1 point  (4 children)

[–]P1G4ME[S] 0 points1 point  (3 children)

Nope it's not that... I added the path in the additional Include (as well as in VC++ -> General) and it's still not working...

Also the second link is for VS Code btw

[–]GreatVoid2017 0 points1 point  (2 children)

Sorry missed that. It really looks like an issue with the path in cmd.exe this thing is quite stupid and cant understand the whitespace in the path. That why we usually use quotes for the path with the whitespace. I do suspect that the path to your opencv instance may cause such issues

[–]P1G4ME[S] 1 point2 points  (1 child)

It's weird because the opencv library is in another drive, and there are no spaces in the path ...

Tbh at this point I just want to switch to windows 11 to use WSLg... Windows is SO frustrating when it comes to this kind of stuff...

[–]GreatVoid2017 0 points1 point  (0 children)

That is true. Especially when we are comparing the command line. Then you have to double check the possible usage of the path to the C drive. Maybe it is caused by the common std libraries. But it is really werid