[CMake] Restrictions on where a binary can be put?

Alexander Neundorf a.neundorf-work at gmx.net
Fri Jan 21 10:41:01 EST 2011


On Friday 21 January 2011, Michael Hertling wrote:
> On 01/20/2011 07:01 PM, Alexander Neundorf wrote:
> > On Sunday 09 January 2011, Michael Hertling wrote:
...
> >>> I don't really understand why you want to get the LOCATION from your
> >>> target, anyway, the get_target_property works fine if you use
> >>> set_target_properties before it. [...]
> >>
> >> ...but SET_TARGET_PROPERTIES() doesn't work fine if it's used after
> >> GET_TARGET_PROPERTY(), even if both operate on different properties.
> >
> > Well, they are not completely different.
> > If I remember correctly, the LOCATION property is "calculcated" when you
> > query it. I think it changes some internal variables. Apparently to a
> > state where setting the target property afterwards doesn't have the
> > desired effect anymore :-/
>
> So, what's your conclusion in this matter? Should the behavior in
> question be considered as a bug or is it alright? IMO, such a subtle

IMO looks quite obvious like a bug. I just wanted to say that there is some 
connection between the properties.

Alex


More information about the CMake mailing list