On Tue, 23 Feb 2010, Laurence Anthony wrote:
> 
> I next rewrote my Perl script removing the "lappend" hack and things worked
> on my computer. But, when I tried to compile with PerlApp everything went
> smoothly (with one warning) until I tried to test the executable, which
> produced an error:
> 
> Can't create
> 'C:\DOCUME~1\Anthony\LOCALS~1\Temp\pdk-Anthony/auto/Tcl/Tcl.dll': Permission
> denied at perlapp line 894.
> BEGIN failed--compilation aborted at
> /<Z:\all_files_20090303\software_development\dnd_testing\dnd_test_ver3_embedding_dnd_in_tkkit.exe>Tkx.pm
> line 206.
> BEGIN failed--compilation aborted at
> dnd_test_ver3_embedding_dnd_in_tkkit.plline 2.

Hi Laurence,

I still can't reproduce the problem here, with the same commandline that you 
are using,
the same version of PerlApp (8.0.1).

Here are a couple of ideas of varying levels of grasping at straws:

You seem to have a copy of the tkkit in your Perl tree at:

    C:\Perl\lib\auto\Tcl\copy_of_tkkit.dll

that will needlessly get bundled into your application, blowing up the size.  
Could you
remove that file (just move it out of the directory) and see if it makes a 
difference
(I doubt it, as I created a copy in my tree as well, and it had no effect)?  
But if
nothing else it will let you generate smaller executables.

I also notice that you run your executable from the Z: drive whereas your local 
drive
seems to be C:.  Could you copy the executable somewhere onto your local disk 
and run
it from there?  If it makes a difference, could you explain what kind of drive 
Z: is?

Also, could you check if the directory 
C:\DOCUME~1\Anthony\LOCALS~1\Temp\pdk-Anthony\auto\Tcl\
actually exist and what the content are?  As I wrote before, PerlApp should not 
be using
that directory to begin with, but I'm wondering if the permission problem 
happens because
the directory already exist and isn't writeable, or if the directory doesn't 
even get created.

Finally, would you mind doing a clean installation of the latest ActivePerl 
5.10.1.1007
and PDK 8.2.1 to see if the problem is still reproducible?  It doesn't really 
make much
sense to spend too much time figuring out the issue if it is already fixed in 
the later
releases (although I would really like to know how this can happen at all).

Cheers,
-Jan

Reply via email to