I'm also running into packaging problems: I created my program on Windows XP, SP3. I used the packager to make it into a .exe and didn't have any problems during the process. However, when I transfer that .exe over to my Virtual Machine and try to run it, I get:
Error in C:/Program Files/Common Files/Shoes/0.r1134/lib/shoes/shy.rb line 62 ! invalid distance too far back So I tried testing it on my computer, only to discover that the .exe doesn't even work there! Error in C:/Program Files/Common Files/Shoes/0.r1134/lib/shoes/minitar.rb line 661 ! Permission denied - C:/DOCUME~1/Roger/LOCALS~1/Temp/shoes-llm.4208/./ Any help for either of these? I really like using Shoes as a development platform, please don't make me go back to Java :) On Sat, May 23, 2009 at 9:12 AM, Sarah Allen <[email protected]> wrote: > Wouldn't the same problem exists for the native code parts of Shoes? > > On May 22, 2009, at 10:39 PM, Cecil Coupe wrote: > >> It's difficult meta problem. I'm on Linux (Ubuntu 9.04) and I'd like a >> little shoes app that front ends ffmpeg. Except.... it has to front end >> the ffmpeg I have, not the one someone thinks I need. Cross platform >> reaching out to system installed dynamic libraries from inside Shoes is >> a problem I shudder to think about. Mostly, Shoes won't. Hint's are in >> the installer code. For good reasons it maybe shouldn't. Bundling your >> own ffmpeg is also a big problem if you cover all the architectures, >> that's no fun either. >> >> ffmepgX was (is) an awesome GUI wrapper. I still miss it on Linux. A >> Shoes version would be a fine achievement. Keep me (or the list) >> informed. >> >> --Cecil >> >> On Fri, 2009-05-22 at 21:37 -0700, Noah Thorp wrote: >>> >>> Cecil. Thanks for the lead I will have a look at that! I agree with >>> you that I would prefer to find the bug rather than downloading files >>> - seem cleaner. I will have a look and see how it goes. It might lead >>> me to automating other aspects of the build process as well once I see >>> how the packaging works. >>> >>> Thanks! >>> Noah >>> >>> On May 22, 2009, at 8:44 PM, Cecil Coupe wrote: >>> >>>> I hate to follow up my own message but >>>> >>>> pack.rb line 156 (my older version of shoes) has this line of ruby >>>> dmg.grow(10) >>>> >>>> That seems like an arbitrary number that some folks have reported. I >>>> don't know what dmg.grow() does, but a hacker might up that to 30 or >>>> 40 >>>> and see what happens. Or one could read the docs for binject. Where >>>> that >>>> pack.rb is on your system and which copy of shoes you are using if you >>>> have multiples... >>>> >>>> Just something to look at. >>>> --Cecil >>>> >>>> >>>> On Fri, 2009-05-22 at 21:00 -0600, Cecil Coupe wrote: >>>>> >>>>> It might be easier to debug and fix the problem than implement a >>>>> workaround, IMHO. It looks like most of the action starts in >>>>> lib/shoes/pack.rb - I don't have an OS X box anymore so I can't be >>>>> very >>>>> helpful. Might be an easy fix if you can find all the parts. >>>>> >>>>> >>>>> >>>>> On Fri, 2009-05-22 at 21:24 -0500, Roy Wright wrote: >>>>>> >>>>>> Maybe as a work around, implement a download and install ffmpeg as >>>>>> needed instead of including the binary in the package? Similar to >>>>>> how a >>>>>> shoes app can download and install shoes... >>>>>> >>>>>> HTH, >>>>>> Roy >>>>>> >>>>>> Noah Thorp wrote: >>>>>>> >>>>>>> Thanks for the encouragement. I have plans to post the open source >>>>>>> transcoder (ffmpeg wrapper) once it had reaches a certain level >>>>>>> of alpha >>>>>>> maturity. It's a very simple but useful app. I could post it to >>>>>>> github >>>>>>> early if it would help troubleshooting. But, it seems like it may >>>>>>> be an >>>>>>> issue simply with including large files in an OS X package. >>>>>>> >>>>>>> Thanks, >>>>>>> Noah >>>>>>> >>>>>>> On May 22, 2009, at 5:31 PM, e deleflie wrote: >>>>>>> >>>>>>>> Hi Noah, >>>>>>>> >>>>>>>> I dont think you are falling outside of the use case it was >>>>>>>> intended >>>>>>>> for ... I think its just a bug. >>>>>>>> >>>>>>>> I dont have a work-around for you .... (maybe someone else >>>>>>>> does) ... >>>>>>>> but if we shout loud enough .... _why might hear our plea to >>>>>>>> have a >>>>>>>> look at this bug. >>>>>>>> >>>>>>>> So it looks like large binaries (5 to 10MB and up?) included in a >>>>>>>> folder and packaged up, for OSX, cause the packager to crash. >>>>>>>> >>>>>>>> Etienne >>>>>>>> >>>>>> >>>>> >>>> >>> >> > > http://www.ultrasaurus.com > > > > -- Roger
