Ability to support dependencies across projects

[jerrymarino]

I'd like to have multiple Xcode projects for a mammoth iOS app. Say, MyApp.xcodeproj ThirdParty.xcodeproj Core.xcodeproj.

Currently, there is dependencies between the targets in these projects. Say, MyApp depends on ThirdParty and Core. Core depends on ThirdParty as well.

I'd like for XcodeGen to be able to partition dependencies across multiple targets within the same workspace. Is this something reasonable or in the cards for XcodeGen.

[yonaskolb]

Yeah, that would be useful. It would require some sort of workspace spec. It’s not in the immediate future as it’s quite a bit of work and I’d like to get XcodeGen to a good and stable place first, but it’s definitely something for down the line

[yonaskolb]

This should work using implicit framework dependencies as described here #224

[rastersize]

@yonaskolb I also have this need and unfortunately using implicit with a framework dependency doesn’t resolve it 😔

My setup involves a Pre-build target from a separate Xcode project. It modifies the app’s Info.plist (e.g. setting the version and build number). As such it needs to happen more or less before anything else or Xcode will fail the build.

I think it would be great to have an option for the target dependency type to note that it’s from an external project. Something like:

Foo:
  dependencies:
    - target: SomeTarget
      project: path/to/external/project.xcodeproj

It’d be up to the user to guarantee that the project exists beforehand, so that XcodeGen can look up the target.

[yonaskolb]

@rasterize how is your target linked? As in what sort of settings does Xcode apply?

[rastersize]

@yonaskolb Sorry for late reply.

My targets aren’t linked. I depend on a pre-build target that executes a few scripts. For example it updates the app’s Info.plist with the current version and build number.

Currently we have the main “App” Xcode project include the Pre-build project. The App project’s main target then has a dependency on the target in the Pre-build project.

We need to do that as part of a separate target. Otherwise the build will fail with Xcode’s new build system. Unless you know of some other method for doing so?

[toshi0383]

@rastersize

I depend on a pre-build target that executes a few scripts. For example it updates the app’s Info.plist with the current version and build number.
We need to do that as part of a separate target. Otherwise the build will fail with Xcode’s new build system. Unless you know of some other method for doing so?

For Info.plists, how about using preprocessed Info.plist? You can modify Info.plist safely in Build Phase before or after compiling.
You can access preprocessed Info.plist at $TEMP_DIR/Preprocessed-Info.plist.