-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Macro] Precise macro plugin dependency during scanning #76732
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
[Macro] Precise macro plugin dependency during scanning #76732
Conversation
@swift-ci please smoke test |
Please test with following PR: @swift-ci please smoke test |
Please test with following PR: @swift-ci please smoke test |
ping |
1 similar comment
ping |
@rintaro you know the plugin infrastructure better than anyone |
@rintaro ping |
Add flag `-load-resolved-plugin` to load macro plugin, which provides a pre-resolved entry into PluginLoader so the plugins can be loaded based on module name without searching the file system. The option is mainly intended to be used by explicitly module build and the flag is supplied by dependency scanner.
Teach dependency scanner to construct build commands using resolved plugin search path option. This ensures the modules that do not have access to the macro plugins will not have a different variant due to different plugin search path. rdar://136682810
cc01e02
to
2d204f8
Compare
Please test with following PR: @swift-ci please smoke test |
Rebase the change and update the test to test the interaction between new options with the other options. |
@rintaro review feedback addressed. |
Teach dependency scanner to track precise dependencies for macro plugin:
This also means if a macro plugin search path is not used, it will not cause an additional module variants due to the search path difference.
rdar://136682810