Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accurate include paths and preprocessor definitions via CMake #133

Open
letmaik opened this issue May 8, 2019 · 4 comments
Open

Accurate include paths and preprocessor definitions via CMake #133

letmaik opened this issue May 8, 2019 · 4 comments

Comments

@letmaik
Copy link
Contributor

letmaik commented May 8, 2019

The vscode CMake Tools extension talks to the C/C++ extension API to provide accurate preprocessor definitions and include paths. If vscode-fortran-support would provide a similar API then the CMake Tools extension could use it in the same way. This would avoid having to manually configure include paths etc. if CMake is used as build system.

@MuellerSeb
Copy link

Any news on this?

@machsix
Copy link
Contributor

machsix commented Sep 7, 2021

https://github.com/rizsotto/Bear

This looks like a cool tool if someone prefer Makefile

@gnikit
Copy link
Member

gnikit commented May 9, 2022

I think I should clarify what the status of this feat req is. You can have extremely accurate and functional include paths by using glob patterns. So using cmake to have accurate include paths is not that important anymore.

The circumstances that I can foresee this being the only solution are:

  • There are conflicting include files, hence using a global include would lead to linter conflicts. Although I am not sure if that is possible when you use the -fsyntax-only flag.
  • You want a plug and play experience with your build system i.e. not having to configure linter paths manually.

@renierm
Copy link

renierm commented Jun 22, 2024

The use case I have for this is a complex and always changing compile environment.

The compile environment that I'm working in, has a large set of dependencies and the versions used change often. This is all managed using multiple include paths with specific versions. It would really help if cmake information could be used to configure fortls environment.

Basically, the conflicting include file scenario.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants