Arch Linux User Repository

Either build the package in a clean chroot or shoot over a patch that fixes compiling with doxygen enabled.

This is failing to compile for me half way through

In file included from /home/neckbear/.cache/yay/loot/src/libloot-0.22.4/src/api/metadata/yaml/plugin_metadata.h:40,
                 from /home/neckbear/.cache/yay/loot/src/libloot-0.22.4/src/api/api_database.cpp:32:
/home/neckbear/.cache/yay/loot/src/libloot-0.22.4/src/api/metadata/yaml/message.h:29:10: fatal error: spdlog/fmt/bundled/args.h: No such file or directory
   29 | #include <spdlog/fmt/bundled/args.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

@sdave.b can you reproduce it in a clean chroot?

I'm experiencing build errors related to linking minizip-ng. Is anyone else getting this, or is this specific to my own system?

[100%] Linking CXX executable LOOT
/usr/bin/ld: external/src/minizip-ng-build/./libminizip.a(mz_strm_zlib.c.o): in function `mz_stream_zlib_open':
mz_strm_zlib.c:(.text+0x1d0): undefined reference to `zng_deflateInit2'
/usr/bin/ld: external/src/minizip-ng-build/./libminizip.a(mz_strm_zlib.c.o): in function `mz_stream_zlib_deflate':
mz_strm_zlib.c:(.text+0x2cf): undefined reference to `zng_deflate'
/usr/bin/ld: external/src/minizip-ng-build/./libminizip.a(mz_strm_zlib.c.o): in function `mz_stream_zlib_close':
mz_strm_zlib.c:(.text+0x3e4): undefined reference to `zng_deflateEnd'
/usr/bin/ld: external/src/minizip-ng-build/./libminizip.a(mz_crypt.c.o): in function `mz_crypt_crc32_update':
mz_crypt.c:(.text+0x16): undefined reference to `zng_crc32'
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/LOOT.dir/build.make:1140: LOOT] Error 1
make[2]: *** [CMakeFiles/Makefile2:304: CMakeFiles/LOOT.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:311: CMakeFiles/LOOT.dir/rule] Error 2

@diedbydisgust, you need to edit ~/.config/LOOT/settings.toml. Here's my entry for Fallout 4, as an example:

[[games]]
folder = 'Fallout4'
local_path = '/home/infernio/Games/steam/steamapps/compatdata/377160/drive_c/users/steamuser/AppData/Local/Fallout4'
master = 'Fallout4.esm'
masterlistSource = 'https://raw.githubusercontent.com/loot/fallout4/v0.18/masterlist.yaml'
minimumHeaderVersion = 0.94999998807907104
name = 'Fallout 4'
path = '/home/infernio/Games/steam/steamapps/common/Fallout 4'
type = 'Fallout4'

Ortham also recently added support for automatically detecting Proton installs, but that's only in the WIP version (will be in LOOT 0.21.0, when that releases). You can check the LOOT github repo for a recent GitHub Actions flatpak build if you'd like to try that.

it didn't recognize games, and don't let me add nothing, "this not a valid windows folder name" it says. how do you use this?

Updating with rustup solved it. Thanks.

@RetiredTurtle, it's complaining about a since-stabilized Rust feature being unstable. Check your rustc --version and update it if you're behind (e.g. rustup update if you're using rustup).

Bumped loot to a newer version and can't reproduce.

If you can still reproduce it in a clean chroot you should probably report it to upstream.

Tried to build it but I get errors. Here is the whole output from the terminal: https://gist.github.com/Fooftilly/218957c97ed022327618af54e0e43c31