view dev/Makefile @ 128:a5ffec18e4cd

test programs: use printf %d format for codec parameters Even though all codec params (both FR and EFR) are small unsigned integers, we use signed int16_t data type for both, for interface reasons: in the case of FR it's the gsm_signal type of libgsm, and in the case of EFR it's the Word16 type of ETSI codec guts. Therefore, the correct printf format is %d, not %u, when the objective is to see what's in the variables (what the compiler sees) and catch any bugs.
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 11 Dec 2022 04:00:13 +0000
parents 3b5958f28a40
children 68215020852b
line wrap: on
line source

CC=	gcc
CFLAGS=	-O2
PROGS=	efr-bit-packing efr-sid-insert gsm0611-silence-fr
DATAOUT=efr-bit-packing.out efr-sid-insert.out gsm0611-silence-fr.out

all:	${PROGS} ${DATAOUT}

efr-bit-packing:	efr-bit-packing.c
	${CC} ${CFLAGS} -o $@ $@.c

efr-bit-packing.out:	efr-bit-packing
	./efr-bit-packing > $@

efr-sid-insert:		efr-sid-insert.c
	${CC} ${CFLAGS} -o $@ $@.c

efr-sid-insert.out:	efr-sid-insert
	./efr-sid-insert > $@

gsm0611-silence-fr:	gsm0611-silence-fr.c
	${CC} ${CFLAGS} -o $@ $@.c -lgsm

gsm0611-silence-fr.out:	gsm0611-silence-fr
	./gsm0611-silence-fr > $@

clean:
	rm -f *.o *.out ${PROGS}