Swift package manager plugins allow us to customize some actions during build time to meet more complex compilation requirements, such as code generation.
Swift package manager plugins allow us to customize some actions during build time to meet more complex compilation requirements, such as code generation.
Compared with Xcode project’s Build Settings, Package.swift is much simpler to use. However, when we convert a Xcode framework project into a Swift package, the XCFramework cannot be built successfully.
Swift 5.5 introduces Swift concurrency. It allows us to write asynchronous code in synchronous mechanism. Greatly reduce the complexity of asynchronous code.
When developing a project, we need to build multiple versions, and each version will have individual environment settings. For example, the development version connects to the development server, and the QA version connects to the QA testing server.
Swift packages are reusable code components. It can contain not only code, but also binary XCFrameworks. Distributing XCFrameworks can protect source code.
After having modularized a project, the project is divided into an app project or a framework project, and several Swift packages. We can easily manage these sub-projects with Xcode workspaces.
Swift Packages are reusable code components. In addition to adding other Swift package dependencies to Swift packages, we can also add Swift package dependencies to Xcode projects.
Swift packages are reusable code components. It can contain code, binaries, and resource files. We can easily use Swift packages in our app projects. This article describes how to build and publish Swift packages.