Re: Linking additional object files into framework project
Re: Linking additional object files into framework project
- Subject: Re: Linking additional object files into framework project
- From: Jonathan Mitchell <email@hidden>
- Date: Fri, 11 Apr 2014 10:28:10 +0100
On 10 Apr 2014, at 23:08, Jens Alfke <email@hidden> wrote:
>
> On Apr 10, 2014, at 2:23 PM, Jonathan Mitchell <email@hidden> wrote:
>
>> A is a standard framework.
>> B is a makefile project that contains a large number (~1300) of auto generated source files. The makefile builds the source into objects but doesn’t link them.
>
> Can you modify the makefile to at least combine the object files into a static library (.a) file? That would make things easier. You can then just add the .a file to your target as though it were any other library. You might be able to add .o files to a target the same way; I’ve never tried it. But I don’t think you need to mess with the linker flags.
>
Something like that would be my preferred approach but B uses a base class defined in A.
I presume that a static library build will fail to link if it cannot resolve all its symbols at link time.
It might be better to try and separate out the dependencies into two separate frameworks.
The end user would then have to link to two frameworks but that might be okay.
Either way the make file will have to link all those objects into something.
Thanks
J
_______________________________________________
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