On Sun, 26 Apr 2020 17:57:23 +0200, Oliver Betz <list...@gmx.net> wrote:
> it was not so difficult as I thought initially so I compiled a 64 bit
> wrapper including the icon:
Great!
I unpacked the zip and tried to run.
First problem: the .exe files are not executable:
H:\cp> wxchordpro_console.exe
Access is denied
So I changed all .exe to executable.
H:\cp> wxchordpro_console.exe
Failed to load Perl DLL "perl530.dll" code 5
Changed all DLLs to executable, too.
H:\cp> wxchordpro_console.exe
Can't open perl script "H:\cp\wxchordpro_console.pl": No such file or
directory
Copied wxchordpro.pl as wxchordpro_console.pl.
I needed a couple of small fixes due to the fact that now we are no longer
running as pp-packaged. This means
- the 'res' directory now needs to be under lib\App\Music\ChordPro
(where it originally is -- it was moved for pp)
- some information is read from module PODs, so PODs must not be stripped.
The above changes also fix the $cfglib error.
While looking at the (modified) source: what is the purpose of
unshift @INC, 'C:\temp\Coordpro_temp\x\inc\lib';
By moving the scripts to a subdirectory scripts, and run as
perl script/wxchordpro.pl
The FindBin stuff also works correctly. In other words, no changes are required
to any of the original sources. (A could be expected!)
Summarizing the workflow becomes:
1. build the application (perl Makefile.PL; make all test).
2. application sources for packaging can be found in blib.
3. construct the perl environment. pp can be helpful with this.
4. create the native wrapper.
Once this has been done:
5. copy the application sources and perl environment to a work directory
6. have InnoSetup package this work directory
Can you pass me the wrapper source and innosetup file?
Nice work,
Johan
