List Info

Thread: new way to install libraries in trunk (please everybody read !)




new way to install libraries in trunk (please everybody read !)
country flaguser name
Germany
2008-02-18 16:25:30
Hi,

maybe you already noticed that some changes to the
CMakeLists.txt.

************************************************************
**************
If you just want a quick workaround to avoid updating
kdelibs and make your 
module build again skip to the end of this email.
************************************************************
**************

KDE 4.1 is supposed to be released also on Windows, and
there the dll part of 
a shared lib has to go in the same directory as the
executable, and the lib 
part has to go in the library directory.

In order to do this, actually the full syntax of the cmake
install() command 
has to be used:
install(TARGETS kdecore kdeui kwrite RUNTIME DESTINATION
$
                                    LIBRARY DESTINATION
$
                                    ARCHIVE DESTINATION
$ )

Since this is a bit lot of typing for everybody, we
introduced a new 
variable "INSTALL_TARGETS_DEFAULT_ARGS", which
contains just these arguments.
So if you install a library in KDE trunk, please do it from
now on using this 
new variables:

install(TARGETS kdecore kdeui
$ )

This will make it work on all platforms, including windows.
Use this only if you install a library to the generic
destination.
If you install a plugin or any other target to a non-default
location, you 
have still to do it as you had to until now.

************************************************************
********
Workaround to make your module build again without updating
kdelibs
************************************************************
********

Since quite a few KDE modules have already been ported to
this new style, this 
also means that they more or less require current kdelibs,
because otherwise 
that variable does not exist.
So you have to update kdelibs (and qt-copy if you haven't
done so yet), build 
and install it.

If you don't want to do that now but later on, there is a
workaround.
The attached file contains the code for the new variable.

Append that at the end of your *installed*
FindKDE4Internal.cmake and you will 
instantly have that variable available. 
The next time you update, build and install kdelibs this
will be overwritten 
with the real version which comes with
INSTALL_TARGETS_DEFAULT_ARGS out of th 
box.

Alex

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

  
[1]

about | contact  Other archives ( Real Estate discussion Medical topics )