-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
IPHONEOS_DEPLOYMENT_TARGET
not followed for some object files
#137326
Comments
Those object files are part of the precompiled compiler-builtins crate. They probably need to be compiled with |
Good, I'm trying to validate this but so far I didn't find the usage of the compiler-builtins crate, I've tryied the command cargo tree output
I know that some of those crates can use the compiler-builtins, like the bitflags crate, but is an optional dependency, so I can say for shure if the compiler-builtins is or isn't in use. There is another way to check its usage? And what crate is using it? If I knew this I can compile the dependency if the right iOS target. edit: forgot to put the output in a code block |
Compiler-builtins is a part of the standard library which is shipped in precompiled form with rustc. |
I can be wrong but this way how compiler-builtins is shipped with rustc looks like a core part of the compiler, not being easy to change, right? I'm thinking how I can circunvent this issue for now, maybe downgrade the compiler version to a older one that compile with the iOS target that I need or compile everything (compiler-builtins + rustc) by myself and compile the project with it. Any of these solutions would work? |
If you are using nightly, you can use |
I'm developing a internal SDK and I have to build it for iOS:
I expected the static library output would follow the
IPHONEOS_DEPLOYMENT_TARGET
all the way through when checking withotool
:Expected output
Instead, some object files were compile with a different IOS target version (
17.2
) as we can see in theminos
ofLC_BUILD_VERSION
:Actual output
In total 1578 but only 145 had these behavior of setting the
minos 17.2
. Is this behavior expected?Meta
rustc --version --verbose
:Addtional information that can be relevant:
bindgen
(ref)#129432
#53808
The text was updated successfully, but these errors were encountered: