-
Notifications
You must be signed in to change notification settings - Fork 168
Cannot package on Windows 7x64 #265
Comments
It's wasn't a known problem until now. Thanks for reporting it. I can Oddly, binject.so is right where the error message says it is. I suspect I'll follow up with a newer version that works once I figure out what's Thanks for the bug report. On 08/27/2014 01:23 PM, Gavin Kistner wrote:
|
This may take some time than either of us like. The only work around would be to do the packaging from OSX or Linux (for an exe). Older versions of 3.2 that I know worked, don't work any more. I hate blaming Windows updates but that's the leading explanation. |
I didn't realize that OS X could package for Windows. That sounds like a reasonable workaround. When packaging a folder of files, how do I instruct Shoes which is the main file? I have tried the GUI Packager on OS X and successfully created a .exe that runs on Windows, but it just spews a bunch of output about non-UTF-8 files:
(second message repeats ≈infinitely) However, manually replacing all |
Sadly, the packager is currently limited to packing one (1) file. It's a big weakness that's on the todo list. One could try packing your directory into a .shy and then package that into an .exe - it might work. |
…indows pe handling. No hfs/dmg. Source code for binject is still there but not used.
@Phrogz (and others watching). I've updated Shoes 3.2.15 (Sept 2 2014 date). It's now working for me: Packaging a single script with Shoes Windows. Packaging a directory hasn't been fixed yet. You'll have to download and reinstall 3.2.15 to test it. |
I am trying to create a self-running .exe on Windows. When I launch Shoes.exe and click on "Package an App with Shoes" nothing happens, but I get the following error in the console:
This is on Windows7x64, running Shoes v3.2.14. Is there a know problem with the packager, and if so is there any workaround?
This file does exist on my hard drive:
C:\Program Files (x86)\Common Files\Shoes\3.2.14-gtk2-32\lib\ruby\2.1.0\i386-mingw32\binject.so
The text was updated successfully, but these errors were encountered: