mirror of
https://github.com/extism/extism.git
synced 2026-01-13 15:57:57 -05:00
5eb8995347
I realized the glibc static build does actually work (though prints warnings at compile time), so I made it no longer hard-coded to the compiler. It's still a bad idea, so I added notes for why you shouldn't do it with glibc.
35 lines
1.0 KiB
Makefile
35 lines
1.0 KiB
Makefile
.PHONY: build
|
|
build:
|
|
$(CC) -g -o example example.c -lextism
|
|
|
|
.PHONY: static
|
|
static:
|
|
$(CC) -g -o example example.c -l:libextism.a -lm
|
|
|
|
# if needed, set PKG_CONFIG_PATH= to the directory with extism*.pc installed
|
|
LDFLAGS=`pkg-config --libs extism`
|
|
.PHONY: pkg-config
|
|
pkg-config:
|
|
$(CC) -g -o example example.c $(LDFLAGS)
|
|
|
|
LDFLAGS_STATIC=`pkg-config --static --libs extism-static`
|
|
.PHONY: pkg-config-static
|
|
pkg-config-static:
|
|
$(CC) -g -o example example.c $(LDFLAGS_STATIC)
|
|
|
|
# This produces an entirely static binary
|
|
#
|
|
# MUSL libc is highly recommended over glibc for this purpose as some glibc
|
|
# functionality such as getaddrinfo, iconv depends on dynamically loading glibc.
|
|
#
|
|
# To build and install libextism with musl for x86_64 in the parent directory:
|
|
# make RUST_TARGET=x86_64-unknown-linux-musl && sudo make RUST_TARGET=x86_64-unknown-linux-musl install
|
|
# Then, from this directory you can build with CC=musl-gcc make fully-static
|
|
.PHONY: fully-static
|
|
fully-static:
|
|
$(CC) -static -g -o example example.c $(LDFLAGS_STATIC)
|
|
|
|
.PHONY: clean
|
|
clean:
|
|
rm -f example
|