Re: How to build some files for some destinations/architecture only?
Re: How to build some files for some destinations/architecture only?
- Subject: Re: How to build some files for some destinations/architecture only?
- From: Jean-Denis MUYS <email@hidden>
- Date: Fri, 23 Sep 2011 15:37:23 +0000
- Thread-topic: How to build some files for some destinations/architecture only?
On 23 sept. 2011, at 17:09, Fritz Anderson wrote:
> On 23 Sep 2011, at 9:57 AM, Jean-Denis MUYS wrote:
>
>> Yes I know about handling that at the C compiler level. But:
>>
>> 1- It's ugly to have to handle build issues at the source-level
>> 2- This sounds like a C-solution only. Unless the C-preprocessor is run on .s files too? I would hate being limited to inline assembly.
>
> Untried: Possibly you could have a separate library target for each architecture that builds a static library from your architecture-specific code, and in the build settings for the principal target add (for instance) -larmassembly as a arch-conditional setting for Other Linker Flags for the ARM architecture, -li86assembly for 32-bit Intel, and so on.
I guess that would work. What a scaffolding!
> You're never going to have a solution that isn't ugly. The core concept of targets is that they embody invariant sets of source files.
That I can try: one target for the device, another target for the simulator. Still ugly I guess, but slightly less.
I'm surprised there isn't anything simpler.
JD
_______________________________________________
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