Manual build issue during part 4 - Fedora Atomic/Bazzite

[MANGOM1LK]

Having a little trouble building this manually (which is frustrating since I can't get the Windows exe running in Wine either). The Linux instructions seem pretty much irrelevant to my distro since it's not only immutable but actually ships without apt. I got a little further using the MacOS instructions since it does ship with Homebrew. Everything works out fine until step 4 where I get this error:

The same thing happens when I use the Release build type (it just jumps straight to the errors about being unable to find Fbx and Unordered Dense). Is this perhaps a case where these are usually available by default but are disabled in Fedora Atomic (and therefore Bazzite)? I was really hoping this could replace my Windows setup for modding and this is really my only roadblock so far.

[Radfordhound]

Hi, in light of all of the nonsense Microsoft has been pulling with Windows 11, I've been a full-time Linux user for some time now. So I can personally guarantee HedgeLib has "first-class" Linux support and should be buildable on any Linux distro. That said, I haven't used your specific distro before.

Building HedgeLib/HedgeTools has been a pain point for a lot of people, it seems, which is a problem - it's supposed to be easy. I plan to rethink the way dependencies are handled soon to make building everything far easier, and hopefully resolve this.

In the meantime, I'd like to help you get it to build on your machine.

The error you showed indicates that CMake cannot find the "unordered_dense" library.

The library in question is this GitHub repository which is likely not available in your distro's package repositories.

So, to build HedgeLib, you'll need to clone that repository and build it yourself first, using CMake.

Normally, I would just install it system-wide. However, you mentioned your distro is immutable, so I'm not sure if you're able to install anything system-wide?

In that case, a workaround would be to install it to a local directory instead.

The README for unordered_dense says, to install it to a local directory, just run these 3 commands:

mkdir build && cd build
cmake -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/unordered_dense_install ..
cmake --build . --target install

Those commands should build and install unordered_dense to the ~/unordered_dense_install directory.

Once you get it built and installed, you should then be able to build HedgeLib by deleting your current HedgeLib build directory, then re-running the CMake configuration command from step 3, but with -DCMAKE_PREFIX_PATH=~/unordered_dense_install added to the end, so that CMake can find the unordered_dense library you installed there.

Please let me know if you have any questions or further errors

[MANGOM1LK]

Thanks for the quick response and for the advice! I got a little further installing unordered_dense to a local directory like you recommended (as I expected, it threw an error when I initially tried installing it system-wide), but now there's another missing package error:

Doing a little googling, I did find another library by this name, but it seems like the GitHub page has been taken down. Do you know anything about this?

[Radfordhound]

I'm glad to hear you got further!

libRad is my library for common helper code that I find myself needing in most projects I create. You can find it here.

You can build/install it like this:

cmake -S . -B build -DCMAKE_BUILD_TYPE=Debug
cmake --install build --prefix ~/unordered_dense_install --config Debug

Replace Debug with Release if you're also building HedgeLib in Release mode.

Then, as before, delete the HedgeLib build folder and re-run step 3 of HedgeLib's build instructions, but with -DCMAKE_PREFIX_PATH=~/unordered_dense_install added to the end.

Note: You can replace ~/unordered_dense_install with any directory you want. I just said to use that path because that's where you already installed unordered_dense to. You can install as many CMake projects as you want all into the same folder, like that. It's completely fine and actually recommended to just use one single folder, as the installed files don't conflict with each other, and that way you don't have to add a separate -DCMAKE_PREFIX_PATH= argument for every single folder you installed something into - you can just use the one.

[MANGOM1LK]

Doesn't seem like this wants to install either unfortunately: