cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
b2170de7b1
openbsd-ports/audio/jack/Makefile

74 lines
1.6 KiB
Makefile
Raw Normal View History

Fix after celt update ok ajacoutot@
2012-04-20 09:28:50 -04:00
# $OpenBSD: Makefile,v 1.21 2012/04/20 13:28:50 dcoppa Exp $
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
SHARED_ONLY = Yes
COMMENT = low latency sound server
Update to jack-0.121.3. README changes from rathov@ tweaks and ok shadchin@
2012-01-24 03:03:52 -05:00
V = 0.121.3
- update to 0.116.1, mostly stability/reliability fixes - add sndio backend playback under aucat server is pretty solid. for full-duplex, starting aucat with 'aucat -l -b 2048' and jackd with just 'jackd -d sndio' seems to work best for me. we want low latency anyway, right ;)
2009-01-11 05:51:45 -05:00
DISTNAME = jack-audio-connection-kit-${V}
new-style LIB_DEPENDS/REVISION, sync WANTLIB, bump where necessary. checked with check-lib-depends and PLIST_DB "make package".
2010-09-05 18:00:13 -04:00
PKGNAME = jack-${V}
Fix after celt update ok ajacoutot@
2012-04-20 09:28:50 -04:00
REVISION = 0
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
SHARED_LIBS += jack 0.0 # 0.28
SHARED_LIBS += jackserver 0.0 # 0.28
CATEGORIES = audio
HOMEPAGE = http://jackaudio.org/
MAINTAINER = Jacob Meuser <jakemsr@openbsd.org>
don't use dynamic SIMD instructions.
2009-01-12 05:45:01 -05:00
# LGPLv2/GPLv2
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
PERMIT_PACKAGE_CDROM = Yes
PERMIT_PACKAGE_FTP = Yes
Update to jack-0.121.3. README changes from rathov@ tweaks and ok shadchin@
2012-01-24 03:03:52 -05:00
PERMIT_DISTFILES_CDROM =Yes
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
PERMIT_DISTFILES_FTP = Yes
Fix after celt update ok ajacoutot@
2012-04-20 09:28:50 -04:00
WANTLIB += c celt0>=1 m pthread readline samplerate sndfile
WANTLIB += sndio termcap
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
- update to 0.116.1, mostly stability/reliability fixes - add sndio backend playback under aucat server is pretty solid. for full-duplex, starting aucat with 'aucat -l -b 2048' and jackd with just 'jackd -d sndio' seems to work best for me. we want low latency anyway, right ;)
2009-01-11 05:51:45 -05:00
MASTER_SITES = ${HOMEPAGE}downloads/
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
convert to new style depends zap default spec that are not needed convert libspecs as well convert p* to REVISION. No package changes
2010-11-14 19:22:45 -05:00
LIB_DEPENDS = audio/libsndfile \
Update to jack-0.121.3. README changes from rathov@ tweaks and ok shadchin@
2012-01-24 03:03:52 -05:00
audio/libsamplerate \
Fix after celt update ok ajacoutot@
2012-04-20 09:28:50 -04:00
audio/celt>=0.11.0
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
Explicitely add libtool to BUILD_DEPENDS as jack autohell uses macros from libtool.m4. Builds fine with ports libtool otherwise.
2010-06-23 13:06:44 -04:00
# uses macros from libtool.m4
convert to new style depends zap default spec that are not needed convert libspecs as well convert p* to REVISION. No package changes
2010-11-14 19:22:45 -05:00
BUILD_DEPENDS = devel/libtool
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
USE_LIBTOOL = Yes
convert to new style depends zap default spec that are not needed convert libspecs as well convert p* to REVISION. No package changes
2010-11-14 19:22:45 -05:00
USE_GROFF = Yes
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
LIBTOOL_FLAGS += --tag=disable-static
Update to jack-0.121.3. README changes from rathov@ tweaks and ok shadchin@
2012-01-24 03:03:52 -05:00
AUTOCONF_VERSION = 2.65
AUTOMAKE_VERSION = 1.10
* clean up sndio(7) driver * update README.OpenBSD * add patches to let it build on gcc2 archs (from Sebastian Reitenbach) * disable audio(4) driver
2010-06-06 21:44:38 -04:00
CONFIGURE_STYLE = autoconf automake
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
CONFIGURE_ARGS += ${CONFIGURE_SHARED} \
- update to 0.116.1, mostly stability/reliability fixes - add sndio backend playback under aucat server is pretty solid. for full-duplex, starting aucat with 'aucat -l -b 2048' and jackd with just 'jackd -d sndio' seems to work best for me. we want low latency anyway, right ;)
2009-01-11 05:51:45 -05:00
--with-default-tmpdir=/var/tmp \
* clean up sndio(7) driver * update README.OpenBSD * add patches to let it build on gcc2 archs (from Sebastian Reitenbach) * disable audio(4) driver
2010-06-06 21:44:38 -04:00
--disable-sun \
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
--disable-portaudio \
don't use dynamic SIMD instructions.
2009-01-12 05:45:01 -05:00
--disable-optimize
update to 0.111.2.1169 - don't bother trying to fix compiler optimization flag tests. they're badly broken/linux spcific, and we don't use them anyway. - the net source client became a "real" client (executable), instead of an "in process" client (plugin) - previous sun_driver patches accepted upstream, plus: * fix cycle timing in duplex mode by moving calculations and function calls out of the poll() synchronization loop * shorten xrun and silence writing/reading messages * remove unused variables * attempt to stop continuous playback underruns in duplex mode that are caused by the capture buffer overrunning * try harder to make sure we have pristine buffers after sun_driver_start() * use native endian audio encodings * report a delay when poll() times out, instead of effectively running a null cycle now jack works on my r10k sgi :)
2008-04-22 05:34:58 -04:00
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
CONFIGURE_ENV = CPPFLAGS="-I${LOCALBASE}/include" \
LDFLAGS="-L${LOCALBASE}/lib" \
update to 0.111.2.1169 - don't bother trying to fix compiler optimization flag tests. they're badly broken/linux spcific, and we don't use them anyway. - the net source client became a "real" client (executable), instead of an "in process" client (plugin) - previous sun_driver patches accepted upstream, plus: * fix cycle timing in duplex mode by moving calculations and function calls out of the poll() synchronization loop * shorten xrun and silence writing/reading messages * remove unused variables * attempt to stop continuous playback underruns in duplex mode that are caused by the capture buffer overrunning * try harder to make sure we have pristine buffers after sun_driver_start() * use native endian audio encodings * report a delay when poll() times out, instead of effectively running a null cycle now jack works on my r10k sgi :)
2008-04-22 05:34:58 -04:00
LIBS="-pthread" \
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
HAVE_DOXYGEN="false"
.ifdef DEBUG
CONFIGURE_ARGS += --enable-debug
.endif
- update to 0.116.1, mostly stability/reliability fixes - add sndio backend playback under aucat server is pretty solid. for full-duplex, starting aucat with 'aucat -l -b 2048' and jackd with just 'jackd -d sndio' seems to work best for me. we want low latency anyway, right ;)
2009-01-11 05:51:45 -05:00
post-extract:
mkdir -p ${WRKSRC}/drivers/sndio
cp ${FILESDIR}/Makefile.am ${FILESDIR}/sndio_driver.{c,h} \
Update to jack-0.121.3. README changes from rathov@ tweaks and ok shadchin@
2012-01-24 03:03:52 -05:00
${WRKSRC}/drivers/sndio
- update to 0.116.1, mostly stability/reliability fixes - add sndio backend playback under aucat server is pretty solid. for full-duplex, starting aucat with 'aucat -l -b 2048' and jackd with just 'jackd -d sndio' seems to work best for me. we want low latency anyway, right ;)
2009-01-11 05:51:45 -05:00
* clean up sndio(7) driver * update README.OpenBSD * add patches to let it build on gcc2 archs (from Sebastian Reitenbach) * disable audio(4) driver
2010-06-06 21:44:38 -04:00
AUTO_ENV= AUTOMAKE_VERSION=${AUTOMAKE_VERSION} \
AUTOCONF_VERSION=${AUTOCONF_VERSION}
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
post-patch:
* clean up sndio(7) driver * update README.OpenBSD * add patches to let it build on gcc2 archs (from Sebastian Reitenbach) * disable audio(4) driver
2010-06-06 21:44:38 -04:00
cd ${WRKSRC}; ${AUTO_ENV} aclocal
pre-configure:
cd ${WRKSRC}; ${AUTO_ENV} automake --add-missing --foreign
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@
2008-03-23 23:01:28 -04:00
.include <bsd.port.mk>
Reference in New Issue Copy Permalink