[Kde-bindings] Fw: building qyoto on Windows

Tue Feb 14 20:24:08 UTC 2012

You need https://gitorious.org/assemblygen/. It is a lib that generates C# wrappers from SMOKE libs and compiles them. There are, however, no example applications that I am aware of.

Congrats on your progress. I'm busy these days but after that I'd like to ask a few questions about the way you built your Qyoto. I didn't generate a VS solution at all, mine were built on the command line.

________________________________
 From: Peter Amstutz <peter.amstutz at tseboston.com>
To: Dimitar Dobrev <dpldobrev at yahoo.com>; KDE bindings for other programming languages <kde-bindings at kde.org> 
Sent: Tuesday, February 14, 2012 10:10 PM
Subject: Re: [Kde-bindings] building qyoto on Windows

Hi, 

I've made some additional progress building on Windows.  The most
    frustrating problem was learning the hard way that cmake searches
    for "FindXXX.cmake" and "XXXConfig.cmake" files differently (the
    former is searched for in CMAKE_MODULE_PATH, the latter searches the
    system PATH).  I eventually resolved that.  The second problem is
    the following code from SmokeConfig.cmake (lines 50-62):

  if(WIN32)
            # DLLs are in the bin directory.
            find_library(SMOKE_${uppercase}_LIBRARY
                smoke${lowercase}
                PATHS "e:/development/smokegenerator/bin"
                NO_DEFAULT_PATH)
        else(WIN32)
            find_library(SMOKE_${uppercase}_LIBRARY
                smoke${lowercase}
                PATHS "e:/development/smokegenerator/lib"
                NO_DEFAULT_PATH)
        endif(WIN32)

This is wrong, because CMake is searching for files in the form
    smokeqtcore.lib, which are in lib/.  The special case for Windows to
    search bin/ should be removed.

Next, I removed references to smokeqttest which did not build.  At
    this point I was able to configure and generate VS 2008 project
    files successfully.  

When I built the solution, I encountered some problems in
    src/handlers.cpp (lines 1669-1672)
DEF_VALUELIST_MARSHALLER( QSslCertificateList,
    QList<QSslCertificate>, QSslCertificate )
DEF_VALUELIST_MARSHALLER( QSslCipherList, QList<QSslCipher>,
    QSslCipher )
DEF_VALUELIST_MARSHALLER( QSslErrorList, QList<QSslError>,
    QSslError )

These symbols were not available for some reason, so I commented
    them out.

Finally I was able to build all the C++ projects.  However there are
    no .csproj files generated by cmake?!  How do I build the C# parts
    of Qyoto and the example applications?

Thanks,
Peter

On 2/14/2012 11:19 AM, Dimitar Dobrev wrote: 
While it's not the greatest news that QtTest fails, it isn't essential at all. No other Qt lib depends on it and .NET unit testing is performed using other tools (like NUnit) anyway.
Good luck onwards. ________________________________ From: Peter Amstutz <peter.amstutz at tseboston.com> To: Kde-bindings at kde.org Sent: Tuesday, February 14, 2012 6:05 PM
Subject: [Kde-bindings] building qyoto on Windows Hello all, I am trying to build Qyoto on Windows.  I understand that this is working for some people, but the process isn't quite flawless.  Here are my experiences so far: Doing a 32 bit build with Visual Studio 2008 on Windows 7 (x64).  I am using Qt 2.7.4 on the assumption that it would be better supported than Qt 2.8.0 which was only released last week.  I built Qt myself from the open source release. Building Smokegen went smoothly.  I had to set CMAKE_INSTALL_PREFIX manually in order to install smokegen to a target directory. Building SmokeQt has been more difficult.  The first problem I had was in having it find Smoke; this was resolved by installing smoke to a separate directory.  It turns out you cannot build SmokeQt against the Smoke build tree; only the installed tree. The second problem was the following error: Entering E:/Development/smokeqt/qtcore
CMake Error at qtcore/QtGuess.txt:139 (list):
list sub-command REMOVE_ITEM requires two or more arguments.
Call Stack (most recent call first):
qtcore/CMakeLists.txt:14 (include) The error at qtcore/QtGuess.txt:139 is this:
  list(REMOVE_ITEM test_targets ${qtdefines_output})
this can be fixed:
  list(REMOVE_ITEM test_targets "${qtdefines_output}") This produces an empty string instead of no string. This underlying problem is that ${qtdefines_output} is empty.  This variable is empty because the qtdefine test program produces no output.  It produces no output because there are no printf() lines are present in qtdefine.cpp. There are no printf() lines because ${qtheaders} is expected to contain #define lines, but does not.  It does not contain any #define lines because ${QT_QTCORE_INCLUDE_DIR}/qglobal.h simply #includes "../../src/corelib/global/qglobal.h" rather than being the "real" qglobal file which the current code expects to find.  Confused yet? I'm not sure if qtdefine actually affects anything, as the script then proceeds to test directly for #defines for the features it cares about.  I think this part of the build script could use some attention from someone who knows more about what it is going on. Finally I am able to run the
 configuration step without any fatal errors, and generate correct solution files.  Everything builds except smokeqttest with the following error.  Is smokeqttest an essential project? 1>------ Build started: Project: smokeqttest, Configuration: Release Win32 ------
1>Linking...
1>   Creating library E:\Development\smokeqt\build\qttest\Release\smokeqttest.lib and object E:\Development\smokeqt\build\qttest\Release\smokeqttest.exp
1>x_1.obj : error LNK2019: unresolved external symbol "public: static struct QMetaObject const QTestEventLoop::staticMetaObject" (?staticMetaObject at QTestEventLoop@@2UQMetaObject@@B) referenced in function "public: static class QString __cdecl QTestEventLoop::tr(char const *,char const *)" (?tr at QTestEventLoop@@SA?AVQString@@PBD0 at Z)
1>E:\Development\smokeqt\build\qttest\Release\smokeqttest.dll : fatal error LNK1120: 1 unresolved externals
1>Build log was saved at "file://e:\Development\smokeqt\build\qttest\smokeqttest.dir\Release\BuildLog.htm" 1>smokeqttest - 2 error(s), 0 warning(s) Assuming smokeqttest is not essential, my next step will be to try to build qyoto. -- Peter Amstutz
Senior Software Engineer
Technology Solutions Experts
Natick, MA
02131 _______________________________________________
Kde-bindings mailing list Kde-bindings at kde.org https://mail.kde.org/mailman/listinfo/kde-bindings 
>
>
>_______________________________________________
Kde-bindings mailing list Kde-bindings at kde.org https://mail.kde.org/mailman/listinfo/kde-bindings 

-- 
Peter Amstutz
Senior Software Engineer
Technology Solutions Experts
Natick, MA
02131 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-bindings/attachments/20120214/25a7c7fd/attachment.html>