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-1169] SwiftPM does not support Xcode project generation for system packages #5463

Closed
swift-ci opened this issue Apr 6, 2016 · 3 comments
Assignees
Labels

Comments

@swift-ci
Copy link
Contributor

swift-ci commented Apr 6, 2016

Previous ID SR-1169
Radar None
Original Reporter paulofaria (JIRA User)
Type Bug
Status Resolved
Resolution Done

Attachment: Download

Additional Detail from JIRA
Votes 1
Component/s Package Manager
Labels Bug
Assignee @aciidb0mb3r
Priority Medium

md5: 43eab0fe11fa0e3134b2edf88b3d51e7

Issue Description:

The command swift build -X doesn't work for system packages.

For example:

git clone https://github.com/Zewo/OpenSSL
cd OpenSSL
swift build -X

Now open OpenSSL.xcodeproj. Build will fail.
To make it work we need to add some configurations manually:

/usr/local/include in Build Settings > Search Paths > Header Search Paths
/usr/local/lib in Build Settings > Search Paths > Library Search Paths

I think the solution would be to support:

swift build -X -Xcc -I/usr/local/include -Xlinker -L/usr/local/lib

Which would add the correct paths to Xcode configuration automatically.
This also makes sense cause this is the command needed to actually build the module.

swift build -Xcc -I/usr/local/include -Xlinker -L/usr/local/lib

CC: @ddunbar

Edit: I think #235 is needed to reproduce.

@ddunbar
Copy link
Member

ddunbar commented Apr 6, 2016

CC @mxcl

@mxcl
Copy link
Contributor

mxcl commented Apr 7, 2016

I guess we better support this.

@ankitspd
Copy link
Member

Fixed by #306

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 5, 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

4 participants