[Kde-bindings] Building QtRuby on MeeGo - any advice?

[Declan McGrath]

Just a quick update, I have managed to get as far a building a basic
RPM for MeeGo with the Ruby bindings. My motivation for doing this was
so I could easily install and uninstall my build of QtRuby - so I
didn't create a proper RPM Spec file or anything. (I have updated the
rough instructions at
http://www.theirishpenguin.com/2010/08/10/ruby-bindings-for-qt-building-qtruby-on-meego-and-creating-an-rpm).

I'm just wondering should I try and build a proper RPM for MeeGo and
'get it into' the MeeGo repositories, or this effort already taking
place? Is there any point in me making an RPM (which is the chosen
MeeGo package format) available for QtRuby or would something like the
gem mentioned in the "New qtbindings gem for Ruby" thread be a better
approach? Just asking to try to reduce duplication of effort where
possible.

In closing, I have to say that my short experience with building
packages using CPack has been great. I can't believe there is such an
easy hook into building RPMs, debs and so on! Does anyone know if
there are any drawbacks to using the CPack approach?

Have a good weekend!
Dec



On Tue, Aug 10, 2010 at 12:36 AM, Declan McGrath
<declan at weuseopensource.com> wrote:
> Just a quick update. QtRuby is happily building on MeeGo though I
> haven't tested it yet. I've gone back to the minimum install approach
> of just copying the qtruby directory out of kdebindings, rather than
> the entirety of kdebindings (though the latter worked as well). I've
> published a very rough guide as to the steps I went through at
>
> http://www.theirishpenguin.com/2010/08/10/ruby-bindings-for-qt-building-qtruby-on-meego/
>
> I will need to do a lot of polish on this blog post (the post is not
> on planetkde) but I just said I'd put it out there now, in case any of
> ye reading it sees something that looks completely wrong, or just
> plain awkward, in the way I've gone about this.
>
> In any case, thanks again for all the help,
> Declan
>
>
>
> On Mon, Aug 9, 2010 at 10:53 PM, Declan McGrath
> <declan at weuseopensource.com> wrote:
>> Hi Chris,
>>
>> This wasn't the problem but very well spotted!
>>
>> In my initial post I was working out of a qtruby directory because I
>> wanted to pull in the minimum amount of stuff to build QtRuby. As I
>> ran in into problems, I started again from scratch this time bringing
>> in all of kdebindings, because I felt it would be easier for you guys
>> to help me - as I thought it would be a more 'natural' way to build
>> QtRuby.
>>
>> Once I get all the teething problems ironed out, I'll return to
>> producing the most minimal QtRuby build that could possibly work blog
>> post.
>>
>> Thanks very much indeed!
>> Dec
>>
>>
>>
>>
>>
>> On Mon, Aug 9, 2010 at 7:13 PM, Chris Burel <chrisburel at gmail.com> wrote:
>>> 2010/8/9 Arno Rehn <arno at arnorehn.de>:
>>>> On Monday 09 August 2010 14:36:08 Declan McGrath wrote:
>>>>> Cmake now runs to completion, which is a good start! When I run 'make'
>>>>> I now get
>>>>>
>>>>> [  1%] Building CXX object
>>>>> smoke/smokebase/CMakeFiles/smokebase.dir/smokebase.o Linking CXX shared
>>>>> library libsmokebase.so
>>>>> [  1%] Built target smokebase
>>>>> make[2]: *** No rule to make target `smoke/qtcore/generator_smoke',
>>>>> needed by `smoke/qtcore/smokedata.cpp'.  Stop.
>>>>> make[1]: *** [smoke/qtcore/CMakeFiles/smokeqtcore.dir/all] Error 2
>>>>> make: *** [all] Error 2
>>>>>
>>>>> Am I making some rookie mistake?
>>>> Make sure you didn't disable the 'generator' subdirectory in ccmake (i.e. the
>>>> BUILD_generator variable should be set to 'ON')
>>> I think you're running cmake on the wrong directory.  Previously, you
>>> had posted:
>>>
>>> * Assuming I'm in qtruby_build, I have the qtruby source code in ../qtruby
>>> * I run
>>>    cmake ../qtruby
>>> If you have a copy of the kdebindings source, then the qtruby
>>> directory is in kdebindings/ruby/qtruby/.  Which would mean you're
>>> running cmake on the qtruby directory directly.  What I think you need
>>> to do is run cmake on the kdebindings/ directory instead.
>>> cd kdebindings top level dir
>>> mkdir build
>>> cd build
>>> cmake ..
>>>
>>> Once cmake finishes, there will be a ruby/qtruby directory created in
>>> your build dir.  cd to that dir and run make in there.
>>>
>>>>
>>>> --
>>>> Arno Rehn
>>>> arno at arnorehn.de
>>>> _______________________________________________
>>>> 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
>>>
>>
>