[cmake-developers] iOS support

[Florent Castelli]

Thanks for the detailed information.
My "hackweek" starts on Monday and I'll start working on these issues then.
I'll work on finding a way to unify toolchain files for simulator and
devices first. I don't think I'll try to work on iOS8 features since my
company is shipping for iOS6 and there are so many things to do :)
Though, I'm not really an iOS developer, there's probably a ton of things
I'll miss. But I have great devs in my company and I'm sure it'll be okay!

I'll keep you updated of my progress during the week and hopefully, I won't
have to call for help here too often :)

/Orphis
On 1 Oct 2014 01:42, "Eric Wing" <ewmailing at gmail.com> wrote:

> Thought of one more.
> I hate how the top, default target is ALL_BUILD. This is problematic
> for both Xcode and Visual Studio because when you use the big giant
> "run" button in the UI, the IDE is confused because ALL_BUILD is an
> aggregate target and not a real thing that can be run. At least for
> Xcode, a bunch of options change dynamically based on the type of
> target selected and building/launching to the device/simulator is not
> an option when on an aggregate target.
>
> It's an annoyance because it interferes with the normal workflow for
> those familiar with the IDEs. And it's an annoyance for those who are
> not familiar with the IDEs because the big giant buttons do nothing
> and they don't understand the IDEs well enough on how to correct the
> issue.
>
> (It's also more work invoking xcodebuild and msbuild because you can't
> rely on the default targets.)
>
> Thanks,
> Eric
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20141001/edf80fa6/attachment-0002.html>