Hi Laurent, I decided to throw away my dev environment VM and create a new one from scratch... new WinXP install from CD and just the methodology I posted before.
This time, it all compiled first time... qt (took about 8 hours), and qutecom both compiled without any issues, and the installer worked straight up without any complaints about DLL's. Many thanks for your help. I'll now go play with customisations :) Incase it helps anyone who's having similar issues to me, here is the environment I've used which has worked out of the box. It may not use the latest version of things, but it does build fine: 1. Clean Win XP Professional install from CD (VMWare under Ubuntu) 2. Boost 1.38 using the boostpro.com installer (http://www.boostpro.com/download/boost_1_38_0_setup.exe) with all variants vs2005 variants of the following: - unit test framework - thread - serialization - program options - signals - date/time 3. Visual C 2005 Express - excluded the IDE. (http://go.microsoft.com/fwlink/?LinkId=51410&clcid=0x409) 4. Microsoft Platform SDK for Windows Server 2003 R2 (http://www.microsoft.com/Downloads/details.aspx?FamilyID=484269e2-3b89-47e3-8eb7-1f2be6d7123a&displaylang=en) - not the updated version which they try to encourage you to download instead. 5. Microsoft DirectX SDK (August 2007) (http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=529F03BE-1339-48C4-BD5A-8506E5ACF571&displaylang=en) 6. QT 4.5.3 Opensource source code distribution (ftp://ftp.qt.nokia.com/qt/source/qt-all-opensource-src-4.5.3.zip). 7. Mercurial 1.5.1 (http://mercurial.selenic.com/) 8. NSIS 2.46 (http://nsis.sf.net/) 9. CMake 2.8.1 (http://www.cmake.org/files/v2.8/cmake-2.8.1-win32-x86.exe) 10. Python 2.6.5 (http://www.python.org/ftp/python/2.6.5/python-2.6.5.msi) 11. Python for Win32 (http://sourceforge.net/projects/pywin32/files/) 12. Qutecom 2.2 via hg (hg clone http://hg.qutecom.org/qutecom-2.2) 13. Environment variables: @call "C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars32.bat" @call "C:\Program Files\Microsoft DirectX SDK (August 2007)\Utilities\Bin\dx_setenv.cmd" @SET QTDIR=C:\qt\qt-all-opensource-src-4.5.3 @SET INCLUDE=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include;%INCLUDE% @SET INCLUDE=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\atl;%INCLUDE% @SET INCLUDE=C:\Program Files\Microsoft DirectX SDK (August 2007)\Include;%INCLUDE% @SET LIB=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Lib;%LIB% @SET LIB=C:\Program Files\Microsoft DirectX SDK (August 2007)\Lib\x86;%LIB% @SET LIB=C:\Program Files\Microsoft DirectX SDK (August 2007)\Lib;%LIB% @SET BOOSTLIBDIR=C:\Program Files\boost\boost_1_38\lib @SET BOOSTINCLUDEDIR=C:\Program Files\boost\boost_1_38 @SET PATH=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin;%PATH% @SET PATH=C:\Program Files\Microsoft DirectX SDK (August 2007)\Utilities\Bin\x86;%PATH% To build -------- 1. Reboot after installing the above 2. Execute batch file containing above environment vars 3. Unzipped the qt sourcecode to 4. cd \qt\qt-all-opensource-src-4.5.3 configure # wait about an hour 5. nmake # wait several hours 6. cd \qutecom-2.2\build 7. cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_VERBOSE_MAKEFILE=1 "NMake Makefiles" .. 8. nmake 9. nmake install Regards, Richard On Sun, 2010-04-25 at 16:40 +0200, Laurent Tarrisse wrote: Le 25/04/10 16:21, Richard Goode a écrit : > > Thanks Laurent. I'm having a hard time working out what I'm missing though. > > My Qt compile is passing the "configure" stage, and I can start the compile > > with nmake. It proceeds to build for about 10 minutes before failing with > > qt\bin\moc.exe exiting with code 0xc0000135. When I run moc.exe it > > manually, > > it reports missing msvcr80.dll. > > > I think there is something wrong at configure step : > Download clean source from Qt > Ensure that no previous moc/qmake are in your path and no QTDIR defined > > I've got several versions of msvcr80.dll on my system, but including any of > > them in the path causes moc.exe to fail with runtime error. > > > I'm currious : What is the result if you copy msvcr80.dll in moc.exe > directory ? > > Am I right to assume vs2005 is the only current way to compile QuteCom? I'd > > read somewhere that mingw and vs2008 were broken? > > > Mingw is broken > vs2008 can be used ... but you will need to rewrite some part of nsis > installer > > Laurent > _______________________________________________ > QuteCom-dev mailing list > [email protected] > http://lists.qutecom.org/mailman/listinfo/qutecom-dev _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
