https://bugs.kde.org/show_bug.cgi?id=357428
--- Comment #5 from Luigi Toscano <luigi.tosc...@tiscali.it> --- (In reply to MaxiPunkt from comment #4) > With a subdir added as suggested, during compilation CMake now complains: > > > add_custom_target cannot create target "BLA_BLA" because another target > > with the same > > name already exists. The existing target is a custom target created in > > source directory > > ... > > ... > > See documentation for policy CMP0002 for more details." > Adding "cmake_policy(SET CMP0002 OLD)" doesn't help. Which version of cmake? I tested it with 3.5, but it should work with older versions. The issue with conflicting targets was solved long time ago. Could you please share the example you are testing? > I still don't get the logic behind all this. Looking at other code-examples: > 1) > http://download.kde.org/stable/kronometer/2.1.0/src/kronometer-2.1.0.tar.xz > 2) http://download.kde.org/stable/ktorrent/5.0/ktorrent-5.0.1.tar.xz > > These projects include translated PO's > => simplified directory-structure (w/o CMakeLists.txt in subdirs) > => "ki18n_install()" is used in CMakeLists.txt (root-dir) > > These projects include translated DOC's > => old directory-structure (incl. CMakeLists.txt in any subdir) > => "kdoctools_install()" is NOT used in CMakeLists.txt (root-dir) > > Is it possible for these projects to use "kdoctools_install()" instead - how > would I do that? > > If there would be no solution for this, what is the propose of > "kdoctools_install()", then? Yes, they can use it. It's just that no one implemented its usage in the scripts which create tarballs, probably because the feature was not advertised. I asked around and there is some work in progress, even if it needs some design decision. See https://phabricator.kde.org/T2433 -- You are receiving this mail because: You are watching all bug changes.