Automatically match up platforms for dependencies and application about carthage HOT 5 CLOSED

Depending on Xcode to Just Work™ is a dangerous game. 🚎

from carthage.

Related to/dependent upon #39.

from carthage.

After reviewing Xcode's plethora of build settings, and what other people are doing to solve this kind of “universal framework” problem, here's what I've found:

• There are seemingly no build paths that are guaranteed to include a platform component, although some happen to sometimes.
• Most people distribute fat iOS device + simulator binaries by manually running lipo at the end of their build. Oh, and this hasn't changed in multiple Xcode major versions (I can attest). 😞

Since we're apparently not going to get any help from the toolchain, here's what I propose:

1. carthage build either builds for OS X or iOS, not both at once. This means we'll need to thread platform information (from the application project) through every dependency somehow. It may even disallow OS X and iOS binaries from existing in parallel, if necessary.
2. For iOS, we automatically perform separate builds for the iphoneos and iphonesimulator SDKs, then roll them together with lipo. This depends on the built .framework having the same structure on both, but that should be acceptable, since we're only going to be building a single target (with different settings).
3. We automatically place the built framework somewhere that is not dependent upon Xcode build settings.

This definitely has some drawbacks over my initial suggestion (most notably the first item above), but it seems good enough for a first release, and doesn't involve stepping on Xcode's toes.

@Carthage/carthage Any thoughts?

from carthage.

carthage build either builds for OS X or iOS, not both at once.

So I understand, we'd have to do this because the build paths don't include a path component?

For iOS, we automatically perform separate builds for the iphoneos and iphonesimulator SDKs, then roll them together with lipo.

👍

from carthage.

we'd have to do this because the build paths don't include a path component?

If you meant “platform component,” yes, that's correct.

Although it occurred to me that we could structure our built binaries in a way that allows both to exist side-by-side. For example, if the application project contained a Binaries folder, maybe we could set up Binaries/iOS and Binaries/Mac, and just ask the user to link whichever platform(s) they care about.

from carthage.