Re: Hundred of C++ linker warnings in Xcode 3: odd but not fatal
Re: Hundred of C++ linker warnings in Xcode 3: odd but not fatal
- Subject: Re: Hundred of C++ linker warnings in Xcode 3: odd but not fatal
- From: Shamyl Zakariya <email@hidden>
- Date: Mon, 3 Dec 2007 14:11:59 -0500
I'll have to see how well this works. Fortunately ( thanks for the doc
link! ) I see that since I *do* use an EXPORT macro which forces
default visibility, this ought not break my plugin loading.
I'll keep the old fingers crossed...
email@hidden
"When you must fail, fail noisily and as soon as possible"
- Rule 12: The Rule of Repair
On Dec 3, 2007, at 1:56 PM, Sean McBride wrote:
On 12/3/07 12:59 PM, Shamyl Zakariya said:
I hate to sound like a total fool, but where does the -
fvisibility=default go? I assume it goes in both the static lib
subtarget build settings as well as the main framework, but does it
go
into gcc's parameters or the linker's? I tried putting it in the
linker's params but got error messages.
Xcode has two checkboxes in its GUI for these: "Inline Methods Hidden"
and "Symbols Hidden By Default". See also:
<http://developer.apple.com/documentation/DeveloperTools/Conceptual/
CppRuntimeEnv/Articles/SymbolVisibility.html>
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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