Troubleshooting • VS Code suddenly not recognizing *.cpp

Hi all,

Edit: Running RPi 5, 8GB, newest available Raspbian distro with everything kept up to date using apt and apt-get.

Sorry to drop in here with a problem, but I'm totally confounded. I'm using VS Code to do a bunch of cpp dev, and have maybe stupidly installed emulation station on the same machine for some fun during the down times.

Since the install, with nothing else at all changing, VS Code's build facilities no longer recognize wildcards in the cmake compile commands. I'm getting:

cc1plus: fatal error: /home/[username]/Desktop/Hex/HexEngine/*.cpp: No such file or directory

I am currently staring at an entire folder at the correct location containing several .cpp files. This used to compile just fine. If I replace the *.cpp with a singular directly referenced cpp file, it compiles that one file just fine but of course misses out on all its dependencies, as it doesn't see the other files in the same folder. Within the terminal, "ls *.cpp" indeed lists the cpp files in the folder, so it's not like the wildcard is broken in the kernel.

This is massively frustrating.

Thanks for any help you might be able to offer.

B

Statistics: Posted by Bortness — Sun Feb 25, 2024 9:14 pm — Replies 0 — Views 7

---