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

[SR-7690] SwiftPM does not print any warnings which is must be emitted at all during build plan including message about pkg-config provider hinting feature #4816

Closed
omochi opened this issue May 15, 2018 · 3 comments
Labels

Comments

@omochi
Copy link
Contributor

omochi commented May 15, 2018

Previous ID SR-7690
Radar rdar://problem/40260898
Original Reporter @omochi
Type Bug
Status Closed
Resolution Done
Environment

macOS High Sierra version 10.13.4
iMac (retina 4K, 21.5-inch, 2017)
Xcode 9.3

Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Bug
Assignee None
Priority Medium

md5: b7f9f5a07573f0cdd6825d07182a7cb7

Issue Description:

SwiftPM does not print any warnings which is must be emitted at all during `build plan` including message about pkg-config provider hinting feature.

In `Build.BuildPlan.plan`, this object print warning via `delegate.warning`.
It includes pkg-config provider hinting feature which is implemented in SE-0063.
https://github.com/apple/swift-evolution/blob/master/proposals/0063-swiftpm-system-module-search-paths.md

But its `delegate` property is always nil.
So these messages does not be printed at all.

It includes other pkg-config resolving failure information.
It makes very hard to debugging trouble about `Package.swift`.
For example, my other ticket about SwiftPM hit this issue.
SwiftPM suppress these warnings and continue to running complete silently,
so my investigation was very hard.
https://bugs.swift.org/browse/SR-7689

@ankitspd
Copy link
Member

@swift-ci create

@ankitspd
Copy link
Member

#1704

@omochi
Copy link
Contributor Author

omochi commented Aug 23, 2018

Thanks

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants