VLC.exe works but LibVLC through VLCJ has errors with plugins

[ryantheseer]

I have installed a custom build of LibVLC on two different Windows 7 PCs. On one, everything seems to run fine. On the other, I run into two different scenarios:

1. When running VLC.exe, it finds 419 modules, including the Live555 module, which is of particular interest because I'm trying to stream a video from RTSP/RTCP/RTP. Video playing runs fine.
2. When running LibVLC.dll through VLCJ Java wrapper (on the same machine that works when run from VLC.exe), it finds 397 modules and it shows 15 of similar warnings:

   Code: Select all

   core libvlc warning: Cannot load module 'xyz.dll' (The specified module could not be found (error 126))

And yet the files are all where they say they are supposed to be, and while running from VLC.exe, they are found and loaded successfully, as the case may be!

It is not a matter of VLCJ not finding the correct VLC installation folder, because if I delete one of these files that it cannot load, it no longer gives me an error for the deleted file.

I looked at one of the files in Dependency Walker, and I notice that most of the files that cannot be loaded depend on libgcc_s_seh-1.dll, a file that was produced by the Windows 64-bit build of VLC, although I notice that in the official release of Windows 64-bit VLC, this file does not exist, but it has an axvlc.dll and an npvlc.dll.

Are these clues enough to fix my problem?

[Rémi Denis-Courmont]

It looks like your question contains its own answer.

[ryantheseer]

Update: I had been using make package-win-common, so I never noticed that when I run package-win-strip, there are errors in the npapi-vlc project due to changes I've made in the VLC source code. I will now have to fix those errors in a custom npapi-vlc.

[ryantheseer]

It has trouble running on other PCs that don't have MingW in the PATH. I followed the instructions to enforce static linking of plugins successfully.