[swift-build-dev] [swift-users] Importing C system libraries

[Kelvin Ma]

CLI’s are nothing to be afraid of :) tbh I find XCode much more difficult
to work with than files and command line invocations.

On Mon, Mar 27, 2017 at 4:16 PM, Michael Ilseman <milseman at apple.com> wrote:

> I don’t know what you’re referring to, but my solution also works for
> pre-open-source versions of Swift.
>
> > On Mar 27, 2017, at 2:10 PM, Jan Neumüller <nasan at slayers.de> wrote:
> >
> > Is it just me, or is Swift moving to much in a command line direction
> since the open sourcing? I feel being left behind as an Xcode user...
> >
> > Jan
> >
> >> On 27 Mar 2017, at 22:59, Michael Ilseman via swift-users <
> swift-users at swift.org> wrote:
> >>
> >> Sure. At a low level, you can create a module.map file and use -L/-l
> flags in your invocation of Swift. If you want to do so at a higher level,
> then perhaps SwiftPM can. CCing swift-build-dev for the SwiftPM part.
> >>
> >>
> >>> On Mar 26, 2017, at 3:20 PM, Kelvin Ma via swift-users <
> swift-users at swift.org> wrote:
> >>>
> >>> Idk if this has been asked before, but is there a way to import C
> libraries into a Swift project without creating a local git repo?
> Preferably something similar to C where you can just `#include` headers and
> then specify the link flags (in Package.swift?)
> >>>
> >>> It’s getting very cumbersome to make a bunch of empty git repos just
> to use libglfw or libcairo.
> >>> _______________________________________________
> >>> swift-users mailing list
> >>> swift-users at swift.org
> >>> https://lists.swift.org/mailman/listinfo/swift-users
> >>
> >> _______________________________________________
> >> swift-users mailing list
> >> swift-users at swift.org
> >> https://lists.swift.org/mailman/listinfo/swift-users
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-build-dev/attachments/20170328/c1349da0/attachment.html>