In this thread 
http://mail.gnome.org/archives/gtk-perl-list/2005-April/msg00206.html

I read that "Just to point it out again: par *does* build a .exe from my 
gtk2-perl-app that 
runs perfectly fine on another windows box without any perl installed -- 
which is par's intention. The thing I am not able to do is include the 
gtk+-libraries into this par/exe, so they need to be installed on the 
"target" machine. This is not really perfect, but with the nice windows 
installer that is available for gtk+, I prefer it against switching to 
perl/tk or writing my own installer..."

So this mean I could package the perl stuff with pp, and run the archive on 
another machine providing that I have installed Gtk before ?

(I didn't try before asking, sorry)

François

> -----Original Message-----
> From: Roderich Schupp [mailto:roderich.sch...@googlemail.com]
> Sent: jeudi, 16. février 2012 09:35
> To: Konovalov, Vadim (Vadim)** CTR **
> Cc: RAPPAZ Francois; par@perl.org
> Subject: Re: packaging gtk2 script: use Gtk2 -init; failed
> 
> On Thu, Feb 16, 2012 at 09:18, Konovalov, Vadim (Vadim)** CTR **
> <vadim.konova...@alcatel-lucent.com> wrote:
> > I am not fully agree here.
> >
> > PAR is well recognized technique, and if you have a fix to CPAN
> module
> > that allows PAR usage to the said module, the chances to get the
> > module updated are high.
> 
> As the current PAR maintainer I beg to differ: PAR is a gross hack.
> 
> > fortunately you've found root of a problem, you need to nail down the
> > exact module in a problem.
> > Is it Pango CPAN module?
> 
> At least Pango and Gtk2.
> 
> >> This dual DLL loading - due to some Perl module misinterprets
> whether
> > XXX.dll already loaded - should be fixed.
> 
> "Perl" doesn't misinterpret anything here.
> Do you understand how DynaLoader and DLL loading on the OS level works?
> 
> > IOW - how exactly it computed that "Cairo.dll" is already loaded?
> 
> I don't know - it's an educated guess. I'm not too familiar with the
> internals how Windows loads DLLs. Feel free to use something like
> sysinternals
> (http://technet.microsoft.com/en-us/sysinternals/bb842062)
> to explore what's really going on.
> 
> Cheers, Roderich

Reply via email to