Adam Basfop Cavendish 032361a177 chore(example): add nvvm library path to LD_LIBRARY_PATH and add back the add example in CI (#190) ...

When linking `libnvvm.so.4` into `librustc_codegen_nvvm.so` shared
library via the `cust_raw` package, we specified the following
parameters in the `build.rs`:

- cargo::rustc-link-search=native=xxx
- cargo::rustc-link-lib=dylib=nvvm

According to the [Cargo documentation](https://doc.rust-lang.org/cargo/reference/build-scripts.html#rustc-link-search),
the path we added to the `rustc-link-search` parameter is not further
populated to the `LD_LIBRARY_PATH` for search by the transitive
dependencies.

> These paths are also added to the dynamic library search path
> environment variable if they are within the OUT_DIR.

The behavior is intended to be limited to the OUT_DIR so the
`libnvvm.so.4`, which lives as a part of the CUDA SDK, is excluded.
Therefore, we must add it to the LD_LIBRARY_PATH manually in our
container build stage.

2025-04-05 13:26:45 -07:00

..

build_guide.yml

Docs: Build guide as mdbook (#5)

2021-11-22 22:06:28 -05:00

ci_linux.yml

chore(example): add nvvm library path to LD_LIBRARY_PATH and add back the add example in CI (#190)

2025-04-05 13:26:45 -07:00

container_images.yml

feat(ci): Split Linux CI workflow and add container images pipeline (#188)

2025-04-03 17:30:16 -07:00

rust.yml

feat(ci): Split Linux CI workflow and add container images pipeline (#188)

2025-04-03 17:30:16 -07:00