perlce-user — Mailing list for PerlCE users (perl for WinCE devices)

RE: [perlce-user] perl on windows 2003

[Massimo B. <mas...@ho...>]

Tks Vadim,
this was the solution.

I did not try the only working binaries.

I am really a beginner.

Tks again
Massimo

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

RE: [perlce-user] perl on windows 2003

[Konovalov, V. <vko...@sp...>]

> for perl-wince I tryed with perl-wince-x86-hpc-wce300.tar.gz 
> (it is a big 
> package)
> 
> but for perlide-wince I tryed all:
> perlide-wince-sh3-pocket-wce300.tar.gz
> perlide-wince-sh4-hpc-wce211.tar.gz
> perlide-wince-x86em-palm-wce211.tar.gz
> perlide-wince-x86em-pocket-wce300.tar.gz
> 
> And all give me the same error.
> 
> I agree with you, I am using the wrong binaries but .... what 
> do I have to 
> use? My processor is:
> Intel(R) PXA255

Look at the table
http://msdn.microsoft.com/embedded/usewinemb/ce/supproc/default.aspx

Your processor there is under ARM category.

Did you followed Merphy laws closely? :) Seems like you tried all but your
configuration ...



Best regards,
Vadim.

RE: [perlce-user] perl on windows 2003

[Massimo B. <mas...@ho...>]

Tks for the answer Vadim,

for perl-wince I tryed with perl-wince-x86-hpc-wce300.tar.gz (it is a big 
package)

but for perlide-wince I tryed all:
perlide-wince-sh3-pocket-wce300.tar.gz
perlide-wince-sh4-hpc-wce211.tar.gz
perlide-wince-x86em-palm-wce211.tar.gz
perlide-wince-x86em-pocket-wce300.tar.gz

And all give me the same error.

I agree with you, I am using the wrong binaries but .... what do I have to 
use? My processor is:
Intel(R) PXA255

Tks
Bye
Massimo


>From: "Konovalov, Vadim" <vko...@sp...>
>To: Massimo Balestra 
><mas...@ho...>,per...@li...
>Subject: RE: [perlce-user] perl on windows 2003
>Date: Tue, 31 May 2005 12:25:46 +0400
>
> > I bought a hp ipaq 2210 with windows mobile 2003. I am new
> > for this kind of
> > devices but I would like to run perl scripts on it.
> >
> > I tryed to download perlce but when I run it it always says
> > "perl is not a
> > valid pocket pc application".
>
>most probably you're trying to run binaries for another processor.
>
>Which namely binaries have you tried?
>
>Vadim.
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Yahoo.
>Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
>Search APIs Find out how you can build Yahoo! directly into your own
>Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
>_______________________________________________
>perlce-user mailing list
>per...@li...
>https://lists.sourceforge.net/lists/listinfo/perlce-user

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

RE: [perlce-user] perl on windows 2003

[Konovalov, V. <vko...@sp...>]

> I bought a hp ipaq 2210 with windows mobile 2003. I am new 
> for this kind of 
> devices but I would like to run perl scripts on it.
> 
> I tryed to download perlce but when I run it it always says 
> "perl is not a 
> valid pocket pc application".

most probably you're trying to run binaries for another processor.

Which namely binaries have you tried?

Vadim.

[perlce-user] perl on windows 2003

[Massimo B. <mas...@ho...>]

Hi,
I don't know if this is the correct place to ask this question but if it is 
not, please, suggest me where to ask.

I bought a hp ipaq 2210 with windows mobile 2003. I am new for this kind of 
devices but I would like to run perl scripts on it.

I tryed to download perlce but when I run it it always says "perl is not a 
valid pocket pc application".

Also perlide (from http://www.rainer-keuchel.de/wince/dirlist.html) gives me 
the same error. (I tryed with all installation files.

Is there somebody who can siggest me how to run any perl on my ipaq?

Thanks
Massimo

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.com/

RE: [perlce-user] PerlCE and "real" console

[Konovalov, V. <vko...@sp...>]

> > by "weight" I mean mostly "size". the Perl tree on my iPAQ is 
> > 10.68 mb, 
> 
> That number could be greatly reduced.
> Not only you can freely delete unused PMs.
> I had few working experiments with Archive::Zip and some 
> modules hidden
> inside zip archive... but this hase little in common with 
> PerlCE... Also
> with many lib files on SD there is no problem with several 
> megabytes more or
> less...

I must correct confusing place before anyone confused:

I mean I tried that approach with PMs inside ZIP succesfully on PerlCE

by "little in common with perlCE" I meant that it does not closely related
to WinCE problems

Vadim.

RE: [perlce-user] PerlCE and "real" console

[Konovalov, V. <vko...@sp...>]

> > You're right, and having Win32::GUI will be a real 
> advantage there...

...

> 
> by "weight" I mean mostly "size". the Perl tree on my iPAQ is 
> 10.68 mb, 

That number could be greatly reduced.
Not only you can freely delete unused PMs.
I had few working experiments with Archive::Zip and some modules hidden
inside zip archive... but this hase little in common with PerlCE... Also
with many lib files on SD there is no problem with several megabytes more or
less...


> guess the 
> Perl/Tk distribution weights some mb more. compiling  
> Win32::GUI for the 
> CE platform shouldn't (I hope) add much more to the desktop version, 
> which actually is ~800kb DLL. but I don't have time to work 
> on it right 
> now, so this isn't really an issue.

Well, size is one aspect of 'lightweight', but startup speed is another one.
Rainer Keuchel notes that his build of Perl/Tk on WinCE is rather slow.
Obviously, he spend some efforts on profiling


> ,_PocketPC_Have_Serious_Design_Limitations which most often appears on
> devices with GSM radio stack, when many processes are always exist to
> support a phone.  

> I don't see how this one is related to PerlCE (more than any other WinCE 
> program, I mean). is there any special reason to consider this as a 
> problem for Perl?

you're right: this has nothing to do with Perl.
But I can't resist explaining when after upgrading to much more powerful
device I got much weaker Perl capabilities...


> > Another one is - probably latest patches to WinCE made some bad changes
and
> > now script often sporadically exits with a message "Exit code 14".
> > 
> > Probably my bad :(
> 
> well, right now I'm trying to run the whole perl test suite on my iPAQ. 
> should take quite a while, but, well, while I'm at the office the iPAQ 
> sits on its cradle doing nothing but sync most of the time; battery 
> time, at least, is not a problem :-)
> 
> I encountered some problems with @INC, but if I come up with something, 
> I will post the results and write an how-to for the wiki.
> 
> I hope that running the test suite should help isolate problems.

sounds very promising.

> 
> > When I did my changes, I sent patches to p5p. I think it is still
reasonable
> > to do same way. There's no WinCE pumpking.
> 
> but maybe a CVS repository on sourceforge could help, don't you think?

I will setup CVS this weekend, then.
If you will be kind to participate perlce project on SF - I'll give you all
permissions to that, just say me your user ID.

If development will have progress, then it will be reasonable to create
mailing list on perl.org: usually they create such lists quite quick.
(Mailing list for users of Tcl::Tk module was kindly created within a day!)

Best regards,
Vadim.

Re: [perlce-user] PerlCE and "real" console

[Aldo C. <da...@pe...>]

Konovalov, Vadim wrote:
> It was in my plans to look closer but, once again, my weak efforts were just
> not enough.
> Also, I asked for an advice in wince-developers ML but no good from that
> side either...

I know the feeling :-)

> You're right, and having Win32::GUI will be a real advantage there...
> 
> But Perl/Tk is very special on WinCE: ported by Rainer Keuchel is only older
> version without unicode, which is noticeable long to start, but another
> approach makes this situation considerable better. I use Tcl::Tk module, so
> things are more lightweight. See URL at
> http://perlce.sourceforge.net/cgi-bin/perlce-tcltkce-wiki.pl?Happy_Screensho
> ts for such screenshot examples

by "weight" I mean mostly "size". the Perl tree on my iPAQ is 10.68 mb, 
which means that I must put it on a Storage Card (not a big deal, as I 
have an SD card that fits inside the iPAQ main body; but my first iPAQ 
only had a Compact Flash jacket, which made it bigger :-). I guess the 
Perl/Tk distribution weights some mb more. compiling  Win32::GUI for the 
CE platform shouldn't (I hope) add much more to the desktop version, 
which actually is ~800kb DLL. but I don't have time to work on it right 
now, so this isn't really an issue.

> One is
> http://perlce.sourceforge.net/cgi-bin/perlce-tcltkce-wiki.pl?Be_Aware,_WinCE
> ,_PocketPC_Have_Serious_Design_Limitations which most often appears on
> devices with GSM radio stack, when many processes are always exist to
> support a phone.  

I don't see how this one is related to PerlCE (more than any other WinCE 
program, I mean). is there any special reason to consider this as a 
problem for Perl? and if this is a design limitation, I think there's 
very little to do, except maybe sign a petition and send it to Microsoft :-)

> Another one is - probably latest patches to WinCE made some bad changes and
> now script often sporadically exits with a message "Exit code 14".
> 
> Probably my bad :(

well, right now I'm trying to run the whole perl test suite on my iPAQ. 
should take quite a while, but, well, while I'm at the office the iPAQ 
sits on its cradle doing nothing but sync most of the time; battery 
time, at least, is not a problem :-)

I encountered some problems with @INC, but if I come up with something, 
I will post the results and write an how-to for the wiki.

I hope that running the test suite should help isolate problems.

> When I did my changes, I sent patches to p5p. I think it is still reasonable
> to do same way. There's no WinCE pumpking.

but maybe a CVS repository on sourceforge could help, don't you think?

> Inserting all kind of information to Wiki  - I am sure all people who have
> usefull things to say - they should share those useful bits.

I will, definitely.

cheers,
Aldo

RE: [perlce-user] PerlCE and "real" console

[Konovalov, V. <vko...@sp...>]

> > As another point, CMD.exe is not supported on (very) old WinCEs
> 
> I know and I understand, but since it is supported on (most commonly 
> used, I guess) non-very-old PocketPC devices, it makes lot of 
> sense to 
> have proper CMD.exe interaction. at least as an option, 
> either at build 
> time or at runtime.

I also think so.
More to say, I think it will be better when PerlCE port will be greatly
reorganized, may be dropping obsolete configs and agreeing on supported
ones...

Yet ruby on WinCE could be happily used from CMD.exe.
Don't know of other languages.

It was in my plans to look closer but, once again, my weak efforts were just
not enough.
Also, I asked for an advice in wince-developers ML but no good from that
side either...


> > IMO,  using PerlIDE is probably a way to make sutuation easier.
> 
> hrm. not quite. I mean, PerlIDE is fine, but I _do_ want 
> PerlCE to be a 
> command line friendly executable. the biggest use I see for Perl on a 

....

I agree with you.


> on the other hand (and on a completely unrelated topic) "real world" 
> applications on a PDA need a GUI very badly. for example, I think 
> porting Win32::GUI on PerlCE should not be terribly hard. at least, 
> should be more light-weight than Perl/Tk. and we all know 
> that weight is 
> an issue here :-)

You're right, and having Win32::GUI will be a real advantage there...

But Perl/Tk is very special on WinCE: ported by Rainer Keuchel is only older
version without unicode, which is noticeable long to start, but another
approach makes this situation considerable better. I use Tcl::Tk module, so
things are more lightweight. See URL at
http://perlce.sourceforge.net/cgi-bin/perlce-tcltkce-wiki.pl?Happy_Screensho
ts for such screenshot examples

Of course native widgets will help.


> 
> > it can be avoided but this is not largest problem, unfortunately :)
> 
> so let's talk about the largest problems first, and my 
> problem then :-)

One is
http://perlce.sourceforge.net/cgi-bin/perlce-tcltkce-wiki.pl?Be_Aware,_WinCE
,_PocketPC_Have_Serious_Design_Limitations which most often appears on
devices with GSM radio stack, when many processes are always exist to
support a phone.  

Another one is - probably latest patches to WinCE made some bad changes and
now script often sporadically exits with a message "Exit code 14".

Probably my bad :(

> 
> seriously, I have a good knowledge of the Perl codebase, internals, 
> build process, etc. as well as good experience on the Win32 
> platform. I 
> have very little spare time at hand, but if there's something 
> I can do 
> for PerlCE, just let me know. eventually, post a todolist on the wiki 
> and I'll see if I can do something.

I have no single doubts about your excellent experience in Perl internals,
externals and surrounding environment!

In case you'll make additions - of course they will be greatly appreciated
by following PerlCE users.

When I did my changes, I sent patches to p5p. I think it is still reasonable
to do same way. There's no WinCE pumpking.

Inserting all kind of information to Wiki  - I am sure all people who have
usefull things to say - they should share those useful bits.

Best regards,
Vadim.

Re: [perlce-user] PerlCE and "real" console

[Aldo C. <da...@pe...>]

Konovalov, Vadim wrote:
> its own window will not show up if -nocolsole option is used
> I am not exactly sure for spelling, but I will be more precise after RTFSing
> a bit.

you're right, I didn't noticed (the option is --noconsole, BTW). this is 
fine, but still output is placed in /perl_stdout.txt, not emitted on the 
command line.

> As another point, CMD.exe is not supported on (very) old WinCEs

I know and I understand, but since it is supported on (most commonly 
used, I guess) non-very-old PocketPC devices, it makes lot of sense to 
have proper CMD.exe interaction. at least as an option, either at build 
time or at runtime.

> IMO,  using PerlIDE is probably a way to make sutuation easier.

hrm. not quite. I mean, PerlIDE is fine, but I _do_ want PerlCE to be a 
command line friendly executable. the biggest use I see for Perl on a 
little device, except for prototyping algorithms, is to script small 
sydadmin tasks (such as backing up important files on a storage card, 
for example), for which a command line interface is much, much better 
than using PerlIDE.

on the other hand (and on a completely unrelated topic) "real world" 
applications on a PDA need a GUI very badly. for example, I think 
porting Win32::GUI on PerlCE should not be terribly hard. at least, 
should be more light-weight than Perl/Tk. and we all know that weight is 
an issue here :-)

> it can be avoided but this is not largest problem, unfortunately :)

so let's talk about the largest problems first, and my problem then :-)

seriously, I have a good knowledge of the Perl codebase, internals, 
build process, etc. as well as good experience on the Win32 platform. I 
have very little spare time at hand, but if there's something I can do 
for PerlCE, just let me know. eventually, post a todolist on the wiki 
and I'll see if I can do something.

cheers,
Aldo

RE: [perlce-user] PerlCE and "real" console

[Konovalov, V. <vko...@sp...>]

> sorry if this question appeared before, I'm new to the list 
> and didn't 
> find anything on the FAQ/ML archive/etc.

in ideal world - this eventually grow throughought WiKi
In real world - it will not be done until someone will do.
But, being even more realistic - information will eventually grow indeed.

> 
> is it possible to have PerlCE _without_ the fake console window, but 
> with _real_ STDIN/STDOUT/STDERR hooks?
> 
> as probably many of you did, I have installed PocketConsole from 
> http://www.symbolictools.de/ and Microsoft's CMD.exe on my 
> iPAQ: so now 
> I have a command prompt. but the current PerlCE, launched from there, 
> still pops up its own window and place its output in 
> /perl_(stdout|stderr|stdin).txt.

its own window will not show up if -nocolsole option is used
I am not exactly sure for spelling, but I will be more precise after RTFSing
a bit.

As another point, CMD.exe is not supported on (very) old WinCEs


> 
> what I would like to have is a Perl executable really 
> interacting with 
> the CLI, as on any regular desktop computer.

IMO,  using PerlIDE is probably a way to make sutuation easier.

> 
> I tried to investigate the issue by looking at the code, but 
> it seems to 
> me that this "fake-console" is a feature of celib, which 
> can't be avoided.

it can be avoided but this is not largest problem, unfortunately :)

[perlce-user] PerlCE and "real" console

[Aldo C. <da...@pe...>]

hello gentlemen,

sorry if this question appeared before, I'm new to the list and didn't 
find anything on the FAQ/ML archive/etc.

is it possible to have PerlCE _without_ the fake console window, but 
with _real_ STDIN/STDOUT/STDERR hooks?

as probably many of you did, I have installed PocketConsole from 
http://www.symbolictools.de/ and Microsoft's CMD.exe on my iPAQ: so now 
I have a command prompt. but the current PerlCE, launched from there, 
still pops up its own window and place its output in 
/perl_(stdout|stderr|stdin).txt.

what I would like to have is a Perl executable really interacting with 
the CLI, as on any regular desktop computer.

I tried to investigate the issue by looking at the code, but it seems to 
me that this "fake-console" is a feature of celib, which can't be avoided.

any hint?

cheers,
Aldo

[perlce-user] RE: Perl for Windows CE

[Konovalov, V. <vko...@sp...>]

> I don't know if you had a chance to read my last post to the 
> Wiki build 
> page, but I overcame the initial problem I had with 
> sys/types.h file. This 
> had to do with the Zip compression program I was using 
> (which, by default, 
> does not preserve directory paths found in compressed archive files).

I did read, but eventually had not time to investigate yet.
Isn't it your compression program Compress::Zlib?

BTW when building perl, it could be easier to place extensions into ./ext
directory for them to be easier rebuilt.

> 
> Now I am on to a different set of problems, and I believe I 
> am running into 
> issues having to do with the latest compilation of Perl 
> (version 5.8.6). 
> When you get a chance, please check it out. Also, I don't see 

Sure!

> too much 
> interest from others -- how many are on the list?

I think - not many.

I beleive people rarely use perl on WinCE: IMHO those who want robust usage
of Perl on pocket devices probably use Linux-based devices, while ordinary
WinCE users rarely want using perlce anyways.

WinCE port requires quite many improvements, but those improvements are not
done, due to many reasons.

Best regards,
Vadim.

[perlce-user] RE: Perl for Windows CE

[Kevin W. <kev...@ho...>]

Hi again,

I don't know if you had a chance to read my last post to the Wiki build 
page, but I overcame the initial problem I had with sys/types.h file. This 
had to do with the Zip compression program I was using (which, by default, 
does not preserve directory paths found in compressed archive files).

Now I am on to a different set of problems, and I believe I am running into 
issues having to do with the latest compilation of Perl (version 5.8.6). 
When you get a chance, please check it out. Also, I don't see too much 
interest from others -- how many are on the list?

Thanks,

Kevin in Chicago

>From: "Konovalov, Vadim" <vko...@sp...>
>To: Kevin Wittmer <kev...@ho...>
>CC: per...@li...
>Subject: RE: Perl for Windows CE
>Date: Tue, 22 Feb 2005 07:43:57 +0300
>
> > Thanks for the reply. In order to build Perl CE for Pocket PC
> > 2003, one item
> > that will need to be added is the machine profile definition
> > for PPC 2003
> > (these map to the platform type and are found in the
> > makefile.ce file).
>
>I did some work to factor those things out, but it requires more polishing
>and such stuff.
>
>
> >
> > I haven't gotten this far. Mostly I have been hung up with
> > the failure to
> > locate sys/types.h. This header file is included from the
> > perl.h header
> > file.
>
>probably you do not have environment variables setted up properly?
>
> >
> > We'll the Wiki link be found at the sourceforge web page.
>
>I set up wiki just few hours ago: for some reasons I did not succeeded
>setting up on SF site directly (although was very close :) but did 
>succeeded
>on other site, so I
>
> > Also, how active
> > is the mailing list.
>
>It has quite low traffic, and since some non-useful messages it becomes
>moderated list. But use freshly installed wiki instead.

[perlce-user] sys/types.h

[Kevin W. <kev...@ho...>]

When we last left off, I was had mentioned that I would first focus on 
building Perl for Windows (using Visual Studio .NET 2003). I was able to 
accomplish and it turned out to be rather easy. Following compilation of 
Perl for Windows, I then switched back to the ../wince directory to pick-up 
with building Perl for Windows CE. When I made another attempt at this 
build, I was back to the following error:


Compiling for wince-arm-pocket-wce300 LIB=C:\Windows CE Tools\WCE300\Pocket 
PC 2002\lib\ARM INCLUDE=C:\Windows CE Tools\WCE300\Pocket PC 2002\include 
PATH=C:\Program Files\Microsoft eMbedded C++ 4.0

clarm.exe -c -nologo -Gf -W3 -I.\include -I..\win32\include -I. -I.. -DW 
IN32 -D_CONSOLE -DNO_STRICT -D_WINDOWS -D_WIN32_WCE=300 -DUNDER_CE=300 -D 
ARM -D arm -D _ARM_ -D _arm_ -DPROCESSOR_ARM -D _MT -D _DLL -DPALM_SIZE 
-DPOCKET_SI ZE -I E:\MYLIBR~1\CELIB-~1.11-\inc -D PERL -O2 -Ot -DPERLDLL 
-DPERL_CORE -D _WINDOWS -D_WIN32_WCE=300 -DUNDER_CE=300 -D ARM -D arm -D 
_ARM_ -D _arm_ -DPROC ESSOR_ARM -D _MT -D _DLL -DPALM_SIZE -DPOCKET_SIZE -I 
E:\MYLIBR~1\CELIB-~1.11- \inc -D PERL -O2 -Ot -DUSE_PERLIO 
-DPERL_EXTERNAL_GLOB -Fowince-arm-pocket-wce30 0\dll\ ..\av.c av.c 
e:\perl\perl.h(380) : fatal error C1083: Cannot open include file: 
'sys/types.h'

No such file or directory
NMAKE : fatal error U1077: 'clarm.exe' : return code '0x2' Stop.
Looking more closing at the list of directories to include, we have the 
following:

INCLUDES = -I.\include -I..\win32\include -I. -I.. (#line 468)

There is also -I E:\MYLIBR~1\CELIB-~1.11-\inc. From what I have been to see, 
none of the directories related to EVC or the Pocket PC platform SDK have 
the sys/types.h header file.

I can locate the types.h header file in the following directory (part of VS 
.NET 2003):

C:\PROGRA~1\MICROS~1.NET\Vc7\include\sys>

In general, where should this header file be sourced from? The Embedded 
Visual C++ (base_ installation, the Windows CE Platform SDK, or the 
device-specific directory (include and lib)?

  - Kevin

[perlce-user] PerlCE installation

[Donato A. <don...@gm...>]

Hello,
I'm a newbie to perlCE and been having trouble (or so I think) running
it on my iPAQ rx3715, here is what ive done already:

downloaded the perl-wince-arm-pocket-wce300.zip file from the sourceforge s=
ite
copied the bin and lib dirs from the zip above to=20
\iPAQ File Store\Perl\
fixed the config.pm
substituted the DynaLoader.pm

is this all that is needed???

--=20
*******************************************
              Donato Azevedo
Engenharia de Controle e Automa=E7=E3o
                      UFMG
*******************************************

[perlce-user] Cannot open include file: 'sys/types.h'

[Kevin W. <kev...@ho...>]

Vadim -- Thank you very much for setting up the Wiki page. Thank you also 
for organizing the Perl CE SourceForge site.

All -- I have posted the following to the Wiki page:

---

Trying to build Perl 5.8.5 for CE

\perl 5.8.5\perl.h(380) : fatal error C1083: Cannot open include file: 
'sys/types.h': No such file or directory NMAKE : fatal error U1077: 
'clarm.exe' : return code '0x2' Stop.

In my latest attempt to build Perl for Windows CE, I have come across the 
error reported above. Part of my problem is trying to understand everything 
the makefile is doing. For example, what exactly is miniperl.exe all about? 
Although I have followed the instructions at http://perlce.sourceforge.net/, 
I still have this problem.

---

In general, does anyone on this list have experience to share with 
attempt(s) to build Perl CE using MS EVC++ 4.0?  I would like to work with 
others on bringing Perl CE up-to-date to build with EVC++ 4.0. Or more 
importantly, build a Perl CE for Pocket PC 2003.

-- Kevin

[perlce-user] perlce, tcltkce wiki setp up

[Konovalov, V. <vko...@sp...>]

Dear all,

due to popular demand (i.e. I decided it) but mostly because it was easy, I
set up a wiki to gather and share information about building perl, tcl/tk on
wince.

For some reasons I did not succeeded setting up on SF site directly
(although was very close :) but did succeeded
on other site. I'll move that wiki to SF when another popular demand to do
so will be :)

Link to it points from http://perlce.sf.net/ so it is
http://www.vkonovalov.ru/cgi-bin/perlce-tcltkce-wiki.cgi

This wiki should be considered as a helper of "perlce" and "tcltkce" SF
projects, and it could be fine if many links to related pages on wiki.tcl.tk
will be, and vice versa, and so on.

Please share your experience.

Best regards,
Vadim.

[perlce-user] RE: Perl for Windows CE

[Konovalov, V. <vko...@sp...>]

> Thanks for the reply. In order to build Perl CE for Pocket PC 
> 2003, one item 
> that will need to be added is the machine profile definition 
> for PPC 2003 
> (these map to the platform type and are found in the 
> makefile.ce file).

I did some work to factor those things out, but it requires more polishing
and such stuff.


> 
> I haven't gotten this far. Mostly I have been hung up with 
> the failure to 
> locate sys/types.h. This header file is included from the 
> perl.h header 
> file.

probably you do not have environment variables setted up properly?

> 
> We'll the Wiki link be found at the sourceforge web page. 

I set up wiki just few hours ago: for some reasons I did not succeeded
setting up on SF site directly (although was very close :) but did succeeded
on other site, so I 

> Also, how active 
> is the mailing list.

It has quite low traffic, and since some non-useful messages it becomes
moderated list. But use freshly installed wiki instead.

[perlce-user] RE: Perl for Windows CE

[Konovalov, V. <vko...@sp...>]

> I came across the SourceForge project for Perl port to 
> Windows CE about a 
> year ago. Since then I have tried on a couple of different 

nothing changed since then :)


> occassions to 
> compile the source code that can be downloaded from 
> http://www.rainer-keuchel.de/wince/perlce.html as well as 
> modifying the 
> wince make files that are included in the standard 5.8.x Perl 
> distribution. 
> Unfortunately, I haven't had a great deal of luck.

PerlCE page on SF contain instructions to compile, they should be working.

If not, feel free to post failing attempts.

> 
> Do you have any suggestions in regards to this?

Okay, I'll set up a WiKi system on this today evening or tomorrow and we'll
see how things are going.
Besides.

RE: [perlce-user] Perl Win32::API & Serial Ports

[Konovalov, V. <vko...@sp...>]

> Has anyone got the 5.8 build to work with Win32::API & 
> Win32::SerialPort?

I don't know!
:)

> I failed, see below for my attempt.  I tried falling back to 
> Rainers' perl56 build together with some Activestate 5.6.0 
> libs, and then I got Win32::API  & SerialPort working.  I'm 
> not sure if its a Dynaloader issue with 5.8. or just a build 
> incompatibility issue.

this is binary compat issue rather than dynaload one.

When building binaries, probably more modules should be placed into ./ext
subdir.
Probably time to rebuild... Don't know.

Actually compared to 5.6.0 CE build 5.8.2 lacks also Win32::OLE and
Compress::Zlib. Later one I succeeded rebuilding locally (together with
PerlIO::gzip)
OTOH 5.8.2 has more other modules, but I am not sure whether they worth the
place they occupy.

If you'll be rebuilding by yourself, I can assits you.
I can rebuild entire stuff with wider libraries (I always include Tcl::Tk
and actively use it), but I can't be sure about timeline... I planned this,
may be within a month...


> 
> Regards,
> Paul
> (copy of email sent to wince-devel list attached)
> 
> Hi,
> 
> I'm struggling to get serial ports working in PerlCE on an iPAQ.
> 
> Probably a produce of my own optimism, but I started with the perl 58
> distribution for arm-ppc at perlce.sourceforge.net
> 
> I then added in the SerialPort files posted on this group. 
> And finally I
> discovered the ARM version of Win32::API posted on Rainers site.
> 
> I've installed everything in (what I believe are) the correct 
> directories, but I
> get the error:
> Can't load /Storage Card/perl58m/lib/auto/Win32/API/API.dll for module
> Win32::API: load_file:Error at /Storage 
> Card/perl58m/lib/Dynaloader.pm line 72.
> at \My Documents\apitest.pl line 5
> 
> This is when running the apitest.pl script. Needless to say 
> the files are
> there. Is this a Dynaloader problem?
> 
> Help! I need to get a working serial implementation on the 
> ipaq, and I'd really
> rather use Perl as thats what I have experience of.
> 
> Can anyone either assist with the above problem, or suggest a 
> known working
> installation version mix (and file locations!!).
> 
> Many thanks,
> 
> Paul.
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive 
> Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> perlce-user mailing list
> per...@li...
> https://lists.sourceforge.net/lists/listinfo/perlce-user
> 

[perlce-user] Perl Win32::API & Serial Ports

[Paul M. <Pa...@or...>]

Hi,

Has anyone got the 5.8 build to work with Win32::API & Win32::SerialPort?

I failed, see below for my attempt.  I tried falling back to Rainers' perl56 build together with some Activestate 5.6.0 libs, and then I got Win32::API  & SerialPort working.  I'm not sure if its a Dynaloader issue with 5.8. or just a build incompatibility issue.

Regards,
Paul
(copy of email sent to wince-devel list attached)

Hi,

I'm struggling to get serial ports working in PerlCE on an iPAQ.

Probably a produce of my own optimism, but I started with the perl 58
distribution for arm-ppc at perlce.sourceforge.net

I then added in the SerialPort files posted on this group. And finally I
discovered the ARM version of Win32::API posted on Rainers site.

I've installed everything in (what I believe are) the correct directories, but I
get the error:
Can't load /Storage Card/perl58m/lib/auto/Win32/API/API.dll for module
Win32::API: load_file:Error at /Storage Card/perl58m/lib/Dynaloader.pm line 72.
at \My Documents\apitest.pl line 5

This is when running the apitest.pl script. Needless to say the files are
there. Is this a Dynaloader problem?

Help! I need to get a working serial implementation on the ipaq, and I'd really
rather use Perl as thats what I have experience of.

Can anyone either assist with the above problem, or suggest a known working
installation version mix (and file locations!!).

Many thanks,

Paul.

[perlce-user] ASK SANTA - Mini Remote Control Cars Are Back

[Elliott P. <arm...@ya...>]

SANTA SAYS - Mini-Cars Are Here At the Christmas Store

If your e-mail will not mae the following hyperlink --- more4me2.com/promo.php?id=94215 --- simply cut-and-paste in your internet browser.

You don't want to miss this ---  more4me2.com/promo.php?id=94215

No thanks: --- more4me2.com/remove.php?id=94215

[perlce-user] SANTA SAYS - Mini Remote Control Cars Are Back

[Barton M. <or...@ya...>]

ASK SANTA - Mini Cars Are Back At the Christmas Store

If your email browser can't make this hyperlink --- more4me2.com/promo.php?id=94215 --- go ahead and cut and paste in your internet browser.

Do not miss this ---  more4me2.com/promo.php?id=94215

No more ads: --- more4me2.com/remove.php?id=94215

[perlce-user] COMMENCE EARNING the INCOME You Deserve In Only days

[Evan S. <fis...@ya...>]

U CAN START EARNING the INCOME You Deserve Right Now

Tired of being turned down because you do not the right educational background?  Did you know that you are a qualified professional but simply lack the requested credentials after your name?  You know you deserve a better salary, more prestige but lack the Educational background  - even though you have the life's knowledge and the abilities requested in today's world?

Tired of being turned down because you do not the right educational background?  Non A.c.c.c. Institutions of Higher Learning will award you a Credential based on your current knowledge and your years of climbing the ladder at work.  Alternative Educational Backgrounds based upon your employment experiences and your ability. Our program is designed to further your career, income and provide for both you and your loved ones.

Give us a call--203/286/2403