24 Sep
2014
24 Sep
'14
9:36 p.m.
Hi all,
during the current building, I noticed on the Debian Jessie that we have new
trouble with newer CMake:
CMake Warning (dev) at cmake/modules/TDEMacros.cmake:434
(get_target_property):
Policy CMP0026 is not set: Disallow use of the LOCATION target property.
Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy
command to set the policy and suppress this warning.
The LOCATION property should not be read from target
"kgreet_classic-module". Use the target name directly with
add_custom_command, or use the generator expression $<TARGET_FILE>, as
appropriate.
There are many such reports on the same topic. I do not know if simply setting
the old behavior is the right way.
IF( POLICY CMP0026 )
CMAKE_POLICY( SET CMP0026 OLD )
ENDIF( POLICY CMP0026 )
See: http://www.cmake.org/cmake/help/v3.0/policy/CMP0026.html
What do you think?
--
Slávek
25 Sep
25 Sep
3:13 a.m.
New subject: R: [trinity-devel] New CMake warning CMP0026
There are many such reports on the same topic. I do
not know if simply setting
the old behavior is the right way.
IF( POLICY CMP0026 )
CMAKE_POLICY( SET CMP0026 OLD )
ENDIF( POLICY CMP0026 )
See: http://www.cmake.org/cmake/help/v3.0/policy/CMP0026.html
What do you think?
Hi Slavek,
as a temporary solution, I would say let's set the use of OLD as you suggested and
then file a bug report to adapt cmake scripts to the NEW way. This may require several
changes (no idea how many or how few at the moment), so it would be better to leave it for
after v14.0.0 is out.
Nevertheless for the future we should do the switch from OLD to NEW, because it could be
possible that sooner or later the OLD way would no longer be supported, no one knows.
What do you think?
Cheers
Michele
PS: the next 3 or 4 days I won't be around at all.
26 Sep
26 Sep
6:49 a.m.
New subject: [trinity-devel] R: [trinity-devel] New CMake warning CMP0026
2014-09-25 7:13 GMT+04:00 Michele Calgaro <michele.calgaro(a)yahoo.it>it>:
Hi Slavek,
as a temporary solution, I would say let's set the use of OLD as you suggested and
then file a bug report to adapt cmake scripts to the NEW way. This may require several
changes (no idea how many or how few at the moment), so it would be better to leave it for
after v14.0.0 is out.
Nevertheless for the future we should do the switch from OLD to NEW, because it could be
possible that sooner or later the OLD way would no longer be supported, no one knows.
https://mail.google.com/mail/u/0/#label/%5Bmaillist%5Dtrinity/148a998e8e988…
What do you think?
Cheers
Michele
PS: the next 3 or 4 days I won't be around at all.
There is no shame in keep using the OLD behavior... According to cmake
developer policy they will never drop support for old behaviors. On
the other hand if you adopt the new policy to be used in general you
drop support for the older cmake versions. But in this particular case
it seems that it may be possible to confirm the requires of new policy
without breaking the old stuff (may be not).
29 Sep
29 Sep
5:36 p.m.
New subject: [trinity-devel] R: [trinity-devel] New CMake warning CMP0026
Dne pá 26. září 2014 Fat-Zer napsal(a):
2014-09-25 7:13 GMT+04:00 Michele Calgaro
<michele.calgaro(a)yahoo.it>it>:
It seems to me that there is no other option than to switch CMP0026 to OLD. By
the way, KDE3Macros contained in the CMake upstream also uses LOCATION
property by the same way. Pushed to GIT:
http://git.trinitydesktop.org/cgit/cmake/commit/?h=origin/master&id=0d5…
--
Slávek
Hi Slavek,
as a temporary solution, I would say let's set the use of OLD as you
suggested and then file a bug report to adapt cmake scripts to the NEW
way. This may require several changes (no idea how many or how few at the
moment), so it would be better to leave it for after v14.0.0 is out.
Nevertheless for the future we should do the switch from OLD to NEW,
because it could be possible that sooner or later the OLD way would no
longer be supported, no one knows.
https://mail.google.com/mail/u/0/#label/%5Bmaillist%5Dtrinity/148a998e8e9
88d3b What do you think?
Cheers
Michele
PS: the next 3 or 4 days I won't be around at all.
There is no shame in keep using the OLD behavior... According to cmake
developer policy they will never drop support for old behaviors. On
the other hand if you adopt the new policy to be used in general you
drop support for the older cmake versions. But in this particular case
it seems that it may be possible to confirm the requires of new policy
without breaking the old stuff (may be not).
3707
days inactive
3712
days old
3 comments
3 participants
participants (3)
-
Fat-Zer -
Michele Calgaro -
Slávek Banko