Re: proper way to manage built 32/64 bit libraries for Xcode 4
Re: proper way to manage built 32/64 bit libraries for Xcode 4
- Subject: Re: proper way to manage built 32/64 bit libraries for Xcode 4
- From: Tobias Ford <email@hidden>
- Date: Tue, 26 Jul 2011 10:53:54 -0500
There are lots of reasons to want to do this. It's a code base that builds both a server and a client using quite a bit of shared code. The libraries can be built however I want them built, since they are external libraries that are built on the command line. It's all managed from a single collection of Xcode projects and makes complete sense to build something as the server as a 64bit application and keep the client as a 32bit application. Some of the libraries are linked into both the client and the server or various content validation tools, server management applications, debugging tool, or editors. It's also a code base that needs to maintain supporting multiple architectures. Not all of these need to be 64bit. It's not that much of an uncommon problem when building this type of code base.
In smaller apple terms, this isn't really any different of a problem then managing ppc and x86.
My question was what's the preferred way of managing external libraries in a code base like this? Should I still be using lipo to create a fat binary of each library that can then be linked against? Or is there a more preferred approach now when using Xcode 4, such as keeping non-fat versions of each architecture and doing something else?
-------------------
Tobias Ford...
On Jul 26, 2011, at 4:22 AM, Christiaan Hofman wrote:
>
> On Jul 26, 2011, at 8:46, Tobias Ford wrote:
>
>> xcode 4 has the option to build both 64 or 32 bit targets from the pop-up target menu and I have several external libraries that are built on the command line. I have everything building and linking fine as a 64 bit application. When building as a 32bit application, my libraries can't be linked against since they happen to be 64bit.
>>
>> What's the best way to manage this problem in Xcode? I don't really want to create a separate target for each architecture. Is building a fat library using lipo the only option or is there another option/solution that I might be overlooking?
>>
>> Thanks.
>>
>> -------------------
>> Tobias Ford...
>
> You make no sense. Why would you even want to build a 32 bit binary if it needs libraries that don't support 32 bits? It would be a complete dummy which could never run, so a complete waste of building time and resources. Really, what do you want?
>
> Christiaan
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden