Skip to content
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

Dependency analysis warnings with Cocoapods #88

Closed
bajtyngier opened this issue May 7, 2018 · 2 comments
Closed

Dependency analysis warnings with Cocoapods #88

bajtyngier opened this issue May 7, 2018 · 2 comments

Comments

@bajtyngier
Copy link

Is there a particular reason for the podspec to include any of it's preserve_paths? It raises the following warnings when building the project:

warning: no rule to process file '/.../Pods/Down/Source/cmark/case_fold_switch.inc' of type sourcecode.pascal for architecture i386
warning: no rule to process file '/.../Pods/Down/Source/cmark/COPYING' of type text for architecture i386
warning: no rule to process file '/.../Pods/Down/Source/cmark/entities.inc' of type sourcecode.pascal for architecture i386
warning: no rule to process file '/.../Pods/Down/Source/cmark/module.modulemap' of type sourcecode.module-map for architecture i386
warning: no rule to process file '/.../Pods/Down/Source/cmark/case_fold_switch.inc' of type sourcecode.pascal for architecture x86_64
warning: no rule to process file '/.../Pods/Down/Source/cmark/COPYING' of type text for architecture x86_64
warning: no rule to process file '/.../Pods/Down/Source/cmark/entities.inc' of type sourcecode.pascal for architecture x86_64
warning: no rule to process file '/.../Pods/Down/Source/cmark/module.modulemap' of type sourcecode.module-map for architecture x86_64
@iwasrobbed
Copy link
Collaborator

Hi @bajtyngier 👋 What version of Xcode and CocoaPods are you using? I am not seeing these warnings in a sample project using Xcode 9.3 on the latest Down v0.5.2 (but I haven't tried w/ a macOS app)

These files are licenses, build files and a framework module header so they were included with a purpose

@iwasrobbed
Copy link
Collaborator

Closing due to no response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants