Re: [CMake] CMake Dependence on C: drive?
Thanks for the sanity check. I'm not really sure what is going wrong then. Not a big deal per se but would really like to figure out what the issue is. Maybe something funky with my PATH variable. This is on Windows 10 x64. -- Mike Jackson On Tue, Feb 19, 2019 at 7:21 PM J. Caleb Wherry wrote: > Seems strange. Just yesterday I pulled down 3.13.4 and had no issues. I > check cmake into our repo so it gets invoked on an assortment of different > drives. I do the same thing you do and just change our bat config file to > point to the new cmake binary. Never had any issues. > > I am running on Win7 but colleagues use Win10 and have not had any issues > either. > > All that to say: shouldn’t be an issue. > > -Caleb > > On Tue, Feb 19, 2019 at 5:05 PM Michael Jackson < > mike.jack...@bluequartz.net> wrote: > >> Currently using CMake 3.13.3 on Windows 10. I have “installed” cmake >> through the .zip download and placed it in E:\DREAM3D_SDK\ >> cmake-3.13.3-win64-x64. >> >> >> >> >> If I now try to use that cmake to configure my source codes I get very >> strange errors (It cannot parse a simple project command) and then >> complains that it cannot find a CMake_MAKE_PROGRAM matching the “-G Ninja”. >> >> >> >> I then went back to using the same version of CMake, but placed on the >> C:/DREAM3D_SDK/cmake-3.13.3-win64-x64 and now everything works as in the >> past, no problems. I have a .bat file that sets up my environment with >> needed paths and such. The ONLY difference between the 2 invocations was >> that I changed the path to reflect the alternate location of CMake. I can >> have 2 difference command prompts open based on this difference and one >> works and one does not. >> >> >> Was/Is there a known limitation where CMake _*must*_ be run from the C: >> drive? >> >> >> >> -- >> >> Michael Jackson | Owner, President >> >> BlueQuartz Software >> >> [e] mike.jack...@bluequartz.net >> >> [w] www.bluequartz.net >> -- > > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake Dependence on C: drive?
Seems strange. Just yesterday I pulled down 3.13.4 and had no issues. I check cmake into our repo so it gets invoked on an assortment of different drives. I do the same thing you do and just change our bat config file to point to the new cmake binary. Never had any issues. I am running on Win7 but colleagues use Win10 and have not had any issues either. All that to say: shouldn’t be an issue. -Caleb On Tue, Feb 19, 2019 at 5:05 PM Michael Jackson wrote: > Currently using CMake 3.13.3 on Windows 10. I have “installed” cmake > through the .zip download and placed it in E:\DREAM3D_SDK\ > cmake-3.13.3-win64-x64. > > > > > If I now try to use that cmake to configure my source codes I get very > strange errors (It cannot parse a simple project command) and then > complains that it cannot find a CMake_MAKE_PROGRAM matching the “-G Ninja”. > > > > I then went back to using the same version of CMake, but placed on the > C:/DREAM3D_SDK/cmake-3.13.3-win64-x64 and now everything works as in the > past, no problems. I have a .bat file that sets up my environment with > needed paths and such. The ONLY difference between the 2 invocations was > that I changed the path to reflect the alternate location of CMake. I can > have 2 difference command prompts open based on this difference and one > works and one does not. > > > Was/Is there a known limitation where CMake _*must*_ be run from the C: > drive? > > > > -- > > Michael Jackson | Owner, President > > BlueQuartz Software > > [e] mike.jack...@bluequartz.net > > [w] www.bluequartz.net > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake > -- Sent from my iPhone SE -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] CMake Dependence on C: drive?
Currently using CMake 3.13.3 on Windows 10. I have “installed” cmake through the .zip download and placed it in E:\DREAM3D_SDK\ cmake-3.13.3-win64-x64. If I now try to use that cmake to configure my source codes I get very strange errors (It cannot parse a simple project command) and then complains that it cannot find a CMake_MAKE_PROGRAM matching the “-G Ninja”. I then went back to using the same version of CMake, but placed on the C:/DREAM3D_SDK/cmake-3.13.3-win64-x64 and now everything works as in the past, no problems. I have a .bat file that sets up my environment with needed paths and such. The ONLY difference between the 2 invocations was that I changed the path to reflect the alternate location of CMake. I can have 2 difference command prompts open based on this difference and one works and one does not. Was/Is there a known limitation where CMake _must_ be run from the C: drive? -- Michael Jackson | Owner, President BlueQuartz Software [e] mike.jack...@bluequartz.net [w] www.bluequartz.net -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
