Re: Per architecture file subsets in a Compile files build phase
Re: Per architecture file subsets in a Compile files build phase
- Subject: Re: Per architecture file subsets in a Compile files build phase
- From: Daniel Rodriguez Troitiño <email@hidden>
- Date: Wed, 18 Mar 2009 12:05:47 +0100
On Wed, Mar 18, 2009 at 09:58, Jan E. Schotsman <email@hidden> wrote:
>
> On Mar 18, 2009, at 9:19 AM, Daniel Rodriguez Troitino wrote:
>
>> I'm trying to adapt a project to use Xcode. This project has to be
>> compiled for several architectures (PPC & x86), and both architectures
>> have some files specific for the architecture (optimized version of
>> some functions, with some inline assembly). Then I have my target (a
>> library), which will be great if it can be a "fat" library.
>>
>> My problem is that I haven't found a way to ask Xcode to compile some
>> files for one architecture, but not for other, and viceversa. I have
>> search high and low in Google and in the list archives and I haven't
>> found a solution.
>
> I simply start and end files with
>
> #if __VEC__
> #endif
>
> or
>
> #if __SSE__
> #endif
>
> assuming this is about Altivec/SSE.
>
> Sometimes I need stub functions too to get everything to compile.
> Like
>
> #if __VEC_
> my_function
> vector code
> #else
> my_function
> {
> }
> #endif
>
> Jan E
Thank you all for your answers. Seems that the preprocessor is the
most popular solution. I will try that, to keep the targets to a
minimun.
Daniel.
_______________________________________________
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