| Age | Commit message (Collapse) | Author | Lines |
|
Its message also spells the project's name as cgit.
|
|
The test rule's note on ordering predates .NOTPARALLEL, which covers
it. The install paths are not compiled in, and a lowercase name is no
easier to override than another.
|
|
A list at the end of the file is easy to miss when a target is added
or renamed.
|
|
cgit's objects are compiled by its own rule rather than git's, so they
took no -MJ flag and a compilation database held only git's sources.
|
|
gen-version.sh was only ever run by this one recipe, so tools/ now
holds just the scripts a person runs.
|
|
The sparse rule put git's SPARSE_FLAGS last, and their -std=gnu99
overrode the gnu17 the sources are built as.
|
|
Neither cgit nor the bundled Git reads the macro it defined.
|
|
cgit builds against Lua 5.5 and serves the same pages with it, but a
host whose only Lua was 5.5 got a binary without Lua from the search.
|
|
ISO C has no conversion between a function pointer and void *, so the
callbacks handed through git's data pointers and the write found by
dlsym stopped the pedantic half of a DEVELOPER=1 build.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Apple clang still defaults to -fcommon, so git's 64 KB packet_buffer
became a common symbol whose size drove a 32 KB section alignment that
ld64 then clamped to the 16 KB page size, warning on every macOS link.
Everywhere else already compiles with -fno-common.
|
|
|
|
Lua only powers the filter extensions, so it stays optional and
autodetected. Autodetection skipped Lua 5.3 and 5.4, so a system with
only those fell back to a build without Lua. The release script still
leaves Lua out unless asked, so its binary needs no Lua at runtime.
|
|
Everything the build generates now lands in build/, so a clean is a
single remove and the source tree stays free of build output.
|