On Mon, Aug 12, 2002 at 12:37:08PM -0700, Mathew, George (RDM) wrote: > Hi, > > Any particular reason why there is no port of perl to VxWorks yet?
No people with both VxWorks access and the time to do something about the situation have showed up so far. > With it popularity among RTOSes, it seems a little strange. I have > never done any porting before... what would it involve to port perl to > VxWorks? To my knowledge, VxWorks is POSIX compliant. Could it be done > by an amateur like me? Possibly. In one end of the spectrum it mean editing a file to suit VxWork's capabilities (which APIS are supported, which header files are available, and so forth), but a lot of the potential complexity depends on how does one compile executables (compiler? cross compiler? a build tool like make?) on VxWorks, and on various capabilities (does VW have dynamic loading, for example). The easiest way to "port" Perl would be if VxWorks has a Bourne-like shell and the usual UNIX shell tools like sed, tr, sort, uniq, awk, etc. available, in that case the whole project might just consist of running a big shell script (possibly also having to write a VxWorks-specific "hints file"). If you are interested, I suggest you contact the mailing list [EMAIL PROTECTED] and state your interest in such a project. > Thanks, > -George -- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack Cohen
