CLion macros have limited VCS understanding (feature request?)

Answered

We have a larger Git project, which includes several smaller and independent CMake projects. The larger project is checked out as a unit, and we then work on the smaller, embedded projects independently.

But for CLion the answer to the Universe And Everything is rooted at the spot where the CMake file is located. That makes it hard to use external tools, because one either has to pinpoint them with full hard-coded paths or try to use $ProjectFileDir + lots of ../../-stuff, since the available macros start and end with the CMake file root folder.

What would be *really* nice was VCS understanding in macros. Example: $VCSRootDir - this would give you the directory where the CMake project was anchored to the VCS of choice. Sometimes that would be the same as $ProjFileDir and sometimes not.

Since all VCS's use a folder structure with a root anchor folder, that should not be difficult to implement. Are we the only folks who thinks CVS support in macros would be a worthwhile feature?

0
1 comment

Hello!

Feel free to create a feature request in the IntelliJ platform's tracker: https://youtrack.jetbrains.com/issues/IDEA

Note that you can change project root in CLion - https://www.jetbrains.com/help/clion/change-project-root-directory.html

0

Please sign in to leave a comment.