Re^9: ActiveState PerlApp + Gtk and themes

In the working directory? Hmm, I’m pretty sure I haven’t seen them, but I might just not have noticed them. I’ll definitely take a look at it again after some sleep, getting GTK+ to deal with . should be way more straightforward than with that weird folder.

When the .exe that PerlApp built runs, it will unpack itself into a directory, some temporary directory that the O/S assigns as you've seen - I think that is the same way on Unix or Windows (of course PathNames are different). The bound files will be in sub-directories from that. I think that you will be able to specify paths based upon "./" in your Perl code for @INC. "./" is the directory that your "unpacked" code is currently running in - whatever that directory path name is.

Comment on Re^9: ActiveState PerlApp + Gtk and themes

Replies are listed 'Best First'.
Re^10: ActiveState PerlApp + Gtk and themes by Ralesk (Pilgrim) on Jan 20, 2012 at 23:27 UTC
I haven’t encountered the packed script itself yet, only the supporting libs and the bound files, during runtime. Nowhere inside `%TEMP%`, not in a recognisable format anyway. But what we need is not the script but the bound files, well, in that case I have some bad news (I think). Way before I installed the strace implementation or Process Explorer, I tried to figure out what was in view for the script, and did a `system("dir");` — I got the files from the directory where I had started the EXE from and not where the unpacked script mysteriously and temporarily lives. And the bound files are nowhere to be seen there unfortunately (I haven’t re-checked, but I think I would have noticed if there had been .dll files where normally there isn’t a single one), only in the previously discussed PID-labeled directory in `%TEMP%`. So I’m afraid I’ll need that absolute path.	[reply] [d/l]
Re^11: ActiveState PerlApp + Gtk and themes by Marshall (Canon) on Jan 30, 2012 at 05:43 UTC
The "bound files" should be relative path to the .exe, ie. ./ (current directory that the .exe is running within). The OS will unpack the Perl .exe into some directory somewhere - what the full path name is, we don't know and should not care.	[reply]
Re^10: ActiveState PerlApp + Gtk and themes by Ralesk (Pilgrim) on Jan 23, 2012 at 13:44 UTC
So, here are the bound files in the perlapp project file: Bind: lib/gtk-2.0/2.10.0/engines/libwimp.dll[file=C:\uhu\gtk\lib\gtk-2.0\2.10.0\engines\libwimp.dll,extract,mode=666] Bind: lib/gtk-2.0/2.10.0/engines/libpixmap.dll[file=C:\uhu\gtk\lib\gtk-2.0\2.10.0\engines\libpixmap.dll,extract,mode=666] Bind: share/themes/MS-Windows/gtk-2.0/gtkrc[file=C:\uhu\gtk\share\themes\MS-Windows\gtk-2.0\gtkrc,text,extract,mode=666] Bind: share/locale/hu/LC_MESSAGES/gtk20.mo[file=C:\uhu\gtk\share\locale\hu\LC_MESSAGES\gtk20.mo,extract,mode=666] Bind: share/locale/hu/LC_MESSAGES/gdk-pixbuf.mo[file=C:\uhu\gtk\share\locale\hu\LC_MESSAGES\gdk-pixbuf.mo,extract,mode=666] Bind: share/locale/hu/LC_MESSAGES/atk10.mo[file=C:\uhu\gtk\share\locale\hu\LC_MESSAGES\atk10.mo,extract,mode=666] Bind: share/locale/hu/LC_MESSAGES/glib20.mo[file=C:\uhu\gtk\share\locale\hu\LC_MESSAGES\glib20.mo,extract,mode=666] Bind: share/locale/hu/LC_MESSAGES/gtk20-properties.mo[file=C:\uhu\gtk\share\locale\hu\LC_MESSAGES\gtk20-properties.mo,extract,mode=666] This will have those files unpacked to `%TEMP%\pdk-%USERNAME%-$$\{lib,share}\...`. The libwimp.dll and the MS-Windows gtkrc file seem to be crucial in getting the UI look right. Libraries are found with help from the `GTK_EXE_PREFIX` environment variable, and shared stuff are found via the `GTK_DATA_PREFIX` envvar. Locale is supposedly controlled by XDG, but `XDG_DATA_DIRS` did not have any effect and it is still searched in `%TEMP%\pdk-%USERNAME%\<Gtk2 hashdir>\`. The Perl code thus needed the following “hack” so GTK+ knows where to look: `if ($windows) { ## $windows as set up earlier in the code = TRUE if ( +$^O eq 'MSWin32' or $^O eq 'MSWin64'); $ENV{GTK_EXE_PREFIX} = "$ENV{TEMP}\\pdk-$ENV{USERNAME}-$$"; $ENV{GTK_DATA_PREFIX} = "$ENV{TEMP}\\pdk-$ENV{USERNAME}-$$"; $ENV{XDG_DATA_DIRS} = "$ENV{TEMP}\\pdk-$ENV{USERNAME}-$$"; ## Has + no effect, see above. }` [download] Now all I need is bundle that other binary I mentioned earlier and possibly figure out how to change the locale lookup dir somehow, and I’m done.	[reply] [d/l]