[Wxlua-users] Re: wxMac - packaging details

[Francesco M. <f18...@ya...>]

Anders F Björklund ha scritto:
> Here is how the Mac packaging works... (="will work")
> 
> Dual: just like Mac OS X itself, this can be done in
> two different ways, the "Mac way" or the "Unix way"
> (with the Mac way being more of the NeXT way really,
> but that is a topic for a whole other discussion...)
> 
> --------------------------------------------------
> 
> 1.
> For the Mac way, I will do static links like this:
> 
> wxLua.app/
>     Contents/
>         Info.plist
>         MacOS/
>             wxlua
>         Resources/
>             wxLua.icns
> wxLuaEditor.app/ (ditto)
> LuaCan.app/ (ditto)
> 
> The "Info.plist" can be generated from Info.plist.in,
> it's an XML file that describes the application...
> 
> This will not get "installed", but the user can drag
> it to /Applications or ~/Applications, or wherever.
> 
> This "wxLua.app" bundle is what we set as the
> application to launch for .lua files, and so on.
> 
> The Samples themselves will just go in a folder.
> Package will be either ZIP or DMG, probably dmg ?
> 
> ---------------------------------------------------------
> 
> 2.
> For the Unix way, it will be shared linked like:
> 
> $PREFIX/bin/wxlua ->
>         $PREFIX/lib/libwxlua_mac_wxlua-2.6.0.dylib
>         $PREFIX/lib/libwxlua_mac_wxbindstc-2.6.0.dylib
>         $PREFIX/lib/libwxlua_mac_wxbind-2.6.0.dylib
>         $PREFIX/lib/libwxlua_mac_wxluasocket-2.6.0.dylib
>         $PREFIX/lib/libwxlua_mac_wxluadebug-2.6.0.dylib
>        $PREFIX/lib/libwx_mac-2.6.0.dylib
> 
> That last library is not provided by wxLua,
> it's the wxWidgets shared library being used.
> (could be either wxMac or wxGTK, and either
> monolithic or split into several - as usual)
> 
>        $PREFIX/lib/libwx_mac_stc-2.6.0.dylib
>        $PREFIX/lib/libstedit.0.dylib
> 
> Will probably link STC and wxStEdit statically ?
> (just to avoid problems in DarwinPorts and Fink)
> 
> On Mac OS X, "commandline" programs launch in the
> background and don't receive any events (sucks!),
> so we will fake this for the "Unix way" by adding
> an oldskool Mac resource fork, including the icon:
> 
> /Developer/Tools/Rez -d wxLua.r Carbon.r -o $PREFIX/bin/wxlua
> /Developer/Tools/SetFile -a C $PREFIX/bin/wxlua
> 
> This will make it look nice, and : receive events too. :)
> All these files will get installed, in the usual $PREFIX.
> 
> ---------------------------------------------------------
> 
> Hope that clears things up ? Mac OS X is a strange hybrid...
this helped indeed to understand Mac world ;)
So, we just need to add to build\macbundle the Info.plist and maybe a 
simple script which calls the utilities to actually build the package, 
isn't it?

I can then add Info.plist to configure list of files to create. It won't 
be used by Unix installations but only by Mac ones...

Francesco