search

microsoft / vscode-cmake-tools

CMake integration in Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=vector-of-bool.cmake-tools
MIT License
1.47k stars 451 forks source link

Fortran support #1506

Open grimgort opened 4 years ago

grimgort commented 4 years ago

choose a gcc version with kit does not impose the fortran compiler of the kit .

It take system path of gfortran

bobbrow commented 4 years ago

This extension hasn't done anything for Fortran at this point. I'm going to mark this as a feature request. Unfortunately, we won't be able to get to this immediately, but we will track the community reactions to this feature request to help us determine the priority.

apthorpe commented 3 years ago

I've had some issues on Windows finding the correct instance of gfortran and I've generally resolved them by adjusting PATH. For example, Strawberry Perl ships with a copy of gfortran; it's not part of a GCC distribution so it causes issues when compiling. I've looked into how the available kits are determined but haven't made much progress.

I'm using CMake and the CMake plugin pretty heavily with Fortran on Linux, Windows, and OSX (long story) and I'm curious if there's anything I can do to help move Fortran support forward either through research or coding.

andreeis commented 3 years ago

@apthorpe, Fortran support is not currently on our roadmap and we also don't have resources to implement this soon. If you would like to research this topic and implement such feature we will be more than happy to review and test a PR.

bilderbuchi commented 3 years ago

If someone takes a stab at this, the extension also emits "[cpptools] Unknown language: Fortran" messages (cf. #1920)

AnnanFay commented 3 years ago

Comments above make it seem as if there is a way to run CMake Tools against Fortran code by manually specifying the location of gfortran.

Can someone quickly outline the settings I need to manually change? Do I need to disable kits or make a custom kit?

github-actions[bot] commented 1 year ago

This issue is now marked as 'stale-old' due to there being no activity on it for the past 720 days. Unless the 'stale-old' label is removed or the issue is commented on, this will be remain open for at least 14 days and then it may be closed. If you would like to make this issue exempt from getting stale, please add the 'stale-exempt' label.