Different visibility in Release version
Different visibility in Release version
- Subject: Different visibility in Release version
- From: Todd Heberlein <email@hidden>
- Date: Fri, 04 Dec 2009 15:13:46 -0800
I have a static library (consisting of C++ code) and a Cocoa app that links against that library. When compiling the Debug version of the Cocoa app Xcode generates no warning values, but the Release version generates a bunch of warning values (example shown below). It seems to complain that the code in the the library has a different visibility (default) than that in the application objects (hidden).
I've tried linking against the debug and release version of the library, but I seem to continue to get the warning values.
Any ideas?
Is there an easy way (other than using eyeballs) to compare Xcode build settings between the Release and Debug versions to see if I have an inconsistent setting? Thanks,
Todd
ld: warning: bool __gnu_cxx::operator!=<amf::VirtualFullProcessTree::Node*, std::vector<amf::VirtualFullProcessTree::Node, std::allocator<amf::VirtualFullProcessTree::Node> > >(__gnu_cxx::__normal_iterator<amf::VirtualFullProcessTree::Node*, std::vector<amf::VirtualFullProcessTree::Node, std::allocator<amf::VirtualFullProcessTree::Node> > > const&, __gnu_cxx::__normal_iterator<amf::VirtualFullProcessTree::Node*, std::vector<amf::VirtualFullProcessTree::Node, std::allocator<amf::VirtualFullProcessTree::Node> > > const&)has different visibility (default) in /Users/heberlei/Development/amf/build/Debug/libAMF.a(AmfVirtualFullProcessTree.o) and (hidden) in /Users/heberlei/Development/ProcessSecurityMonitor/build/ProcessSecurityMonitor.build/Release/ProcEx.build/Objects-normal/x86_64/BrowserViewController.o
|
_______________________________________________
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