This maintains proposals for changes and user-visible enhancements to the Swift Programming Language.
This maintains proposals for changes and user-visible enhancements to the Swift Programming Language.
rballard/swift-package-manager 0
The Package Manager for the Swift Programming Language
pull request commentapple/swift-package-manager
Check what compiler flags are available
@swift-ci please smoke test macos
comment created time in 7 hours
pull request commentapple/swift-package-manager
Fix a problem in the logic to generate manifest source from existing parsed manifest structs
@swift-ci please smoke test macos
comment created time in 7 hours
pull request commentapple/swift-package-manager
Pass compiler flags to alllow use of `@main` in single-source-file executable modules
@swift-ci please smoke test macos
comment created time in 7 hours
pull request commentapple/swift-package-manager
[5.4] Enable symlink support explicitly
@swift-ci please smoke test
comment created time in 9 hours
pull request commentapple/swift-package-manager
[5.4] Enable symlink support explicitly
thanks for opening this @stevapple, we will keep an eye out for if/when we do a 5.4 dot release
comment created time in 9 hours
pull request commentapple/swift-package-manager
Handle both SwiftArgParser 0.3.x and 0.4.x output.
@swift-ci test
comment created time in 9 hours
PR opened apple/swift-package-manager
pr created time in 9 hours
pull request commentapple/swift-package-manager
Android: add cross-compilation flags
Sigh, I made one last formatting change without testing and Python's complaining about that on the CI: I will never understand where line breaks are allowed in Python.
This pull works with the way the SPM build currently builds some release libraries with CMake and most everything else with the bootstrap SPM, but Boris wants to move the SPM build to a full SPM bootstrap. I'm fine with waiting for that change because it will allow me to simplify this pull and remove one of the bootstrap script flags I otherwise need, provided changing the build to SPM only doesn't take months or something.
I will submit a pull for the 5.5 branch once this is in.
comment created time in 10 hours
pull request commentapple/swift-package-manager
Check what compiler flags are available
@swift-ci please smoke test
comment created time in 10 hours
pull request commentapple/swift-package-manager
Pass compiler flags to alllow use of `@main` in single-source-file executable modules
@swift-ci please smoke test macos
comment created time in 10 hours
pull request commentapple/swift-package-manager
Fix a problem in the logic to generate manifest source from existing parsed manifest structs
@swift-ci please smoke test macos
comment created time in 10 hours
PR opened apple/swift-package-manager
Enable symlink support explicitly
This is a cherry-pick of commit 5f80bd7 from main.
Motivation:
enable git symlink support for Windows
Modifications:
pass core.symlinks=true to git clone operations
Result:
repositories cloned by SwiftPM will have core.symlinks set to true
pr created time in 12 hours
pull request commentapple/swift-package-manager
[SE-0301] Package Editor Commands Implementation
Now that 5.5 has branched, this should be ready to merge. I attempted to rebase it, but there have been too many changes in the last 6 months so I wasn't able to preserve the history. I can break it up again into separate PRs if needed
Thanks, @owenv. I don't think there's any need to break it into separate PRs. I'll review again and work with you to land in main.
comment created time in 13 hours
pull request commentapple/swift-package-manager
Pass compiler flags to alllow use of `@main` in single-source-file executable modules
@swift-ci please smoke test
comment created time in 14 hours
pull request commentapple/swift-package-manager
Android: add cross-compilation flags
@buttaface please note we have branched 5.5 to release/5.5 so once this is merged we will need a corresponding PR if we need this to be included in 5.5
comment created time in 14 hours
pull request commentapple/swift-package-manager
Android: add cross-compilation flags
@neonichu have your concerns here been addressed and this is ready to be merged?
comment created time in 14 hours
pull request commentapple/swift-package-manager
Android: add cross-compilation flags
@swift-ci please smoke test
comment created time in 14 hours
pull request commentapple/swift-package-manager
Fix a problem in the logic to generate manifest source from existing parsed manifest structs
@swift-ci please smoke test
comment created time in 14 hours
Pull request review commentapple/swift-package-manager
Fix a problem in the logic to generate manifest source from existing parsed manifest structs
class ManifestSourceGenerationTests: XCTestCase { try testManifestWritingRoundTrip(manifestContents: manifestContents, toolsVersion: .v5_3) } + func testPackageDependencyVariations() throws {+ let manifestContents = """+ // swift-tools-version:5.3
I have modified this test to be 5.4 and extended the checking to check for the expected presence of space depending on the tools version.
comment created time in 14 hours
push eventapple/swift-package-manager
commit sha 08b69abe3b1541c5c7e63d100447a0859be7ad03
Generalize MiscellaneousTests.testOverridingSwiftcArguments() to be architecture-neutral (#3414) (#3416) This unit test was already specific to macOS, and this fix doesn't change that; what it does is to make the architecture the same as the host. The old hardcoding of x64_64 seems to work on the desktop even on Apple Silicon, but does not appear to work in CI. This also fixes the use of 10.20 as a hypothetical future macOS release. It also renames the test to reflect the apparent intent of the test. rdar://76770888 (cherry picked from commit 6eae39c591fb9937bbb5890f4564c070b8c4b78b)
push time in 14 hours
PR merged apple/swift-package-manager
This is the 5.5 nomination of a fix of a unit test. Please see https://github.com/apple/swift-package-manager/pull/3414 for details.
pr closed time in 14 hours
push eventapple/swift-package-manager
commit sha f7337ec8e1fef86a419af4c08e7bcc4020b4bdb6
Mark the SwiftPM produced by the 5.5 branch as a release build (#3413) Among other things this disables the use of 999.0 as a valid package tools version.
push time in 14 hours
PR merged apple/swift-package-manager
Mark SwiftPM binaries produced from the 5.5 branch as release instead of development binaries. Among other things this disables the use of 999.0 as a valid package tools version.
Motivation:
This is done for every release branch once it has been created. As this change is only made on the release branch, main continues to be marked as a development branch.
Modifications:
- change a boolean flag in SwiftPM
pr closed time in 14 hours
pull request commentapple/swift-package-manager
Fix experimental-api-diff command and add a test
thanks for your patience @owenv. 5.5 was just branched this weekend so we are finally ready to take this, @neonichu can work with you to land
comment created time in 15 hours
pull request commentapple/swift-package-manager
Use forwarding symlinks to reduce toolchain installation size
thanks for your patience @krzyzanowskim. 5.5 was just branched this weekend so we are finally ready to take this, @abertelrud can work with you to land
comment created time in 15 hours
pull request commentapple/swift-package-manager
[SE-0301] Package Editor Commands Implementation
thanks for your patience @krzyzanowskim. 5.5 was just branched this weekend so we are finally ready to take this, @abertelrud can work with you to land
comment created time in 15 hours
pull request commentapple/swift-package-manager
Refactor global verbosity value to parameters
thanks for your patience @krzyzanowskim. 5.5 was just branched this weekend so we are finally ready to take this. would you like to rebase, or do you prefer someone take this over / close and re-do, etc?
comment created time in 15 hours
pull request commentapple/swift-package-manager
(WIP) allow custom override path when searching for `Package.swift` manifest file
@kelvin13 Is this ready for review, or do you have any questions about how to proceed to get it ready?
comment created time in 15 hours
PR closed apple/swift-package-manager
It's more practical for SwiftPM to create the parent directory for a package as opposed to having the user mkdir, cd, and then finally initialize their package.
We turn this:
$ mkdir MyPackage
$ cd MyPackage
$ swift package init
Into this:
$ swift package init --name MyPackage
pr closed time in 15 hours