• 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
Re: decyphering ld's cryptic error messages
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: decyphering ld's cryptic error messages


  • Subject: Re: decyphering ld's cryptic error messages
  • From: Dave Thorup <email@hidden>
  • Date: Tue, 9 Aug 2005 13:45:27 -0400

On Aug 9, 2005, at 2:41 AM, Stefan Werner wrote:

It turned out that in my case, the project to build the wxWidgest library and the project using it weren't using the exact same preprocessor defines. If you're using the Xcode project that comes with wxWidgets, the target build settings have an item called "PREPROCESSOR MACROS" that is set to something like "NO_GCC_PRAGMA __WXMAC__ wxUSE_BASE=1 _FILE_OFFSET_BITS=64 _LARGE_FILES __WXMAC_XCODE__=1 WX_PRECOMP=1 MACOS_CLASSIC", depending on what target you build. Copy that to your main project as it is, that's what made it work for me. It seems like just having setup.h correct is not sufficient.

Why this would break only linking of a few symbols but not cause any problems in the compiling stage, I have no clue. Unfortunately, wxWidgets is defining lists and a few other basics using cascades of macros which make it hard to determine what is really going on. I was studying preprocesses code for a while, but that's very time- consuming (especially when using Xcode's editor).

Thanks, this worked for me too. I'm actually using the Unix shell scripts to build wxWidgets (the Xcode project wasn't updated very often when I started using wxWidgets). To get the preprocessor macros that you need when using the Unix build process all you need to do is run this in your build folder (after you've run configure):


wx-config --cxxflags

This outputs the header search paths that you need as well as the macros that need to be defined. Like you I don't know why this didn't cause a compile problem and only showed up as a link error. I'm just happy to get it working.

Thanks!
_____________________________

Dave Thorup
Software Engineer
email@hidden

http://www.kuwan.net
Defaults Manager - The premier editor for Mac OS X's User Defaults / Preferences database.



_______________________________________________ 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: 
 >decyphering ld's cryptic error messages (From: Stefan Werner <email@hidden>)
 >Re: decyphering ld's cryptic error messages (From: Dave Thorup <email@hidden>)
 >Re: decyphering ld's cryptic error messages (From: Stefan Werner <email@hidden>)

  • Prev by Date: TEST ONLY-NO NEED TO READ (not getting any xcode mail so testing if i send that i receive)
  • Next by Date: Re: DOS path separators - more info
  • Previous by thread: Re: decyphering ld's cryptic error messages
  • Next by thread: Re: decyphering ld's cryptic error messages
  • Index(es):
    • Date
    • Thread