Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

.a static libraries and forced local exports

Here's a weird one -- I understand why, just wondering if there is a way around. As I understand it, .a static libs are just a collection of unlinked .a files (OK, makes sense - now that I know to look on IBM's site for this info :)

The problem I have is if two of the .a files (within the lib) refer to functions in each other, i.e.:

File one.c

void do_it(int x)
{
do_it_in_two(x);
}

File two.c

void do_it_in_two(int x)
{
}

Then "do_it_in_two" must be exported to anybody using the library EVEN though it's only needed locally in the library (must be put in my exports file.) Since the linking happens IN the application where I included the library, I get link errors there if the functions aren't exported.

Is there a way to work around this?

[>] Brian
_______________________________________________
projectbuilder-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/projectbuilder-users
Do not post admin requests to the list. They will be ignored.


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.