>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.
Kathy,
RuntimeBuilder knows how to put *perl* libraries into the resource fork of
a compiled app, however, it is impossible to put XS built libraries, which
are C code into the runtime app. You'll notice the same "shared libs"
directory in my compiled perl project: http://www.disobey.com/amphetadesk/
As for another way of building a perl runtime, I know of none. You can,
however, ship the "shared libs" directory with your program (as I have
done) - users won't have to have Perl.
Another option is to try and replicate the MoreFiles code yourself, using
pure perl - this would bypass the C code (at the expense of speed) and
cause a single file for your users. Whether this is possible in your case
will be half the fun of finding out (due to dependencies from other modules
and so forth).
Dartmouth, eh? I'm in Concord, NH.
--
ICQ: 2927491 / AOL: akaMorbus
Yahoo: morbus_iff / Jabber: [EMAIL PROTECTED]
[EMAIL PROTECTED] / http://www.disobey.com/
