swift-package-manager | The Package Manager for the Swift Programming Language | iOS library

 by   apple Swift Version: 0.6.0 License: Apache-2.0

kandi X-RAY | swift-package-manager Summary

kandi X-RAY | swift-package-manager Summary

swift-package-manager is a Swift library typically used in Mobile, iOS applications. swift-package-manager has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

The Swift Package Manager is a tool for managing distribution of source code, aimed at making it easy to share your code and reuse others’ code. The tool directly addresses the challenges of compiling and linking Swift packages, managing dependencies, versioning, and supporting flexible distribution and collaboration models. We’ve designed the system to make it easy to share packages on services like GitHub, but packages are also great for private personal development, sharing code within a team, or at any other granularity. Swift Package Manager includes a build system that can build for macOS and Linux. Starting with Xcode 11, Xcode integrates with SwiftPM to provide support for including packages in iOS, macOS, watchOS, and tvOS applications. The SourceKit-LSP project leverages libSwiftPM and provides Language Server Protocol implementation for editors that support LSP.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              swift-package-manager has a medium active ecosystem.
              It has 9275 star(s) with 1283 fork(s). There are 388 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 584 open issues and 773 have been closed. On average issues are closed in 233 days. There are 54 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of swift-package-manager is 0.6.0

            kandi-Quality Quality

              swift-package-manager has 0 bugs and 0 code smells.

            kandi-Security Security

              swift-package-manager has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              swift-package-manager code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              swift-package-manager is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              swift-package-manager releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of swift-package-manager
            Get all kandi verified functions for this library.

            swift-package-manager Key Features

            No Key Features are available at this moment for swift-package-manager.

            swift-package-manager Examples and Code Snippets

            No Code Snippets are available at this moment for swift-package-manager.

            Community Discussions

            QUESTION

            Swift Package Manager - Failed to parse the manifest
            Asked 2021-Nov-19 at 10:23

            I'm trying to migrate a CocoaPod to SPM. It should be very simple, but for some reason I keep getting the error "Failed to parse manifest file".

            The repo with the library an be found here: https://github.com/agcoesbenr/RBSManager/tree/swift-package-manager

            ...

            ANSWER

            Answered 2021-Nov-19 at 10:23

            I don't know from where you got only your error message, but it's incomplete. In Terminal.app, if you do $> swift build, you'll get this error:

            Source https://stackoverflow.com/questions/70032847

            QUESTION

            Swift Package Manager, target based dependency
            Asked 2021-Jul-16 at 13:40

            I'm trying to get dependency target based in SPM, I have Package.swift defined here:

            So I have RxSwift defined in package dependencies but it's NOT used in target ReCaptcha but only in target ReCaptchaRx

            What I expected to happen:

            If I choose to select only one target without Rx I expected it to fetch only ReCaptcha dependency and ignore Rx.

            What actually happen:

            After importing only ReCaptcha I'm getting package resolved but unusable, if I choose on import window ReCaptchaRx I'm getting as expected usable Rx what is fine. But why then SPM even fetching and resolving RxSwift in this case?

            Question

            Why Xcode is resolving RxSwift on target that does not have a dependency to it? Can that be prevented? I would expect similar behaviour as with AppSwizzle in this example that if target is not used is not being resolved.

            Source code:

            This is an open source library available here: https://github.com/JakubMazur/ReCaptcha/blob/swift-package-manager/Package.swift

            If you want to checkout this in SPM will resolve package from https://github.com/JakubMazur/ReCaptcha on branch swift-package-manager

            ...

            ANSWER

            Answered 2021-Jul-16 at 13:40

            Basically, Swift Package Manager is not yet sophisticated enough to not resolve all transitive dependencies, even if they are exclusively used by a target you are not depending on.

            While it is clutter that all transitive dependencies show in the Xcode sidebar package dependencies list, I do not believe it implies that your Demo app would actually ship with any of those unused targets/dependencies. It is only clutter in the sense that they show in that sidebar and that they are checked out in cache directories.

            Slightly different: as of SPM 5.2, SPM is smart enough to not download transitive dependencies only used by your dependencies' test targets. Perhaps one day this will be improved to cover the case you ask about as well.

            Source https://stackoverflow.com/questions/68408989

            QUESTION

            The package product 'MyLibrary' cannot be used as a dependency of this target because it uses unsafe build flags
            Asked 2021-Jun-09 at 00:06

            I'm trying to add SPM support for my library. I need to define unsafeFlags for one of my library's targets (In order to import Swift code into Objective-C++):

            ...

            ANSWER

            Answered 2021-Jun-09 at 00:06

            .unsafeFlags are not allowed for dependencies specified with a version. The workaround is to specify the version with a commit hash.

            Detailed discussion and another workaround for monorepos at https://forums.swift.org/t/override-for-unsafeflags-in-swift-package-manager/45273

            Source https://stackoverflow.com/questions/67889931

            QUESTION

            Firebase [Swift Package Manager]: no such module FirebaseRemoteConfig
            Asked 2021-May-30 at 08:16

            After I read the instructions listed here for how to add Firebase as a dependency to a Swift package, I couldn't get it to work, here's my Package.swift manifest:

            ...

            ANSWER

            Answered 2021-May-30 at 08:16

            I figured out the solution, but unfortunately it's not documented on Firebase Docs, I have to add the .platforms array in the Package.swift manifest specifying a version that supports FirebaseRemoteConfig, for example:

            Source https://stackoverflow.com/questions/67758983

            QUESTION

            Symbolicating Swift Package Manager builds
            Asked 2021-May-07 at 21:46

            Swift Package Manager can be a convenient way to build swift projects, and, if you (remove the absolute toolchain @rpath it adds to your binary), you can even distribute its builds.

            But SPM doesn't seem to produce .dSYM debug symbol packages, so how can you symbolicate the crash reports?

            Is there a better way than using swift package generate-xcodeproj and then getting Xcode to create the build and dSYMs, effectively reducing SPM to .xcodeproj shorthand?

            ...

            ANSWER

            Answered 2021-May-07 at 21:46

            UPDATE
            swift build -c release seems to create a dSYM package by default. But if you suddenly decided you wanted your debug build to have dSYMs too, then read on.

            You can get dSYM output from SPM's swift build, by passing -g and -debug-info-format=dwarf to swiftc. To do this from swift build the arguments must each be escaped with -Xswiftc:

            Source https://stackoverflow.com/questions/67441066

            QUESTION

            CoreData Model within Swift Package
            Asked 2021-Apr-07 at 17:27

            I am trying to put a CoreData model into a Swift Package to extract my model code / classes from my main codebase.

            I have done the following to recreate the issue I'm having from scratch:

            • Create a new swift package called SampleModelPackage (File -> New -> Swift Package)
            • Created a Core Data Model Definition File (Create File -> New -> File | iOS -> Core Data -> Data Model)
            • Saved it in the Sources/SampleModelPackage directory alongside the auto-generated SampleModelPackage.swift

            Now - when I attempt to open the Model.xcdatamodelId file in Xcode, it just shows me a "Version" icon (see screenshot), whereas creating a Core Data Model file in a Project or Framework will allow me to edit the model.

            The second / follow up question would be how would I then extend the code-gem'd model files as normal? And how would I load that model definition (normally I would use a Bundle ID and the model file name)

            I have tried adding the model file to the resources array of the Package.swift file (using .process and using .copy) as described on this page: https://developer.apple.com/documentation/swift_packages/bundling_resources_with_a_swift_package

            Or more generally, is this even possible? (this article https://ishabazz.dev/blog/2020/7/5/using-core-data-with-swift-package-manager seems to imply that packaging core data models like this is possible)

            (I am using Xcode 12.4)

            ...

            ANSWER

            Answered 2021-Apr-07 at 17:27

            You need to create your Core Data model in an ordinary Xcode project, then you can create your package and drag the model to it. (This is also what was done in the linked article if you look carefully even though it was not clearly described).

            I believe the the best thing is to manually generate the source code files for your entities and add them to your package. You load the model using Bundle but instead of Bundle.main you use Bundle.module

            Source https://stackoverflow.com/questions/66990642

            QUESTION

            'openssl/arm_arch.h' file not found when integrating Firebase with Swift-Package-Manager
            Asked 2021-Mar-26 at 14:35

            Using Swift-Package-Manager, Swift5.3.2, iOS14.4.1, XCode12.4,

            I am trying to integrate Firebase into my iOS App.

            I use the Swift Package Manager for Firebase (Beta) as described here.

            After successfully integrating most packages from the Firebase selection choice (since I need most of them), I get the following error in Xcode:

            'openssl/arm_arch.h' file not found

            It seems to happen in the File crypto.c of the BoringSSL dependency added by the Firebase dependency. (see screenshot)

            I know the problem has be described before (such as here, here, here and here). However, most of the people use Cocoapods. But in my case, I use the Swift Package Manager. So I open up this question again:

            What do I need to do when Xcode said 'openssl/arm_arch.h' file not found ?

            ...

            ANSWER

            Answered 2021-Mar-26 at 14:35

            Yes, as is referenced in the comments, 7.9.0 was initially a bad release for the Firebase Swift Package Manager distribution. It was fixed and the 7.9.0 repo tag updated but Xcode/SPM caching prevented the new tag from being honored for people rerunning, so we made an equivalent 7.9.1 release to definitively fix the issue.

            Full details at https://github.com/firebase/firebase-ios-sdk/issues/7777

            Source https://stackoverflow.com/questions/66785715

            QUESTION

            How do you archive Swift Package Dependencies to include in your XCFramework for binary distribution as a Swift Package?
            Asked 2021-Feb-19 at 18:02

            Goal is to host a git repo for a Swift Package to distribute proprietary code as a binary in a XCFramework. The source code has dependencies on other Swift Packages. Listing the dependencies in the .package config is not enough. Simply asking consumers to import dependencies is not an option, as they may be making use of the same packages at different levels. The main problem I am trying to solve is how to resolve these dependencies when my Swift Package is imported into a project.

            1. Each dependency package should be archived and wrapped into the XCFramework as well, right?
            2. How would I do that?

            The packages I am using are also available in a CocoaPod as well.

            1. Would it be easier to import them as pods for the purpose of archiving?

            I have gone thru the following resources and SO posts, but can not find answer to this specific purpose.

            ...

            ANSWER

            Answered 2021-Feb-17 at 16:41

            I faced into same issue couple of months ago and haven't found a proper solution so I just started to use Cocoapods for distribution and this script for archiving my framework target which have some Cocoapods as a dependencies:

            Source https://stackoverflow.com/questions/65692618

            QUESTION

            SwiftUI project builds successfully for simulators but Product > Archive fails with errors in a Swift package
            Asked 2021-Feb-11 at 13:10

            I created my first Swift package by following this article on medium and added it to a Swift project. I can build and run the project containing the package (and many other packages) on simulators fine, but Product > Archive generates errors in my Swift package. The errors all seem to suggest that SwiftUI has not been imported, when it has.

            Here's a snippet of the code with a few of the errors:

            ...

            ANSWER

            Answered 2021-Feb-11 at 13:10

            Please add supported platforms to your Package.swift.

            This could look like this:

            Source https://stackoverflow.com/questions/66147965

            QUESTION

            Fail resolve swift package hosted on azure devops in azure pipeline, SSH fingerprint failed to verify
            Asked 2020-Nov-27 at 09:21

            I know this is common question but none of the solution working for me.

            I've a swift package hosted on private repo in azure devops. In pipeline, i've setup task Install SHH key following document with passphrase and locally swift package resolve, authentication success. But in pipeline it fails with message "SSH fingerprint fail to verify".

            I searched a-lot and there are few links below sharing, solution i've tried so far Adding identity to known_host, manually calling swift package resolve.

            https://developercommunity.visualstudio.com/content/problem/1025313/swift-package-manager-the-server-ssh-fingerprint-f.html

            https://discuss.bitrise.io/t/xcode-11-resolving-packages-fails-with-ssh-fingerprint/10388

            https://bonkowski.net/posts/ios-azure-pipeline/

            I'm not sure, is there any way to get detail logs?

            ...

            ANSWER

            Answered 2020-Nov-27 at 09:21

            Resolved, it was because of dev.azure.com it should be ssh.dev.azure.com, while adding host entry to known_hosts.

            Source https://stackoverflow.com/questions/64965930

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install swift-package-manager

            Please use this guide for learning package manager basics.
            The package manager is available as part the Swift toolchains available on Swift.org) including snapshots for the latest versions built from main branch. For installation instructions for downloaded snapshots, please see the Getting Started section of Swift.org. The Swift Package Manager is also included in Xcode 8.0 and all subsequent releases.

            Support

            For Quick Help use the swift package --help command. For documentation on using Swift Package Manager, creating packages, and more, see the documentation directory. For documentation on developing the Swift Package Manager itself, see the contribution guide. For detailed documentation on the package manifest API, see PackageDescription API. For release notes with information about changes between versions, see the release notes.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/apple/swift-package-manager.git

          • CLI

            gh repo clone apple/swift-package-manager

          • sshUrl

            git@github.com:apple/swift-package-manager.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular iOS Libraries

            swift

            by apple

            ionic-framework

            by ionic-team

            awesome-ios

            by vsouza

            fastlane

            by fastlane

            glide

            by bumptech

            Try Top Libraries by apple

            swift

            by appleC++

            foundationdb

            by appleC++

            ml-stable-diffusion

            by applePython

            turicreate

            by appleC++

            darwin-xnu

            by appleC