Jan Lindemann
85ddd44cd1
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 4m15s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 4m35s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 4m18s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 4m54s
CI / Packaging test (push) Successful in 0s
PYTHON_RUNNER is defined in py-run.mk but is more generally useful, e.g. for hand-rolled test Makefiles. It's also a cheap definition. Lift it into py-defs.mk instead. Signed-off-by: Jan Lindemann <jan@janware.com> Assisted-by: unsloth/Qwen3.8-27B-GGUF:Q4_K_M with pi.dev v1.1.0
25 lines
582 B
Makefile
25 lines
582 B
Makefile
include $(JWBDIR)/make/defs.mk
|
|
include $(JWBDIR)/make/py-defs.mk
|
|
include $(JWBDIR)/make/test-guard.mk
|
|
include $(JWBDIR)/make/run-success.mk
|
|
|
|
EXE ?= $(firstword $(wildcard main.py runme.py test.py *.py))
|
|
EXE_ARGS ?=
|
|
|
|
all:
|
|
install:
|
|
clean:
|
|
distclean:
|
|
test: all testability
|
|
|
|
run:
|
|
$(PYTHON_RUNNER) $(EXE) $(EXE_ARGS)
|
|
$(RUN_SUCCESS_CREATE_MARKER)
|
|
|
|
run.sh:
|
|
echo -e "#!/bin/bash\n\nexport PYTHONPATH=$(PYTHONPATH)\nset -x\nexec $(PYTHON) $(EXE)" '"$$@"' > $@.tmp
|
|
chmod 755 $@.tmp
|
|
mv $@.tmp $@
|
|
clean.py-run:
|
|
rm -rf run.sh
|
|
clean: clean.py-run
|