You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given a .sln file and a legacy project, a repo maintainer would not want to accept any commits with generated CMakeLists.txt files in each subfolder.
A non-invasive and potentially less time consuming would be to add an option to create a single (though large) cmake file with a possibility to override path to the source root dir. This way one could use cmake to build and customize visual-studio-based legacy project without modifying the source tree/repo/gitignore.
The text was updated successfully, but these errors were encountered:
Given a
.sln
file and a legacy project, a repo maintainer would not want to accept any commits with generatedCMakeLists.txt
files in each subfolder.A non-invasive and potentially less time consuming would be to add an option to create a single (though large) cmake file with a possibility to override path to the source root dir. This way one could use cmake to build and customize visual-studio-based legacy project without modifying the source tree/repo/gitignore.
The text was updated successfully, but these errors were encountered: