On 25 Feb 2008, at 5:44 PM, Adam R. Maxwell wrote: > In article <[EMAIL PROTECTED]>, > Christiaan Hofman <[EMAIL PROTECTED]> wrote: > >> On 11 Feb 2008, at 10:27 PM, Adam R. Maxwell wrote: >> >>> Unfortunately, the damn Omni frameworks prevent using the 10.5 SDK >>> with >>> a 10.4 deployment target, so the best option (4) doesn't work, and >>> cross-development is a huge pain. >> >> You have any idea what's wrong? Is it th fact they check for >> MAC_OS_X_VERSION_MIN_REQUIRED? It seems to me they should check >> MAC_OS_X_VERSION_MAX_ALLOWED instead. > > I tried making that change early on, but it didn't work. Since > they're > reimplementing symbols that exist in the runtime on 10.5, the linker > complains. Since they declared all of their crap as inline > functions in > a framework header, it all gets pulled into BD as well, so you can't > compile the frameworks against 10.4u and the main app against 10.5. > > One possible solution is to move the functions into a bundle that gets > loaded at runtime on 10.4. I'm not sure if it's possible to do that > early enough, since they're called during runtime setup. Certainly > using NSBundle wouldn't work, so it would probably have to be done > using > CFBundle and __attribute__ ((constructor)), or possibly dlopen. > > -- > adam
They should have done something like I have done now in Skim's version of OBUtilities. Replacing the 10.5-only functions should depend on a run-time condition, not a compile-time condition. Christiaan ------------------------------------------------------------------------- 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/ _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
