|
From: James W. W. <os...@jw...> - 2006-05-09 16:09:15
|
On May 9, 2006, at 8:29 AM, Sean McBride wrote: > 1) <http://www.quesa.org/> still says 1.7 is the latest, with a > 2005 date. > 2) the file "/quesa_1.8_sdk_mac/Quesa Read Me.html" says "Welcome > to the > 1.7 release of Quesa...". > 3) is the sourceforce cvs server still not working? It's not for me. From the SourceForge site status page: ( 2006-05-05 07:55:54 - Project CVS Service ) As of 2006-05-05 we are still waiting on all the hardware for the replacement CVS infrastructure. A few of the machines we received from our vendor had disk issues shortly after configuration, so we are vetting all the systems for issues, and reloading a few of them. The service deployment itself is running smoothly and we don't anticipate any problems other than the existing hardware issues that we are working through with the vendor. We are currently estimating a deployment for the end of next week (May 12th). > 4) looking at the target settings for the 'Static Lib (Univ)' > target, I > see that only the Debug configuration is built universal, and the > release isn't. An oversight I assume? Yes, sorry. > 5) are the static lib and framework that are already built and > included > in quesa_1.8_sdk_mac debug or release builds? Release. Debug builds just seemed too huge. Rumor has it that an upcoming version of Xcode may make this less of a problem. > 6) the Xcode project settings have DYLIB_CURRENT_VERSION = 1.7 and > DYLIB_COMPATIBILITY_VERSION = 1.6. I'm guessing the former should > be 1.8? Probably. I've never actually used those version numbers for anything, have you? |