-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix linker flags for dynamic libraries when executing command plugin #9091
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
base: main
Are you sure you want to change the base?
Conversation
@swift-ci test |
1 similar comment
@swift-ci test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. Could you please add a test to CommandPluginTests in PackageCommandTests.swift that covers this case?
ofc! |
@owenv added, can you run the CI please? |
@swift-ci test |
} | ||
} | ||
|
||
@Test(arguments: getBuildData(for: SupportedBuildSystemOnAllPlatforms)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's ok to wrap this in something like this for now to get to a passing CI run:
withKnownIssue {
} when: {
ProcessInfo.hostOperatingSystem == .windows
|| (ProcessInfo.hostOperatingSystem == .linux && data.buildSystem == .swiftbuild)
}
There are some unrelated issues setting up the runtime library paths on linux for plugin executables which I haven't fixed yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wrapped! thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@owenv can you rerun the CI again, please?
@swift-ci test |
Not sure what the proper process is as this affects both Darwin and Linux, but if possible to cherry-pick this for a future 6.2 it would be fantastic as it would unblock the work in progress for ordo-one/package-benchmark#318 - currently there is no way to do that with a plugin without breaking benchmark users CI. |
@swift-ci test |
@swift-ci test windows |
@owenv @plemarquand not sure what's with the windows build? |
Sorry, missed this - I think a retry may address it @swift-ci test Windows |
Windows seems to be hitting some repeated infra timeout, which should be unrelated to the change here @swift-ci please test Windows |
latest run
looks like the known issue is a little too broad |
removed windows from the known issue, could you run the CI again please? |
I suspect this is still going to fail when the host is Windows and buildSystem == .swiftbuild, but let's give it a try in the meantime @swift-ci test |
ok, fixed the when condition to:
|
@swift-ci test |
just going to assign this to myself so I don't lose track. Thanks for your patience working through the test issues |
@swift-ci test Windows |
No problem, thank you for your assistance! |
The
|
foundation was broken for a few hours yesterday @swift-ci test Windows |
@swift-ci test self hosted |
1 similar comment
@swift-ci test self hosted |
now hitting #9150 |
@swift-ci test |
Add appropriate
-tool
suffix to linker flags in dynamic libraries when executingswift package command_plugin
.Motivation:
Resolves the following issue: #9062
Modifications:
Add appropriate
-tool
suffix to linker flags in dynamic libraries when executingswift package command_plugin
.Result:
Executing
swift package command_plugin
with dynamic dependencies works.