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

Warning 'couldn't find pc file' when using SwiftPM #719

Closed
nkristek opened this issue Dec 27, 2019 · 6 comments
Closed

Warning 'couldn't find pc file' when using SwiftPM #719

nkristek opened this issue Dec 27, 2019 · 6 comments

Comments

@nkristek
Copy link

When importing Starscream version 3.1.1 (currently latest) using SwiftPM I get the warning couldn't find pc file. I tried version 3.1.1 and master branch, when using 3.1.0, the warning does not appear.

Steps to reproduce

  • create new iOS project (File > New > Project > iOS > Single View App)
  • add SwiftPM dependency (File > Swift Packages > Add Package Dependency...), select either exact version 3.1.1 or branch master
  • build
@patburns
Copy link

patburns commented Mar 3, 2020

Also have this warning. It's because of this issue in swift-nio-zlib-support:

apple/swift-nio-zlib-support#3

Of which starscream currently depends on.

@patburns
Copy link

patburns commented Mar 4, 2020

I commented in the other two threads. I don't have the context on why streamscreeam uses swift-nio-zli-support, but you can "silence" this warning by installing pkg-config on the device that you are compiling on:

brew install pkg-config

This really isn't a fix but a workaround. Maybe it should be considered adding this to the documentation for this project? Or maybe evaluated how swift-nio-zli-support is being used?

@nkristek
Copy link
Author

nkristek commented Mar 6, 2020

Thank you for that workaround

@yspreen
Copy link

yspreen commented May 22, 2020

Two and a half months later and it's still an issue... Do I really have to add this to the common issues page of our project? Or is there a proper fix?

@yspreen
Copy link

yspreen commented May 22, 2020

Since 3.1.0 does not have this issue, is there any crucial functionality missing from the latest version?

@nkristek
Copy link
Author

This issue seems to come from swift-nio. Thus I will close this issue, thanks!

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

3 participants