I haven't been following things very closely for a while, but the reason I got involved with Inline in the first place is that I didn't want to mess with XS when providing a Perl binding for my open-source workflow toolkit wftk. It's a standard ASCII-C package, under Windows it's a DLL. What are my options at this point for providing an easily installable package based on Inline under Windows and under Unix? Back in the early Inline days I managed to get Perl compiled using mingw32 and thus included Inline that way for experimental purposes, but a package based on that probably wouldn't work with ActiveState Perl under Windows. Not that I've tried, actually.
Should be possible. I've used Inline C to build a perl extension (module) that binds to a third-party dll. The XS code that is autogenerated (on Win32) can be used to build a module that does not depend upon the Inline module. That same XS code works on linux, as well as on both mingw-built and msvc-built perls for win32.
Do we have cookbook examples for installation/distribution questions like this? Or should I attempt to write some?
'perldoc Inline-FAQ' - "How do I create a binary distribution using Inline ?". (Btw, you will probably find that windows binaries built with mingw perl work fine on ActiveState perl, and vice-versa.)
'perldoc Inline::C-Cookbook' - "Exposing Shared Libraries"
Cheers, Rob
--
Any emails containing attachments will be deleted from my ISP's mail server before I even get to see them. If you wish to email me an attachment, please provide advance warning so that I can make the necessary arrangements.
