[swift-evolution] [swift-build-dev] [Review] SE-0038 Package Manager C Language Target Support
BAILEYC at uk.ibm.com
Thu Feb 18 15:25:29 CST 2016
Thanks for putting this proposal together - having the ability to build
and link to C dependencies is going to be a huge step forward and this
very much looks like a step in the right direction.
I know there's been some discussion about being able to invoke custom
build targets and/or link to local dependencies. I agree that we don't
want to pre-design the entire solution but iterate in the right direction
and get feedback as we go. One thing we can do is look at some of the
challenges and solutions from other languages.
If we look at Node.js/NPM, as the most used language package manager, it
highlights the high usage of native modules. Most native modules have a
dependency on "nan" which has >6.5M downloads a month and approaching 1000
As an example, one of those dependents is "zmq" (30K+ downloads/month)
which provides Node.js bindings for ZeroMQ. This provides a Node.js
wrapper around the zeromq library (installable via homebrew, apt-get etc).
The NPM approach is that at install/build time, the binding.gyp file can
be configured to check for the presence of the library, and to add the
necessary include and link flags.
I know that supporting that kind of scenario is outside of the scope of
this proposal - is it however a direction we're headed to?
From: Rick Ballard via swift-build-dev <swift-build-dev at swift.org>
To: swift-evolution-announce at swift.org
Cc: swift-evolution <swift-evolution at swift.org>,
swift-build-dev at swift.org
Date: 17/02/2016 02:12
Subject: [swift-build-dev] [Review] SE-0038 Package Manager C
Language Target Support
Sent by: swift-build-dev-bounces at swift.org
Hello Swift community,
A review of “Package Manager C Language Target Support” for the Swift
Package Manager begins now and runs through Monday, February 22th. The
proposal is available here:
Reviews are an important part of the Swift evolution process. All reviews
should be sent to the swift-evolution mailing list at
or, if you would like to keep your feedback private, directly to the
What goes into a review?
The goal of the review process is to improve the proposal under review
through constructive criticism and, eventually, determine the direction of
Swift. When writing your review, here are some questions you might want to
answer in your review:
* What is your evaluation of the proposal?
* Is the problem being addressed significant enough to
warrant a change to the Swift Package Manager?
* Does this proposal fit well with the feel and direction
of the Swift Package Manager?
* If you have you used other package managers with a
similar feature, how do you feel that this proposal compares to those?
* How much effort did you put into your review? A glance,
a quick reading, or an in-depth study?
More information about the Swift evolution process is available at
swift-build-dev mailing list
swift-build-dev at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution