loot / libloot

94%

master: 94%

LAST BUILD ON BRANCH update-custom-target-name

branch: update-custom-target-name

CHANGE BRANCH

x

Reset

Sync Branches

• update-custom-target-name
• actions-permissions
• add-audits
• better-error-line-numbers
• c++20
• c++20-wrapper
• c4711
• cargo-vet
• ci-npm-cache
• ci-updates
• cmake-vars
• conditional-cleaning-data
• coverage-ci
• cxx-fix
• decouple-condition-cache
• dependency-notices
• disable-cxx-lto
• emit-anchors-aliases
• fix-dependabot
• fix-metadata-write
• fix-msvc-warning
• fix-node-vulns
• fix-permission
• improve-readmes
• master
• misc
• misc-changes
• misc-fixes
• prep-0.28.2
• prevent-base-class-slicing
• regex-fix
• regex-tests
• regress
• release-0.28.4
• remove-32-bit-builds
• rename-target
• replace-install-action
• rust-rewrite
• support-regex-modifiers
• support-symlinks
• symlink-support
• test-long-paths
• undo-cargo-toml-change
• unique-plugin-interface
• update-audits
• update-c++-game-wrapper
• update-cargo-vet
• update-cxx
• update-deps
• update-doc
• update-docs
• update-lci
• update-locks
• update-napi-build
• update-napi-derive
• update-napi-rs
• update-nodejs-lockfiles
• update-regress
• update-release-job
• update-rust-ini
• update-unicase
• userlist-parity
• uv-ci
• yaml-fixes

Build # 21098706151

Build Type

push

github

Committed by Ortham

Commit Message

Change name of internal CMake custom target

It shows up when using libloot as a FetchContent dependency, and it's a bit confusing to have libloot and libloot-cpp-build when the latter isn't the one that a C++ project should really depend on.

libloot-cargo may still be confusing, but at least indicates what is involved.

Run Details

12259 of 13065 relevant lines covered (93.83%)

142.95 hits per line