On Wed, 2002-07-17 at 19:02, drieux wrote: > > On Wednesday, July 17, 2002, at 03:21 , Chas Owens wrote: > [..] > > however Inline::C is not always available, > [..] > > http://search.cpan.org/search?dist=Inline > > yes???? from the Readme it notes: > > "Inline saves you from the hassle of having to write and compile your own > glue code using facilities like XS or SWIG. Simply type the code where you > want it and run your Perl as normal. All the hairy details are handled for > you. The compilation and installation of your code chunks all happen > transparently; all you will notice is the delay of compilation on the > first run." > > > Hence the limiting factor is the existence of a compiler on > the host where the code will run???? > > Or is there a way to get the C code to pre-compile and ship that, > as one can do with the XS 'hassle' approach.... > > He said noting some of the info available in the document.... > > ciao > drieux
Well, Inline creates a directory called (by default) _Inline in the directory where the perl script resides that holds the compiled C code (and some form of checksum to keep it from recompiling unless it needs to). I would guess it is possible to copy that directory to your target platform (assuming they are have binary compatibility). I think I remember reading in the docs that it is possible to create a module using Inline that is compiled on one machine and delivered to another. <joke>All of this should be moot anyways since all machines <snide voice>worth using</snide voice> come with a compiler.</joke> -- Today is Pungenday the 52nd day of Confusion in the YOLD 3168 Grudnuk demand sustenance! Missile Address: 33:48:3.521N 84:23:34.786W -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
