Front page | perl.perl5.porters |
Postings from November 2013
On 5 November 2013 02:34, bulk88 via RT <perlbug-followup@perl.org> wrote: > On Mon Nov 04 16:09:31 2013, shay wrote: >> With that corrected, the build now succeeds and I get the expected >> perl.exe, perl519.dll and XS module DLLs :-) >> > > Congratulations. I dont have much else to say. > > So what was wrong with my initial instructions? the root dir names inside the archives of the 2 libraries to download, and the "-release" on celib's $MACHINE specific linking lib folder when the "make libs for newer build" copy rename is done. > > Other problems with EVC4 are the build env batch files break very easily if any of the vars are already defined, and they were on your machine. > Yes, I agree, that was pretty painless. Thanks for the help. My only concern is that the build used a very old compiler which MS is doing its best to remove all traces of and (unavoidably, it seems) some third-party things which could disappear any time, but for now it certainly seems to work. I think your instructions (with the necessary minor corrections) should go into the source somewhere. Is there a "README" type document about WinCE anywhere (I don't see one at a quick look)? If not then either add a top-level READM.wince, or else add a WinCE section into README.win32. I don't mind doing this in the near future in you don't have time. Please could you post instructions (to this ticket) on how to build with Smart Devices? I'm interested in trying that too, as a more up to date build option.Thread Previous | Thread Next