• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Dependent/injected tests vs. linker visibility
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • Prev by Date: Re: Where are the interface builder components?
  • Next by Date: Re: NSFileManager thread safety?
  • Previous by thread: Re: message to zombie NSWindowController
  • Next by thread: How to replace ComboBoxCell with TextFieldCell when not editing
  • Index(es):
    • Date
    • Thread