Re: [fluid-dev] Re: Jack CVS error?

[Frank Barknecht]

Hallo,
Josh Green hat gesagt: // Josh Green wrote:

> Ahh, I see what you are getting at now.  I don't quite understand why
> fluid~ would have to be built with the same dependencies as the
> libfluidsynth library though.  Shouldn't those dependencies get resolved
> when fluid~ links to libfluidsynth?  Forgive my ignorance of how fluid~
> works :) 

I'm actually very ignorant how linking works, and that probably is
worse. ;) 

Anyway fluid~ is built using these commands (2 lines): 

g++ -c -ffast-math -DNDEBUG -O3 -march=athlon -pthread -fPIC
-DFLEXT_SYS=2 -I../../../pd/src -I/usr/include/flext fluid/main.cpp -o
pd-linux/release-single/main.opp

g++ -pthread -shared  -Wl,-S -L../../../pd/bin -L/usr/lib -o
pd-linux/release-single/fluid~.pd_linux
pd-linux/release-single/main.opp  -lfluidsynth -lflext-pd_s

So I just link with libfluidsynth. The resulting binary in turns looks like
this (".pd_linux" is just the suffix Pd expects for externals plugins): 

$ ldd pd-linux/release-single/fluid~.pd_linux
        linux-gate.so.1 =>  (0xffffe000)
        libfluidsynth.so.1 => /usr/lib/libfluidsynth.so.1 (0xb7ecb000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7def000)
        libm.so.6 => /lib/tls/libm.so.6 (0xb7dca000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7dbf000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7dad000)
        libc.so.6 => /lib/tls/libc.so.6 (0xb7c75000)
        libladcca.so.2 => /usr/lib/libladcca.so.2 (0xb7c6b000)
        libuuid.so.1 => /lib/libuuid.so.1 (0xb7c68000)
        libreadline.so.5 => /lib/libreadline.so.5 (0xb7c3b000)
        libncurses.so.5 => /lib/libncurses.so.5 (0xb7bf8000)
        libjack-0.100.0.so.0 => /usr/lib/libjack-0.100.0.so.0 (0xb7be1000)
        libasound.so.2 => /usr/lib/libasound.so.2 (0xb7b2d000)
        libdl.so.2 => /lib/tls/libdl.so.2 (0xb7b29000)
        /lib/ld-linux.so.2 (0x80000000)

Most of these "cross-dependencies" like readline, ncurses etc. are not used in
fluid~ itself at all.

> The drivers are currently used by other applications such as
> QSynth and Swami, so I don't see those dependencies going away for this
> major revision of FluidSynth. 

Ah, no need to hurry at all, it is generally working fine the current way for
probably years now. 

Ciao
-- 
 Frank Barknecht                 _ ______footils.org_ __goto10.org__