Building for iOS / iphonesimulator

[TheVitya]

Hello,

First of all, I want to say that I really like the project; it’s incredibly helpful to me.

I am trying to build a simple library using the Xcode generator. I haven’t seen any remarks or notices suggesting that corrosion does not support this setup.

However, when I try to build it using the build.sh script, I encounter a "Permission Denied" error. The same error occurs when I attempt to build it directly in Xcode.

I suspect this issue might be related to the combination of Xcode and Cargo because running the scripts manually from the terminal does not result in the same error.

I’m not sure what else to try at this point, as I’ve explored nearly every idea that came to mind.

I would greatly appreciate it if you could point me in the right direction to resolve this issue.

Thank you in advance for your help!

Repo: https://github.com/TheVitya/corrosion

[jschwe]

Do you have the same problem when using Xcode and building for mac?
Corrosion does test in CI that using the XCode Generator works, but I'm not sure if anyone has used corrosion to build for iOS before.

[TheVitya]

Yes, mac works, from Xcode and also using the build script. I have added the mac build lines to the build.sh file.

[TheVitya]

The initial error seems to be fixed, the generated SDKROOT was a bit faulty, but I think that was my fault. Now when I am trying to build it I get the following error: ld: library 'System' not found. I have seen that there is a related issue to that, but the paths that are mentioned there seems good. I think you would get the same error if you try it, the repo is updated.

cmake: 3.31.2
cargo: 1.83.0
mac: 14.5 (23F79)
rustc: 1.83.0

[jschwe]

I currently don't have any time to investigate this myself, but PRs are welcome. As I mentioned, I'm not aware of anyone using corrosion for iOS development right now, so this might require some investigation.

ld: library 'System' not found

You might need to do something similar as here for MacOS < 13 and set LIBRARY_PATH.

[TheVitya]

I have compared what env variables do I have when Xcode runs the generated commands and what I have when I run it from the terminal directly. I have noticed that one PATH variable was missing, after adding it to the corrosion commands (cxx-bridge + build) it seems to be working fine. Not sure if it is Xcode config related issue or not, but it works :)

I will dedicate some time to check other solutions, just let me know if somebody also facing the same issue when running the build script here, or this happens only for me.

Xcode: 16.1
cmake: 3.31.2
cargo: 1.83.0
mac: 14.5 (23F79)
rustc: 1.83.0

[jschwe]

The usual way to set environment variables is to put the VAR=value after the ${CMAKE_COMMAND} -E env.
In this case it probably doesn't matter though.

Can you check what ${PATH} is set to by default in your shell and try to bisect which is the problematic entry in your PATH?