| Age | Commit message (Collapse) | Author | Lines |
|
The release build took lua alone, so its binary could not be tested
as built, and a Mac without pkg-config could not name LuaJIT for it.
|
|
exec skipped the EXIT trap, so every run left its three probe files in
TMPDIR.
|
|
|
|
|
|
|
|
Nothing passes parse_args an argv, since t0401 imports only
split_cgi_output.
|
|
The release script described a -Wformat-nonliteral run it does not
make, and the development script's header retold the flags below it.
|
|
It is now named like build-development.sh, so the two sort together in
tools/.
|
|
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.
|
|
Git's Makefile sets CC = cc, which wins over a CC in the environment, so
CC=clang ./tools/release-build.sh probed clang's flags and then built
with cc.
|
|
|
|
Git's Makefile defaults prefix to $HOME and compiles it into exec-cmd.o
as the fallback runtime prefix, so each build embedded the path of
whoever ran it and no two builders could produce the same bytes. The
release script also maps the build directory out of the debug info,
which otherwise differs between checkouts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
The hardening flags are ELF specific and would break local macOS
development, so they stay out of the default build.
|
|
cgit runs as a CGI program, so previewing it normally means running
Apache or nginx, and Python 3.13 removed its built-in CGI handler. It
is a development aid and not meant to face the internet.
|