Re: [trinity-devel] tdelibs FTBFS: cmake 2.8.12: INTERFACE_LINK_LIBRARIES vs. LINK_INTERFACE_LIBRARIES
20 Dec
2013
20 Dec
'13
4:47 p.m.
You could reference e.g. gentoo bugzillaand other:
https://bugs.gentoo.org/show_bug.cgi?id=490194
It's resolved here so I haven't
The trinity is not the only project that is affected the gentoo
also mentions ldc(d compiller) and openvas.
Consider this: KDE is completely cmake based. Slackware 14.1 comes
with cmake 2.8.12.0. All of the KDE packages compiled for the
official Slackware 14.1 release. I'm assuming without these
problems. Convincing the Slackware maintainer that cmake 2.8.12.0
is problematic needs a good explanation.
That KDE compiled without failure and Trinity does not compile
leads to an obvious question of what are the Trinity folks doing
"wrong" that the KDE folks are doing "right"?
Right now I don't understand the issues involved. I'm not a
developer or coder. I'm a packager and tester who is devoted to
keeping Trinity alive. These cmake problems are above and beyond my
full understanding. I can't ask the Slackware maintainer to update
to cmake 2.8.12.1 "just because." Trinity is not "officially"
supported in any distro. Emphasis on "officially." Asking distro
maintainers to update cmake needs a clear explanation --- something
I am not able to do. Somebody who understands the details of all of
these problems could write something that I could forward to the
Slackware maintainer.
That said, as I reported in a previous post, I still can't build
Trinity after I updated to 2.8.12.1 on my own. :-)
Darrell
20 Dec
20 Dec
10:21 p.m.
New subject: [trinity-devel] tdelibs FTBFS: cmake 2.8.12: INTERFACE_LINK_LIBRARIES vs. LINK_INTERFACE_LIBRARIES
2013/12/20 Darrell Anderson <darrella(a)hushmail.com>
You could
reference e.g. gentoo bugzillaand other:
https://bugs.gentoo.org/show_bug.cgi?id=490194
It's resolved here so I haven't
The trinity is not the only project that is affected the gentoo
also mentions ldc(d compiller) and openvas.
Consider this: KDE is completely cmake based. Slackware 14.1 comes
with cmake 2.8.12.0. All of the KDE packages compiled for the
official Slackware 14.1 release. I'm assuming without these
problems. Convincing the Slackware maintainer that cmake 2.8.12.0
is problematic needs a good explanation.
That KDE compiled without failure and Trinity does not compile
leads to an obvious question of what are the Trinity folks doing
"wrong" that the KDE folks are doing "right"? Right now I don't understand the issues involved.
I'm not a
developer or coder. I'm a packager and tester who is devoted to
keeping Trinity alive. These cmake problems are above and beyond my
full understanding. I can't ask the Slackware maintainer to update
to cmake 2.8.12.1 "just because." Trinity is not "officially"
supported in any distro. Emphasis on "officially." Asking distro
maintainers to update cmake needs a clear explanation --- something
I am not able to do. Somebody who understands the details of all of
these problems could write something that I could forward to the
Slackware maintainer.
I intended suggest to provide some over reason than trinity for maintainer.
IMO it would be better not to mantion TDE at all... I think you understand
why...The nice one would be to point on the same errors in openvas.
I don't know the specific of slackware but IMO the requests for bumping new
version are not require such big reasons.
I can't find the corresponding bug report in cmake's bugzilla but it seems
that fix is here:
http://cmake.org/gitweb?p=cmake.git;a=commit;h=ef10b87cc1e87343a778c89d8a41…
NOTE: I can't reproduce your cmake _errors_ from the first message with
2.8.12 as well as 2.8.12.1. Also for me the warning message is different in
2.8.12:
=============================
Policy CMP0022 is not set: INTERFACE_LINK_LIBRARIES defines the link
interface. Run "cmake --help-policy CMP0022" for policy details. Use the
cmake_policy command to set the policy and suppress this warning.
Static library target "tdespell2base-static" has a INTERFACE_LINK_LIBRARIES
property. This should be preferred as the source of the link interface for
this library. Ignoring the property and using the link implementation as
the link interface instead.
=============================
In 2.8.12.1 it's the same as yours...
To be honest, I'm not fully understand it too... Just now I run into that
I even don't clearly understand how cmake_policy() works and supposed to
work. >_<
That said, as I reported in a previous post, I still
can't build
Trinity after I updated to 2.8.12.1 on my own. :-)
it seems this is because of your patch... for me it produces broken
export-*-shared.cmake files and as a consequence broken
${PREFIX}/share/cmake/tdelibs.cmake.
try to build without it... Don't forget to rebuild and _reintstall_
tdelibs. ;)
4024
days inactive
4024
days old
1 comments
2 participants
participants (2)
-
Darrell Anderson -
Fat-Zer