On Tuesday, 14 November 2006 16:22, Chris Cannam wrote:
> 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?
Yes. EventFilterDialog.h has some "#ifdef COMPILE_DEPRECATED" which moc is not
able to parse. They are not needed in the header anyway, only in the .cpp
source. Please, can somebody clean it?
> 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.
I will revert to static libraries while looking for an alternative. But not
tonight, I'm very tired.
> * 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.
Sorry. It was my fault. I've committed now a change to allow you to set
whatever prefix you want now. You can use two methods.
To configure the program, using a different prefix:
$ cmake . -DCMAKE_INSTALL_PREFIX=/opt/kde
To use the previously configured prefix, but installing to a different place:
$ make install DESTDIR=/home/your/local/installation
I recommend the second way. Please remember that the data/ directory is not
installed yet. I'm not done yet.
> * Didn't we used to default to installing in /usr/local, anyway? People
> usually like that.
No. With out former scons buildsystem we used the KDE prefix as a default. It
is a safe choice for users that don't know what they are doing, instead of
forcing them to type something like:
$ ./configure --prefix=`kde-config --prefix`
> * LRDF has pkg-config support, it shouldn't be necessary to do the
> build-probe test for it.
Thanks, I will look into it. I want to review all the pkg-config stuff, as I
don't like it at all as it is now. I want to have something like this:
$ cat CMakeLists.txt
[...]
ALSA_MINIMUM_VERSION=1.0
FIND_PACKAGE(ALSA)
IF(ALSA_FOUND)
[...]
Regards,
Pedro
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
