Support build action by adding the --action
option in the command.
#2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes we want to use
xcodebuild build ...
insteadxcodebuild archive ...
, because artifacts generated byxcodebuild build ...
contain more debug information. For example:.swiftsourcefile
will only be generated when invoked by thexcodebuild build ...
command.The xcframework of Alamofire generated by the
swift-create-xcframework --platform ios --action build --xc-setting OTHER_SWIFT_FLAGS="-debug-prefix-map $PWD=." Alamofire
command are as below:Output of
swift-create-xcframework --platform ios --action archive --xc-setting OTHER_SWIFT_FLAGS="-debug-prefix-map $PWD=." Alamofire
command are as below(no.swiftsourceinfo
file):The
.swiftsourceinfo
file can be used to jump to the definition in the source code. Our team usually compiles third-party modules from source code to XCFramework to reduce compile time, and we also want to retain the ability to jump source code by clicking a property or class. Therefore we implemented--action
option to configure the action used byxcodebuild
insideswift-create-xcframework