The SDL Perl module is a binding to libsdl (and various other libraries, to be precise). Those are written in C and thus have to be compiled separately for every architecture and OS. The SDL Perl module also comprises compiled shared object files (such as Audio.so), which serve as glue code between the Perl interpreter and the above mentioned libraries. When you say "use SDL::Audio;" perl dynamically loads Audio.so behind the scenes, which in turn loads libsdl.so, etc.
In other words, to be able to run your SDL Perl code, those platform specific shared object files need to be installed on the target systems your code should run on. This means that - unlike with a pure-Perl module - you can't just bundle up your Perl code plus the required modules and expect it to run on every system where a standard Perl is installed. You'd either have to create a different bundle for each combination of architecture, OS, and major Perl-version (not recommended), or tell your potential users to install the SDL Perl module plus the dependent libs themselves on their system (e.g. using available precompiled packages). Once they are installed, your same Perl code will of course run on both Windows and Linux — in that sense it's "cross-platform".
Hope this clears it up.
In reply to Re^7: sound and gamepad support in Perl?
by Anonyrnous Monk
in thread sound and gamepad support in Perl?
by AGhoulDoingPerl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |