![]() ![]() As I understood it, there's a potential for file conflicts when building multiple crate types at a time? I would rather have an open issue about fixing that as a known limitation, rather than an open issue to enable shared library building. ![]() I'd be glad to help with a pull request, but I don't see how much work would be required beyond the patch I'm already doing on my own distribution. I hope this can help others stuck in the same situation. I can now finally build Rust shared libraries for iOS, after years waiting for an upstream fix. ![]() & "./$/install.sh" "-prefix=$ToolchainPrefix" $DirName = $FileName -Replace ".tar.xz","" New-Item -ItemType Directory -Path $DownloadPath | Out-Null New-Item -ItemType Directory -Path $ToolchainPrefix | Out-Null $ToolchainPrefix = Join-Path $RustupToolchains "prebuilt" $RustupToolchains = Resolve-Path "~/.rustup/toolchains" The static libraries also don't necessarily trim unused code paths, so they're really what's the next move? As you can understand, static linking for iOS is very annoying as it means special treatment for one platform, but also the inability to easily ship libraries in packages built separately without symbol conflicts. I've been blocked on this for a while, we have a growing number of Rust libraries that we build for Windows, macOS, Linux, Android and iOS in nuget packages with C# wrappers on top. I concur, the issue does appear to be fixed by PR #95847 (closed without merging) and #88130 (closed without merging) - now the real question is, how do we get this fixed upstream? I've never made my own custom, patched Rust distribution before, and that doesn't look like a very simple thing to do, and even if it was, that's the kind of work that would likely take days of trial and error until it all works perfectly and is integrated into our CI environment. To the best of my knowledge (based on reading issues and PR) it is still an unresolved issue. As far as I can tell, this issue has been addressed with PR #95847 (closed without merging) and #88130 (closed without merging). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |