On Sun, Aug 01, 2010 at 05:57:37PM -0400, Ana Guerrero wrote:

> Until version 0.9.3-7, hydrogen used to build in non-linux arches
> (hurd-i386, kfreebsd-{amd64,i386}), with upload 0.9.4-1, a build
> dependency on libportmidi-dev was added and since this package is not
> present in the non-linux arches, hydrogen can not build in those archs
> anymore.

Just to give a small clarification: hydrogen also has jackmidi, which is
in all ways superior to portmidi. So at least from this point of view,
not having portmidi on non-linux arches isn't really a problem. Au
contraire, it's the better choice anyway.

> but it looks like the scons build system does not support kfreebsd system
> anyway:
> scons --directory="." CC="cc" CFLAGS="-g -O2 -g -Wall -O2" CXX="g++" 
> CXXFLAGS="-g -O2 -g -Wall -O2"   libarchive=1 portaudio=1 portmidi=1 lash=1 
> prefix=/usr optflags="-g -O2 -g -Wall -O2" 
> scons: Reading SConscript files ...
> Exception: Platform 'gnukfreebsd8' not supported:

I think I can fix this. At least I know why it's broken, so let's see
how far we can get with some tweaks to Sconscript.

> So.. if you want the package migrate to testing, you will have to fix this
> and get non-linux packages OR ask for removal from the current non-linux
> packages and drop totally non-linux support (no very nice option!).

On a side note, I don't think there's at least one hydrogen user out
there running on kFreeBSD. In contrast to Linux, the FreeBSD kernel has
never been tailored to low latency and deterministic scheduling due to
its focus on server machines.

Linux kernel developers have put much effort into realtime scheduling,
many of the RT patches have been integrated into mainline during the
last decade. FreeBSD is nowhere near, so technically speaking, as of
now, it's only second choice for audio production.

However, this won't prevent me from trying my best to get you a working
hydrogen on kFreeBSD. ;)


mail: a...@thur.de      http://adi.thur.de      PGP/GPG: key via keyserver

pkg-multimedia-maintainers mailing list

Reply via email to