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
Currently, the 2 ways to link libtorch*.so files is static or dynamic. For dynamic, libtorch needs to be installed on the system where tch-rs is being built. I am exploring a feature where libtorch*.so would not need to be present while tch-rs is built, and only the target system where tch-rs is being run needs to have those libraries installed.
This would make projects (like wasmtime) which depend on tch-rs be able to build without libtorch being installed. The actual linking/mapping of symbols would happen at runtime.
This is similar to what openvino-rs does in runtime linking, although the way to do it would differ here since the bindings are generated in 2 levels, as mentioned in this issue.
Let me know if this feature would be useful, and any feedback. Thanks.
The text was updated successfully, but these errors were encountered:
Currently, the 2 ways to link libtorch*.so files is
static
ordynamic
. Fordynamic
, libtorch needs to be installed on the system where tch-rs is being built. I am exploring a feature where libtorch*.so would not need to be present while tch-rs is built, and only the target system where tch-rs is being run needs to have those libraries installed.This would make projects (like wasmtime) which depend on tch-rs be able to build without libtorch being installed. The actual linking/mapping of symbols would happen at runtime.
This is similar to what
openvino-rs
does in runtime linking, although the way to do it would differ here since the bindings are generated in 2 levels, as mentioned in this issue.Let me know if this feature would be useful, and any feedback. Thanks.
The text was updated successfully, but these errors were encountered: