Re: On the road again with Gtk2 and PAR::Packer

Can someone explains the difference between Glib.dll and Glib.xs.dll ?

The only difference is the name.
On my own builds of perl (on Windows) the dll would be named Glib.dll, but on Strawberry the same file gets named Glib.xs.dll.
On my builds of Windows perls:

C:\>perl -V:dlext
dlext='dll';
[download]

On recent builds of Strawberry Perl:

C:\>perl -V:dlext
dlext='xs.dll';
[download]

That's about all there is to it.
That Config setting is detected by EU::MM and influences the Makefile generated by the 'perl Makefile.PL' step.

I'm not sure how this will impact upon PAR::Packer, but this part of what you provided looks correct to me:

-l 'C:/strawberry/perl/site/lib/auto/Cairo/Cairo.xs.dll'
-l 'C:/strawberry/perl/site/lib/auto/Glib/Glib.xs.dll'
-l 'C:/strawberry/perl/site/lib/auto/Gtk2/Gtk2.xs.dll'
-l 'C:/strawberry/perl/site/lib/auto/Pango/Pango.xs.dll'
[download]

whereas this part looks incorrect to me:

-l 'C:\docs\perl_dll\Pango.dll'
-l 'C:\docs\perl_dll\Glib.dll'
-l 'C:\docs\perl_dll\Gtk2.dll'
-l 'C:\docs\perl_dll\Cairo.dll'
[download]

IIRC, Strawberry chose this option to avoid name clashes.
Say you are building an extension named Some::Module that accesses a C library named "module" via its dll named "module.dll".
When you build Some::Module, you create a dll named "Module.dll".
Both "Module.dll" and "module.dll" are different files and both are needed by Some::Module - but Windows, being case-insensitive, is unable to distinguish between them and you won't even be able to get Some::Module to load.
So ... Strawberry names the perl dll "Module.xs.dll", and windows has no problems distinguishing between the 2 dlls that are needed.

Cheers,
Rob

Comment on Re: On the road again with Gtk2 and PAR::Packer Select or Download Code

Replies are listed 'Best First'.
Re^2: On the road again with Gtk2 and PAR::Packer by swl (Prior) on Feb 13, 2019 at 21:17 UTC
Edit: Sorry, the files are differently named here, so the first para does not entirely apply here (although the xs.dll files should not need to be packed). My guess is the path. --- If I understand correctly, the two Gtk2.dll, Glib.dll etc files in this case serve different purposes. One is the actual Gtk2 dll, the other is the xs file. PAR::Packer will pack the xs versions automatically, so they should need to be specified using `--link/-l`. The others do need to be packed. I wonder if the issue is some other Gtk2.dll is earlier in the path? If one uses the PPMs provided by Syphilis then Gtk2.dll is called s1sgtk-win32-2.0-0.dll so there is considerably less chance of ambiguity in the path. That file also lives next to the Gtk2.dll file so is found by the PAR search. (This differs from the other related dlls from that source, which are in the ...\perl\bin folder, which is maybe relevant).	[reply] [d/l]
Re^3: On the road again with Gtk2 and PAR::Packer by syphilis (Archbishop) on Feb 14, 2019 at 00:54 UTC
If I understand correctly, the two Gtk2.dll, Glib.dll etc files in this case serve different purposes. One is the actual Gtk2 dll, the other is the xs file. The names of the actual Gtk2 dlls should all begin with "lib" - eg "libglib-2.0-0.dll", "libcairo-2.dll", "libpango-1.0-0.dll",etc. (At least that's how it is with my gtk2 installation.) I think any files named "Gtk2.dll" and "Glib.dll" would be the ones that were created for the Gtk2 and Glib perl modules. PAR::Packer will pack the xs versions automatically Ok - to have stated otherwise would be my mistake. This would then suggest to me that it's unnecessary (and possibly error-prone) to specifically pack any files named "Glib.dll", "Gtk2.dll", "Pango.dll", "Cairo.dll". The structure of the ppm packages has changed a bit in recent years. Currently, the s1s*.dll files should all be installed into perl/bin. I figure your chances of encountering another dll with the same name is about the same as winning a major lottery without even having a ticket. Cheers, Rob	[reply]
Re^4: On the road again with Gtk2 and PAR::Packer by swl (Prior) on Feb 14, 2019 at 05:04 UTC
siphylis makes a good point regarding the dll names. WRT the PPM structure, and as a side note, the current tarball referred to by the `PPM-Sisyphusion-Gtk2_dll` ppd has `s1sgtk-win32-2-.0-0.dll` in `arch\auto\Gtk2` and the other DLLs under `\script`. It seems to work, though, so I see no need to change it.	[reply] [d/l] [select]
Re^5: On the road again with Gtk2 and PAR::Packer by syphilis (Archbishop) on Feb 14, 2019 at 07:50 UTC
Re^3: On the road again with Gtk2 and PAR::Packer by frazap (Monk) on Feb 14, 2019 at 07:32 UTC
PAR::Packer will pack the xs versions automatically, so they should need to be specified using --link/-l. The others do need to be packed. PAR::Packer packed the xs.dll with including lib/auto/Gtk2 ... But with these inclusion, I have the error `GLib-GObject-CRITICAL`. See https://www.mail-archive.com/par@perl.org/msg05011.html	[reply] [d/l]
Re^2: On the road again with Gtk2 and PAR::Packer by frazap (Monk) on Feb 22, 2019 at 11:50 UTC
Rob, How comes that in the Gtk2 stack you compiled for sisyphusion, the pango.dll which need Glib.dll and Cairo.dll find them in the packed exe (in inc/lib/auto/ ...) despite they are not in the shlib/ARCH/ folder ? Is that obvious for you ? F	[reply]