Bundled Tk app won't start

[simon andrews (BI)]

I’m trying to package a small Tk based Perl application, but after running the Cava build successfully I can’t get it to start.  The build completes OK with no warnings or errors, and the packager looks to have identified all the modules to bundle OK.  However when I try to start the application I get the error:

 

Unrecognized character \x1F; marked by <-- HERE after <-- HERE near column 1 at D:/StoresUpdate/release/MyApp/lib/std/Tk.pm line 1.

Compilation failed in require at D:/StoresUpdate/release/MyApp/lib/std/cavaexecscript/stores_interface.pl line 3.

BEGIN failed--compilation aborted at D:/StoresUpdate/release/MyApp/lib/std/cavaexecscript/stores_interface.pl line 3.

 

Looking at the files in /lib/std/ I can see all of the .pm files I expect, but all of their contents appear to be binary data rather than the original text files.  Is this how it’s supposed to be?

 

Any clues as to how I can work out what’s going wrong here?

 

Thanks

 

Simon.

 

The Babraham Institute, Babraham Research Campus, Cambridge CB22 3AT Registered Charity No. 1053902.

The information transmitted in this email is directed only to the addressee. If you received this in error, please contact the sender and delete this email from your system. The contents of this e-mail are the views of the sender and do not necessarily represent the views of the Babraham Institute. Full conditions at: www.babraham.ac.uk

[Cava Support]

Hi,

Could you try the 2.0.74 pre-release Cava Packager from

http://www.cavapackager.com/download/cava-packager-msw-x86-2-0-74.exe

(or 64 bit at)

http://www.cavapackager.com/download/cava-packager-msw-x64-2-0-74.exe

This should solve both the Tk issue and the problem you were having
starting from network paths.

Let me know if it works.

Regards

Mark

--
User Support
Cava Development Tools
Package and Distribute Perl Applications
http://www.cavapackager.com/

[Cava Support]

Hi,

There was a problem with the 2.0.74 pre-release and Perl 5.14

fixes are in the 2.0.75 pre-release from

http://www.cavapackager.com/download/cava-packager-msw-x86-2-0-75.exe

(or 64 bit at)

http://www.cavapackager.com/download/cava-packager-msw-x64-2-0-75.exe

Regards

Mark

[simon andrews (BI)]

Mark,

I was halfway through a reply to say that the UNC path problem was fixed but the Tk problem was still present when I saw your additional update.

I've just tried the project using v2.0.75 and the Tk script now builds and runs. Huge thanks for such a quick reply and fix.

There's just one remaining minor problem which is that when I exit the Tk program I get a standard dialog from windows to say the program has stopped working and that it is checking for a solution to the problem. This doesn't happen when I run the original script through a local perl interpreter. I guess that something isn't exiting cleanly to cause this, but this is a minor point for us at the moment and I can use what I have.

Many thanks again for a great and useful program.

Simon.

Hi,

http://www.cavapackager.com/download/cava-packager-msw-x86-2-0-75.exe

(or 64 bit at)

http://www.cavapackager.com/download/cava-packager-msw-x64-2-0-75.exe

Regards

Mark

The Babraham Institute, Babraham Research Campus, Cambridge CB22 3AT Registered Charity No. 1053902.
The information transmitted in this email is directed only to the addressee. If you received this in error, please contact the sender and delete this email from your system. The contents of this e-mail are the views of the sender and do not necessarily represent the views of the Babraham Institute. Full conditions at: www.babraham.ac.uk<http://www.babraham.ac.uk/email_disclaimer.html>

[Cava Support]

Hi

On 10/04/2012 16:18, simon andrews (BI) wrote:

> There's just one remaining minor problem which is that when I exit the Tk program I get a standard dialog from windows to say the program has stopped working and that it is checking for a solution to the problem. This doesn't happen when I run the original script through a local perl interpreter. I guess that something isn't exiting cleanly to cause this, but this is a minor point for us at the moment and I can use what I have.

When you get the chance to try yet another pre-release, the following
should fix the fault on exit.

http://www.cavapackager.com/download/cava-packager-msw-x86-2-0-76.exe

(or 64 bit at)

http://www.cavapackager.com/download/cava-packager-msw-x64-2-0-76.exe

Regards

Mark

[simon andrews (BI)]

On 10 Apr 2012, at 18:04, Cava Support wrote:

>> When you get the chance to try yet another pre-release, the following should fix the fault on exit.
>
> http://www.cavapackager.com/download/cava-packager-msw-x86-2-0-76.exe

Just tested this and it does indeed fix the problematic exit status.

Thanks again!

Simon.