tqchen opened a new pull request, #19719:
URL: https://github.com/apache/tvm/pull/19719

   This PR slims `tvm.libinfo` into a thin *info* layer that delegates path
   discovery to the `tvm_ffi.libinfo` primitives and never loads libraries.
   Loading responsibilities move to `tvm.base`, and the various ad-hoc
   path-finding helpers are phased out in favor of the tvm-ffi resolvers.
   
   ## Changes
   
   - **libinfo**: add `find_libtvm_runtime()` (resolves `libtvm_runtime` via
     `_find_library_by_basename` + `_resolve_and_validate`) and
     `find_tvm_include_path()` (TVM's own `include/`). `find_include_path()` now
     returns `[find_tvm_include_path(), *tvm_ffi.libinfo.include_paths()]`, 
folding
     in the FFI + dlpack + python-helper include dirs. Remove `find_lib_path`,
     `get_dll_directories`, `use_runtime_lib`, `split_env_var`, and
     `load_backend_libs`.
   - **base**: receive `load_backend_libs` and the backend DSO list; the
     runtime-only switch becomes a strict `TVM_USE_RUNTIME_LIB == "1"` check.
   - **rpc**: `with_minrpc` uses `find_libtvm_runtime()` (the `runtime` kwarg is
     retained as an inert back-compat parameter); the rpc server `load_library`
     resolves the literal library name against the current working directory.
   - **wasm**: move the `web/dist` asset search into `emcc.find_wasm_lib`, used 
by
     `emcc.create_tvmjs_wasm` and the tvmjs asset lookup.
   - **hexagon**: fix a latent bug where `_get_hexagon_rpc_lib_dir` called a
     non-existent `tvm_ffi.libinfo.find_lib_path`; it now relies solely on the
     `HEXAGON_RPC_LIB_DIR` environment variable.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to