Heikki, Thanks for the reply. > It would be nice if you created a patch of your findings. Such a patch could > be put to trunk, which is currently RG1.7.* branch.
Will do. I didn't pull RG1.7.2 out from svn (just your release package) so it'll take me a short while to get that setup so I can use svn to make the patch file. I agree with your policy of stopping development of the RG1.7.* branch. I think most new users will have QT4 so the port has to be the first priority. I've now used svn to obtain the /branches/qt4 repository (is this the right one?) I don't fully understand why I had problems with the build of RG1.7.2. I now find that my OS had QT4 (limited install) and QT3 (full install). I don't think this was the cause of the problems but it could be something to look out for. On that point, I've started building QT4 4.4.3 from source (wow it's big - 3 hours and 2.2G so far!!!) The default configure option is to support QT3 (-qt3support). Is this what you guys are building with? I've not read the porting to QT4 guide yet (http://doc.trolltech.com/4.4/porting4.html) but if possible, we should look to test on builds without QT3 support. Anyway, back to getting QT4 4.4.3 to build. My distro has a 30MB implementation of 4.3.2 but kdelibs4 requires >4.4 - boring. I may be gone sometime! but when I return, hopefully, I'll be able to do something useful. Regards Chris -----Original Message----- From: Heikki Johannes Junes [mailto:[email protected]] Sent: Sun 1/4/2009 8:41 PM To: Chris Fryer Cc: [email protected] Subject: Re: [Rosegarden-devel] Interested in contributing 2009/1/4 chrisf <[email protected]> > > Hello RG Dev Team, Welcome! Now seems like we have second Chris. > > I've spent the last couple of days building RG1.7.2 on a PuppyLinux distro. > Major issues were in compilation - 20 odd files had QString/std::string > inconsistencies and one lacked #include <utility> for access to std::pair > It would be nice if you created a patch of your findings. Such a patch could be put to trunk, which is currently RG1.7.* branch. We were planning to publish RG1.7.3, but it was cancelled. The reason for the cancellation could be put in such a way that due to limited resources of the developers, we did not want to drive the development of the stable branch (trunk) and the development branch (rg-qt4) too far apart. However, seems like there is some new development in the RG1.7.* branch. > > Anyway, now I've got it working, I love it. Only thing is (as you've noted > on the wiki) QT4 port is imperative and removing kde dependence would be > really nice. PuppyLinux is 90MB, QT4 is 30MB, RG is 10MB ... the necessary > parts of kde (kdelib, arts and kdebase, afaik) are 130MB!!!!! > I am also getting more and more excited of the fact that the QT4 branch is approaching the moment it compiles! > > My linux experience is fairly limited but I've got many years experience > writing C++ code on lots of different systems (mostly embedded, as it goes, > but I'm a fast learner!). > > I would be very happy to contribute (probably best at the C rewrite part of > things) and if someone could point me at a task, I'll setup SVN and get on > with it! > > Best Regards > Chris You may choose from the following: (1) At the moment, it would be nice if you would pick up or own task. Fix your favorite bug or implement a feature request of your own. First task is to find out a task for you. (2) In practice, if you set up SVN and try to compile the QT4 branch, even the smallest patch which would help to compile the source would be nice. (3) We do have a ToDo list: http://www.rosegardenmusic.com/wiki/dev:summer_code But these tasks are not necessarily the easiest or the most obvious ones, or, they are UI related and can be reliably implemented only with a compiling source. Unfortunately, the development of new features is stalled, because only bugs fixes are put to 1.7.* branch and everybody is waiting rg-qt4 to compile before implementing new features. Otherwise, the stable branch and QT4 branch may be driven far apart. Best Regards, and Happy New Year, Heikki
------------------------------------------------------------------------------
_______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
