Hi Michael, had a nice holiday? ziege@ito.umnw.ethz.ch writes: >I'm still working on a way to build a standalone app from a perl script, >which doesn't need the required modules to be installed on the machine on >which it runs. So far that works fine by extracting the modules and placing >them as TEXT resources in the resource fork of the app as shown earlier. >But it doesn't with modules which load dynamically shared libraries >(extension modules) e.g. the toolbox modules. So my question: Is there a >way to include these libraries as resources into the runtime version as >well? Any suggestions? Currently, there is no such way, as MacPerl does an explicit search for the library and then loads it with GetDiskFragment, if my memory serves me. However, there is no inherent reason why MacPerl couldn't search its own data or resource fork for the fragment first; I can probably implement that quickly. So your job would be to merge the libraries into either the data or resource fork. The data fork would have the advantage that virtual memory works better, so I tend to favor that solution. OTOH, the resource fork would probably work easier for you. What do you prefer? Matthias ----- Matthias Neeracher <neeri@iis.ee.ethz.ch> http://www.iis.ee.ethz.ch/~neeri "I'm set free to find a new illusion" -- Velvet Underground ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch