Re: [MacPerl] RuntimeBuilder and MacPerl 5.6.1

2002-05-30 Thread Morbus Iff
>I will see if I can build amphetadesk with my latest version >of standalone builder and report here. Awesome. Make sure you use the latest CVS sources. Of special importance is that the lib/ directory SHOULD NOT NOT NOT be included in the runtime. The lib/ directory is intended to be shipped

Re: [MacPerl] RuntimeBuilder and MacPerl 5.6.1

2002-05-30 Thread Axel Rose
Hello Morbus, I will see if I can build amphetadesk with my latest version of standalone builder and report here. I fear the lot of questions users might have because of dynamic module loading like require $module Those situations cannot be solved. For the moment I'm happy to help everybody d

Re: [MacPerl] RuntimeBuilder

2001-07-08 Thread Bart Lateur
On 07 Jul 2001 21:08:08 EDT, Katherine Richmond wrote: >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. I've begun checking out RunTimeBuilder.dp, I've already found a few min

Re: [MacPerl] RuntimeBuilder

2001-07-07 Thread Morbus Iff
>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.

Re: [MacPerl] RuntimeBuilder

2001-05-02 Thread Bart Lateur
On Wed, 2 May 2001 20:20:15 -0700, Bill Becker wrote: >I have a question: How does one go about telling the system how much >memory to assign an app? > >Likely not relevant, as are most of my questions, but since it >happens to be the topic du jour, I thought I'd ask. This might depend on the

Re: [MacPerl] RuntimeBuilder

2001-05-02 Thread Bill Becker
I have a question: How does one go about telling the system how much memory to assign an app? Likely not relevant, as are most of my questions, but since it happens to be the topic du jour, I thought I'd ask. >MacPerl, OTOH, is doing all the hard work, and can use all the spare >memory that yo

Re: [MacPerl] RuntimeBuilder

2001-05-02 Thread Bart Lateur
On 02 May 2001 19:35:30 EDT, Katherine Richmond wrote: > RuntimeBuilder does work now. That's good to hear. > I >gave both MacPerl and RunTimeBuilder.pm 8 MB ram. Probably could go lower, but >I'm just thrilled that it works! A droplet doesn't need much memory. All it does, it get a list of t

RE: [MacPerl] RuntimeBuilder

2001-05-02 Thread Katherine Richmond
I meant to say RuntimeBuilder.dp. --- Katherine Richmond wrote: --- You wrote: Did you try it with as much memory as you can give it? --- end of quote --- Pete, Thank you so much for replying. I discovered that I had two copies of MacPerl, and I was not giving the RAM to the correct one! Run

RE: [MacPerl] RuntimeBuilder

2001-05-02 Thread Katherine Richmond
--- You wrote: Did you try it with as much memory as you can give it? --- end of quote --- Pete, Thank you so much for replying. I discovered that I had two copies of MacPerl, and I was not giving the RAM to the correct one! RuntimeBuilder does work now. I gave both MacPerl and RunTimeBuilder.

RE: [MacPerl] RuntimeBuilder

2001-05-02 Thread Pete Prodoehl
Did you try it with as much memory as you can give it? Pete > -- > From: [EMAIL PROTECTED] > Sent: Sunday, April 29, 2001 6:02 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [MacPerl] RuntimeBuilder > > I have downloaded Runti