Skip to content

Adapt QNX support to the introduction of LINKER_DRIVER #398

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jakepetroules
Copy link
Collaborator

No description provided.

@jakepetroules
Copy link
Collaborator Author

I'm not thrilled with how QNX leaks out of its plugin. I think LINKER_DRIVER can't be an enum and this has to be done in a somewhat more flexible way instead. Any particular ideas?

Maybe LINKER_DRIVER can be a plain string, and we set it to clang by default in Settings.swift. For LD_OPTIMIZATION_LEVEL I think we need something like LINKER_DRIVER_IS_GCC_COMPATIBLE and maybe an extension point that returns a list of gcc-compatible linker drivers?

@dschaefer2
Copy link
Member

I'm not thrilled with how QNX leaks out of its plugin.

I'm not thrilled swift-build needs to know about QNX. I look forward to adding it to the Swift SDK story and how swift-build can deal with new platforms it's never heard about :).

@jakepetroules
Copy link
Collaborator Author

jakepetroules commented Apr 11, 2025

We'll see. Swift SDKs can only go so far, even the compiler has to have knowledge of specific platforms to a certain point.

Keep in mind part of the motivation here is to identify what sort of things actually need to become configurable to support various different platforms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants