Skip to content

Added option to enable CMake Install #2907

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

Merged
merged 1 commit into from
Sep 4, 2020

Conversation

gmittert
Copy link
Contributor

@gmittert gmittert commented Sep 3, 2020

Since SwiftPM does its own installation using the bootstrap script, it
hides the CMake install target to only be enabled on Windows which
doesn't use the bootstrap script. But when bootstrapping using CMake on
non Windows platforms, it would be nice to be able to enable them.

Since SwiftPM does its own installation using the bootstrap script, it
hides the CMake install target to only be enabled on Windows which
doesn't use the bootstrap script. But when bootstrapping using CMake on
non Windows platforms, it would be nice to be able to enable them.
@gmittert
Copy link
Contributor Author

gmittert commented Sep 3, 2020

@swift-ci please test

@gmittert
Copy link
Contributor Author

gmittert commented Sep 3, 2020

@swift-ci please smoke test

@neonichu
Copy link
Contributor

neonichu commented Sep 3, 2020

Yep, I think @compnerd mentioned that he also wanted this for the Windows port.

(great branch name btw)

@neonichu
Copy link
Contributor

neonichu commented Sep 3, 2020

macOS failure seems unrelated:

Build timed out (after 45 minutes). Marking the build as failed.

@neonichu
Copy link
Contributor

neonichu commented Sep 3, 2020

@swift-ci please smoke test macOS

@neonichu
Copy link
Contributor

neonichu commented Sep 3, 2020

  • Multiple (2) Option or Flag arguments are named "--enable-code-coverage".

That sounds as if it could be related to recent argparser changes, but not sure why it wouldn't have shown up so far.

@neonichu
Copy link
Contributor

neonichu commented Sep 3, 2020

Can definitely reproduce locally with swift test --parallel and this assertion is coming from ".../.build/checkouts/swift-argument-parser/Sources/ArgumentParser/Parsable Types/ParsableArguments.swift".

@natecook1000 would you be able to take a look?

@natecook1000
Copy link
Member

I'm seeing this in master with ArgumentParser version 0.3.1, as well — looks like it's an actual ambiguity that the new version diagnoses between these two declarations:

https://github.com/apple/swift-package-manager/blob/master/Sources/Commands/SwiftPackageTool.swift#L543-L546
https://github.com/apple/swift-package-manager/blob/master/Sources/Commands/Options.swift#L191-L193

Quickest way to resolve is to version lock ArgumentParser at 0.3.0, but ultimately it'd be great to resolve that ambiguity (there are probably way too many things declared in SwiftOptions).

neonichu added a commit to neonichu/swift-package-manager that referenced this pull request Sep 4, 2020
Version 0.3.1+ triggers an assertion, so we pin the previous version
until we can investigate this further.

swiftlang#2907 (comment)
neonichu added a commit that referenced this pull request Sep 4, 2020
Version 0.3.1+ triggers an assertion, so we pin the previous version
until we can investigate this further.

#2907 (comment)
@neonichu
Copy link
Contributor

neonichu commented Sep 4, 2020

@swift-ci please smoke test

@neonichu neonichu merged commit eca7824 into swiftlang:master Sep 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants