1 Jun
2009
1 Jun
'09
12:06 p.m.
Stéphane Letz <letz(a)grame.fr> writes:
Le 1 juin 09 à 15:23, Nedko Arnaudov a écrit :
You dont link at all. You have to explicitly load the libarary and
resolve functions in it. I.e. like filling method pointers in the
virtual table of object of abstract class.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Stéphane Letz <letz(a)grame.fr> writes:
On Windows, you can use LoadLibrary() API function to load
libjack.dll.
On Linux, dlopen() can be used to load libjack.so.
Yes, but with what library do you link your code? AFACS the point is
that if libjack.so is missing, then the application does not start...
if no weak link strategy is used. What do
you think Stephane, can native jack clients on windows
achieve
performance which is almost at par as native ASIO apps ?
If we release LinuxSampler with jack support we have probably to
ship
libjack (otherwise the app does not start) with the sampler and it
could be that it conflicts with an
already installed jack.
Well I also recently had this kind of "weak" link requirement for
libjack on Linux. I think OSX supports some kind of weak linking with
any compiled framework, but the situation is less clear on Windows on
Linux. A possible solution would be to provide a special
"libweakjack" library with the appropriate bahaviour for that.