emscripten-core / emscripten-core/emscripten
Force to always link against an absolute path
- Dominant language
- C++
- Stars
- 27.6k
- Forks
- 3.6k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 105
Description
In the `emscripten-forge` project we deal with a couple of dynamic libraries that link against each other. Unfortunately, we run into issues with the libraries being linked with non-absolute paths (filename only) and are not discovered properly in the preloaded libraries.
Our libraries are preloaded at `/home/user/myenv/lib/libfoo.so` while the library that links to foo searches for `foo.so` only (and tries to download `/foo.so` (while the library is either available in the emscripten filesystem or also already preloaded).
I think we could fix our issue if we could convince the WASM linker to always link with absolute paths. Maybe there is already a way to do that?
Another related issue we found is that the WASM preloader currently doesn't preload `.so` files that end with ABI versions, e.g. `libfoo.so.2.1.3` is not detected as "canHandle" because the check only checks for `.endsWith(".so")`.
Contributor guide
Assessment
This issue has not been assessed yet.