Dependent/injected tests vs. linker visibility
Dependent/injected tests vs. linker visibility
- Subject: Dependent/injected tests vs. linker visibility
- From: Jim Correia <email@hidden>
- Date: Mon, 16 Nov 2009 22:56:26 -0500
[Moved from Xcode-Users since it really isn’t an Xcode issue.]
I have some dependent/injected unit tests to test application-specific
functionality. I've added a test that calls a C function which is
defined in the application. This causes a link-time error because, by
default, applications are compiled with -fvisibility=hidden.
What practical solution are you all using for this problem?
- Globally make symbols visible?
- Only for Debug (or a Test specific) configuration?
- Mark specific symbols, as required for the unit tests, to be visible?
- Avoid using dependent/injected tests?
Jim_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden