Small problem with PolkitQt
Dario Freddi
drf54321 at gmail.com
Sun Jan 10 17:17:30 CET 2010
Sorry for the late answer, troubled life is back.
On Wednesday 30 December 2009 21:38:12 Alexander Neundorf wrote:
[..]
>
> In general determining install locations are the responsibility of the
> project which is being built. I mean, if I chose to install something to
> $HOME/inst it shouldn't matter where PolkitQt is installed.
>
> What we do for the other install dirs like BIN_INSTALL_DIR etc. in kdelibs
> is the following:
> if the variable (e.g. KDE4_AUTH_POLICY_FILES_INSTALL_DIR) has not been
> explicitely set, and if the current CMAKE_INSTALL_PREFIX is the same as the
> kdelibs install prefix, then we reuse the variable (e.g.
> KDE4_AUTH_POLICY_FILES_INSTALL_DIR) from kdelibs.
>
> Look for the macro _SET_FANCY() in
> kdelibs/cmake/modules/FindKDE4Internal.cmake.
>
> Does this do what you want ?
Unfortunately not. The problem here is that we really want to store some data:
KAuth is backend based, and we have no knowledge at build time (outside
KDELibs) of which backend was built, hence how to handle it.
This is probably a reason why I'd put stuff in
CreateKDELibsDependencies.cmake. I'd add two variables: one,
KDE4_AUTH_BACKEND_NAME, carrying the name of the chosen backend, and one,
KDE4_AUTH_POLICY_FILES_INSTALL_DIR carrying the location of the policy files
install dir, if any (which is required unless we decide to install
findpolkitqt*.cmake).
Now, the logic for selecting the backend name is
kdecore/auth/ConfigureChecks.cmake, where the KAUTH_BACKEND variable is set.
Once that is done, finding out the value of KDE4_AUTH_POLICY_FILES_INSTALL_DIR
is a breeze. The only problem I see is that putting straight into
CreateKDELibsDependenciesFile.cmake set(KDE4_AUTH_BACKEND_NAME
${KAUTH_BACKEND}) fairly doesn't work. Is there a way to pull the variable
there without having to move the checks in kdecore/auth/ConfigureChecks.cmake
downwards in the tree?
>
> Alex
>
--
-------------------
Dario Freddi
KDE Developer
GPG Key Signature: 511A9A3B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20100110/04eef68e/attachment.sig
More information about the Kde-buildsystem
mailing list