Use universal build settings

[gfontenot]

Curry is a really simple framework, and it sucks to have to manage multiple
targets and schemes to properly distribute it. Instead, we can use some clever
xcconfigs to let a single framework target (and a single scheme) build
multiple frameworks for us.

[gfontenot]

I want to test this against some demo apps to make absolutely sure this works as advertised.

[gfontenot]

Confirmed that this works against https://github.com/gfontenot/platformtests

🎉

[paulyoung]

I've been thinking about this since I saw it in kylef/Mockingjay. Would be great if it's a viable solution!

[gfontenot]

Ditto. Ever since you pointed this out as a potential option, I haven't been able to stop thinking about it.

On Nov 3, 2015, at 18:30, Paul Young notifications@github.com wrote:

I've been thinking about this since I saw it in kylef/Mockingjay. Would be great if it's a viable solution!

—
Reply to this email directly or view it on GitHub.

[paulyoung]

The only potential downside I can see to this is described here: the-grid/Disc#9

[paulyoung]

Specifically:

Because Mockingjay is a universal framework, Xcode can't infer the correct device for the scheme so sometimes combinations like Disc-iOS > My Mac can be set. This means sometimes having to manually pick the correct device for the scheme before building or running tests.

[paulyoung]

But that's only a problem because we disabled implicit dependencies.

[gfontenot]

That's interesting though, and honestly might be enough of a PITA to avoid this (unfortunately).

[gfontenot]

I wish Apple would support this kind of thing natively.

[paulyoung]

There may be a way around it but I tried a few things and haven't been able to find one.

I want to reiterate that using the default build scheme settings, "Find Implicit Dependencies" is enabled and doesn't appear to be subject to that behavior.

[gfontenot]

I'm going to go ahead and close this. I think it'd be nice, but it seems like it's more headache than it's worth.