Open
Description
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.
Activity
MuellerSeb commentedon Apr 22, 2020
Any news on this?
machsix commentedon Sep 7, 2021
https://github.com/rizsotto/Bear
This looks like a cool tool if someone prefer Makefile
gnikit commentedon 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:
-fsyntax-only
flag.compile_commands.json
from cmake #668renierm commentedon 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.