Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Universal Binary #7

Closed
CyberSkull opened this Issue Dec 30, 2011 · 15 comments

Comments

Projects
None yet
3 participants

If you are still using 10.5 as the base SDK for Vienna, I'd really appreciate it if you compiled it as a Universal Binary! By setting the architecture flag to 32_64_universal (as I recall) will make a full build compatible with all PowerPC and Intel architectures.

Owner

barijaona commented Jan 14, 2012

You might be interested by this : https://github.com/barijaona/vienna-rss/downloads

It is based on the 10.6 SDK, but should run on PowerPC machines (10.5).

And as far as I know, it is also the only 64 bits binary currently available... Seems significantly faster on my config.

The base SDK provides the minimum version that the compiled application will work on. For 10.5 compatibility, the SDK must be changed to 10.5.

Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /Users/trevor/Downloads/Vienna.app/Contents/MacOS/Vienna
Reason: Incompatible library version: Vienna requires version 6.0.0 or later, but libcurl.4.dylib provides version 5.0.0

Owner

barijaona commented Jan 14, 2012

Funny, I am on Snow Leopard, but I just had the same issue with Ansani's version here http://forums.cocoaforge.com/viewtopic.php?f=18&t=23979&p=132136

I (naïvely ?) thought the "MacOS X deployment target" value should handle this...

For maximum compatibility, it is probably safer to statically link a few libraries... I'll have a look at this.

I got it again:

Dyld Error Message:
Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /Users/trevor/Downloads/Vienna.app/Contents/MacOS/Vienna
Reason: Incompatible library version: Vienna requires version 6.0.0 or later, but libcurl.4.dylib provides version 5.0.0

It looks to me like Vienna either needs to change the minimum requirements for libcurl to version 5 or include a copy of the current version of libcurl.

Owner

barijaona commented Jan 15, 2012

The Vienna code is using libcurl only once, to parse a date... (see XMLParser.m)

I moved the call to a separate framework, built using the 10.5 SDK. This way, it does not require libcurl version 6 anymore.

I am wondering anyway if there isn't a more efficient and robust enough way to parse a string representing a date... For instance ISO boredzo's 8601 date formatter https://bitbucket.org/boredzo/iso-8601-parser-unparser

Weird, I still get the same error.

I downloaded the source zip and found that the baseSDK is 10.6 while the deployment target is 10.5. I'm trying a build now in Xcode 3.1.3.

I got 223 build errors related to missing GUI delegates. ;p

Oh, this was the master branch. What branch should I build to test this?

@barijaona Ok, I grabbed that and I still can't build it. Note: I did find that you need to set the deployment target to 10.5 and the SDK for the dev and release to 10.5.

As for why I can't build it, either I am missing a piece or converting from newer Xcode to my older version is causing an issue. Could you please save a copy of the .xcodeproj file in 3.1 compatible format? Perhaps name it Vienna-xcode3.1.xcodeproj?

Owner

barijaona commented Jan 16, 2012

I don't have XCode 3.1, but I modified it to be 3.2.6 compatible. I just uploaded a binary at https://github.com/barijaona/vienna-rss/downloads

That version launches! :D

Customize toolbar does not work though.

Member

ansani commented Jan 17, 2012

Hi guys!
I'm currently work on this issue.
I tested a preliminary release on my 10.6.x mac and app launches without any problem.

I'll do some other tests and I plan to release short.

(Of course I mean the google_reader_support branch.

Salvatore

Owner

barijaona commented Jan 28, 2012

The official master currently supports universal building (tested on Snow Leopard with Xcode 3.2.6).

@CyberSkull : if you have a Leopard machine, please test...

@barijaona barijaona closed this Jan 28, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment