diff options
| author | Kevin Ottens <ervin@kde.org> | 2009-08-25 14:42:41 +0000 |
|---|---|---|
| committer | Kevin Ottens <ervin@kde.org> | 2009-08-25 14:42:41 +0000 |
| commit | fc1d82ab81a377b931e9bdbc1f842a3e804e6eee (patch) | |
| tree | c11c28f583ad43f52a4a8a0acea45e368bfd4ecc /modules/FindPyQt.py | |
| parent | 6f3e9e9fb2fce5412ef5e4b710f52d965e20d337 (diff) | |
| download | extra-cmake-modules-fc1d82ab81a377b931e9bdbc1f842a3e804e6eee.tar.gz extra-cmake-modules-fc1d82ab81a377b931e9bdbc1f842a3e804e6eee.tar.bz2 | |
Handle relative paths gracefully for kde4_add_kcfg_files macro.
If the passed arguments have a relative path, the generated files end up
with the same relative path in the build dir, otherwise the old behavior
is applied (generated files end up in the current build dir).
(Actually we might want to investigate a similar trick for files
generated from ui files, and moc files as I seem to remember having a
similar issue with moc files in solid a while ago, workarounded by
changing lots of filenames...)
Should work fine with existing code, I only had to make a small
adjustment in plasma desktop shell (committed a minute ago).
CCMAIL: kde-buildsystem@kde.org
svn path=/trunk/KDE/kdelibs/; revision=1015454
Diffstat (limited to 'modules/FindPyQt.py')
0 files changed, 0 insertions, 0 deletions