[Kde-bindings] Install Windows Binaries

Dimitar Dobrev dpldobrev at yahoo.com
Sat Oct 26 10:19:41 UTC 2013


    I assume you mean MonoDevelop on Windows. Remember, the dependency of CppSharp does not work outside of Windows yet.

    Dimitar




On Saturday, October 26, 2013 1:39 PM, Manickkavasakam <manikk.h at gmail.com> wrote:
 
Let me try compiling Qyoto in monodevelop  :)




On Sat, Oct 26, 2013 at 3:24 PM, Dimitar Dobrev <dpldobrev at yahoo.com> wrote:

    Manikk,
>
>
>    It's OK, no need to compile from source.
>
>
>    Dimitar
>
>
>
>
>On Saturday, October 26, 2013 12:50 PM, Manickkavasakam <manikk.h at gmail.com> wrote:
> 
>Hi Dimitar,
>
>I have downloaded Qt5.1.1 mingw binaries, installed with source components. Is that ok? Or I need to compile Qt5.1.1 from source.
>
>Thanks,
>Manikk
>
>
>
>
>On Thu, Oct 24, 2013 at 7:39 PM, Dimitar Dobrev <dpldobrev at yahoo.com> wrote:
>
>    Hello Manikk,
>>
>>
>>    Thank you for your offer. Here's what you need to get started:
>>    1. Have a Windows machine at your disposal, the project dependency that does most of the work - CppSharp - only works on Windows for now;
>>    2. Install a MinGW version of Qt; VC++ Qt is not supported for now;
>>    3. Download the source and compile; to run it, you need to pass the paths to your qmake and your make (with MinGW Qt on Windows the latter is .../Qt/Qt5.1.1/Tools/mingw48_32/bin/mingw32-make.exe);
>>    4. The way it works:
>>        - you have a driver object which you configure; most importantly, you set the headers you want to wrap; for more details, take a look at Setup(Driver driver) in QtSharp.cs;
>>
>>        - Cpp.Parser, which is a .NET wrapper around Clang's parser, parses the specified headers and, using the types in CppSharp.AST, builds an object tree containing all types, functions and variables present in these headers;
>>        - the object tree is then passed to CppSharp.Generator, which generates the source code that wraps the specified headers (note: only source files are generated for now, compilation is up to the user; I have some plans for automatic compilations but I'm not there yet).
>>    
>>
>>    For details on CppSharp itself, see https://github.com/mono/CppSharp. Its maintainer, Joao Matus, is more than helpful about questions, contributions, reported bugs, requested features, etc.
>>
>>
>>
>>    I have a few tasks in mind you can write to me about as soon as you've set the project up.
>>
>>
>>    Best regards,
>>    Dimitar   
>>
>>
>>
>>On Thursday, October 24, 2013 3:42 PM, Manickkavasakam <manikk.h at gmail.com> wrote:
>> 
>>Hi Dimitar,
>>
>>
I would like to contribute on the bindings you have been working on. 
>>
>>Also I don't have much experience with C++ neither C#. I am coming from Actionscript background and right now working on PHP on day to day basis in a startup. But I fell bit comfortable with C# rather than PHP and C++ and I like Qt.
>>
>>So,where to start? And how it works basically? What sort of things I need to read to get started?
>>
>>Thanks,
>>Manikk
>>
>>
>>
>>
>>On Thu, Oct 24, 2013 at 4:35 PM, Dimitar Dobrev <dpldobrev at yahoo.com> wrote:
>>
>>    About putting a note about deprecation, I've been hesitant about it since the existing Qyoto does work in quite a few cases and I don't have the alternative ready yet. Distributions pack the old Qyoto because it had already been integrated with their builds when I started working on the project. I never got around to talk to them about the new version with all the problems SMOKE and especially the existing Qyoto had. So, yes, you're kind of right it was about miscommunication.
>>>    If you insist on doing it, the version would be 4.0.7 because there have been no changes to the code since.
>>>    The new version, while I'm going to test each release, won't depend on the Qt version. Unlike SMOKE, which required tons of manual configuration per Qt version, the new approach does not require any. The most that could happen would be for the parser to choke on some retarded C++ construct in a header, and such a case would be fixed as soon as possible. That said, I target Qt 5 but it wouldn't be too hard to wrap other versions, including older ones.
>>>    About the guy with C# and QML, could you please send me a link? I've read about someone asking about C# bindings for Qt/QML but not someone working on it.
>>>
>>>
>>>    Regards,
>>>    Dimitar
>>>
>>>
>>>
>>>
>>>On Thursday, October 24, 2013 1:21 PM, Mat Arge <argemat1010 at gmail.com> wrote:
>>> 
>>>On Thursday 24. October 2013 02:37:51 Dimitar Dobrev wrote:
>>>>     No problem, Mat, I'm here to help.
>>>>     git://anongit.kde.org/assemblygen is actually the later version, the one
>>>> that the uploaded binaries have been generated from. Notice that while the
>>>> older version at git://anongit.kde.org/qyoto does have a more recent
>>>> commit, it is a single one by one of the KDE admins to simply fix the
>>>> build. So what you need is at git://anongit.kde.org/assemblygen. 
>>>
>>>OK, understood. Is there a particular reason, why the qyoto repository is not 
>>>"officially" deprecated (with a statement on the homepage and/or in the repo 
>>>itself). I am asking, because the problem is that all the distribution I 
>>>checked (OpenSuse, Fedora, Debian, Ubuntu, Arch) package the old repository 
>>>and not the new one. Since I am not aware of a technical reason for that (like 
>>>an application depending on it), I assume this is just due to a 
>>>miscommunication.
>>>
>>>Anyway, I'll start by trying to build a new package for OpenSuse and see if I 
>>>can get it in. What version number would the current assemblygen version be? 
>>>4.11.2 (as KDE's), 4.10.3 (as the only git tag suggests) or 4.0.7 (as the 
>>>version of the windows binary)?
>>>
>>>> That said,
>>>> even the version at git://anongit.kde.org/assemblygen is not being
>>>> developed any more. It depends on SMOKE which has been abandoned itself, so
>>>> I had to choose another base to step on. The result is being developed at
>>>> https://github.com/ddobrev/Qyoto. However, it hasn't been completed yet,
>>>> I'm going to make an announcement when it has. However, this new version is
>>>> going to be source-compatible with the current one so you could write your
>>>> code and later simply change your references to the new libraries.
>>>
>>>Do you have any time estimation, when this will be ready? Is this still for 
>>>QT4 or are you targeting QT5?
>>>
>>>By the way, in case you missed it: A few weeks ago, a guy announced on the 
>>>mono mailing list, that he wants to try a C# binding for QML. Maybe that's 
>>>interesting for your work there.
>>>
>>>cheers
>>>
>>>Mat
>>>
>>>>     Regards,
>>>>     Dimitar
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Thursday, October 24, 2013 11:39 AM, Mat Arge <argemat1010 at gmail.com>
>>>> wrote:
>>>> 
>>>> OK, that helps. Or at least I thought so first, I am still confused. I tried
>>>> to contact the OpenSuse people about their outdated package, but they said
>>>> they just build it from upstream.
>>>> I looked at your git, and found  that there are currently two repositories.
>>>> One which builds the new style with qyoto-qtcore.dll/libqyoto-native.so at
>>>> git://anongit.kde.org/assemblygen, and another one which builds the old
>>>> style (qt-dotnet.dll/libqyoto.so)
 at git://anongit.kde.org/qyoto.
>>>> Even more confusing, the git://anongit.kde.org/qyoto repository appears to
>>>> be the more current one (more recent git commit, more recent git tag).
>>>> 
>>>> Also, I don't really get the versioning theme of qyoto. The tags in the git
>>>> repositories appear to follow the version number of KDE, while the stuff
>>>> from your homepage (Windows binaries 4.0.7, API documentation 4.0.6) have a
>>>> different version scheme.
>>>> 
>>>> Sorry for beeing troublesome, but I am really trying to get my head around
>>>> it.
>>>> 
>>>> cheers
>>>> Mat
>>>> 
>>>> On Wednesday 23. October 2013 06:25:38 Dimitar Dobrev wrote:
>>>> >     The qtdotnet version has
 been deprecated for years.
>>>> >
>>>> >     Dimitar
>>>> >
>>>[...]
>>>
>>>_______________________________________________
>>>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
>>>
>>>
>>
>>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-bindings/attachments/20131026/9101230f/attachment-0001.html>


More information about the Kde-bindings mailing list