addons/mp3/Makefile

MP3OBJS=common.o dct64_i386.o decode_ntom.o layer3.o tabinit.o interface.o

ifeq ($(OSARCH),FreeBSD)
OSVERSION=$(shell make -V OSVERSION -f /usr/share/mk/bsd.port.subdir.mk)
CFLAGS+=$(if $(OSVERSION)<500016,-D_THREAD_SAFE)
LIBS+=$(if $(OSVERSION)<502102,-lc_r,-pthread)
INCLUDE+=-I/usr/local/include
CFLAGS+=$(shell if [ -d /usr/local/include/spandsp ]; then echo "-I/usr/local/include/spandsp"; fi)
endif # FreeBSD

ifeq ($(OSARCH),NetBSD)
CFLAGS+=-pthread
INCLUDE+=-I/usr/local/include
endif

ifeq ($(OSARCH),OpenBSD)
CFLAGS+=-pthread
endif

all: $(MP3OBJS)

clean:
	rm -f *.o *.so *~
	rm -f .*.o.d
Move Asterisk-addons modules into the main Asterisk source tree. Someone asked yesterday, "is there a good reason why we can't just put these modules in Asterisk?". After a brief discussion, as long as the modules are clearly set aside in their own directory and not enabled by default, it is perfectly fine. For more information about why a module goes in addons, see README-addons.txt. chan_ooh323 does not currently compile as it is behind some trunk API updates. However, it will not build by default, so it should be okay for now. git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@204413 65c4cc65-6c06-0410-ace0-fbb531ad65f3 2009-06-30 16:40:38 +00:00			`MP3OBJS=common.o dct64_i386.o decode_ntom.o layer3.o tabinit.o interface.o`

			`ifeq ($(OSARCH),FreeBSD)`
			`OSVERSION=$(shell make -V OSVERSION -f /usr/share/mk/bsd.port.subdir.mk)`
			`CFLAGS+=$(if $(OSVERSION)<500016,-D_THREAD_SAFE)`
			`LIBS+=$(if $(OSVERSION)<502102,-lc_r,-pthread)`
			`INCLUDE+=-I/usr/local/include`
			`CFLAGS+=$(shell if [ -d /usr/local/include/spandsp ]; then echo "-I/usr/local/include/spandsp"; fi)`
			`endif # FreeBSD`

			`ifeq ($(OSARCH),NetBSD)`
			`CFLAGS+=-pthread`
			`INCLUDE+=-I/usr/local/include`
			`endif`

			`ifeq ($(OSARCH),OpenBSD)`
			`CFLAGS+=-pthread`
			`endif`

			`all: $(MP3OBJS)`

			`clean:`
			`rm -f .o .so *~`
			`rm -f .*.o.d`