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

Reply via email to