[cmake-developers] Policy CMP0043

[Steve Wilson]

In working with my older build system with CMake from the master branch, I quickly ran into policy CMP0043: Ignore COMPILE_DEFINITIONS_<Config> properties.   My build system makes heavy use of the COMPILE_DEFINITIONS_<Config>, COMPILE_FLAGS_<Config>, LINK_FLAGS_<Config> paradigm for setting compiler/linker options.    While I didn’t see a specific policy for COMPILE_FLAGS moving to COMPILE_OPTIONS, the sources seem to indicate that COMPILE_FLAGS_<Config> (and indeed the use of COMPILE_FLAGS) will be deprecated in favor of COMPILE_OPTIONS and the newer methods of modifying COMPILE_OPTIONS such as target_compile_options().    Of course I would assume that LINK_FLAGS and LINK_FLAGS_<Config> would go this route as well.   I noticed however that target_link_options() does not exist.    Two questions:

1. Is there a plan to move LINK_FLAGS to a LINK_OPTIONS replacement and provide a target_link_options() command?   (BTW, where could I find the master feature plans and timetables?)

2.  If so, is someone already working on this implementation?

If not, I’ve started an implementation branch of my own, but realized I probably shouldn’t walk too far down that road without getting answers for these two questions.

Thanks,

Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 236 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20140129/bc0eb965/attachment.sig>