Skip to content

6.0: [SE-0301] Implement package manifest editing command-line options #7494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

DougGregor
Copy link
Member

swiftlang#7477)

Introduce support for adding a new product to the package manifest,
both programmatically (via PackageModelSyntax) and via the
`swift package add-product` command. Help for this command is:

    OVERVIEW: Add a new product to the manifest

USAGE: swift package add-product <name> [--type <type>] [--targets
<targets> ...] [--url <url>] [--path <path>] [--checksum <checksum>]

    ARGUMENTS:
      <name>                  The name of the new product

    OPTIONS:
--type <type> The type of target to add, which can be one of
                              'executable', 'library', 'static-library',
'dynamic-library', or 'plugin' (default: library)
--targets <targets> A list of targets that are part of this product
      --url <url>             The URL for a remote binary target
      --path <path>           The path to a local binary target
      --checksum <checksum>   The checksum for a remote binary target
      --version               Show the version.
      -h, -help, --help       Show help information.

(cherry picked from commit a408054)
@DougGregor
Copy link
Member Author

@swift-ci please test

@DougGregor
Copy link
Member Author

I'd also like to pick up #7486 in this PR once it's ready

@MaxDesiatov MaxDesiatov changed the title [SE-0301] Implement package manifest editing command-line options 6.0: [SE-0301] Implement package manifest editing command-line options Apr 24, 2024
@MaxDesiatov MaxDesiatov added the swift 6.0 Related to Swift 6.0 release branch label Apr 24, 2024
rintaro and others added 2 commits April 24, 2024 19:05
Also, use `SPMSwiftSyntax::` namespace to avoid potential name conflict
issues.

(cherry picked from commit 4f83c6d)
In the case that a shared copy of swift-syntax is being used to build,
allow the sources to be unavailable. If the user specifies
`SWIFTPM_PATH_TO_SWIFT_SYNTAX_SOURCE`, that will be preferred,
otherwise, we fallback to the upstream git repository.

(cherry picked from commit dbd8945)
@DougGregor
Copy link
Member Author

@swift-ci please test

@DougGregor DougGregor enabled auto-merge (squash) April 25, 2024 02:06
@DougGregor
Copy link
Member Author

@swift-ci please test Windows

@DougGregor
Copy link
Member Author

@swift-ci please test macOS

@DougGregor DougGregor merged commit 470b863 into swiftlang:release/6.0 Apr 25, 2024
5 checks passed
@DougGregor DougGregor deleted the se-0301-package-manifest-editing-6.0 branch April 25, 2024 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
add to change log enhancement package manifests changes to package manifest APIs swift 6.0 Related to Swift 6.0 release branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants