[CMake] Rebuilding cmake itself on Windows

2013-04-12 Thread Paul Smith
Hi all; I need to rebuild cmake to incorporate a fix that has been added since the last release (I could get a nightly build but I was hoping to use released cmake with just the fix I need to reduce risk) and which is causing my builds to fail sometimes. For Linux and MacOS this was quite simple

Re: [CMake] Rebuilding cmake itself on Windows

2013-04-12 Thread Jean-Christophe Fillion-Robin
Hi Paul, Set option CMAKE_INSTALL_PREFIX to a location of your choice Then, build INSTALL target Hth Jc On Fri, Apr 12, 2013 at 4:46 PM, Paul Smith p...@mad-scientist.net wrote: Hi all; I need to rebuild cmake to incorporate a fix that has been added since the last release (I could get a

Re: [CMake] Rebuilding cmake itself on Windows

2013-04-12 Thread Paul Smith
On Fri, 2013-04-12 at 17:04 -0400, Jean-Christophe Fillion-Robin wrote: Hi Paul, Set option CMAKE_INSTALL_PREFIX to a location of your choice Then, build INSTALL target Hi; thanks a lot for your answer! I was able to set CMAKE_INSTALL_PREFIX; thanks for that. Can you give a specific

Re: [CMake] Rebuilding cmake itself on Windows

2013-04-12 Thread Jean-Christophe Fillion-Robin
Hi, Since the syntax can change between version of Visual Studio, you could try to use cmake directly: cd C:\path\to\project-build cmake.exe --build . --target INSTALL --config Release See http://www.cmake.org/cmake/help/v2.8.10/cmake.html#opt:--builddir Alternatively, you could also

Re: [CMake] Rebuilding cmake itself on Windows

2013-04-12 Thread Michael Jackson
I usually use: msbuild /p:Configuration=Release INSTALL.vxproj Which seems to work on VS 2010 SP1 ___ Mike JacksonPrincipal Software Engineer BlueQuartz SoftwareDayton, Ohio

Re: [CMake] Rebuilding cmake itself on Windows

2013-04-12 Thread Paul Smith
On Fri, 2013-04-12 at 18:07 -0400, Jean-Christophe Fillion-Robin wrote: Since the syntax can change between version of Visual Studio, you could try to use cmake directly: cd C:\path\to\project-build cmake.exe --build . --target INSTALL --config Release That worked perfectly; I wasn't