123 lines
5.5 KiB
Makefile
123 lines
5.5 KiB
Makefile
#!/usr/bin/make
|
|
#^^^^ help emacs select makefile mode
|
|
#
|
|
# This is a sub-make for building a standalone wasmfs-based
|
|
# sqlite3.wasm. It is intended to be "include"d from the main
|
|
# GNUMakefile.
|
|
########################################################################
|
|
MAKEFILE.wasmfs := $(lastword $(MAKEFILE_LIST))
|
|
|
|
sqlite3-wasmfs.js := sqlite3-wasmfs.js
|
|
sqlite3-wasmfs.wasm := sqlite3-wasmfs.wasm
|
|
sqlite3-wasmfs.wasm.c := $(dir.api)/sqlite3-wasm.c
|
|
|
|
CLEAN_FILES += $(sqlite3-wasmfs.js) $(sqlite3-wasmfs.wasm) \
|
|
$(subst .js,.worker.js,$(sqlite3-wasmfs.js))
|
|
|
|
########################################################################
|
|
# emcc flags for .c/.o/.wasm.
|
|
sqlite3-wasmfs.flags =
|
|
#sqlite3-wasmfs.flags += -v # _very_ loud but also informative about what it's doing
|
|
|
|
########################################################################
|
|
# emcc flags for .c/.o.
|
|
sqlite3-wasmfs.cflags :=
|
|
sqlite3-wasmfs.cflags += -std=c99 -fPIC -g
|
|
sqlite3-wasmfs.cflags += -pthread
|
|
sqlite3-wasmfs.cflags += -I. -I.. -I$(dir.top)
|
|
sqlite3-wasmfs.cflags += $(SQLITE_OPT) -DSQLITE_WASM_WASMFS
|
|
|
|
sqlite3-wasmfs.extra.c :=
|
|
ifeq (1,1)
|
|
# To get testing1.js to run with $(sqlite3-wasmfs.js) we need...
|
|
sqlite3-wasmfs.extra.c += $(jaccwabyt_test.c)
|
|
endif
|
|
|
|
########################################################################
|
|
# emcc flags specific to building the final .js/.wasm file...
|
|
sqlite3-wasmfs.jsflags := -fPIC
|
|
sqlite3-wasmfs.jsflags += --no-entry
|
|
sqlite3-wasmfs.jsflags += --minify 0
|
|
sqlite3-wasmfs.jsflags += -sMODULARIZE
|
|
sqlite3-wasmfs.jsflags += -sSTRICT_JS
|
|
sqlite3-wasmfs.jsflags += -sDYNAMIC_EXECUTION=0
|
|
sqlite3-wasmfs.jsflags += -sNO_POLYFILL
|
|
ifeq (,$(sqlite3-wasmfs.extra.c))
|
|
sqlite3-wasmfs.jsflags += -sEXPORTED_FUNCTIONS=@$(dir.api)/EXPORTED_FUNCTIONS.sqlite3-api
|
|
else
|
|
# need more exports for jaccwabyt test code...
|
|
sqlite3-wasmfs.jsflags += -sEXPORTED_FUNCTIONS=@$(dir.wasm)/EXPORTED_FUNCTIONS.api
|
|
endif
|
|
sqlite3-wasmfs.jsflags += -sEXPORTED_RUNTIME_METHODS=FS,wasmMemory,allocateUTF8OnStack
|
|
# wasmMemory ==> for -sIMPORTED_MEMORY
|
|
# allocateUTF8OnStack ==> wasmfs internals
|
|
sqlite3-wasmfs.jsflags += -sUSE_CLOSURE_COMPILER=0
|
|
sqlite3-wasmfs.jsflags += -sIMPORTED_MEMORY
|
|
#sqlite3-wasmfs.jsflags += -sINITIAL_MEMORY=13107200
|
|
#sqlite3-wasmfs.jsflags += -sTOTAL_STACK=4194304
|
|
sqlite3-wasmfs.jsflags += -sEXPORT_NAME=sqlite3InitModule
|
|
sqlite3-wasmfs.jsflags += -sGLOBAL_BASE=4096 # HYPOTHETICALLY keep func table indexes from overlapping w/ heap addr.
|
|
sqlite3-wasmfs.jsflags += --post-js=$(post-js.js)
|
|
#sqlite3-wasmfs.jsflags += -sFILESYSTEM=0 # only for experimentation. sqlite3 needs the FS API
|
|
# Perhaps the wasmfs build doesn't?
|
|
#sqlite3-wasmfs.jsflags += -sABORTING_MALLOC
|
|
sqlite3-wasmfs.jsflags += -sALLOW_TABLE_GROWTH
|
|
sqlite3-wasmfs.jsflags += -Wno-limited-postlink-optimizations
|
|
# ^^^^^ it likes to warn when we have "limited optimizations" via the -g3 flag.
|
|
sqlite3-wasmfs.jsflags += -sERROR_ON_UNDEFINED_SYMBOLS=0
|
|
sqlite3-wasmfs.jsflags += -sLLD_REPORT_UNDEFINED
|
|
#sqlite3-wasmfs.jsflags += --import-undefined
|
|
sqlite3-wasmfs.jsflags += -sMEMORY64=0
|
|
sqlite3-wasmfs.jsflags += -sINITIAL_MEMORY=128450560
|
|
sqlite3-wasmfs.fsflags := -pthread -sWASMFS -sPTHREAD_POOL_SIZE=2 -sENVIRONMENT=web,worker
|
|
sqlite3-wasmfs.jsflags += $(sqlite3-wasmfs.fsflags)
|
|
speedtest1-common.eflags += -sEXPORTED_FUNCTIONS=@$(dir.wasm)/EXPORTED_FUNCTIONS.speedtest1
|
|
#sqlite3-wasmfs.jsflags += -sALLOW_MEMORY_GROWTH
|
|
#^^^ using ALLOW_MEMORY_GROWTH produces a warning from emcc:
|
|
# USE_PTHREADS + ALLOW_MEMORY_GROWTH may run non-wasm code slowly,
|
|
# see https://github.com/WebAssembly/design/issues/1271 [-Wpthreads-mem-growth]
|
|
ifneq (0,$(enable_bigint))
|
|
sqlite3-wasmfs.jsflags += -sWASM_BIGINT
|
|
endif
|
|
|
|
$(sqlite3-wasmfs.js): $(sqlite3-wasmfs.wasm.c) $(sqlite3-wasm.c) $(sqlite3-wasmfs.extra.c) \
|
|
EXPORTED_FUNCTIONS.api $(sqlite3-wasm.js) $(MAKEFILE) $(MAKEFILE.wasmfs) \
|
|
$(post-js.js)
|
|
@echo "Building $@ ..."
|
|
$(emcc.bin) -o $@ $(emcc_opt) $(emcc.flags) \
|
|
$(sqlite3-wasmfs.cflags) $(speedtest1-common.eflags) $(sqlite3-wasmfs.jsflags) $(sqlite3-wasmfs.wasm.c) $(sqlite3-wasmfs.extra.c)
|
|
chmod -x $(sqlite3-wasmfs.wasm)
|
|
$(maybe-wasm-strip) $(sqlite3-wasmfs.wasm)
|
|
@ls -la $@ $(sqlite3-wasmfs.wasm)
|
|
|
|
wasmfs: $(sqlite3-wasmfs.js)
|
|
all: wasmfs
|
|
|
|
########################################################################
|
|
# speedtest1 for wasmfs. Re. sqlite3-wasm.o vs sqlite3-wasm.c:
|
|
# building against the latter (predictably) results in a slightly
|
|
# faster binary.
|
|
speedtest1-wasmfs.js := speedtest1-wasmfs.js
|
|
speedtest1-wasmfs.wasm := $(subst .js,.wasm,$(speedtest1-wasmfs.js))
|
|
speedtest1-wasmfs.eflags := $(sqlite3-wasmfs.fsflags)
|
|
speedtest1-wasmfs.eflags += $(SQLITE_OPT) -DSQLITE_WASM_WASMFS
|
|
speedtest1-wasmfs.eflags += --post-js=$(sqlite3-wasmfs.js)
|
|
$(speedtest1-wasmfs.js): $(MAKEFILE) $(MAKEFILE.wasmfs)
|
|
#$(speedtest1-wasmfs.js): $(sqlite3-wasmfs.js)
|
|
$(speedtest1-wasmfs.js): $(speedtest1.cs) $(sqlite3-wasmfs.js) \
|
|
EXPORTED_FUNCTIONS.speedtest1
|
|
@echo "Building $@ ..."
|
|
$(emcc.bin) \
|
|
$(speedtest1-wasmfs.eflags) $(speedtest1-common.eflags) \
|
|
$(speedtest1.cflags) \
|
|
$(sqlite3-wasmfs.cflags) \
|
|
-o $@ $(speedtest1.cs) -lm
|
|
$(maybe-wasm-strip) $(speedtest1-wasmfs.wasm)
|
|
ls -la $@ $(speedtest1-wasmfs.wasm)
|
|
|
|
speedtest1: $(speedtest1-wasmfs.js)
|
|
CLEAN_FILES += $(speedtest1-wasmfs.js) $(speedtest1-wasmfs.wasm) \
|
|
$(subst .js,.worker.js,$(speedtest1-wasmfs.js))
|
|
# end speedtest1.js
|
|
########################################################################
|