Added support for derivedDataPath.#1143
Added support for derivedDataPath.#1143mdiep merged 1 commit intoCarthage:masterfrom bartoszj:derivedData
Conversation
| return create | ||
| <*> m <| Option(key: "configuration", defaultValue: "Release", usage: "the Xcode configuration to build") | ||
| <*> m <| Option(key: "platform", defaultValue: .All, usage: "the platforms to build for (one of ‘all’, ‘Mac’, ‘iOS’, ‘watchOS’, 'tvOS', or comma-separated values of the formers except for ‘all’)") | ||
| <*> m <| Option(key: "derived-data", defaultValue: "", usage: "path to the custom derived data folder") |
There was a problem hiding this comment.
This default value should be nil and derivedDataPath should be String?.
There was a problem hiding this comment.
When I use nil and String I receive an error:
Missing argument for --derived-data
According to the specification:
If this is nil, this option is always required.
Is there any workaround for this, or maybe I'm doing something wrong?
There was a problem hiding this comment.
I'll take another look and get back to you. Sorry!
There was a problem hiding this comment.
As it stands, Commandant doesn't support that. I've opened a PR that would make it possible. Let's give it a few days to see what comes of that.
|
Thanks for the pull request! I left a few notes that will require some changes. Leave a comment when you've addressed them and I'll take another look. |
|
@mdiep |
|
I've updated my code to use |
|
That's great! Thanks for updating it and for being patient! |
2 participants
Hi,
I've added support for
-derivedDataPathoption forxcodebuild. With this option it would be possible to separate derived data folders between e.g. Jenkins jobs, or users could select own derived data folder and remove it after the frameworks have been built.