Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Xcode <-> CW Discrepancy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode <-> CW Discrepancy

Subject: Re: Xcode <-> CW Discrepancy
From: Sailesh Agrawal <email@hidden>
Date: Wed, 20 Jul 2005 00:22:33 -0700

Tomas Zahradnicky wrote:

Hi,
I've noticed yesterday that one code compiles very differently with Xcode and Codewarrior. That is:
  struct A {
    struct B {
       static vector<B*> sSymbol;
    };
  };
  extern vector<B*> A::B::sSymbol;
Codewarrior generates reference to an undefined symbol (correct) (U type) which resides in a framework while g++ generates static symbol (S type) and link warning that this symbol exists in my binary and the framework. I tried forcing it undefined with -u MANGLED_NAME_FOR_sSymbol but with no luck.

Is this misbehavior a bug?


K this is a complete shot in the dark but:

May be this is due to the fact that XCode projects export all symbols by default. Try turnning that off: http://developer.apple.com/documentation/DeveloperTools/Conceptual/XcodeUserGuide21/Contents/Resources/en.lproj/05_08_bs_linking/chapter_35_section_6.html

good luck!
_______________________________________________
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



References:  
  >Xcode <-> CW Discrepancy (From: Tomas Zahradnicky <email@hidden>)




Prev by Date:
Xcode <-> CW Discrepancy

Next by Date:
Re: XCode 2.1 and Copy Files

Previous by thread:
Xcode <-> CW Discrepancy

Next by thread:
Re: Distributed builds on headless XServe

Index(es):

Date
Thread