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


in reply to Re: Unix.dll not Found in PerlApp
in thread Unix.dll not Found in PerlApp

Hi, thanks for your reply.

When I get the warning it looks like it is looking for Unix.dll in the auto folder. If I am not mistaken, that's something generated by PerlApp's (XSLoader ?) during runtime. I have the Unix.pm from my Perl installation and somehow, it probably uses the Unix.pm to generate a Unix.dll. All other dlls have been created by PerlApp except this one. Do I have to make it (Unix.dll) ? It is probably failing in creating it automatically and that is why I cannot find it. My question is therefore how do I make it or where do I download it? These were my settings for PerlApp:

perlapp --trim Mac::Glue::; extractors::; auto::SetDualVar::; Locale::Maketext::Lexicon::; Test::Manifest::; VMS::DCLsym::; Win32::TieRegistry::; Data::Lazy::; SetDualVar::; Win32::FileOp::; Win32::Locale::; Log::Contextual::WarnLogger::; Encode::HanExtra::; I18N::Langinfo::; Ext::MM_Unix::; File::Spec::;version::; auto::ExtUtils::Unix::; ExtUtils::MM_Unix --add version::; File::Spec::Functions; File::Spec; File::Spec::Win32; File::Spec::Unix --icon C:\Users\Cmdr_Colstel\Downloads\1440576270_appicns_iTunes.ico --lib L:\Perl64\bin --norunlib --nologo --verbose --force --exe Key_Fl +ipper.exe --perl L:\Perl64\bin\perl.exe Key_Flipper.pl

I was forced to add the module File::Spec::Unix because File::Spec::Win32 references it and PerlApp fails to create an executable without it. But even upon adding the module, PerlApp fails to create the Unix.dll in the auto folder. Any help is appreciated. Thanks.

Replies are listed 'Best First'.
Re^3: Unix.dll not Found in PerlApp
by dasgar (Priest) on Sep 15, 2015 at 17:24 UTC

    It looks like you're using a lot of options - especially --trim (presumably to reduce the size of the executable that is created). Have you tried to reducing the the number of PerlApp options that you use to see if you can successfully create a working executable? Just was wondering if you might have conflicting options or an option that is preventing PerlApp from including the needed modules.

    Otherwise, I'd agree with the suggestion about using ActiveState's user forums to ask for help for using ActiveState's product.

      Yeah, I do have a lot of added modules. Didn't intend for it, but as I ran PerlApp to create the executable, it kept saying it couldn't find this or that module. So as I added the modules manually and it found them and the errors disappeared. However, it still gets stuck on Unix.dll. If I find out how to get\create it, that should be the missing piece.

      The program is supposed to wrap all modules/dlls, along with my script, in a package so it doesn't need an installed version of Perl on the executing Windows machine.

      I will consult with ActiveState as you suggested. Just thought someone might have run across the same situation here. Thanks.

        By comparing PathTools v3.62 to v3.75 Unix.pm, it is easy to see the newer version did away with XLSloader and simply replaced lines 10 thru 22 with: require Cwd;