maybe remove your CMakeCache.txt

Laurent

Le 19 mars 2011 à 00:46, Veljko Milisavljević a écrit :

> Hm, funny , now I have the same error,although rc and cl are in path:
> 
> c:\qutecom\qutecom-2.2>cmake -DCMAKE_BUILD_TYPE=Debug -G "NMake Makefiles"
> -- The C compiler identification is MSVC
> -- The CXX compiler identification is MSVC
> CMake Error: your RC compiler: "CMAKE_RC_COMPILER-NOTFOUND" was not found.   
> Please set CMAKE_RC_COMPILER to a valid compiler pa
> th or name.
> -- Using FREE VC TOOLS, NO DEBUG available
> -- Check for working C compiler: C:/Program Files/Microsoft Visual Studio 
> 8/VC/bin/cl.exe
> CMake Error: your RC compiler: "CMAKE_RC_COMPILER-NOTFOUND" was not found.   
> Please set CMAKE_RC_COMPILER to a valid compiler pa
> th or name.
> CMake Error: Internal CMake error, TryCompile configure of cmake failed
> -- Check for working C compiler: C:/Program Files/Microsoft Visual Studio 
> 8/VC/bin/cl.exe -- broken
> CMake Error at C:/Program Files/CMake 
> 2.6/share/cmake-2.6/Modules/CMakeTestCCompiler.cmake:32 (MESSAGE):
>   The C compiler "C:/Program Files/Microsoft Visual Studio 8/VC/bin/cl.exe"
>   is not able to compile a simple test program.
> 
>   It fails with the following output:
> 
> 
> 
> 
> 
>   CMake will not be able to correctly generate this project.
> Call Stack (most recent call first):
>   CMakeLists-owbuild.txt:3 (project)
>   CMakeLists.txt:1 (include)
> 
> 
> -- Configuring done
> 
> c:\qutecom\qutecom-2.2>cl
> Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for 
> 80x86
> Copyright (C) Microsoft Corporation.  All rights reserved.
> 
> usage: cl [ option... ] filename... [ /link linkoption... ]
> 
> c:\qutecom\qutecom-2.2>rc
> fatal error RC1107: invalid usage; use RC /? for Help
> 
> 2011/3/19 Laurent Tarrisse <laur...@mbdsys.com>
> Yes, it is the issue
> 
> hg clone http://hg.qutecom.org/qutecom-2.2 
> 
> Laurent
> 
> Le 19 mars 2011 à 00:17, Veljko Milisavljević a écrit :
> 
>> I have it already.
>> I am trying to build the stable release taken from: 
>> http://www.qutecom.org/downloads/QuteCom-2.2.tar.gz
>> It doesn't have a .hg folder inside. Maybe that is the issue.
>> 
>> 
>> 2011/3/19 Laurent Tarrisse <laur...@mbdsys.com>
>> install or/and mercurial to your path
>> 
>> Laurent
>> 
>> Le 19 mars 2011 à 00:09, Veljko Milisavljević a écrit :
>> 
>>> This time it was better:
>>> 
>>> 
>>> c:\qutecom\debug>build
>>> 
>>> c:\qutecom\debug>cmake -DCMAKE_BUILD_TYPE=Debug -G "NMake Makefiles"
>>> -- The C compiler identification is MSVC
>>> -- The CXX compiler identification is MSVC
>>> -- Check for CL compiler version
>>> -- Check for CL compiler version - 1400
>>> -- Check if this is a free VC compiler
>>> -- Check if this is a free VC compiler - no
>>> -- Check CL platform
>>> -- Check CL platform - 32 bit
>>> -- Check for working C compiler: C:/Program Files/Microsoft Visual Studio 
>>> 8/VC/bin/cl.exe
>>> -- Check for working C compiler: C:/Program Files/Microsoft Visual Studio 
>>> 8/VC/bin/cl.exe -- works
>>> -- Detecting C compiler ABI info
>>> -- Detecting C compiler ABI info - done
>>> -- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio 
>>> 8/VC/bin/cl.exe
>>> -- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio 
>>> 8/VC/bin/cl.exe -- works
>>> -- Detecting CXX compiler ABI info
>>> -- Detecting CXX compiler ABI info - done
>>> -- Found Mercurial (hg): C:/Program Files/TortoiseHg/hg.exe
>>> abort: there is no Mercurial repository here (.hg not found)
>>> CMake Error at owbuild/owbuild/OWEnsureOutOfSourceBuild.cmake:18 (message):
>>>   A separate build directory is required, please create one and run cmake
>>>   from this directory
>>> Call Stack (most recent call first):
>>>   CMakeLists-owbuild.txt:16 (ow_ensure_out_of_source_build)
>>>   CMakeLists.txt:1 (include)
>>> 
>>> 
>>> -- Configuring done
>>> 
>>> 2011/3/18 Laurent Tarrisse <laur...@mbdsys.com>
>>> Try this :
>>> 
>>> Create a folder qutecom-2.2/debug/
>>> cd qutecom-2.2/debug/
>>> 
>>> cmake .. -G "NMake Makefiles"
>>> 
>>> (do not add other define)
>>> 
>>> Laurent
>>> 
>>> Le 18 mars 2011 à 23:54, Veljko Milisavljević a écrit :
>>> 
>>>> Right ,
>>>> it wasn't in the path. This time I added it and add also a 
>>>> -DCMAKE_RC_COMPILER
>>>> and here's the error. It seems that it doesn't understand path with spaces 
>>>> correctly. It has merged current path with the part of the path to cl.exe
>>>> 
>>>> C:\Users\veljko\Documents\Projects\QuteCom\QuteCom-2.2\qutecom-2-2>cmake 
>>>> -DCMAKE_BUILD_TYPE=Debug -DCMAKE_RC_COMPILER=C:/Program
>>>> Files/Microsoft Visual Studio 8/VC/bin/rc.exe -G "NMake Makefiles"
>>>> Make Error: The source directory 
>>>> "C:/Users/veljko/Documents/Projects/QuteCom/QuteCom-2.2/qutecom-2-2/8/VC/bin/rc.exe"
>>>>  does not
>>>> xist.
>>>> pecify --help for usage, or press the help button on the CMake GUI.
>>>> 
>>>> :\Users\veljko\Documents\Projects\QuteCom\QuteCom-2.2\qutecom-2-2>
>>>> 
>>>> 
>>>> 
>>>> 2011/3/18 Laurent Tarrisse <laur...@mbdsys.com>
>>>> I think your "setting" script miss something : it seems that C:/Program 
>>>> Files/Microsoft Visual Studio 8/VC/bin/ is not in your PATH …
>>>> 
>>>> What is the result of   :    rc.exe /?
>>>> 
>>>> Laurent
>>>>  
>>>> Le 18 mars 2011 à 23:20, Veljko Milisavljević a écrit :
>>>> 
>>>>> Here's the screenshot,
>>>>> a little bit more readable
>>>>> 
>>>>> 
>>>>> 2011/3/18 Veljko Milisavljević <mveljk...@gmail.com>
>>>>> Thank you everyone,
>>>>> I will install VS 2005 and try again.
>>>>> 
>>>>> 
>>>>> Veljko
>>>>> 
>>>>> 2011/3/18 Laurent Tarrisse <laur...@mbdsys.com>
>>>>> You should use visual 2005 and use Start/All Programs/Microsof Visual 
>>>>> Studio 2005/Visual Studio Tools/Visual Studio 2005 Command Prompt
>>>>> 
>>>>> Laurent
>>>>> 
>>>>> Le 18 mars 11 à 14:19, Veljko Milisavljević a écrit :
>>>>> 
>>>>>> I'm typing from command line.Is that ok?
>>>>>> Right, I should install 2005 
>>>>>> because on the web site says:
>>>>>> 
>>>>>> The most mature compiler supported is Visual C++ 2003 (version 7.1).
>>>>>> 
>>>>>> Visual C++ 2005 (version 8.0) is supported as well.
>>>>>> 
>>>>>> Visual Studio 2008 hasn't been tested yet.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 2011/3/18 Laurent Tarrisse <laur...@mbdsys.com>
>>>>>> Sorry i mean Visual 2005 command prompt
>>>>>> 
>>>>>> Laurent
>>>>>> 
>>>>>> Le 18 mars 11 à 14:15, Laurent Tarrisse a écrit :
>>>>>> 
>>>>>>> Hello,
>>>>>>> 
>>>>>>> Maybe you are not using Visual 2008 command prompt ?
>>>>>>> 
>>>>>>> Laurent
>>>>>>> 
>>>>>>> 
>>>>>>> Le 18 mars 11 à 14:05, Veljko Milisavljević a écrit :
>>>>>>> 
>>>>>>>> Here's what I done so far:
>>>>>>>> installed nsis,python,dxsdk,winsdk and cmake
>>>>>>>> created a QTDIR environment variable and pointed it to unpacked 
>>>>>>>> qt-4.5.3
>>>>>>>> didn't do anything with boost
>>>>>>>> Then went to QuteCom  build folder
>>>>>>>> and typed:
>>>>>>>> cmake -DCMAKE_BUILD_TYPE=Debug -G "NMake Makefiles"
>>>>>>>> 
>>>>>>>> error is: 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> :\QuteCom-2.2\qutecom-2-2-fd680f034aa8>cmake -DCMAKE_BUILD_TYPE=Debug 
>>>>>>>> -G "NMake
>>>>>>>> - The C compiler identification is MSVC
>>>>>>>> - The CXX compiler identification is MSVC
>>>>>>>> - Using FREE VC TOOLS, NO DEBUG available
>>>>>>>> - Check for working C compiler: C:/Program Files/Microsoft Visual 
>>>>>>>> Studio 8/VC/b
>>>>>>>> - Check for working C compiler: C:/Program Files/Microsoft Visual 
>>>>>>>> Studio 8/VC/b
>>>>>>>> Make Error at C:/Program Files/CMake 
>>>>>>>> 2.6/share/cmake-2.6/Modules/CMakeTestCComp
>>>>>>>>  The C compiler "C:/Program Files/Microsoft Visual Studio 
>>>>>>>> 8/VC/bin/cl.exe"
>>>>>>>>  is not able to compile a simple test program.
>>>>>>>> 
>>>>>>>>  It fails with the following output:
>>>>>>>> 
>>>>>>>>   Change Dir: 
>>>>>>>> C:/QuteCom-2.2/qutecom-2-2-fd680f034aa8/CMakeFiles/CMakeTmp
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>  Run Build Command:nmake /NOLOGO "cmTryCompileExec\fast"
>>>>>>>> 
>>>>>>>>        C:\Windows\system32\nmake.exe -f
>>>>>>>>  CMakeFiles\cmTryCompileExec.dir\build.make /nologo -L
>>>>>>>>  CMakeFiles\cmTryCompileExec.dir\build
>>>>>>>> 
>>>>>>>>        "C:\Program Files\CMake 2.6\bin\cmake.exe" -E 
>>>>>>>> cmake_progress_report
>>>>>>>>  
>>>>>>>> C:\QuteCom-2.2\qutecom-2-2-fd680f034aa8\CMakeFiles\CMakeTmp\CMakeFiles 
>>>>>>>> 1
>>>>>>>> 
>>>>>>>>  Building C object CMakeFiles/cmTryCompileExec.dir/testCCompiler.c.obj
>>>>>>>> 
>>>>>>>>        C:\PROGRA~1\MICROS~2\VC\bin\cl.exe
>>>>>>>>  @C:\Users\mrdbgd\AppData\Local\Temp\nmF3C4.tmp
>>>>>>>> 
>>>>>>>>  testCCompiler.c
>>>>>>>> 
>>>>>>>>  Linking C executable cmTryCompileExec.exe
>>>>>>>> 
>>>>>>>>        C:\PROGRA~1\MICROS~2\VC\bin\cl.exe /nologo
>>>>>>>>  @CMakeFiles\cmTryCompileExec.dir\objects.rsp
>>>>>>>>  @C:\Users\mrdbgd\AppData\Local\Temp\nmF3F4.tmp
>>>>>>>> 
>>>>>>>>  LINK : fatal error LNK1181: cannot open input file 'kernel32.lib'
>>>>>>>> 
>>>>>>>>  NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~2\VC\bin\cl.exe' : 
>>>>>>>> return
>>>>>>>>  code '0x2'
>>>>>>>> 
>>>>>>>>  Stop.
>>>>>>>> 
>>>>>>>>  NMAKE : fatal error U1077: 'C:\Windows\system32\nmake.exe' : return 
>>>>>>>> code
>>>>>>>>  '0x2'
>>>>>>>> 
>>>>>>>>  Stop.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>  CMake will not be able to correctly generate this project.
>>>>>>>> all Stack (most recent call first):
>>>>>>>>  CMakeLists-owbuild.txt:3 (project)
>>>>>>>>  CMakeLists.txt:1 (include)
>>>>>>>> 
>>>>>>>> 
>>>>>>>> - Configuring done
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 2011/3/18 Chris Maciejewski <ch...@wima.co.uk>
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> Can you please post error message you are getting when tying to build?
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Chris
>>>>>>>> 
>>>>>>>> 2011/3/18 Veljko Milisavljević <mveljk...@gmail.com>:
>>>>>>>> > Hi all,
>>>>>>>> > does someone have a document on how to build
>>>>>>>> > from sources?
>>>>>>>> > I have downloaded :
>>>>>>>> > QuteCom-2.2.tar.gz
>>>>>>>> > winSDK.zip
>>>>>>>> > qt-4.5.3
>>>>>>>> > pywin32-211.win32-py2.5
>>>>>>>> > python-2.5.2
>>>>>>>> > nsis-2.44
>>>>>>>> > dxSDK
>>>>>>>> > cmake-2.6.0
>>>>>>>> > boost.1.38
>>>>>>>> > I am on Windows 7
>>>>>>>> > thanks
>>>>>>>> > Veljko
>>>>>>>> _______________________________________________
>>>>>>>> QuteCom-dev mailing list
>>>>>>>> QuteCom-dev@lists.qutecom.org
>>>>>>>> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> QuteCom-dev mailing list
>>>>>>>> QuteCom-dev@lists.qutecom.org
>>>>>>>> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> QuteCom-dev mailing list
>>>>>>> QuteCom-dev@lists.qutecom.org
>>>>>>> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> QuteCom-dev mailing list
>>>>>> QuteCom-dev@lists.qutecom.org
>>>>>> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> QuteCom-dev mailing list
>>>>> QuteCom-dev@lists.qutecom.org
>>>>> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
>>>>> 
>>>>> 
>>>>> 
>>>>> <qutecom.JPG>
>>>> 
>>>> 
>>>> _______________________________________________
>>>> QuteCom-dev mailing list
>>>> QuteCom-dev@lists.qutecom.org
>>>> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
>>>> 
>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> QuteCom-dev mailing list
>>> QuteCom-dev@lists.qutecom.org
>>> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
>>> 
>>> 
>> 
>> 
>> _______________________________________________
>> QuteCom-dev mailing list
>> QuteCom-dev@lists.qutecom.org
>> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
>> 
>> 
> 
> 
> _______________________________________________
> QuteCom-dev mailing list
> QuteCom-dev@lists.qutecom.org
> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
> 
> 

_______________________________________________
QuteCom-dev mailing list
QuteCom-dev@lists.qutecom.org
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to