There is a EXE_FILES attribute but this is strictly for specifying Perl scripts to include with the module
Are you sure about that ? I find that any file specified in EXE_FILES gets installed into INSTALLBIN (irrespective of what that file contained).
Cheers, Rob Update:Minor correction - changed "INST_BIN" to "INSTALLBIN". Update: However, this is probably not the ideal way to go about it. On Win32, not only does the EXE_FILE get installed into INSTALLBIN, but a copy of that file ("converted" to a batch file, and given a '.bat' extension) is also installed into INSTALLBIN - the assumption apparently being that EXE_FILE's are, in fact, supposed to be executable. | [reply] |
When I list them in EXE_FILES they get processed by pl2bat so what ends up in Perl/bin is a *.exe and a *.exe.bat
This is messy and so I was trying to find a cleaner way of doing this.
Thanks.
| [reply] |
I discovered a solution for this. MakeMaker configures the build to execute any *.PL (caps required on extenstion) files in the same directory as the Makefile when 'make' and 'make install' are executed.
| [reply] |