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

[perlce-user] help to compiling the Perl for wince5

[Thiago de S. V. <thi...@rf...>]

I am having problems to compiling the Perl for wince5, i followed =
instructions of the site but i didn=B4t have success. Some body could =
help me with instructions for wince5. or some body have a binary version =
for x86?? 

Re: [perlce-user] How to compile PERLCE to WINDOWS MOBILE 5.0

[Uwe V. <uwe...@gm...>]

Hello Vadim,

> All should go smoothly for latest perl source (5.9.4, or even latest
> branch), once you'll have prerequisites (listed at perlce.sf.net) and
> follow instructions in README.wince file.
> 
> Did you tried just following compilation instructions, BTW ?  :)
> 
> I'm planning re-check its status at this weekend.

Last time I tried I had lots of trouble too. When you re-check, can you
please make .cab file, which contains the console too, so that a not so
experienced user can install perl on his pocket pc? The architecture
would be ARM.


Thank you very much,

bye,
Uwe

Re: [perlce-user] How to compile PERLCE to WINDOWS MOBILE 5.0

[Vadim <va...@vk...>]

tsv wrote:

>How to compile PERLCE to WINDOWS MOBILE 5.0 ??
>Please some body helpe-me??
>  
>
All should go smoothly for latest perl source (5.9.4, or even latest
branch), once you'll have prerequisites (listed at perlce.sf.net) and
follow instructions in README.wince file.

Did you tried just following compilation instructions, BTW ?  :)

I'm planning re-check its status at this weekend.

BR,
Vadim.

[perlce-user] How to compile PERLCE to WINDOWS MOBILE 5.0

[tsv <ts...@te...>]

How to compile PERLCE to WINDOWS MOBILE 5.0 ??
Please some body helpe-me??

Re: [perlce-user] error Can't locate lib.pm in @INC (@BEGIN failed--compilation abort)

[Konovalov, V. V. (Vadim)** C. ** <vko...@Lu...>]

>  I use perl 5.6 on my pocket pc.

this ML is for 5.8 and above

but you're not off-topic anyway :)

>  
>  I get the error:  Can't locate lib.pm in @INC (@BEGIN 
>  failed--compilation abort)
>  
>  Has anybody any idea to solve this problem.

I beleive you need registry settings, like was pointed on Rainer's web page.

BR,
Vadim. 

[perlce-user] error Can't locate lib.pm in @INC (@BEGIN failed--compilation abort)

[Anton v. d. S. <ant...@ch...>]

Hello perl guru's,

I use perl 5.6 on my pocket pc.

I get the error:  Can't locate lib.pm in @INC (@BEGIN 
failed--compilation abort)

Has anybody any idea to solve this problem.

Regards,

Anton Vandersteen
Eindhoven\The Netherlands

RE: [perlce-user] Compilation instructions for WM5

[Konovalov, V. V. (Vadim)** C. ** <vko...@Lu...>]

> I would like to try out perl on my XDA Mini S (Qtek 9100) with Windows
> Mobile 5.0.

You should check the table at
http://msdn.microsoft.com/embedded/usewinemb/ce/supproc/default.aspx
and find your processor here.

Your processor name is in the control panel in your device.

Then rebuilding or using existing proper binaries is just like for someone else...

> 
> Can someone please provide compilation instructions with Visual Studio
> 2005? Or is there a binary for WM5?

Best regards,
Vadim.

[perlce-user] Compilation instructions for WM5

[Uwe V. <uwe...@gm...>]

Hello,

I would like to try out perl on my XDA Mini S (Qtek 9100) with Windows
Mobile 5.0.

Can someone please provide compilation instructions with Visual Studio
2005? Or is there a binary for WM5?


Thank you very much,

bye, Uwe

[perlce-user] Re: Merge WinCE and Win32 directories -- Initial patch

[demerphq <dem...@gm...>]

On 5/1/06, Vadim <va...@vk...> wrote:
>
> > Since folks seemed interested (and since i apparently have some free
> > time I didnt expect) I put the current state of my merging efforts
> > online as
> >
> >  http://flux8.com:8079/perl/win.tar.bz2
>
>
> Attached is a patch against this, and also updated directory online.
>
> http://feather.perl6.nl/~vkon/win-28029.zip
> (Thanks to Juerd for providing this for Perl6 efforts, I hope he will
> not be disappointed by using perl6 resource for perl5 needs, as we're
> moving towards perl6 anyways :):)
> (zip is not needed if attached patch is used)
>
> Another 2 tiny patches are to perl.h and perlio.c
>
> Because now host perl and cross-compiled perl are built in the same dir,
> I propose to have config.h for cross-compilation to be named "xconfig.h"
>
> Looking at perlio.c, it is a bit strange to have "config.h" included
> from there; is it unavoidable?? perlio.c is the only C file including
> "config.h", thus making it very different.
>
> Now stuff builds okay; I didn't tried running executables yet, but there
> should be no problem on this.

Great! Ive been too busy to work on it this w/e but I will follow up soon.

> >
> > Just to recap my methodology was as follows:
> >
> > First i diffed WinCE and Win32 and realized that there were basically
> > three classes of file:
> >
> > A. Additions in Win32 that hadnt been applied to the wince directory.
> > B. Stuff in the WinCE directory that had been written with Win32
> > compatibilty in mind
> > C. Suff in the Wince directory that had assumed that Win32 stuff didnt
> > matter.
>
>
> remarkably, win/include/sys/socket.h just lost some twisted stuff during
> merger, because for some reason win32/include/sys/socket.h contained
> some "WINCE" #ifdef-s which were never happen.

I think that might have been me, I merged much of the changes that
were in socket.h in the wince directory into the win32 directory
already, and raphael applied the patch.

>
> > Miscleaneous stufff:
> >
> > One difference that i decided in the favour of the Win32 branch was
> > the icon for the exe. Im not sure if the WinCE one was intended as a
> > lower resolution icon or not, it certainly was smaller. Possibly this
> > change needs to be enhanced to allow selecting the icon from the
> > cmdline.
>
>
> I just didn't pay enough time for looking into win32/makeico.pl and
> wince/makeico.pl closely; actually I did small steps in merging of such
> files earlier.

In some ways I like the way the Wince build does the ico stuff better
than I like the way the mainline does it.

> >
> > An interesting issue are the additional files in the WinCE directory,
> > some of them (the batch files) are kindof interesting and long term
> > might be made to do the right thing for a normal win32 build. Likewise
> > there are some interesting stuff in the Makefile.ce
>
>
> may be wince-only batch files should be in separate subdirectory?

Well, if you really think so then sure, but I was think not, just to
encourage the idea that long term it would be nice to have as many of
them as possible do the right thing regardless. It seemed to me that
some of them are almost like a first step towards a win32  configure
process, which seems to me to be useful.

> To summarize, I am very glad of this merger process: not only number of
> files will be smaller, also some build features will become available
> (e.g. static links).

Thats great, thanks a bunch for your help!

Cheers,
Yves

--
perl -Mre=3Ddebug -e "/just|another|perl|hacker/"

[perlce-user] Re: Merge WinCE and Win32 directories -- Initial patch

[Vadim <va...@vk...>]

>Because now host perl and cross-compiled perl are built in the same dir,
>I propose to have config.h for cross-compilation to be named "xconfig.h"
>
>  
>
Here I had an idea to explain why there was a change into perl.h, but
lost my words and forgot to search them :)

>I just didn't pay enough time for looking into win32/makeico.pl and
>wince/makeico.pl closely; actually I did small steps in merging of such
>files earlier.
>  
>
sorry my English is worse at night :(
s/pay/paid/; s/such files/similar files/;


Will be happy to explain better and spend more efforts on this.

BR,
Vadim.

[perlce-user] Re: Merge WinCE and Win32 directories -- Initial patch

[Vadim <va...@vk...>]

> Since folks seemed interested (and since i apparently have some free
> time I didnt expect) I put the current state of my merging efforts
> online as
>
>  http://flux8.com:8079/perl/win.tar.bz2


Attached is a patch against this, and also updated directory online.

http://feather.perl6.nl/~vkon/win-28029.zip
(Thanks to Juerd for providing this for Perl6 efforts, I hope he will
not be disappointed by using perl6 resource for perl5 needs, as we're
moving towards perl6 anyways :):)
(zip is not needed if attached patch is used)

Another 2 tiny patches are to perl.h and perlio.c

Because now host perl and cross-compiled perl are built in the same dir,
I propose to have config.h for cross-compilation to be named "xconfig.h"

Looking at perlio.c, it is a bit strange to have "config.h" included
from there; is it unavoidable?? perlio.c is the only C file including
"config.h", thus making it very different.

Now stuff builds okay; I didn't tried running executables yet, but there
should be no problem on this.

>
> Just to recap my methodology was as follows:
>
> First i diffed WinCE and Win32 and realized that there were basically
> three classes of file:
>
> A. Additions in Win32 that hadnt been applied to the wince directory.
> B. Stuff in the WinCE directory that had been written with Win32
> compatibilty in mind
> C. Suff in the Wince directory that had assumed that Win32 stuff didnt
> matter.


remarkably, win/include/sys/socket.h just lost some twisted stuff during
merger, because for some reason win32/include/sys/socket.h contained
some "WINCE" #ifdef-s which were never happen.



> Miscleaneous stufff:
>
> One difference that i decided in the favour of the Win32 branch was
> the icon for the exe. Im not sure if the WinCE one was intended as a
> lower resolution icon or not, it certainly was smaller. Possibly this
> change needs to be enhanced to allow selecting the icon from the
> cmdline.


I just didn't pay enough time for looking into win32/makeico.pl and
wince/makeico.pl closely; actually I did small steps in merging of such
files earlier.

>
> An interesting issue are the additional files in the WinCE directory,
> some of them (the batch files) are kindof interesting and long term
> might be made to do the right thing for a normal win32 build. Likewise
> there are some interesting stuff in the Makefile.ce


may be wince-only batch files should be in separate subdirectory?

To summarize, I am very glad of this merger process: not only number of
files will be smaller, also some build features will become available
(e.g. static links).

Best regards,
Vadim.

[perlce-user] Re: Merge WinCE and Win32 directories -- Initial patch

[demerphq <dem...@gm...>]

On 4/28/06, Vadim <va...@vk...> wrote:
>
> >> In a merge process, I see 2 different paths:
> >>  - 1. just move ./wince/* into subdir of win32. Easy but essentially
> >> hiding a problem under a carpet.
> >>  - 2. integrate closely. This is harder, yet this brings another
> >> problem. Wince port uses CELIB, which, unfortunately, isn't very
> >> perfect, and probably it will not be needed at all when WinCE OS will
> >> provide enough C library functions (this is why CELIB currently
> >> needed); so "polluting" win32 with CELIB has its drawbacks.
> >>
> >> So please go and merge as you see fit.
> >>
> >> I'll provide my help with any choosen way of doing things.
> >
> >
> > Im going the #2 route. Cant we make CELIB load only when UNDER_CE?
>
>
> Fine. I hope 'win32' tree will not be polluted to much to annoy win32
> people.
>
> Yet, you should not bother about CELIB, and indeed it is loaded only
> UNDER_CE.
>
>
> >
> > Maybe we should take this offlist? Or is this interesting to others?
> > Maybe Steve P?
>
>
> perlce.sf.net has its mailing list, but it is calm now, so we can easily
> take this offlist, and may be CC per...@li... :)

Since folks seemed interested (and since i apparently have some free
time I didnt expect) I put the current state of my merging efforts
online as

  http://flux8.com:8079/perl/win.tar.bz2

Just to recap my methodology was as follows:

First i diffed WinCE and Win32 and realized that there were basically
three classes of file:

 A. Additions in Win32 that hadnt been applied to the wince directory.
 B. Stuff in the WinCE directory that had been written with Win32
compatibilty in mind
 C. Suff in the Wince directory that had assumed that Win32 stuff didnt mat=
ter.

Because of this I did the following:

 1. Set up a new dir 'Win' based on the contents of the Win32 directory.

 2. Copy the contents of the Wince directory over the Win32 contents,
thus after this step hypothetically Wince should have been able to
build ok.

 3. Started merging content from the Win32 to Win directory so that
eventually the files were identical. If the content was case A the
changes were to the Win directory, for case B  it was to the Win32
directory and for case C it was to both. But I mostly tackled the case
A and B stuff first and left the C for later.

4. As changes were applied to the Win32 directory I checked that at
least it builds "out of the box" for win32. The result was the patch I
sent in to Win32.

Eventually it should be that the Win directory contains exactly the
same content as the Win32 directory, plus any files that are in the
WinCE directory that are not in the Win32 directory. And it should be
possible to build for both platforms from the Win directory. At that
point I guess the final patch would be to move the new files from
wince directory to the win32 directory and then delete the rest.

I dont know how P5P would like to handle stuff like this in source
control. It seems to me that putting the "Win" directory under source
control would make it easier to track the changes, even if it meant
that for a short time blead would have three win directories. Because
after not that long it would only have one. Anyway, thats obviously
not my call. :-)

Miscleaneous stufff:

One difference that i decided in the favour of the Win32 branch was
the icon for the exe. Im not sure if the WinCE one was intended as a
lower resolution icon or not, it certainly was smaller. Possibly this
change needs to be enhanced to allow selecting the icon from the
cmdline.

An interesting issue are the additional files in the WinCE directory,
some of them (the batch files) are kindof interesting and long term
might be made to do the right thing for a normal win32 build. Likewise
there are some interesting stuff in the Makefile.ce

Now that we know for sure that UNDER_CE will be defined when building
for CE we can change all the stuff that says _WIN_CE to say UNDER_CE.

cheers
Yves
--
perl -Mre=3Ddebug -e "/just|another|perl|hacker/"

[perlce-user] Re: Merge WinCE and Win32 directories -- Initial patch

[Vadim <va...@vk...>]

>> In a merge process, I see 2 different paths:
>>  - 1. just move ./wince/* into subdir of win32. Easy but essentially
>> hiding a problem under a carpet.
>>  - 2. integrate closely. This is harder, yet this brings another
>> problem. Wince port uses CELIB, which, unfortunately, isn't very
>> perfect, and probably it will not be needed at all when WinCE OS will
>> provide enough C library functions (this is why CELIB currently
>> needed); so "polluting" win32 with CELIB has its drawbacks.
>>
>> So please go and merge as you see fit.
>>
>> I'll provide my help with any choosen way of doing things.
>
>
> Im going the #2 route. Cant we make CELIB load only when UNDER_CE?


Fine. I hope 'win32' tree will not be polluted to much to annoy win32
people.

Yet, you should not bother about CELIB, and indeed it is loaded only
UNDER_CE.


>
> Maybe we should take this offlist? Or is this interesting to others?
> Maybe Steve P?


perlce.sf.net has its mailing list, but it is calm now, so we can easily
take this offlist, and may be CC per...@li... :)

Best regards,
Vadim.

[perlce-user] RE: Build PERLCE 5.8.8 for WinCE 4.20 (Windows Mobile 2003 SE) o n Dell Axim X30

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

> > > required to user LWP extension.
> > I doubt porting LWP will be easy...
> In fact, URI seams to be the only extension that is missing 
> to run LWP based
> perl script. See the following perl-stderr log:
> 
> Can't locate URI.pm in @INC (@INC contains: /Storage Card/usr/perl/lib

its pure-perl, just copy to ./lib/ and use!


> 
> That's frustating because the error reported during URI extension

you'll see more frustrating moments than that, in perlce...

> compilation seams to be that the miniperl argument list is 
> too long. Isn't
> it a work around for this "too long argument" issues (see URI 
> extension
> building log file attached in this morning email )

URI:
Warning: prerequisite MIME::Base64 2 not found.

Did you tried providing prerequisite?

Compress::Zlib:
c:\temp\perl\perl-5.9.3\ext\compress-zlib-1.41\gzio.c(180) : error C2065:
'errno' : undeclared identifier

Can you try declaring "errno" as extern int temporarily?

I'll try myself in some near future

BR,
Vadim.

[perlce-user] Re: Build PERLCE 5.8.8 for WinCE 4.20 (Windows Mobile 2003 SE) on Dell Axim X30

[fpirou <fp...@ho...>]

> > required to user LWP extension.
> I doubt porting LWP will be easy...
In fact, URI seams to be the only extension that is missing to run LWP based
perl script. See the following perl-stderr log:

Can't locate URI.pm in @INC (@INC contains: /Storage Card/usr/perl/lib
/Storage Card/usr/perl/lib .) at (eval 1) line 3.
Compilation failed in require at /Storage Card/usr/perl/lib/HTTP/Request.pm
line 5.
Compilation failed in require at /Storage Card/usr/perl/lib/LWP/UserAgent.pm
line 12.
BEGIN failed--compilation aborted at /Storage
Card/usr/perl/lib/LWP/UserAgent.pm line 12.
Compilation failed in require at \Network\A0919434 on
DNCS40\Florent\seloger_grab.pl line 3.
BEGIN failed--compilation aborted at \Network\A0919434 on
DNCS40\Florent\seloger_grab.pl line 3.

That's frustating because the error reported during URI extension
compilation seams to be that the miniperl argument list is too long. Isn't
it a work around for this "too long argument" issues (see URI extension
building log file attached in this morning email )

Thanks in advanced,

\Flo

----- Original Message ----- 
From: "Konovalov, Vadim" <vko...@sp...>
To: "fpirou" <fp...@ho...>
Cc: <per...@li...>
Sent: Tuesday, February 28, 2006 10:46 AM
Subject: RE: Build PERLCE 5.8.8 for WinCE 4.20 (Windows Mobile 2003 SE) on
Dell Axim X30


> > I build some perl extension.
> > But, there are errors when building URI and Compress-Zlib. Those are
>
> Compress-Zlib is in CORE since 5.9.x, so should b eno prob...
>
>
>
> > required to user LWP extension.
>
> I doubt porting LWP will be easy...
>
>
> > Could you have a quick look of the attached log files? (Those are
> > standard CPAN extension)
> > Why Is POSIX extension not supported in PERLCE?
>
> because CELIB isn't supporting POSIX wery well, yet it supports quite old
> WinCE versions.
> WinCE, since 2.0 version, has much more supported library functions, and
> nearly 50% of WinCE functions are now obsolete, in WinCE-4.20 and above.
>
> However getting situation improved requires many efforts, which are not
hard
> but time consuming
>
> Vadim.
>

[perlce-user] RE: Build PERLCE 5.8.8 for WinCE 4.20 (Windows Mobile 2003 SE) o n Dell Axim X30

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

> I build some perl extension.
> But, there are errors when building URI and Compress-Zlib. Those are

Compress-Zlib is in CORE since 5.9.x, so should b eno prob...



> required to user LWP extension.

I doubt porting LWP will be easy...


> Could you have a quick look of the attached log files? (Those are
> standard CPAN extension)
> Why Is POSIX extension not supported in PERLCE?

because CELIB isn't supporting POSIX wery well, yet it supports quite old
WinCE versions.
WinCE, since 2.0 version, has much more supported library functions, and
nearly 50% of WinCE functions are now obsolete, in WinCE-4.20 and above.

However getting situation improved requires many efforts, which are not hard
but time consuming

Vadim.

[perlce-user] RE: Build PERLCE 5.8.8 for WinCE 4.20 (Windows Mobile 2003 SE) o n Dell Axim X30

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

> It finally compiled!! Thanks a lot for your help.
> 
> Now, I would like to compile extensions. Especially LWP, 
> Date::calc and
> Spreadsheet::Writer
> How can I add those extension to the perlCE compiling scripts 
> (Makefile.ce)?

Obviously you do not need to recompile pure-perl modules;

To compile XS extension just copy it into ./ext/ directory of built
sourcetree.
(this is actually what I am planning to do for perlCE project)

Its not hard to also manage C extensions.

> Do I have to do it like Tcl72 does?

How tcl72 does?  :)

> 
> I noticed that compare to 
> http://www.rainer-keuchel.de/wince/perlce.html or
> some extension where missing in 5.9.3 lib folder (like win32::OLE,
> win32::serial, ...). Is it useful?

I hope when you copy "adopted" by Rainer source files into ./ext/ you'll
build fine...

> 
> Cheers
> 
> Flo

Best regards,
Vadim.

[perlce-user] RE: Build PERLCE 5.8.8 for WinCE 4.20 (Windows Mobile 2003 SE) o n Dell Axim X30

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

> I manage to work around "windows.h" miniperl.exe compilation issue, by
> adding all INCLUDE and LIB as necessary

good...

> Well ... it finally compiled miniperl.
> 
> Afterward, it fails compiling perlce after generating all .obj in
> C:\TEMP\PERL\perl-5.8.8\wince\wince-arm-pocket-wce300\dll with the
> following message.
> 
> Compiling for wince-arm-pocket-wce300
> LIB=C:\Windows CE Tools\WCE300\MS Pocket PC\lib\ARM
> INCLUDE=C:\Windows CE Tools\WCE300\MS Pocket PC\include
> PATH= C:\Program Files\Microsoft eMbedded C++ 4.0\EVC\wce420\bin
> 
>         if not exist ..\lib\auto mkdir ..\lib\auto
>         cd ..\ext\DynaLoader
>         C:\TEMP\PERL\perl-5.8.8\wince\..\miniperl.exe -I..\..\lib
> -MCross=wince-arm-pocket-wce300 DynaLoader_pm.PL
> syntax error at 
> ..\..\xlib/wince-arm-pocket-wce300/Config_heavy.pl line
> 53, near "x;"
> Compilation failed in require at
> .\..\xlib/wince-arm-pocket-wce300/Config.pm line 66.
> NMAKE : fatal error U1077: 'C:\WINDOWS\system32\cmd.exe' : return code
> '0xff'Stop.
> Any Idea? What does this step do?

Config_heavy.pl is unfortunate difference WRT Config.pm between 5.8.2 and
5.8.8; I beleive this change in Config.pm behaviour between 5.8.x versions
was not good.
I beleive latest 5.9.x snapshot free of this problem.

However, things should be already easy to fix, but please tell me what do
you see near line 53 of your file
..\..\xlib/wince-arm-pocket-wce300/Config_heavy.pl, near "x;"

This is just slight perl script error, which, once found, will be easy to
fix.

> 
> Microsoft eMbedded C++ 4.0 didn't install EVC/WCE300, Where can I find
> it? Should I have to download and install "eMbedded Visual Tools 3.0 -
> 2002 Edition" necessarily? 

I beleive you already have working cross-compilation (until proven
otherwise:)

BR,
Vadim.

RE: [perlce-user] Unresolved external symbols

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

> I had to play around with the makefile and add some include 
> directories.

5.8.7 do not build cleanly, it requires a patch that I sent to p5p, but it
was not accepted for inclusion yet.
5.9.3 do have fixes in makefiles.

Anyway, fixes to makefiles should be tiny, and I attached those to 5.8.7.


> Then I had to add FindExt.pm and re.pm to perl-5.8.7/lib

this isn't right. Could you explain what error forced you to do so?


> 
> Then I had to fix an error in the generated Config_heavy.pm
> 
> And even then it still won't build; I get 'unresolved 
> external symbol' errors:
> 
> malloc.obj : error LNK2019: unresolved external symbol sbrk 
> referenced in function 
> getpages
> malloc.obj : error LNK2019: unresolved external symbol 
> malloced_size referenced in 
> function perl_get_emergency_buffer
> malloc.obj : error LNK2019: unresolved external symbol 
> get_mstats referenced in 
> function Perl_dump_mstats
> 
> Has anyone seen and maybe solved this error?

I didn't.
However, something makes me think you didn't "play around with the makefile"
correctly.

perlce tries to use perl's memory allocation, as it is much faster than
system's one.

Vadim.

[perlce-user] Unresolved external symbols

[<jal...@ho...>]

Building on Windows XP with Visual Studio .NET 2003 and the SDK for Pocket PC 
2002

I had to play around with the makefile and add some include directories.

Then I had to add FindExt.pm and re.pm to perl-5.8.7/lib

Then I had to fix an error in the generated Config_heavy.pm

And even then it still won't build; I get 'unresolved external symbol' errors:

malloc.obj : error LNK2019: unresolved external symbol sbrk referenced in function 
getpages
malloc.obj : error LNK2019: unresolved external symbol malloced_size referenced in 
function perl_get_emergency_buffer
malloc.obj : error LNK2019: unresolved external symbol get_mstats referenced in 
function Perl_dump_mstats

Has anyone seen and maybe solved this error?

[perlce-user] RE: [wince-devel] Re: Porting Perl 5.8.7 to CE 5.0

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

> > I sent a patch to p5p to make 5.8.7 build ok, and its not currently
> > commited, because of code freeze.
> 
> With my changes, when I try to run the test suite (after copying the

may be you should show your changes? :)
Why not discussing those at p5p or perlce MLs?

> files 1 at a time, unfortunately), I run out of memory before a single
> test runs.  Even in Platform Builder's CE emulator with 256 megabytes
> allocated to the emulator.
> 
> 9 times out of 10, the stack trace when it prints the error 
> message is:
> 
> PERL58!emergency_sbrk()  line 1234
> PERL58!getpages()  line 1704 + 8 bytes
> PERL58!morecore()  line 1951 + 16 bytes
> PERL58!Perl_malloc()  line 1466
> PERL58!Perl_realloc()  line 2295 + 8 bytes
> PERL58!Perl_push_scope()  line 134 + 28 bytes
> PERL58!Perl_pp_enter()  line 1702
> PERL58!Perl_runops_standard()  line 37 + 24 bytes
> PERL58!S_run_body()  line 2003
> PERL58!perl_run()  line 1923
> PERL58!RunPerl()  line 231 + 8 bytes
> PERL!main()  line 36 + 28 bytes
> 
> I have no idea how to even start troubleshooting this problem.  Any
> suggestions?

I beleive this is a mess with a config.h (or similar files).

> 
>     UmberGryphon
>     (who wonders if Vadim has this problem)

I never tried running Platform Builder and emulator.
I did tried running some tests at 5.8.0-tobe, and did few steps on
automating this: this isn't hard, as there is a command to invoke a command
on PocketPC, and there are some helpers in ./wince/ perl dir.

See results http://perlce.sf.net/test-16694.zip There are many files named
like ._op_pos.t-perl-stdout.txt with a contents like
1..4
ok 1
ok 2
ok 3
ok 4

... but I never analyzed details of these...

It will be good if you'll revive this.

I am planning doing more updates to ./wince/ within perl distribution this
week.

Best regards,
Vadim.

[perlce-user] RE: [wince-devel] Porting Perl 5.8.7 to CE 5.0

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

> After much hammering (much of it figuring out various details of Perl
> and/or Windows CE development), I've gotten most of Perl 5.8.7
> compiling on Windows CE 5.0.  But I've gotten into cross-compiling the
> extension modules, and things have gotten really weird on me.

most probably this is because 5.8.7 (and following) sourcetrees need some
adjustments.

I'll look into this today.

And what are your changes?

Also, it is pity wiki on SF is now read-only, so I can't even place my
advices there :(
May be I'll move wiki into another place.


> 
> I get through building Cwd.dll fine, but after that, I constantly get
> complaints that "The application or DLL
> {feh}\perl-5.8.7\xlib\wince-arm-hpc-wce500\auto\Cwd\Cwd.dll is not a
> valid Windows image." from C:\Perl\bin\perl.exe, which I am using in
> place of miniperl because I don't have a non-cross-compiler installed
> on this machine.
> 
> All I can figure is that because of the changes to @INC that happen in
> Cross.pm, the native Perl is trying to load the cross-compiled Cwd.dll
> instead of the one in C:\Perl that it should be loading.  But those
> changes to @INC are important, apparently.  How am I supposed to get
> around this?

Makefile.ce contains macro HPERL, which is host perl, and it can be ajusted
to your location, but then you need to be careful on not getting it rebuild
accidentally (there will be no harm and no good, just a mess)
You can copy Cross.pm to your perl location, and you need to carefully check
whether @INC search path does right thing: it must hide normal Config.pm and
have only "alien" Cross.pm from target platform.

Changes in @INC only to find proper Config.pm, and they are not intended to
find Cwd.dll of another platform...  It's pity Cwd.dll is an external
library, and probably it is searched in wrong place, indeed, but you can
avoid this problem *before* messing @INC in Cross.pm -- by loading it in
Cross.pm!

Vadim.

[perlce-user] DBI module

[Jason D. <jas...@du...>]

Hi

I have installed perlce on my Axim X30 pocket PC running
Windows Mobile 2003.  It works great but I would like to
use the DBI module.

I can download the DBI module but the makefile doesn't work and
I am too much of a newbie to know what to do.

Can you help?  Can I just put the right files in the right directories?

Many thanks

Jason Drew

RE: [perlce-user] Win32 modules for WinCE

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

> I don't find the Perl modules for Win32::API and Win32::OLE, may anybody
help me?
> I need a version for WinCE 3.0, Poket PC, ARM CPU (I'm using a Trium
Mondo, with Perl 5.8.2 installed..).

unfortunately Win32::OLE module is not available in binaries for perl-5.8.2,
although those are not hard to rebuild (based on Rainer's efforts)
As for Win32::API, I beleive it hardly has many sence for WinCE.

Best regards,
Vadim.

[perlce-user] Win32 modules for WinCE

[Spinato A. <Ale...@ma...>]

I don't find the Perl modules for Win32::API and Win32::OLE, may anybody
help me?
I need a version for WinCE 3.0, Poket PC, ARM CPU (I'm using a Trium
Mondo, with Perl 5.8.2 installed..).

Thanks a Lot
Alessandro