Sisyphus wrote: > ----- Original Message ----- > From: "Mark T. Kennedy" <[EMAIL PROTECTED]> > . > . > >> 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. >> > > I take it you have no problem creating the source distro for your > Inline::C-dependent module. The question is how do you also build the shared > library as part of the build process of your module ?
right. > > If my assessment is correct, you could try looking at 'perldoc perlxstut'. > It might have some pertinent info. > You'll probably also want to take a look at 'perldoc ExtUtils::MakeMaker'. > You'll be making use of either the 'LIBS' or 'MYEXTLIB' config option. (If > you're ok with makefiles, then the EU::MM documentation may be *all* that > you need.) i've been using unix since 1981 (really) so yes i'm comfortable with 'make' :-). i think i even met stu feldman once in the early 90's. i read ExtUtils::MakeMaker completely and looked at SDBM_File in the standard perl dist. it looks like there is a way to add rules to the generated make file and you can use that to cd into a subdir and run a make to build a shared library. but how do you tell the subdir makefile where to install it? and how do you update the .pm file (the Inline::C 'LIBS' setting) to point at it when it is local for testing and installed for prod? /mark > > Cheers, > Rob >
