in reply to Re: Perl, Wince and DBI
in thread Perl, Wince and DBI

Thanks for the quick answers

Thing is, on Wince I do not even have a command prompt! Oh joy. I think you can get a command prompt download but is the module installation suitable for this platform?

I am running Apache on the PDA and so far so good.

Jason

Replies are listed 'Best First'.
Re^3: Perl, Wince and DBI
by tphyahoo (Vicar) on Oct 03, 2005 at 10:29 UTC
    Is ppm suitable for win32 for handhelds? There are test results for dbi on various operating systems are here but win32 for handhelds isn't mentioned. Maybe if it works for regular windows it works here or maybe not... so just try it. By the way, in terms of getting error messages to post them to perlmonks, you can just copy from the dos window of course, or you might want to try something like

    ppm install http://whatever/whatever.ppm > output.txt 2>&1 output.txt

    to get both the standard output and error output from ppm into a text file. good luck!

      Unfortunately, there are several forces working against me, firstly my complete novice knowledge of Perl and secondly my bemusement at the totally different interface and setup of WinCE (it does deserve the name).

      I don't even have ppm.

      The error message I get when I run the makefile is:

      "Can't locate auto/POSIX/autosplit.ix in ......." goes off the page and there is no scroll bar or wrap round

      "at /Storage Card/perl58m/lib/POSIX.pm ........."

      "Can't locate DBI/DBD.pm in @INC (@INC co........"

      "BEGIN failed--compilation aborted at \St........."

      I don't think that anything that works under windows works on WinCE. Everything seems specifically compiled/written for these devices

      Jason

        Well, if you are running this from the dos prompt (you do get one in win ce I hope!?), using the > output.txt 2>&1 output.txt incantation, you should be able to at least get that error into a text file.
      ppm install http://whatever/whatever.ppm > output.txt 2>&1 output.txt
      That kind of redirection doesn't work in command.com, with which I'm (more) familiar. I don't have the slightest idea about cmd.exe, but if you're implying that it ought to work in it, then I'm glad to know that; OTOH I don't have the slightest idea about the WinCE environment, whatever it is, either...