On 4/15/07, Dennis Schridde <[EMAIL PROTECTED]> wrote: > Am Sonntag, 15. April 2007 schrieb Per Inge Mathisen: > > On 4/14/07, Ari Johnson <[EMAIL PROTECTED]> wrote: > > > 1. OpenAL. MacOS X 10.4 provides an OpenAL framework, which I use in > > > building Warzone. I just include the framework in the .app file that > > > gets built, so that it will run on 10.3. But this is probably bad > > > practice. And 10.4 is required for a universal binary anyhow. It's > > > possible to build one that will work on 10.3 and 10.4, but it's a > > > royal hassle. So we can kill off support for OSX prior to 10.4 > > > "Tiger" ... and probably not that many people would really notice, > > > especially given that most of the bugs the Mac port has are from > > > people who are running on 10.4 boxes with Intel chips anyhow. > > > > Let's do that for 2.1. By the time we release 2.1, most people will > > probably be running MacOSX 10.6 anyway ;-) > > > > > 2. Other external libraries. Currently, I compile the Mac port by > > > using DarwinPorts to install automake, jpeg, libmad, libogg, libpng, > > > libsdl, libsdl_net, libvorbis, and physfs. > > > > You won't need automake for binaries, and libjpeg and libpng are > > already installed on 10.4 as unix type shared libraries, IIRC. That > > leaves libmad, libogg, libsdl, libsdl_net, libvorbis and physfs. I > > think you can safely skip libmad, because people should use the ogg > > files anyway. The SDL and ogg stuff are probably available as > > frameworks somewhere. That should leaves physfs. Doesn't it already > > have an Xcode project? Its maintainer is a Mac-fan, so it would > > surprise me if it doesn't. Sorry, don't have time to google these > > myself, but it looks doable to me. > Icculus switched over to CMake for the trunk not too long ago, so PhysFS 1.1.1 > has XCode support. I don't know what he plans for 1.0, though. >
PhysFS 1.0.0 doesn't, but I made a project file easily enough. My 10.4 system actually doesn't have libpng or libjpeg, and even if it did most of the libraries that come installed without installing the developer tools are ppc-only so that doesn't help toward a universal binary. Anyhow, I am working on an Xcode project to do all of this. Right now, with the versions of the external libraries I have been using for Warzone, it compiles all of them fine and then tries to compile Warzone, starting with lib/framework. The problem I have right now is that a MacOS header file that Xcode is including in some bizarre chain cause keyDown and mouseDown to be defined as enum values, whereas we define them as functions. Would it be a crime against nature to rename our functions to work around this? I can try to figure out how to un-include the offending header file, if so. Ari _______________________________________________ Warzone-dev mailing list [EMAIL PROTECTED] https://mail.gna.org/listinfo/warzone-dev
