Build failure on `lore-storage`: OODLE_LIB_DIR not set (Compilation blocked by proprietary dependency)

[MilesONerd]

Hi!

While attempting to compile Lore from source on Linux (Arch Linux, Cargo/Rustc 1.x), the build process fails during the compilation of the lore-storage crate due to a missing proprietary dependency.

Steps to Reproduce

1. Clone the repository: git clone https://github.com/EpicGames/lore.git
2. Run cargo build --release inside the root directory.

Terminal Output

error: failed to run custom build command for lore-storage v0.8.4-nightly

Caused by:
process didn't exit successfully: .../build-script-build (exit status: 101)
--- stderr
thread 'main' panicked at lore-storage/build.rs:10:58:
OODLE_LIB_DIR not set: NotPresent

Context & Question

Since Oodle is a proprietary compression library owned by Epic/RAD Game Tools and its SDK is not publicly available for general Linux distribution package maintainers (like the Arch Linux AUR), this completely blocks community-driven compilation and packaging.

Are there any plans to introduce a fallback feature flag to compile Lore using open alternative compressors (like Zstd or LZ4, which are already listed in the root Workspace Cargo.toml) when OODLE_LIB_DIR is not present?

This would greatly benefit package maintainers and the open-source community trying to test and adopt Lore natively.

[ahaczewski]

According to https://epicgames.github.io/lore/developing/decisions/00016-compression-algorithm-selection/ they already switched to Zstd.

[mjansson]

The use of oodle should be optional - if you have access to Oodle and want to use it, you can set that environment variable, enable the oodle feature and compile it in.

Out of the box, the build should detect that the oodle feature is not enabled and not even attempt to read that env var. I just verified that this works on a clean machine. This is on line 8 in that build script you just got an error in.

if env::var("CARGO_FEATURE_OODLE").is_ok()

Did you enable the oodle feature?