ApiExtractor compiles without libxml2 and libxslt available by default so I don't think it has anything to do with that. This is the error I'm getting right now when trying to compile GeneratorRunner:
[100%] Building CXX object tests/CMakeFiles/sphinxtabletest.dir/sphinxtabletest. cpp.obj sphinxtabletest.cpp Linking CXX executable sphinxtabletest.exe sphinxtabletest.cpp.obj : error LNK2001: unresolved external symbol "public: vir tual class QMap<class QString,class QString> __thiscall QtDocGenerator::options( void)const " (?opti...@qtdocgenerator@@ube?av?$q...@vqstring@@V1@@@XZ) sphinxtabletest.cpp.obj : error LNK2001: unresolved external symbol "protected: virtual class QString __thiscall QtDocGenerator::fileNameForClass(class Abstract MetaClass const *)const " (?filenameforcl...@qtdocgenerator@@MBE?AVQString@@PBVA bstractMetaClass@@@Z) sphinxtabletest.cpp.obj : error LNK2001: unresolved external symbol "public: vir tual bool __thiscall QtDocGenerator::doSetup(class QMap<class QString,class QStr ing> const &)" (?dose...@qtdocgenerator@@uae_nabv?$q...@vqstring@@V1@@@@Z) sphinxtabletest.cpp.obj : error LNK2001: unresolved external symbol "protected: virtual void __thiscall QtDocGenerator::generateClass(class QTextStream &,class AbstractMetaClass const *)" (?generatecl...@qtdocgenerator@@MAEXAAVQTextStream@@ PBVAbstractMetaClass@@@Z) sphinxtabletest.cpp.obj : error LNK2001: unresolved external symbol "protected: virtual void __thiscall QtDocGenerator::finishGeneration(void)" (?finishGenerati o...@qtdocgenerator@@MAEXXZ) sphinxtabletest.cpp.obj : error LNK2019: unresolved external symbol "public: __t hiscall QtXmlToSphinx::QtXmlToSphinx(class QtDocGenerator *,class QString const &,class QString const &)" (??0QtXmlToSphinx@@q...@pavqtdocgenerator@@ABVQString@@ 1...@z) referenced in function "private: class QString __thiscall SphinxTableTest:: transformXml(char const *)" (?transform...@sphinxtabletest@@AAE?AVQString@@p...@z ) sphinxtabletest.exe : fatal error LNK1120: 6 unresolved externals LINK failed. with 2 NMAKE : fatal error U1077: '"C:\Program Files\CMake 2.8\bin\cmake.exe"' : return code '0xffffffff' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 9.0\VC\Bin \nmake.exe"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 9.0\VC\Bin \nmake.exe"' : return code '0x2' Stop. With git bisect I was able to narrow it down to this commit: http://qt.gitorious.org/pyside/generatorrunner/commit/5f465d1eedff7727d005e2724dbc56960b0f313b and this change seems to fix the problem: diff --git a/CMakeLists.txt b/CMakeLists.txt index 7804e7d..ef04d8a 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -8,7 +8,7 @@ find_package(ApiExtractor 0.7 REQUIRED) option(BUILD_TESTS "Build tests." TRUE) if(MSVC) - set(CMAKE_CXX_FLAGS "/Zc:wchar_t- /EHsc /DWIN32 /D_WINDOWS /D_SCL_SECURE_NO_WARNINGS") + set(CMAKE_CXX_FLAGS "/Zc:wchar_t- /EHsc /DWIN32 /D_WINDOWS /DGENRUNNER_EXPORTS /D_SCL_SECURE_NO_WARNINGS") else() option(ENABLE_GCC_OPTIMIZATION "Enable specific GCC flags to optimize library size and performance. Only available if (CMAKE_HOST_UNIX) On Thu, Aug 26, 2010 at 6:42 AM, Hugo Parente Lima <[email protected]> wrote: > On Wednesday 25 August 2010 23:47:40 you wrote: >> Hi Hugo, >> >> I tried running the script and it's failing with an error compiling >> generatorrunner. It seems to be the same problem with unresolved >> symbols while linking sphinxtabletest that also happens if I try to >> compile it myself. Is there a convenient way to log all of the >> output? Each step seems to happen in a different command prompt that >> closes and leaves behind no detailed information about what went wrong. > > Yeah, It's a known issue, I intent to fix it asap. > > You have libxml2 or libxslt installed on your system and maybe something is > wrong with them. > > You can disable this dependence passing -DDISABLE_DOCSTRING=1 when calling > cmake to compile ApiExtractor. > >> Would you mind e-mailing me your installer binary so I could try it >> out while we figure out what is wrong? > > We'll release a tech preview of the Windows version today or tomorrow, so is > better to wait few hours =] > >> Thanks, >> >> Patrick >> >> > Message: 2 >> > Date: Tue, 24 Aug 2010 19:25:52 -0300 >> > From: Hugo Parente Lima <[email protected]> >> > To: [email protected] >> > Subject: [PySide] Status Report: PySide on Windows >> > Message-ID: <[email protected]> >> > Content-Type: text/plain; charset="us-ascii" >> > >> > After some commits and tests this past sprint, PySide finally >> > compiles on MS >> > Windows without problems. >> > >> > We did tests mostly on MSVC 2008 but also on MingGW. A Windows >> > installer and >> > the proper scripts to automate their creation are also ready to be >> > used. >> > >> > Surprisingly the windows installer has only 1,8MiB, yes, the >> > Windows binaries >> > are much smaller than the Linux ones and as you can imagine, our >> > installer >> > does provide the Qt libraries, so you need to install them by >> > yourself. (the >> > MSVC 2008 version), this can be changed in the future depending on >> > your >> > opinions about the matter. >> > >> > The installer will be available to download just on the next PySide >> > release, >> > but if you really want to test PySide on Windows right now you have >> > two >> > options: >> > >> > - Download the script used to create the installer and create it >> > with your own >> > hands (preferred way, because you will also test my script). >> > - Ask me on IRC (hugopl at freenode, #pyside) and I can send to you >> > the >> > installer binary I have on my computer. >> > >> > To create the installer by your own is easy: follow the recipe: >> > - Download and install cmake 2.8. >> > - Download python, 2.6 or 2.7. >> > - Download and install some git for windows. >> > - Download and install MS Visual Studio Express 2008. <-- 2008!!, >> > NOT 2010 >> > - Download and install Qt library for MSVC2008. >> > - Download and install InnoSetup. >> > - Put InnoSetup executable (iscc) on your system path >> > - Put cmake on your system path. >> > - Put git on your system path. >> > - git clone git://gitorious.org/pyside/packaging.git >> > - cd packaging\windows >> > - cscript createpackage.js >> > - wait... >> > - Enjoy PySide on Windows! >> > >> > Known issues: >> > >> > - When the script tries to run the PySide tests all will fail, this >> > is because >> > you need shiboken.dll on your system path and the script doesn't do >> > it yet. >> > - I didn't tested the combination MSVC2010 and Qt binaries >> > (compiled with >> > MSVC2008). >> > - 4 tests still failing on windows, but we are investigating them. >> > >> > Anyway, now we can finally create PySide applications on Windows :-D >> > >> > Good hacking everyone. >> > >> > >> > ------------------------------ > > -- > Hugo Parente Lima > INdT - Instituto Nokia de Tecnologia > _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
