On Thu, Jun 21, 2012 at 12:22 PM, Thomas Sondergaard <[email protected]
> wrote:

> On 2012-06-21 17:23, David Cole wrote:
>
>> If you want it to work with iOS apps, then you have to set
>> CMAKE_XCODE_EFFECTIVE_**PLATFORMS as of its introduction, which was
>> version 2.8.6.
>>
>> That feature was introduced to enable seamless switching between
>> simulator and device builds, and to enable running in the debugger for
>> either.
>>
>
> OK, but I'm still a little mystified as everything builds fine without it,
> until you get to linking an executable with the output from a library
> target, and then CMake suddenly doesn't know where it put it?
>
> Thanks,
>
>
> Thomas
>
>
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/**
> opensource/opensource.html<http://www.kitware.com/opensource/opensource.html>
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/**CMake_FAQ<http://www.cmake.org/Wiki/CMake_FAQ>
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/cgi-**bin/mailman/listinfo/cmake-**developers<http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers>
>


Yes, CMake doesn't know where the file ends up because CMake doesn't know
which platform you've chosen within Xcode. Which is actually a problem for
install rules on such a project. See these open bug reports:

  http://public.kitware.com/Bug/view.php?id=12506
  http://public.kitware.com/Bug/view.php?id=12640

What we presently have was a bit of a compromise to quickly/easily enable
the switching and debugging behavior improvements within Xcode. It needs
more work to be a complete feature.


HTH,
David
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers

Reply via email to