GuofangandClaude Sonnet 5 3c1f37e1d5 Add libproxyprotocol to the Debian, Rocky, and Alpine build environments
Upstream ships only a Makefile with no install target, so each image
compiles src/proxy_protocol.c with -fPIC, archives it into
libproxyprotocol.a, and installs the header manually, matching this
project's static-PIC-library convention.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016Xj6cCTEVsr5PM43uTsbq8
2026-09-14 15:15:52 +08:00

Source Stack Build Environments

Debian 13, Rocky Linux 9, and Alpine Linux container build environments with a C/C++ toolchain, CMake, and Git preinstalled, compatible with both Docker and Podman. The Alpine image builds the stack against musl libc. GitHub HTTPS URLs are routed through gh-proxy.com. For the libraries included in the images, their pinned versions, and build details, see INCLUDED_LIBRARIES.md.

Build

Each build script automatically selects Docker or Podman:

./build-all.sh
./debian13/build.sh
./rockylinux9/build.sh
./alpine3.24/build.sh

Use environment variables to select the container engine or override image names:

CONTAINER_ENGINE=podman IMAGE_NAME=my-build-env ./rockylinux9/build.sh

Run

docker run --rm -it debian13-source-stack
docker run --rm -it rockylinux9-source-stack
docker run --rm -it alpine3.24-source-stack
S
Description
No description provided
Readme
317 KiB
0 Stars 1 Watchers 0 Forks
Languages
Dockerfile 86.3%
Shell 9.9%
CMake 3.8%