On 11/13/2015 05:14 AM, David Faure wrote: > OK then we could go for static libraries, to preserve that.
That sounds good. > Anyway I like incremental changes so my plan is > 1) build with cmake exactly what is being built now > 2) make one big static library with everything except main() > 3) write a first unit test This seems logical. > Unfortunately one-big-static-lib means every test will take a long time > to link, so building the tests would have to be off by default otherwise > you guys will get slowed down during development. I defer to you to work out the best plan there. I think most of the core users run debug builds routinely. When we had unit tests back in the day, I never ran them. As you probably expect, I almost never run release builds myself. > BTW another major advantage of a buildsystem like cmake is that you'll > be able to (more easily) use KDevelop or QtCreator to hack on the code. > For now I generated a fake .pro file to be able to use QtCreator, > (and then telling qtcreator to never run qmake) but that's a hack. That does sound like an advantage. I use QtCreator with Fakevim for many side projects, but I still do all the work on Rosegarden from the command line, with real vim. It would really boost my efficiency to use an IDE. It annoys me that I am so versed in such a bizarre and quirky editor, but I'm stuck with the finger memory. I did a project with Android Studio, which has a positively excellent IDE, and I drove myself crazy trying to use vim commands, and then having to erase the garbage from my code. -- D. Michael McIntyre ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
