----- Original Message ----- From: "Eric Wilhelm" <[EMAIL PROTECTED]> . . > > <snip> > >And then run the Inline::C script with the config option: > > > >WRITE_XS_FILE_ONLY => ['.', 'Module', 'My::Module', 'My::Module'] > > Ok, I still don't like the idea of manually modifying the code as part > of the build process. IIRC, one couldn't do the above as a > -MInline=... argument because of the array ref, but we can work through > that.
It was just a demo of the concept written in terms that I could understand. If there's a better means to the end, then I have no objection to that. (And if you can improve on what we get at "the end", so much the better.) . . > > And here is the real rub for me. Most of my Inliney modules started > life that way and I would prefer to continue development in that mode > rather than switching to XS. I certainly respect your right to do things the way *you* want :-) > It sounds like your use-case is more > along the lines of "generate the XS and start a module around it." Yep. A lot of what followed in your post was a little difficult for me to understand - I'm not really up to date with Module::Starter or Module::Build, and Inline has options that I don't know much about. (The fact that I don't really understand XS, MakeMaker, and a whole host of other stuff probably doesn't help, either.) If there was something there that you wanted my response to, just let me know and I'll try to oblige :-) If this functionality were to be achieved through a module in the "Module" namespace, does it still hook into the Inline::C functions (ie does it 'require "Inline/C.pm";' ) ? Or does it work entirely independent of the Inline modules ? Cheers, Rob
