New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aggregate target fails to build #1

Closed
thestoics opened this Issue Feb 8, 2012 · 3 comments

Comments

Projects
None yet
2 participants
@thestoics
Collaborator

thestoics commented Feb 8, 2012

Lets use this issue as our troubleshooting thread.

Things I did:

  • Changed the default configuration target to Release for the aggregate target

However, this had no bearing on the success or failure of the build. I was able to successfully build the static framework without issue using the same version of Xcode as you have.

I built it the following ways:

  • Select StaticFramework-iOS -> Command->B
  • The output is a static framework in build/Release-iphoneuniversal

and

xcodebuild -target StaticFramework-iOS -configuration Release

with the same results.

This leads me to believe that has to be how we have Xcode configured outside of the project configuration. I suspect you have it configured to put builds in a derived location as opposed to to what the project specifies.

I'll look into that next.

thestoics added a commit that referenced this issue Feb 8, 2012

@thestoics

This comment has been minimized.

Show comment
Hide comment
@thestoics

thestoics Feb 8, 2012

Collaborator

I've updated the build script to work with both derived and project specified build directories.

The reason it failed, unfortunately, is due to how Xcode works in how it chooses where to put builds. When a target is built on the command line using xcodebuild -- which is what we are doing in our run scripts -- it does not used the derived directory. Meaning that the static library builds were being placed where the project specified the builds to be.

I've updated the build scripts to ensure that build directory is set in xcodebuild to reflect the derived build location used by the aggregate target.

Collaborator

thestoics commented Feb 8, 2012

I've updated the build script to work with both derived and project specified build directories.

The reason it failed, unfortunately, is due to how Xcode works in how it chooses where to put builds. When a target is built on the command line using xcodebuild -- which is what we are doing in our run scripts -- it does not used the derived directory. Meaning that the static library builds were being placed where the project specified the builds to be.

I've updated the build scripts to ensure that build directory is set in xcodebuild to reflect the derived build location used by the aggregate target.

@kwylez

This comment has been minimized.

Show comment
Hide comment
@kwylez

kwylez Feb 8, 2012

Owner

Justin...man thank you for the continued help on this! I added a few more classes so it was easier for people to test out. I created a simple project and added the framework and it worked just fine. I will probably do a little bit more cleanup on this test project and add in some configuration files for Xcode

Owner

kwylez commented Feb 8, 2012

Justin...man thank you for the continued help on this! I added a few more classes so it was easier for people to test out. I created a simple project and added the framework and it worked just fine. I will probably do a little bit more cleanup on this test project and add in some configuration files for Xcode

@kwylez kwylez closed this Feb 8, 2012

@thestoics

This comment has been minimized.

Show comment
Hide comment
@thestoics

thestoics Feb 8, 2012

Collaborator

No problem. Glad to be of help!

Collaborator

thestoics commented Feb 8, 2012

No problem. Glad to be of help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment