Not bad so far. Things I tried:
* Running the cmake 2.0.0 I have on the system, just to see what would happen. Result: pass. It complains and bombs out. It's not 100% clear that the failure is connected to the complaint about the cmake version, but there's enough to make you very suspicious. * Running make without running (the right version of) cmake, to see whether it would regenerate the makefiles that I had left over from that original multi-makefile approach. Dodgy, this one -- it appeared to work, but with signs of cache amnesia (e.g. it reported it had found LRDF, and then built without it). Not recommended. * Running the right version of cmake and trying again. Not enough to recover from the prior mess. I ended up deleting the CMakeFile and cmake* and updating from svn again. * Running the right cmake in this new clean system. Looks good so far. Building now with all options enabled. We do get some reports of: /home/studio/rosegarden/reorganisation/src/gui/dialogs/EventFilterDialog.h:188:Warning: Unexpected variable declaration. and so on for lines up to 220 when generating EventFilterDialog.moc -- a conditional compilation thing? Other bits: * No, I don't at all like the way it builds the base, misc and sound directories more than once. I don't agree with the rationale for it in our case either -- we very much do not want to admit the possibility of having these files built with different options in the two processes. It's important that we know they're the same in both. If there's no other fix, then yes we would have to use static libraries. * How do I change the install target? I always install development builds to a directory particular to the build, for example this branch would usually go to $HOME/rosegarden/install/reorganisation (or elsewhere depending on the machine). I can't work out how to tell cmake to do that -- I tried going into ccmake and editing the install directory there, but it seems to set it back to /usr as soon as I press the configure key. Also, I'd prefer to know how to do it without using an interactive tool. * Didn't we used to default to installing in /usr/local, anyway? People usually like that. * LRDF has pkg-config support, it shouldn't be necessary to do the build-probe test for it. I haven't actually tried installing the build yet because I don't want to overwrite /usr. Running it in-place appears to work. Chris ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
