On Mon, Jan 5, 2009 at 11:37 AM, Chris Fryer <[email protected]> wrote: > I built and modified your 1.7.2 code from the main "get the stable" > source code link - I didn't know at the time that I should've got it > from SVN. > To make the patch file, I got 1.7.2_RC2 from SVN and diff'd to my > source.
Ah, right. No, for fixes to the mainstream (working) Rosegarden you should checkout the SVN trunk, and then (once you've tested your fixes in that build) use svn diff to get a patch against the latest trunk. Of course most of the work that is going on at the moment is in the Qt4 branch instead, but that is neither bug nor feature work -- it's first of all just "getting it to build", which will shortly be followed by "getting it not to crash straight away on startup", followed by "getting it to display something in the window" and then a long phase of "getting it to do all the stuff 1.7 does". In principle, the Qt4 port is a direct port in the sense that (almsot) all of the 1.7 functionality will still be there in the code afterwards (it isn't a rewrite), but it's reasonable to suppose that it won't all actually work for some time. To get an idea of where we've reached with the Qt4 port, the best thing probably is to check it out and build it. The CMake build system should get you much of the way there, or there is a simpler makefile called qt4-makefile which we are using temporarily during the porting process -- you can edit the include paths at the top of this and then build against it. An invocation I use quite a bit is "make -f qt4-makefile -k 2>&1 | tee make.log" which builds everything, ignoring errors, writing a log file that I can then scan for errors. Of the 581 source files in my tree, I make it 558 that compile now (that's 96%). Of the rest, maybe 10 will be fixed in the course of the work I'm doing just now (sorting out action construction calls and replacing KXMLGUI), leaving a dozen or so that are likely to need more thought. Chris ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
