[CMake] Issues with VS2005 Pro, CMake 2.4.8, Win XP, ParaView

Mike Jackson imikejackson at gmail.com
Fri May 23 10:53:21 EDT 2008


Well my last email was wrong about 2003.net. I forgot to tell CMake to
use the 2003.net generator and so got a wrong message. After clearing
everything out and trying again, this time using a VS2003.Net command
prompt and telling cmake to use the Visual Studio 2003.Net generator I
can get a valid project made.

Also, to embellish on my last email, I used the dependencywalker
utility to discover that the MSVCR80.dll could not be found. I don't
really know where to look for it either. (VS Newbie)..

Mike

On Fri, May 23, 2008 at 10:46 AM, David Cole <david.cole at kitware.com> wrote:
> c0000135 is the "unable to locate dll" exception, not c0150004...
>
> I could not find what c0150004 means using google, although apparently it
> occurs frequently to people with Vista when it tries to do automatic
> updating.... :-P
>
> I suspect if you can run it under the debugger, you might be able to catch
> the exception and determine where it is coming from. (See Visual Studio's
> exception dialog in the GUI via the "Debug > Exceptions..." menu.)
>
>
> HTH,
> David
>
>
> On Fri, May 23, 2008 at 10:28 AM, Bill Hoffman <bill.hoffman at kitware.com>
> wrote:
>>
>> Mike Jackson wrote:
>>>
>>> Here ya go.. Hope this helps.
>>>
>>
>>
>> OK, so the error log has this:
>>
>> Determining the endianes of the system passed. The system is big
>> endianTest produced following output:
>> Microsoft (R) Visual Studio Version 8.0.50727.42.
>> Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
>> ------ Build started: Project: cmTryCompileExec, Configuration: Debug
>> Win32 ------
>> Compiling...
>> Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for
>> 80x8
>> Copyright (C) Microsoft Corporation.  All rights reserved.
>> cl /Od /D "WIN32" /D "_WINDOWS" /D "_DEBUG" /D "CMAKE_INTDIR=\"Debug\"" /D
>> "_MBCS" /FD /EHsc /RTC1 /MDd /Fo"cmTryCompileExec.dir\Debug\\"
>> /Fd"D:/workspace/ParaView3/vs2005/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.pdb"
>> /W3 /c /Zi /TC   /Zm1000
>>
>> "..\..\..\..\..\Applications\CMake_2.4.8\share\cmake-2.4\Modules\TestBigEndian.c"
>> TestBigEndian.c
>> Compiling manifest to resources...
>> Linking...
>> Embedding manifest...
>> Build log was saved at
>> "file://d:\workspace\ParaView3\vs2005\CMakeFiles\CMakeTmp\cmTryCompileExec.dir\Debug\BuildLog.htm"
>> cmTryCompileExec - 0 error(s), 0 warning(s)
>> ========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped
>> ==========
>> Exit code 0xc0150004
>>
>> So, cmTryCompileExec builds just fine.  When CMake tries to run it, it
>> gets an Exit code 0xc0150004.  I think that means that it can not find a
>> dll.
>>
>> I would recommend cmake --debug-trycompile on a simple project:
>>
>> project(foo C)
>> include(TestBigEndian)
>> TEST_BIG_ENDIAN(TEST_BIG)
>>
>> Run cmake once on this without --debug-trycompile.  Then delete the
>> TEST_BIG stuff from the CMakeCache.txt, and re-run cmake on the project with
>> --debug-trycompile.  This will leave cmTryCompileExec.exe on your disk and
>> you can try to run it.
>>
>> You may want to try this tool: http://www.dependencywalker.com/
>>
>> It will help figure out what dll's are missing.
>>
>> -Bill
>>
>>
>> _______________________________________________
>> CMake mailing list
>> CMake at cmake.org
>> http://www.cmake.org/mailman/listinfo/cmake
>
>



-- 
Mike Jackson
imikejackson _at_ gee-mail dot com


More information about the CMake mailing list