grep is needed by the "libnabo-master\CMakeLists.txt" file to find revision
But not every Windows machine have a "grep.exe" in the Windows Path. However It is available in VS typically in a set of Unix command supplied by Microsoft in
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\usr\bin\"
I did NOT want to add this to my PATH variable (may interfere with mingw), then I fix that by an ugly patch of the "libnabo-master\CMakeLists.txt"
replacing line 13
Could be good to modify "libnabo-master\CMakeLists.txt" to search for grep and use the rather generic one supplied by MS VS as alternate if none found. (BTW most of the Path is already found during the Compiler analysis phase of "Config" of CMAKE)
grep is needed by the "libnabo-master\CMakeLists.txt" file to find revision But not every Windows machine have a "grep.exe" in the Windows Path. However It is available in VS typically in a set of Unix command supplied by Microsoft in "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\usr\bin\"
I did NOT want to add this to my PATH variable (may interfere with mingw), then I fix that by an ugly patch of the "libnabo-master\CMakeLists.txt" replacing line 13
COMMAND "grep "NABO_VERSION " nabo/nabo.hby
COMMAND "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\Common7\\IDE\\CommonExtensions\\Microsoft\\TeamFoundation\\Team Explorer\\Git\\usr\\bin\\grep.exe" "NABO_VERSION " nabo/nabo.hAnd it worked fine.
Could be good to modify "libnabo-master\CMakeLists.txt" to search for grep and use the rather generic one supplied by MS VS as alternate if none found. (BTW most of the Path is already found during the Compiler analysis phase of "Config" of CMAKE)