• 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
Question about symbol visibility link warning
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Question about symbol visibility link warning


  • Subject: Question about symbol visibility link warning
  • From: Brant Sears <email@hidden>
  • Date: Thu, 19 Feb 2009 13:29:50 -0500

I'm seeing the same link warning about symbol visibility many times when my project links to a static library for wxWidgets version 2.8 that was built with XCode.

ld warning: wxDCBase::DrawBitmap(wxBitmap const&, int, int, bool)has different visibility (default) in /Users/brant/src/projects/initial/ src/mac/lib/libwx_mac_static.a(renderg.o) and (hidden) in /Users/brant/ src/projects/initial/src/mac/build/initial.build/Development/ static.build/Objects-normal/i386/BackgroundPanel.o

I do not completely understand this warning. My project is trying to import a symbol as "hidden"? And the static library has it as "default".

I read something on the GCC wiki about this symbol visibility stuff being for the purpose of making applications load dlls faster - and some other benefits.

Can an application load a "hidden" symbol? What exactly does hidden mean?

And how can I fix these warnings properly? I checking the box "Symbols Hidden by Default" in the XCode project to build the wxWidgets static library, recompiled the project, and double checked to make sure I was linking against that version. This did not have an effect on the behavior when compiling my application.

I would appreciate any advice.
_______________________________________________
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


  • Follow-Ups:
    • Re: Question about symbol visibility link warning
      • From: John Mikros <email@hidden>
  • Prev by Date: Debugger internal error
  • Next by Date: Shark not profiling correctly on command-line tool
  • Previous by thread: Debugger internal error
  • Next by thread: Re: Question about symbol visibility link warning
  • Index(es):
    • Date
    • Thread