Hi Eduardo, On 4/2/2010 2:58 PM, Eduardo Poyart wrote: > I'd like to help make CS work on Mac OS X again
Help would be appreciated. In addition to issues you raise, there are several open tickets in the issue tracker. Here are four (but there may be others): http://trac.crystalspace3d.org/trac/CS/ticket/631 http://trac.crystalspace3d.org/trac/CS/ticket/633 http://trac.crystalspace3d.org/trac/CS/ticket/670 http://trac.crystalspace3d.org/trac/CS/ticket/703 > - I have OS X 10.6, and the current head revision fails to build for me. > I made it build if I change the SDK we're using from 10.4u to 10.5. What exactly failed? Does it build if you configure CS with the --disable-universal-binary option? Whether 10.4u or 10.5 is the default, we should (hopefully) be able to support both. > OSX > 10.6 introduced many changes to the system, deprecating many things. I > suspect that's what broke it. I don't know if it builds for someone that > has 10.5. If it does, it was some change introduced with 10.6. If not, > head revision is broken for OS X in general. Best would be to post the error message(s), configuration information, and so forth. I strongly recommend using the issue tracker (http://trac.crystalspace3d.org/trac/CS/) and opening a ticket for each distinct problem you encounter. This will help to ensure that provided information and related discussion remain associated with the problem description, and that the issue can more easily be found by others experiencing the same. > - Architectures have to match between libraries. Specifically, you can't > build zlib for x86-64 and CS for i386. The trouble is: starting with > 10.6, GCC defaults to x86-64. So people building zlib with default > values will have problems building CS with default values. The error is > subtle: configure simply reports zlib is not detected. Note that there is a To-Do item related to adding x86_64 to CS's "universal binary" support. http://trac.crystalspace3d.org/trac/CS/ticket/633 > Based on the above, I propose two steps: > - Update our OSX requirements from 10.4 to 10.5 - or at least make it > default to 10.5 and let people specify 10.4 if they know what they're doing; A more dynamic solution may be warranted, such as detecting which SDK is installed, rather than assuming 10.4u (the present hard-coded value) or 10.5. > - Similarly, change the default architecture to x86-64 to match modern > OSX's default architecture. A more proper approach would be instead to implement ticket #633 rather than merely shifting the problem to developers using somewhat older systems. Also, for developer's who don't care about older systems, configuring with --disable-universal-binary should side-step this issue altogether. It may be meaningful to disable this by default, though it is not clear that doing so would be any better than having it enabled by default since there still are many 32-bit machines out there (and even PowerPC machines). -- ES ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[email protected]?subject=unsubscribe
