I have run the older 5.6 on both a Zaurus and a 3G PDA phone, both
with smaller memories than the VX6700, and including DBI::PurePerl and a
pure perl DBD, so hopefully my much smaller spamkiller script
would run OK. But I fear it may be 5.8 dependent
(esp. the req'd Net::POP3 modules). And I'd like to
run my weblog analyzer scripts, and maybe run ssh from
http://www.rainer-keuchel.de/software.html.
Guess I'll see how far I can get
w/ the older version before trying to DIY w/ the latest (even tho
it would be kewl).
BTW Is your WinCE version free of Serious Design Limitations?
I saw that, and did some more digging (the linked thread is 2 years
old), and there are some oddly related issues that popped up during
my research (mostly fixed by registry hacks).
BTW: on perlce, you mention the threaded build is a memory pig...
have you tried building with the latest threads changes ? I wonder if
the stack tuning would help any ? Also, which version of WinCE were
you running ? (I'd be running WinMobile 5.0)
And even tho I said I didn't need any GUI stuff...do you have
any idea if Win32::GUI has any hope of running on WinCE ?
Anyway, thanks for all the info.. | [reply] |
you look prepared for the battle, I no more fear for you to lose the sanity :):)
I have cassiopeia(MIPS) PocketPC 3.0, and also have some ARM-enabled device with PocketPC 4.20
When you'll be running 5.0, could you please look at "serious limitation" there? :)
As for threads - I did the build (so compiler did not choke), but actual threading was not working, rather all threads were waitning for other threads.
I am not optimistic for threading on Win32, so IMO WinCE even not worth trying... (your opinion may vary, of course :)
As for Win32::GUI - I think there are chances for it to work, albeit stripped version. Just comment out what will be not working, and remaining stuff will work. Actually WinCE C library is quite good at Win32 GDI, yet CELIB has some more.
Look at CELIB sources, there are many Win32-like functions.
| [reply] |
