I am using RuntimeBuilder to create a stand-alone MacPerl app called ImageDrop.
When a user drops an image onto ImageDrop, he is asked some questions, replies
stored in file's comment field, and then the image is ftped to a server.
To use RunTimeBuilder, you drop your MacPerl text file (drop.pl) onto
RunTimeBuilder.dp. It then creates the stand-alone app, giving the following
information:
Checking for imported modules...
Saving "drop.pl" as Runtime in
"Whitney:C A P S T O N E D O C S:P E R L:drop f:drop.run"...
Saving imported modules in resource fork of drop.run...
Copied module Tie:Hash.pm into resource fork.
Copied module Carp.pm into resource fork.
Copied module Mac:MoreFiles.pm into resource fork.
Copied module Config.pm into resource fork.
Copied module Exporter.pm into resource fork.
Copied module strict.pm into resource fork.
Copied module UNIVERSAL.pm into resource fork.
Copied module File:Copy.pm into resource fork.
Copied module File:Basename.pm into resource fork.
Copied module vars.pm into resource fork.
Copied module AutoLoader.pm into resource fork.
Copied module DynaLoader.pm into resource fork.
Finished.
RunTimeBuilder.dp creates a folder called drop folder. Inside that is drop.run
and a folder called shared libs. Inside shared libs is a library file called
MoreFiles.
My question is, why do I have to have the drop folder with the shared libs in
it? I thought RunTimeBuilder put the libraries in the resource fork? The
drop.run app that it creates is not really stand-alone. It won't run unless you
have the shared libs folder in the same directory as drop.run.
Does anyone have experience wih RunTimeBuilder.pm? Is there any other way to
create a stand-alone Perl app on the Mac? I need to distribute the app to users
who don't have MacPerl, so they can drop images into our archive system.
Thanks,
Kathy Richmond
