John Labenski wrote: > Anders, what do you think needs to change to make compiling on OSX run > smoothly?
Not much, maybe just need to add a little to the fixup scripts... > My preferred method of compiling both wxWidgets and wxLua is to create > a dir "wxLua/config_osxud" (unicode, debug) and then running > $../configure --prefix=/Users/john/.../wxLua/config_osxud > $make > so everything is nicely within the config_osxud dir and I can quickly > delete that to start over. > I create a link ~/bin/wx-config -> to my preferred wx-config, where > ~/bin in first in my bash path. Right, I have pretty much the same but in my /usr/local instead. My wxWidgets installation is a 10.4+ Universal Binary configuration, so the configure is a little (=much) more convoluted but similar. I also made sure to install the OpenGL and the STC components. Normally I build the regular wx libs as "monolithic", though. > Ok, so this is not "standard" as opposed to installing to a "system" > dir like /usr/local , but I do not want to have to dig out and delete > the installed files when drastic changes are necessary. Okies. Guess you could use something like /opt/wxWidgets too ? > So... anyway > > 1) I see that after running the above that wxLua.app (all the apps) > are installed into apps/. Should we change the target, for example, > wxLua.app/Contents/PkgInfo in the generated apps/Makefile to create > wxLua.app in bin/ ? I'm fine with having the bundles in "apps", and "bin" stay sane. If anything, they should go in "Applications" or something... ? And it should probably use Frameworks, instead of regular dylibs. Porting to Xcode projects could also be done, even more Kool-Aid. But that's all a lot of hassle, so might as well keep it in "apps". Makes wxMac more similar to the other ports (wxGTK and wxMSW), even if the wxWidgets guys have decided* that you need to either wrap the binaries in bundles or to add resource forks to them if you want them to be able to receive any events after startup. * see http://lists.wxwidgets.org/archive/wx-dev/msg83276.html > 2) What is the deleting and moving part of > distrib/macbundle/copydylibs.command supposed to do? > I think it assumes that you've run $./configure in the root dir of > wxLua. > > $cd distrib/macbundle > $copy ../lib/*.dylib . <--- ? should be ../../lib/*.dylib ? > $rm libwxlua_macud_wxlua_2.8.0.dylib <- the symbolic link > What about the other symbolic link libwxlua_macud_wxlua_2.8.dylib? > $mv real lib to *0.dylib > I get what the install_name_tool parts are doing. It's supposed to move all required wx libraries into the apps folder so that all the app bundles are "clickable". Should probably have one copy of wxWidgets and wxLua for each application, but I put them all next to the apps to cut down on the insane amount of bloat otherwise. This was for the "stand-alone" installation, in the DMG. For MacPorts, nothing is relinked and everything links off to the ${prefix} (normally it is set to /opt/local) There it can have a dependency on the "wxWidgets" port (or "wxgtk" for X11), so doesn't have to bundle anything. > If I understand correctly we want the real dylibs renamed to > reallibname.0.dylib, which was originally a link. Finally where does > all these libs go? When the script ends it looks like they'll still be > in distrib/macbundle. Well, one could copy the "real" dylibs and the symlinks too, think I was just lazy - and wanted less clutter for the user. Double-check the wxLua DMG to make sure, but I think is was meant to be run from within the "apps" folder ? Other was just a copy. http://downloads.sourceforge.net/wxlua/wxlua-2.8.4.1-tiger.dmg > 3) After compiling with the above method, wxLua.app segfaults because > it's confused about what dynamic libs to use. When I run > $otool -L wxLua.app/Contents/MacOS/wxLua > I see that it's linked to all my wx-config libs except for > /usr/lib/libwx_macud_stc_2.8.0.dylib and same for the gl lib. Ugh. I > see that the Osx replacement for LD_LIBRARY_PATH is dyld, but is there > a simpler way? Do you not have this problem? I'm not using the old Apple wxWidgets libraries, and I'm using the "release" variant instead of the "debug" variant. I haven't updated the above script for wxLua 2.8.7.0 yet, but it was used for wxLua 2.8.4.1 - as far as I remember... --anders ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
