Skip to content
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

[swift2objc] Investigate target triple option #1782

Open
liamappelbe opened this issue Dec 4, 2024 · 0 comments
Open

[swift2objc] Investigate target triple option #1782

liamappelbe opened this issue Dec 4, 2024 · 0 comments
Assignees

Comments

@liamappelbe
Copy link
Contributor

What does this option actually do? It's not being used to resolve Int to Int32/Int64, because we still see Ints in the symbolgraph. Maybe the only important part of the triple is the OS? Or maybe it doesn't do anything at all to the symbolgraph, and only affects the other outputs like the dylib? But if we don't pass this option when extracting a symbolgraph from a precompiled module, we get an error.

Try passing a bunch of different targets, varying CPU, OS (iOS vs macOS vs simulator), and OS version, and diff the json symbolgraphs.

Once we know what effect it has on the output, we can improve the API. If the OS is the only bit that matters, replace the target triple config option with an OS enum. If it has no effect, it should be removed. If it has some other important effect, we should consider generating symbolgraphs for all targets (or perhaps a user selected subset) and merging the symbolgraphs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant