<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Deniz,<div class=""><br class=""></div><div class="">Thanks for the response! I tested it out and it seems to work exactly as you describe :)</div><div class=""><br class=""></div><div class="">I don’t want to depend on an un-released version of CMake though. The original desire is because I kept making mistakes / adding definitions for one and not the other (code duplication at its finest…).</div><div class=""><br class=""></div><div class="">I discovered that I can populate one, e.g. only modify <i class="">mylib_obj</i><b style="font-style: italic;" class=""> </b>and then later grab these properties to add to the interface:</div><div class=""><br class=""></div><div class=""> get_target_property(MYLIB_OBJ_INTERFACE_COMPILE_DEFINITIONS mylib_obj INTERFACE_COMPILE_DEFINITIONS)</div><div class=""><br class=""></div><div class="">and also the same for INTERFACE_COMPILE_OPTIONS etc. (Note: for anybody reading this, understand that INTERFACE_COMPILE_DEFINITIONS is desired here, COMPILE_DEFINITIONS includes private items which I do not want in this case).</div><div class=""><br class=""></div><div class="">Is getting the properties and then later setting them a reasonable solution here, or is this a bad idea?</div><div class=""><br class=""></div><div class="">-Stephen</div><div class=""><br class=""></div></body></html>