[vlc-devel] Enhancement Request...
adanecito at yahoo.com
Fri Apr 4 01:12:01 CEST 2008
I get emails from time to time on using JVLC and the
one thing they initially run into is not understanding
that vlc needs to know where the dlls are for the
windows environment unless you organize your
deployment package where the plugins directory is
located in the same directory as the executable.
Then once they get past that the developers try to
graduate to the next level. They use another java
deployment mechanism called web start that puts the
dlls into a cache directory. The problem then is the
cache directory can not be readily found except via a
class loading mechanism that as of the latest beta
release is no longer available. So okay the last and
least favorite way to handle this issue is to create a
second copy (remember the first copy is in java web
start cache) of the dlls somewhere in the user file
system where they can be written and read via the java
Yep mightly complex and needless work caused by a
recent change by Sun. I asked them to revert it back
and maybe they will but figured this should be easier
if the first dll loaded could figure out where it was
loaded from and use that to get the other dlls.
I am hoping this new quirk by Sun does not break the
new jna model developed by the jvlc team.
--- Pierre d'Herbemont <pdherbemont at free.fr> wrote:
> On Apr 3, 2008, at 4:52 PM, Rémi Denis-Courmont
> > Le Thursday 03 April 2008 17:28:37 Pierre
> d'Herbemont, vous avez
> > écrit :
> >> Hi Tony!
> >> On Apr 3, 2008, at 3:45 PM, Tony Anecito wrote:
> >>> I have a simple enhancement request. That is if
> >>> lib path is not passed to vlc on a command line
> >>> libs figure out where they are and use that
> path. In
> >>> other words do not even assume that they are
> >>> to where the exe starting up in a plugins
> >>> but the library say vlc-control query the os and
> >>> where it is and then use that path.
> >> Actually that what is being done on windows and
> Mac OS X (and BeOS
> >> too). Isn't it working?
> > Hmm, isn't Windows using the executable path
> rather than the library
> > path? I
> > don't even know if DLLs can find their run-time
> True. I didn't understand the question actually. On
> Mac OS we do
> detect the framework and fix up the path
> accordingly. We could do the
> same with libvlc. I don't know if it is possible on
> Windows. Does
> someone do?
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
More information about the vlc-devel