Comments (4)
${fileDirname} is not a stable path, so that variable is not supported in our configurations. Currently our extension only allows for per-file configurations via compile_commands.json
and configurationProvider
.
I believe this has been requested before, but I'm not sure that we kept that issue. We could maybe detect variables like ${fileDirname} and create a hidden configuration provider for them. I'll mark this as a feature request.
from vscode-cpptools.
Ok, thanks.
just to explain a bit more: my first guess was, to write those include paths without the ${fileDirname}
variable but that didn't work either. The goal is, that the search behavior is the same as the compiler does. There I have the same include structure. So in the end it would also be sufficient for me to just write ../../h
. The extensions just needs to know that the start for all included header files is the current file.
from vscode-cpptools.
If your files all have a common parent folder, you could do: /project/commonparent/**/h
and /project/commonparent/**/incs
and we'll figure out the include paths for you.
from vscode-cpptools.
Hi,
thanks for the advice. But using /folder/**/h
slows down my whole vscode. And nothing works.
from vscode-cpptools.
Related Issues (20)
- Intellisense reports 'namespace "std" has no member' on Linux/clang-18/libc++ HOT 1
- clang-format is not executed in default terminal HOT 3
- Special cases where variables are highlighted in the color of the macro definition HOT 2
- If there are multiple functions with the same name, cannot jump from the c++ header definition to the source file implementation HOT 2
- How to let VS CODE print std::string of libc++?
- Color for CALL STACK in debugg session
- Macro incorrectly parsed HOT 5
- extension error HOT 1
- Intellisense is totally broken when I include this header file HOT 1
- Missing hyperlink to file with error HOT 1
- version 1.20.5 unable to find standard library header file. HOT 2
- It doesn't detect the libraries HOT 2
- Customize / disable context menu options
- Within a macro, IntelliSense does not suggest members of a structure that is referenced through another macro HOT 1
- Cannot build and debug because the active file is not a C or C++ source file. macos HOT 2
- C/C++ Intellisense taking too long to start up even with small workspaces HOT 2
- Implementation header included at the end of a declaration header is not processed
- Refactor P2P references for Internal Build Errors
- incorrectly formed universal character name using \u{...} HOT 1
- Debugger target command line args containing semicolon are truncated HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vscode-cpptools.