Cannot develop for Leopard on Xcode 4

Bug #739089 reported by Hofman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sparkle
Confirmed
High
Unassigned

Bug Description

It is not possible to compile Sparkle on Xcode 4 while supporting 10.5.x. The reason is that Xcode 4 requires the use of the 10.6 SDK, while Sparkle links to libcrypto, which is not compatible with the version available on 10.5.x.

Isn't it possible to replace the DSA verification code by something that is compatible, rather than the very problematic openssl?

BTW, why does it link to libcrypto using an explicit linker flag, rather than adding libcrypto to the link build phase? It took me a lot of time to figure out what was going wrong.

Revision history for this message
Andy Matuschak (andymatuschak) wrote :

I'm not sure it makes sense to do this, given that we still want to support 10.4 and 10.5. If the Sparkle framework links against the 10.6 SDK in Xcode, we won't get appropriate build warnings/errors when we use methods that didn't exist in older versions.

Changed in sparkle:
status: New → Won't Fix
Revision history for this message
Hofman (cmhofman) wrote :

Why have you marked this "won't fix"? This is a serious problem. Very soon, Lion will be out, which does not support Xcode 3.x. This effectively means that you won't be able to build Sparkle as it currently is on Lion. I think this needs to be fixed, and it needs to be fixed very soon, before Lion comes out (which is this month).

And your remark about warning and errors is really irrelevant, you can say the same for 10.4 but you apparently don't care there. And an inconvenience most definitely doesn't trump an impossibility.

Revision history for this message
Andy Matuschak (andymatuschak) wrote :

Yeah, my attitude has changed as the characteristics of the final released version have become clearer.

There's a patch that should help this at https://github.com/andymatuschak/Sparkle/pull/20, though I won't have a chance to review for a bit.

Changed in sparkle:
status: Won't Fix → Confirmed
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.