List Info

Thread: instalations and native libs




instalations and native libs
user name
2006-11-14 14:13:16
Hi Damencho,

On 11/14/06, Damian Minkov < damenchodamencho.com">damenchodamencho.com> wrote:
Hi,

There was a problem with the installations I've just fixed them(we
haven't added the bundles and libs for the sip,msn and callhistory).


Great! Does this mean that we now have a working windows installation? 

But as the jmf libs are in the bundle what about the natvie libs. where

Good question. However, I think the problem does not only concern JMF and that we need a more generic rule for natives. We're going to need native libs for jdics as well and I am sure that other cases would also appear. So here's what I suggest. Inside lib we have a "native" directory. Inside this directory we can create os-specific subdirs that contain shared libs for the corresponding OS ( e.g. native/macosx native/windows native/linux and etc.). We put all native libs directly inside these subdirectories.

The scripts that generate the installers would then get the libs (.so or .dll) that they need and make sure that when the installed sip-communicator is executed, its LD_LIBRARY_PATH or PATH env vars contain all the dlls that were in the corresponding native/xxx dir.

How does this sound? I feel that I might have been unclear so let me know if I need to explain further.

Damencho would this be ok for the IzPack packages? Martin, Pavel, Romain, would that be ok for your packages?

Emil
&nbsp;

to place them so they can be added to the path or library path ?

damencho

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net">dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net">dev-helpsip-communicator.dev.java.net


[1]

about | contact  Other archives ( Real Estate discussion Medical topics )