At 06.14 98.02.02, Toni Zollikofer wrote: >I while ago, found out (with some hints from Chris Nandor) that Droplets or >runtime modules do not work without the MacPerl package, if they reference >libraries or modules (with "use" or "require"). >At least, I found it impossible to recursively paste in everything whats >called during execution (if there IS a way, please tell me). Well, actually, droplets will not run AT ALL without the MacPerl executable. Runtimes will run without the executable, but not without libaries that it needs. However, TEXT libraries and modules can be embedded in the resource fork of the runtime, so you do not need an extra folder. The only problem then is shared/dynamic libraries, that cannot (yet) be embedded. For those, there are only two options: either put them in a folder, OR use the 68K-only BigMacPerl app to save your runtime. This version of MacPerl has all the MacPerl shared libraries linked in statically, so there is no need for accessing them externally (my whichMacPerl app does this). The script to save the TEXT libraries in the resource fork has been posted many times, and is also on the MacPerl CD-ROM (ExtractModules is its name). If you need it, I can e-mail it to you. The only thing this droplet does not do for you is it does not embed autoloaded files ... if it still says it can't find files after you run the droplet, you can just add those extra ones by hand, using ResEdit. You should see, in the TEXT resource, how it all works. Have fun, -- Chris Nandor mailto:pudge@pobox.com http://pudge.net/ %PGPKey=('B76E72AD',[1024,'0824 090B CE73 CA10 1FF7 7F13 8180 B6B6']) #== New Book: MacPerl: Programming for the Rest of Us ==# #== Publishing Date: Early 1998. http://www.ptf.com/macperl/ ==# ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch