I am the ecasound FreeBSD port maintainer. I just sent an update of
ecasound to version 2.0.2 and it works fine, good job! :)

I am now trying to compile ecawave (again). The first problem I stumbled
upon is that ecawave is not linking with the proper qt library on fbsd
here. Here, to link with qt2 you have to specify -lqt2, not -lqt.

I have attached patches to the Makefiles that fix this issue.

The second problem I had is with the eternal -pthread flag on FreeBSD.
You need it to link with pthreaded apps. And ecasound is one. And
ecasound-config --libs, for some reason, doesn't give -pthread in the
list. So I had to include that in the patch too.

But I still have problems. First is that horrible warning message when
linking:

/usr/lib/libc.so.4: WARNING! setkey(3) not present in the system!
/usr/lib/libc.so.4: warning: this program uses gets(), which is unsafe.
/usr/lib/libc.so.4: warning: mktemp() possibly used unsafely; consider
using mkstemp()
/usr/lib/libc.so.4: WARNING! des_setkey(3) not present in the system!
/usr/lib/libc.so.4: WARNING! encrypt(3) not present in the system!
/usr/lib/libc.so.4: warning: tmpnam() possibly used unsafely; consider
using mkstemp()
/usr/lib/libc.so.4: warning: this program uses f_prealloc(), which is
not recommended.
/usr/lib/libc.so.4: WARNING! des_cipher(3) not present in the system!
/usr/lib/libc.so.4: warning: tempnam() possibly used unsafely; consider
using mkstemp()

this is probably due to ecawave or ecasound libs linking to -lc_r or
something. I noticed ecawave linking to -lgcc, this might not be good.

I don't know, really.

So now I can compile it. And run it! :) But when I start it, I have the
message: "Warning! Can't access temporary directory
/tmp/ecawave-anarcat. Ecawave may not work properly." The thing is that
the directory is there. It exists...

This really looks promising. Is it possible to make multi-track mixing
with ecawave? This is mostly why I would use it. I mainly need it to mix
seperate wave files together and "align" them on arbitrary boundaries.

On a side note, is there planned support for ESound/nas/rplay/aRts API?