-
Notifications
You must be signed in to change notification settings - Fork 97
Update macro usage bookkeeping when replacing a target with a dynamic variant #90
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
Conversation
@swift-ci test |
I gave this a try on my real world project and unfortunately Xcode doesn't get very far before a crash in I've attached it below, am I able to provide any other information that might help nail down the cause?
|
@Brett-Best when built in debug mode, there are a few parts of the macro evaluation subsystem which can overflow the stack due to a missing tail call optimization on larger projects. I expect a release build wouldn't hit that crash. |
I'm not sure if it's possible but the little plugin that launches Xcode, it would be good if that could be configured to do release builds. I'll do it manually and invoke the same set of commands and get back to you! Appreciate the PR and responses! |
Confirmed that this PR fixes the issue we were facing and building in release fixes the crash above. TYSM! |
@swift-ci please test macOS |
Was suggested in #90 (comment) and I think it makes sense since the main use case of the plugin is probably to test "real" projects which are more likely to not work in debug builds.
@swift-ci test macOS |
Was suggested in #90 (comment), this adds support for `--release` and `--configuration release` to switch to release config.
Was suggested in #90 (comment), this adds support for `--release` and `--configuration release` to switch to release config.
Previously, we failed to update swiftMacroImplementationDescriptorsByTarget, targetsRequiredToBuildForIndexing, and targetsWhichShouldBuildModulesDuringInstallAPI when doing this replacement.
Resolves #73