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

Simpler API for carthage build --no-skip-current #1411

Closed
3lvis opened this Issue Jul 31, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@3lvis
Contributor

3lvis commented Jul 31, 2016

  • carthage version: 0.16.2
  • xcodebuild -version: Xcode 7.3.1 Build version 7D1014
  • Are you using --no-build? No
  • Are you using --no-use-binaries? No
  • Are you using --use-submodules? No

Feature request:

I have to Google every single time I use carthage build --no-skip-current is there a simpler API for carthage build --no-skip-current? Something more memorable like:

carthage build --archive

So then I can do

carthage archive

Or maybe

carthage archive --building, so I can skip the build command?

Thanks for your help.

@mdiep mdiep added the enhancement label Aug 2, 2016

@mdiep

This comment has been minimized.

Member

mdiep commented Aug 2, 2016

carthage help build might be helpful. ☺️

But I do think it'd be worth adding a variant that both builds and archives. carthage build --archive makes sense to me. Want to open a pull request? 😄

@3lvis

This comment has been minimized.

Contributor

3lvis commented Nov 2, 2017

Tried looking into this but it's quite difficult, I get an error in currying the BuildCommand inside the method evaluate.

Binary operator '<|' cannot be applied to operands of type 'CommandMode' and 'Argument<[Any]>'

https://github.com/3lvis/Carthage/tree/add-archive-option-to-build

@mdiep

This comment has been minimized.

Member

mdiep commented Nov 5, 2017

I think you just need to change defaultValue: nil to defaultValue: false. Since public let archive: Bool, nil isn't a valid value. This causes type inference to fail, leading to the unhelpful error that you shared above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment