You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sounds like a reason able request. I guess we need to work about ABI compatibility, but that sounds like a pre-existing problem for any program linking against libclang?
We are already shipping it in the non-release builds, since they are dylib builds. The release builds are statically linked and currently don't ship any dylibs.
I'd have to look; I imagine it wouldn't be too hard to do at least on Linux on Mac, but less sure about Windows. I guess we'd probably need to ship some headers too; IIRC we don't currently.
Regarding ABI compatibility, that's not something we can maintain across our releases currently, because we don't ship from release branches.
Activity
WIP: enable rust for wasm/emscripten
WIP: enable rust for wasm/emscripten
WIP: enable rust for wasm/emscripten
WIP: enable rust for wasm/emscripten
sbc100 commentedon Sep 24, 2025
Sounds like a reason able request. I guess we need to work about ABI compatibility, but that sounds like a pre-existing problem for any program linking against libclang?
Do you know how to enable and install libclang using CMake flags. The rules we use are here: https://chromium.googlesource.com/emscripten-releases/+/refs/heads/main/src/build.py#726
WIP: enable rust for wasm/emscripten
WIP: enable rust for wasm/emscripten
WIP: enable rust for wasm/emscripten
sbc100 commentedon Aug 15, 2026
@dschuff how hard/costly would it be to start building/shipping libclang.so?
dschuff commentedon Aug 17, 2026
We are already shipping it in the non-release builds, since they are dylib builds. The release builds are statically linked and currently don't ship any dylibs.
I'd have to look; I imagine it wouldn't be too hard to do at least on Linux on Mac, but less sure about Windows. I guess we'd probably need to ship some headers too; IIRC we don't currently.
Regarding ABI compatibility, that's not something we can maintain across our releases currently, because we don't ship from release branches.