• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

loot / libloot / 20655803096 / 1
93%
master: 94%

Build:
Build:
LAST BUILD BRANCH: update-docs
DEFAULT BRANCH: master
Ran 02 Jan 2026 10:21AM UTC
Files 37
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

02 Jan 2026 10:20AM UTC coverage: 93.252% (+0.01%) from 93.238%
20655803096.1

push

github

Ortham
Rename CMake target from loot to libloot

On Windows using "loot" causes a name collisions with LOOT itself:

- for the MSVC project name, it clashes with LOOT's own project,
  despite the difference in case. This means that you can't build LOOT
  in Visual Studio when using FetchContent to handle the libloot
  dependency (running CMake on the CLI works though).
- for the PDB file, LOOT has LOOT.pdb and libloot has loot.pdb, which
  appear to be the same due to file paths being case-insensitive. This
  makes it more difficult to debug LOOT with the relevant debug info
  loaded.

Renaming the CMake target adds a "lib" prefix to the Visual Studio
project name and the artifact filenames:

- loot.vcxproj* -> libloot.vcxproj*
- loot.dll -> libloot.dll
- loot.lib -> libloot.lib
- loot.pdb -> libloot.pdb

The Linux build artifact filenames are unchanged, as they already had
the "lib" prefix.

11083 of 11885 relevant lines covered (93.25%)

71.45 hits per line

Source Files on job 20655803096.1
  • Tree
  • List 37
  • Changed 37
  • Source Changed 37
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 20655803096
  • 20420b83 on github
  • Prev Job for on rename-target (#20655716874.2)
  • Next Job for on rename-target (#20658961411.2)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc