http://qs321.pair.com?node_id=1203292


in reply to PerlApp and Win32::Unicode

I am not at a system where I can even try to replicate your problem. However, I suggest that you add additional use statements: use Win32; and use Win32::Unicode; above what you have now. Give that a go and let us know what happens.

Replies are listed 'Best First'.
Re^2: PerlApp and Win32::Unicode
by IB2017 (Pilgrim) on Nov 13, 2017 at 20:36 UTC

    THANK YOU! You made my day. It now works. However, I add too add an explicit use arybase; (I have no idea what it is) as it was missed when I run the new exe. The following works fine with my 5.16:

    use Win32; use Win32::Unicode; use Win32::Unicode::File; use arybase; print "Hello"
      ... add too add an explicit use arybase; (I have no idea what it is) ...

      See arybase on CPAN.


      Give a man a fish:  <%-{-{-{-<

      Hooray! Glad this worked for you.
      I had to do something similar 20+ years ago when I built my first complicated exe with PerlApp. How I figured that out is lost to antiquity.

      If you have a somewhat recent version of PerlApp, I recommend using the GUI. This makes some of the options easier to understand. Just type "perlapp" with no command line args and the GUI will start. It is possible to add an icon for desktop display. I believe it is also possible to force arbitrary files into the exe although I would use that feature with extreme caution and I haven't done that myself. I can mention this now because you are solving your problem in what I consider "the right way". Forcing a .dll manually is not, in my experience "the right way".