newbie2
September 27th, 2006, 06:37 PM
Considering some of the vitriol dropped into the comments section of the Penguin.SWF blog post he wrote, Melanson may not be so glad he tried to answer the question.
He placed the blood-stained finger of blame on three things: libraries, libraries, and libraries:
While we have the plugin limping along on our development machines, there comes a point where we need to hand off builds to our QA team for testing. This is when we notice that the plugin works great on our dev boxes, but hardly or not at all on any other distributions.
Generally, the problem is libraries, libraries, libraries. For example, the player dynamically opens libasound.so to dig out the ALSA audio functions. I recently learned that the 'libasound.so' symlink is only available on systems with the right devel packages installed. The proper file to open is 'libasound.so.2'. Hopefully. Repeat for the rest of the dynamic library loads.
http://www.webpronews.com/expertarticles/expertarticles/wpn-62-20060927LinuxFlashPlayerSagaContinues.html
:rolleyes:
He placed the blood-stained finger of blame on three things: libraries, libraries, and libraries:
While we have the plugin limping along on our development machines, there comes a point where we need to hand off builds to our QA team for testing. This is when we notice that the plugin works great on our dev boxes, but hardly or not at all on any other distributions.
Generally, the problem is libraries, libraries, libraries. For example, the player dynamically opens libasound.so to dig out the ALSA audio functions. I recently learned that the 'libasound.so' symlink is only available on systems with the right devel packages installed. The proper file to open is 'libasound.so.2'. Hopefully. Repeat for the rest of the dynamic library loads.
http://www.webpronews.com/expertarticles/expertarticles/wpn-62-20060927LinuxFlashPlayerSagaContinues.html
:rolleyes: