BTW, can you tell me, why the programs made using the Tk library are not accessible at all for screen readers? (while Win32::GUI is very accessible) Because of the TCL/TK library, or because of its port to perl...?
Thank you. Teddy ----- Original Message ----- From: "Jan Dubois" <[EMAIL PROTECTED]> To: "'Jeff Griffiths'" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Friday, December 23, 2005 21:49 PM Subject: RE: Why is PerlApp's .exe package smaller than PAR? > On Fri, 23 Dec 2005, Jeff Griffiths wrote: > > Thomas, Mark - BLS CTR wrote: > >>> Also, I may end up distributing more than 1 Perl application to the > >>> same host. Is there a way for multiple distributions to share common > >>> libraries (maybe core dlls) so that the file can be even smaller? I > >>> don't mind if the libraries are thrown into windows/system32/. > >>> That's fine. > > [...] > > > This is my best impression of how our implementation works, I'm sure > > Jan can shed more light on the specifics. > > Sure, please let me know if there are specific questions. Ideally I > would like to see that discussion on the PDK mailing list, where it > is "more" on topic. > > Here is a snippet of what I wrote previously on the PDK list in response > to a different question: > > | A library is indeed just another PerlApp program (or PerlCtrl or > | whatever). However, it may make sense to just put a little dummy stub > | program into your library. Personally, I would also give a library a > | .dll extension on Windows even though it is not really a DLL when you > | build it with PerlApp. > | > | The idea is simply to put all shared modules into a single executable: > | > | perlapp --scan app1.pl --scan app2.pl --shared private stub.pl --exe lib.dll > | perlapp --use lib.dll --xclude --shared private app1.pl > | perlapp --use lib.dll --xclude --shared private app2.pl > | > | Both the library and the applications must be compiled using the -- > | shared option. Otherwise they won't be able to access each others > | bundled modules at runtime. > | > | If you want to put your lib.dll and the perl58.dll into a separate > | directory (which I recommend), then you also want to use the --runlib > | option for the latter 2 commands. > > Cheers, > -Jan > > > > _______________________________________________ > Perl-Win32-Users mailing list > [email protected] > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs _______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
