|
From: Francesco M. <f18...@ya...> - 2006-12-22 19:01:31
|
Anders F Björklund ha scritto: > Francesco Montorsi wrote: > >> I don't understand exactly what needs to be done to get this, >> however... >> (i.e. which is the post-process step?) > > Sorry, the post-process would be either of: > 1) Rez (Carbon.r, wxLua.r), SetFile > 2) mkdir/cp (wxLua.icns), Info.plist > > i.e. either make resource fork, or make bundle. > This could of course easilly be scripted... see my other mail about Rez & SetFile. Don't know about step #2.... what does it do? Should it go in makefiles (not so easy to do) because it's _required_ for getting wxLua apps to work or rather it's something related to the distribution/packaging process which could be scripted in a separate distrib/macbundle/make.sh script? >>> Works good on Mac OS X 10.4, anyway. Looks good, too: >>> http://www.algonet.se/~afb/wx/wxlua28-wxluasudoku.png >> great, I've added also this screenshot (I also added the other ones you >> posted - thanks!). > > Once wxLua 2.8.0 is release, we can synchronize screenshots... actually I forgot to update thumbnails. Done now. >>> Of course, then one might as well wrap the program with >>> a call to "wxlua" and not use freeze in the first place ? >> AFAIK wxluafreeze basically just do that: i.e. wraps the user's lua >> script with a wxlua interpreter... > > Yes, but I meant wrapping it in a shell script: > #!/bin/sh > wxlua `dirname $0`/myprogram.wx.lua > > Just so that the user has something to double-click :-) yes, of course it could be done. But wxluafreeze has the advantage of not requiring an external wxlua installed (i.e. it's the equivalent of the Python freeze)... Francesco |