Sisyphus wrote: > ----- Original Message ----- > From: "Mark T. Kennedy" <[EMAIL PROTECTED]> > To: <inline@perl.org> > . > . >> my typical wrapper consists of a single 'pm' file which invokes Inline::C >> to AUTOWRAP a shared >> library. > > Then you shouldn't have to make any special allowance for the fact that > Inline::C is involved - except for specifying Inline-0.44 as a dependency. > Just treat it the same as you would for any other pure perl module, and > Inline::C should, I think, take care of the rest. (I normally use EU::MM, > but I expect the same would hold wrt M::B.) > > If you want to remove the dependency upon Inline::C and turn your module > into a usual XS type of build, then you might find InlineX::XS and/or > InlineX::C2XS useful. (Those modules could do with a decent workout.) > > Cheers, > Rob >
then i guess for me the issue isn't about the early or late generation of the XS glue from Inline, it is about the simpler problem of using any of the existing module tools (EU:MM or M::B) to build and deploy a C shared library for use with my Inline::C-dependent module. anyone know where to look for examples/documentation for that? i tried yesterday but couldn't find anything in a man page or online. i even looked into my CPAN 'build' cache but all the examples were either XS or involved complex hand-written Makefile.PL's. any pointers/examples would be greatly appreciated. /mark
