Anders F Björklund ha scritto:
> Francesco Montorsi wrote:
> 
>>> I did a compromise, and linked all 4 apps towards the same
>>> copy of wxWidgets and wxLua libraries to keep the size down.
>>> The following script was used to copy the libs into "apps",
>>> and rename: http://www.algonet.se/~afb/wx/copydylibs.command
>>> (it changes the dylib library paths, from PREFIX=usr/local
>>> to a relative path f @executable_path/../../.. instead)
>> thanks, I've added that script to wxLua/distrib/macbundle
> 
> I didn't include the wx libraries in the default copy, since
> you might want to leave them separate (followed the .bat file)
> As long as the .app are left in the wxLua folder, it should be
> OK. Moving the .dylib files to /usr/local/lib should also work.
> 
> For a stand-alone release of one app, one can tweak the script
> to keep the dylibs in @executable_path (i.e. the MacOS folder)
> Or rebuild everything statically, if that approach is preferred.
> Will probably do a Portfile for DarwinPorts, with external libs.
great, thanks!



>>> It requires Mac OS X 10.4, but runs on both PowerPC and Intel.
>> I've selected for "Architecture" the "Mac Universal (PPC/x86)" choice,
>> then, in the SF download page.
> 
> Looks good, and I've tested the program on Intel and PowerPC.
> (It's possible to build a version for 10.1-10.3, if required)
I don't know much about 10.1 and 10.3 but if they are old versions (as I 
suspect) I wouldn't take the burden of supporting them with binary 
releases...

> Another minor item is that the application menu now says
> "app_wxlua", so we might want to rename the MacOS executable
> inside the bundle to read "wxLua" instead
ok - but to be sure: on my linux the executable generated is already 
named "wxlua" (and not "app_wxlua"), isn't it so also on your Mac?

> - and also do a
> matching change in the Info.plist under CFBundleExecutable ?
ok but I don't understand if the app_wxlua-thing is a mac-only thing 
(because e.g. of some mac-specific thing) or rather a bug in bakefile 
which generates on Mac executables with the wrong name (i.e. with the 
"app_" prefix...)...


> We might also want to add a Xcode project, besides autoconf ?
> (not sure if it needs any scripts/conf, or if it would be easy)
bakefile already contains some code to generate XCode projects but 
that's not working yet... so I'd wait for that format to be fully 
supported by bakefile (I know: it may take a lot of time to see it fully 
done but taking on the burden of maintaining an additional set of XCode 
project files, not automatically generated isn't going to help).

Thanks,
Francesco


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
wxlua-users mailing list
wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users

Reply via email to