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

Xcode 7: "directory not found for option" warnings for /Frameworks folder #166

Closed
deemadden opened this Issue Aug 11, 2015 · 7 comments

Comments

Projects
None yet
5 participants
@deemadden

deemadden commented Aug 11, 2015

This is a dup of Quick issue #360 (Quick/Quick#360). Same problem, different project.

Building projects with Nimble included as a Cocoapod in the project under Xcode 7 beta 5 result in the warning:

ld: warning: directory not found for option '-F/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.0.sdk/Developer/Library/Frameworks'

Upon inspection, it doesn't appear as though the folder is there. I have seen this issue in custom framework contexts, and have been able to resolve it by removing the reference from Build Settings.

@jeffh

This comment has been minimized.

Show comment
Hide comment
@jeffh

jeffh Aug 13, 2015

Member

Hey @deemadden,

Thanks for filing this issue. I don't know about Xcode 7 beta 5, but previous beta versions also gave this warning. Removing the extra framework include causes Quick & Nimble to not build (after full clean). I haven't looked at it since, but it would be idea to resolve.

Member

jeffh commented Aug 13, 2015

Hey @deemadden,

Thanks for filing this issue. I don't know about Xcode 7 beta 5, but previous beta versions also gave this warning. Removing the extra framework include causes Quick & Nimble to not build (after full clean). I haven't looked at it since, but it would be idea to resolve.

@taiheng

This comment has been minimized.

Show comment
Hide comment
@taiheng

taiheng Sep 7, 2015

For some reason the location of the XCTest.framework has moved in Xcode 7 betas from the old path at

 /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.0.sdk/Developer/Library/Frameworks 

to

/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks

It's possible to fix this temporarily until the framework paths are updated in the project by creating a symbolic link to the new path in terminal:

cd /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.0.sdk
mkdir -p Developer/Library
cd Developer/Library
ln -s ../../../../Library/Frameworks/ Frameworks

I'm not sure if this is a permanent change or not and am hesitant to create a pull request correcting the path.

taiheng commented Sep 7, 2015

For some reason the location of the XCTest.framework has moved in Xcode 7 betas from the old path at

 /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.0.sdk/Developer/Library/Frameworks 

to

/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks

It's possible to fix this temporarily until the framework paths are updated in the project by creating a symbolic link to the new path in terminal:

cd /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.0.sdk
mkdir -p Developer/Library
cd Developer/Library
ln -s ../../../../Library/Frameworks/ Frameworks

I'm not sure if this is a permanent change or not and am hesitant to create a pull request correcting the path.

@AnthonyMDev

This comment has been minimized.

Show comment
Hide comment
@AnthonyMDev

AnthonyMDev Sep 10, 2015

@taiheng Since this seems to be the case now, after the GM Release, I'm willing to bet the change is permanent.

AnthonyMDev commented Sep 10, 2015

@taiheng Since this seems to be the case now, after the GM Release, I'm willing to bet the change is permanent.

@taiheng

This comment has been minimized.

Show comment
Hide comment
@taiheng

taiheng Sep 11, 2015

I don't see this issue in cocoapods on swift-2.0 branch. I've fixed it for carthage builds in #185.

taiheng commented Sep 11, 2015

I don't see this issue in cocoapods on swift-2.0 branch. I've fixed it for carthage builds in #185.

@AnthonyMDev

This comment has been minimized.

Show comment
Hide comment
@AnthonyMDev

AnthonyMDev Sep 11, 2015

Really? I'm still seeing this issue on the GM release with 2.0.0-rc3. Maybe they have fixed it since rc3

AnthonyMDev commented Sep 11, 2015

Really? I'm still seeing this issue on the GM release with 2.0.0-rc3. Maybe they have fixed it since rc3

@jeffh

This comment has been minimized.

Show comment
Hide comment
@jeffh

jeffh Sep 15, 2015

Member

This should be resolved on master now (swift-2.0 branch has been merged into master too). Closing.

Reopen/create a new issue if you still see this. Thanks!

Member

jeffh commented Sep 15, 2015

This should be resolved on master now (swift-2.0 branch has been merged into master too). Closing.

Reopen/create a new issue if you still see this. Thanks!

@jeffh jeffh closed this Sep 15, 2015

ChenYilong added a commit to ChenYilong/CollectionViewClassifyMenu that referenced this issue Jan 6, 2016

@deju

This comment has been minimized.

Show comment
Hide comment
@deju

deju Mar 1, 2016

@taiheng It works for me.

deju commented Mar 1, 2016

@taiheng It works for me.

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