Getting rid of the LIB_INSTALL_DIR hack on windows

[Christian Ehrlicher]

Alexander Neundorf schrieb:
> On Tuesday 15 January 2008, Alexander Neundorf wrote:
>> On Saturday 12 January 2008, Ralf Habacker wrote:
>>> Michael Pyne schrieb:
>>>> On Saturday 12 January 2008, Christian Ehrlicher wrote:
> ...
>>>> Especially since it documents
>>>> the intent better (i.e. use this for libraries, not for anything else).
>>>>
>>>> Then we could switch libraries to use install_kde4_library() and leave
>>>> the rest alone.
>>> Because there are already kde4_... macros, i suggest to use
>>> kde4_install_library() as macro name
>> If we really want that (I object, will discuss later), the name would have
>> to start with KDE4_ .
>> I'm currently exchanging emails with the cmake developers, so for now
>> please don't commit any changes.
> 
> Ok, if we can come up with a patch we can have something like the following in 
> cmake 2.6 (i.e. maybe for KDE 4.2):
> 
> install(TARGETS kfoo kbar USE_PROPERTIES)
> 
> Then everything related to the targets kfoo and kbar (dll, lib, but also 
> associated headers and resource files) will be installed to their destination 
> directories. These directories will be set per target using 
> set_target_properties(), which can be hidden in KDE in 
> KDE4_ADD_EXECUTABLE/LIBRARY/PLUGIN().
> If you have a better suggestion instead of "USE_PROPERTIES" let me know (e.g. 
> USE_TARGET_PROPERTIES).
> 
Looks fine.
maybe

install(TARGETS kfoo kbar USE_PROPERTIES foo)

where foo contains all informations about the install locations?



Christian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20080121/3d35fc9b/attachment.pgp