Re: [swift-users] Incorrect Fisher-Yates shuffle in example code

Thank you for working on this! On Sun, Dec 17, 2017 at 11:07 PM, Saagar Jha via swift-users < swift-users@swift.org> wrote: > > Saagar Jha > > On Dec 17, 2017, at 22:24, Nevin Brackett-Rozinsky via swift-users < > swift-users@swift.org> wrote: > > …well that was more complicated than I anticipate

Re: [swift-users] Wrapping ImageMagick in a Swift Package

Hi Toni, You're not supposed to build the system module package (because there is nothing to build). Tag and add this package as a dependency and then try to import the `TestPkg` module that you defined in the modulemap. The error here is bogus and is tracked by https://bugs.swift.org/browse/SR-53

Re: [swift-users] SwiftPM on Linux Failed

Thanks for the detailed info. I was able to reproduce this. There seems to be some problem with importing modules without their swiftdoc in Ubuntu 14.04. I've filed https://bugs.swift.org/browse/SR-5800 > On 30-Aug-2017, at 1:26 PM, adelzh...@qq.com wrote: > > export SWIFT_HOME=/opt/swift/4.0-d

Re: [swift-users] SwiftPM on Linux Failed

Hey, Can you post the steps you followed to install the Swift toolchain? Also, can you post the output of: $ swift build -v Thanks! On Tue, Aug 29, 2017 at 8:14 PM, adelzhang via swift-users < swift-users@swift.org> wrote: > > Hi, everyone. > > Installing swift on linux is not that easy. Follo

Re: [swift-users] SwiftPM manual dependency management

> On 22-Jul-2017, at 3:37 PM, Geordie Jay wrote: > > > Geordie J mailto:geo...@gmail.com>> schrieb am Fr. 21. > Juli 2017 um 14:39: > Hi Ankit, thanks for your reply. > >> Am 21.07.2017 um 07:33 schrieb Ankit Aggarwal via swift-users >> mailto:swift-u

Re: [swift-users] SwiftPM manual dependency management

+swift-build-dev > On 21-Jul-2017, at 6:09 PM, Geordie J wrote: > > Hi Ankit, thanks for your reply. > >> Am 21.07.2017 um 07:33 schrieb Ankit Aggarwal via swift-users >> mailto:swift-users@swift.org>>: >> >> >> >> On Th

Re: [swift-users] SwiftPM manual dependency management

On Thu, Jul 20, 2017 at 10:34 PM, Geordie J via swift-users < swift-users@swift.org> wrote: > Hi all, > > My team and I are trying to use SwiftPM to develop a relatively complex > app with multiple dependencies, all of which are being developed locally > and in parallel. The reason for this is com

Re: [swift-users] "swift package describe" performs fetch

Hi Toni, This looks like a bug, can you file a JIRA at bugs.swift.org? On Thu, Apr 6, 2017 at 9:10 PM, Toni Suter via swift-users < swift-users@swift.org> wrote: > Hi everyone, > > I would like to obtain detailed information about a package and all its > dependencies in an automated fashion. At

Re: [swift-users] Package Manager and iOS apps

Hi Tim, You can read about plan for supporting iOS here and SwiftPM 4 roadmap here . You can write your package in a way that it

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

Yep, we need to have better support for system packages. Unfortunately it is not covered in the Swift 4 Package Manager roadmap , but community driven proposal are always welcomed! > On 30-Mar-2017, at 12:25 AM

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

I agree that libressl isn't a good example because of the security questions it raises, but libYAML is a good self contained package IMO. With custom targets layout proposal, the forks can be replaced by submodules. The problem with apt-get approach is, it takes away the "portability" from the p

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

> On 29-Mar-2017, at 11:22 AM, kelvinsthirt...@gmail.com wrote: > > I figured that was the intention, but we can’t be too surprised that everyone > is maintaining personal modulemap repositories (and polluting search results > — just try googling for a Swift PNG library!), especially when this

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

I think the idea was that there will be one such repository which other packages can use, that too only until the system libraries start shipping their standard modulemap. I thought we had this written down in our documentation somewhere but couldn't find it. Maybe Daniel can expand on this. On W

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

In this case, these are just umbrella headers. If your modulemap contains absolute path to the header, then you don't need the header files, but SwiftPM will probably warn about this. Note that this is a "hack" to have system packages inside a single repository. The correct way is to have system

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

Hi, Apologies for not replying to this earlier. You can have multiple targets in a single package. Each target can either be Swift or C-family. The type of target is determined by the sources contained in it (*.c/*.cpp etc means C target, *.swift means Swift target). So if you want to create mult

Re: [swift-users] using "swift build" with code that depends on frameworks

Hi, Yep the ordering was fixed in this PR: https://github.com/apple/swift-package-manager/pull/715 SwiftPM will offer build settings in future to handle this properly. On Tue, Jan 31, 2017 at 11:05 PM, Aaron Bohannon via swift-users < swift-users@swift.org> wrote: > I am trying to compile code f

Re: [swift-users] SwiftPM package naming question

Feel free to send a sample package you're having issue with! On Mon, Jan 30, 2017 at 1:47 PM, David Sweeris via swift-users < swift-users@swift.org> wrote: > > On Jan 29, 2017, at 11:56 PM, Ankit Aggarwal > wrote: > > The package manager will pick name from manifest if the sources are inside > S

Re: [swift-users] SwiftPM package naming question

The package manager will pick name from manifest if the sources are inside Sources directory or in the root directory. Documentation here: https://github.com/apple/swift-package-manager/blob/ master/Documentation/Reference.md#module-format-reference On Mon, Jan 30, 2017 at 9:48 AM, David Sweeris

Re: [swift-users] SwiftPM package naming question

The package manager will pick name from manifest if the sources are inside Sources directory or in the root directory. Documentation here: https://github.com/apple/swift-package-manager/blob/ master/Documentation/Reference.md#module-format-reference On Mon, Jan 30, 2017 at 9:48 AM, David Sweeris

Re: [swift-users] System Modules and pkgConfig

In tls+Swift.h, you already have included the tls.h so you shouldn't need to specify this line `header "/usr/local/opt/libressl/include/tls.h"` at all in the modulemap. > On 29-Dec-2016, at 1:18 AM, Etan Kissling via swift-users > wrote: > > Addition: > > Example system module as I have it n

Re: [swift-users] SwiftPM: import ncurses -> conflicting types

ncurses is already present in the macOS sdk, so you don't need to install it via brew. In CNCurses package, create a file called "shim.h": $ cat shim.h #include "ncurses.h" and change the modulemap to this: $ cat module.modulemap module CNCurses [system] { header "shim.h" link "ncurses" e