<div dir="ltr">"The environment is setup with a cmd called "run CMake.cmd" and attached with the extension 'cmd' changed to 'ceemde'<br><br>"Where is the source code" =./ is assuming the directory from where I run CMakeSetup as the working directory. Causes the error dialog<br>
---------------------------<br>Error<br>---------------------------<br>CMake Error: The source directory "./build/CMakeFiles/CMakeTmp" does not exist.<br>Specify --help for usage, or press the help button on the CMake GUI.<br>
<br>(Press Cancel to suppress any further messages.)<br>---------------------------<br>OK Cancel <br>---------------------------<br><br><br>Does not make a "Visual Studio 9 2008 Win64". The folder does exist relative from my working directory "C:\OpenGL\OpenSceneGraph\trunk". But not from the cmake directory "C:\OpenGL\cmake-2.6.1-win32-x86\bin"<br>
<br>By putting in the full path for "Where is the source code" = "C:\OpenGL\OpenSceneGraph\trunk" the CMakeSetup goes further. Then I run into the issue of using "C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/bin/amd64/cl.exe" as the compiler and linker for a 64 bit machine and the following error dialog appears:<br>
<br>=====Error Dialog========<br>---------------------------<br>Error<br>---------------------------<br>CMake Error at C:/OpenGL/cmake-2.6.1-win32-x86/share/cmake-2.6/Modules/CMakeTestCCompiler.cmake:32 (MESSAGE):<br> The C compiler "C:/Program Files (x86)/Microsoft Visual Studio<br>
9.0/VC/bin/amd64/cl.exe" is not able to compile a simple test program.<br><br> It fails with the following output:<br><br> Change Dir: C:/OpenGL/OpenSceneGraph/trunk/build/CMakeFiles/CMakeTmp<br><br> <br><br> Run Build Command:C:\PROGRA~2\MICROS~1.0\Common7\IDE\VCExpress.exe<br>
CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec<br><br> <br><br><br> Microsoft (R) Visual C++ Express Edition Version 9.0.30729.1.<br><br><br> Copyright (C) Microsoft Corp 2007. All rights reserved.<br>
<br><br> <br><br><br> The project consists entirely of configurations that require support for<br> platforms which are not installed on this machine. The project cannot be<br> loaded.<br><br><br> The project consists entirely of configurations that require support for<br>
platforms which are not installed on this machine. The project cannot be<br> loaded.<br><br><br> Invalid project<br><br><br> <br><br><br> Use:<br><br><br> vcexpress [solutionfile | projectfile | anyfile.ext] [switches]<br>
<br><br> <br><br><br> The first argument for devenv is usually a solution file or project file.<br><br><br> You can also use any other file as the first argument if you want to have<br> the<br><br><br> file open automatically in an editor. When you enter a project file, the<br>
IDE<br><br><br> looks for an .sln file with the same base name as the project file in the<br><br><br> parent directory for the project file. If no such .sln file exists, then<br> the<br><br><br> IDE looks for a single .sln file that references the project. If no such<br>
single<br><br><br> .sln file exists, then the IDE creates an unsaved solution with a default<br> .sln<br><br><br> file name that has the same base name as the project file.<br><br><br> <br><br><br> Command line builds:<br>
<br><br> devenv solutionfile.sln /build [ solutionconfig ] [ /project<br> projectnameorfile [ /projectconfig name ] ]<br><br><br> Available command line switches:<br><br><br> <br><br><br> /Log Logs IDE activity to the specified file for troubleshooting.<br>
<br><br> /ResetSettings Restores the IDE's default settings, optionally resets to<br><br><br> the specified VSSettings file.<br><br><br> /SafeMode Launches the IDE in safe mode loading minimal windows.<br>
<br><br> <br><br><br> Product-specific switches:<br><br><br> <br><br><br> /debugexe Open the specified executable to be debugged. The<br><br><br> remainder of the command line is passed to this<br><br><br>
executable as its arguments.<br><br><br> /useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variables<br><br><br> instead of IDE paths for VC++ builds.<br><br><br> <br><br><br> To attach the debugger from the command line, use:<br>
<br><br> VsJITDebugger.exe -p <pid><br><br><br> <br><br> <br><br> CMake will not be able to correctly generate this project.<br>Call Stack (most recent call first):<br> CMakeLists.txt:30 (PROJECT)<br><br><br>
<br>(Press Cancel to suppress any further messages.)<br>---------------------------<br>OK Cancel <br>---------------------------<br>===========<br><br><div class="gmail_quote">On Tue, Sep 23, 2008 at 5:07 PM, Bill Hoffman <span dir="ltr"><<a href="mailto:bill.hoffman@kitware.com">bill.hoffman@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">Roger Martin wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Setting the full path fixes it. I'm wondering, on relative paths, if the cmake home/bin directory is the root.<br>
<br>
Yes, ./ is the current directory of the project from where I run a cmd script.<br>
<br>
------------<br>
With the paths fixed as you pointed out, I then get an error dialog with ...<br>
The C compiler "C:/Program Files (x86)/Microsoft Visual Studio<br>
9.0/VC/bin/amd64/cl.exe" is not able to compile a simple test program.<br>
...<br>
But by hand-build-environment, I can compile and link a 64 bit program with cl.exe and the Windows SDK<br>
<br>
I use Netbeans and Visual C++ 2008 Express IDE's.<br>
<br>
But for some complex projects such as <a href="http://www.openscenegraph.org" target="_blank">http://www.openscenegraph.org</a> CMake is the right tool.<br>
<br>
</blockquote>
<br></div>
I am still not quite following what works for you and what does not work for you. Can you describe when the ./ does not work and what steps you take?<br>
<br>
Also, for the compiler not working, can you give the full error message? If possible send the CMakeCache.txt and the CMakeFiles/CMakeOutput.log and CMakeFiles/CMakeError.log files.<br>
<br>
You do have to run CMake from an environment that works. So, running CMakeSetup from the start menu may cause trouble if the global PATH and env is not correct.<br><font color="#888888">
<br>
-Bill<br>
</font></blockquote></div><br></div>