feat: xcodebuildlog2sil #86
Open
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.
Hey.
Sorry for the large amount of changes 😅.
1. Use one folder and Package.swift for all targets.
If you want to build just one target it's still easy, because
swift
CLI have the--target
parameter.swan-xcodebuildlog2sil
I can't use
swan-xcodebuild
because it overrides code signing in my project and brakes build.On my side when xcodebuild command executed it executed with a pipe
| tee xcodebuld.log | xcbeautify
, so I have logs.What I needed is to convert logs to sil, so I created a new target
swan-xcodebuildlog2sil
which does the conversion.Since there was a clear code duplication between
swan-xcodebuild
andswan-xcodebuildlog2sil
I put log parsing and SIL sections saving logic in a shared lib SwanSwiftBuildLogParser.If it's too much, I'm open to suggestion on how to split it.