• 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 16:33:34 -0500

I have some dependent/injected unit tests. 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
 _______________________________________________
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

  • Prev by Date: Prevent gdb from stays running when executable exits with non-zero result?
  • Next by Date: Re: custom build location
  • Previous by thread: Prevent gdb from stays running when executable exits with non-zero result?
  • Next by thread: How to tell GCC where to find source code?
  • Index(es):
    • Date
    • Thread