• 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
Issues in Locating Headers and Libs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Issues in Locating Headers and Libs


  • Subject: Issues in Locating Headers and Libs
  • From: Andreas Grosam <email@hidden>
  • Date: Tue, 23 Dec 2003 18:13:17 +0100

Hi All,

I wanted to know, if someone else has noticed an issue with locating headers and libraries within its appropriate folders.

When switching the compiler - eg. from GCC 3.3 to GCC 2.95.2 in the Rules panel, I expect that the system libraries like libstdc++.a will be located in the corresponding folder. However, the path to this lib will not be changed accordingly, but the lib remains the same which is ALLWAYS located in /usr/lib/gcc/darwin/3.3.
Furthermore, when changing the target system for instance /Developer/SDKs/MacOSX10.1.5.sdk, this has no effect on the library search path.
The path to this lib is set as an "absolut path" (I wonder, but this is the default) - perhaps a different setting might help here. So, how can I set paths relative to the target SDK chosen?
(In order to test this, I simply added a new Rule for C and C++ sources using the GCC 2.95.2 before the system rule.)


Here, my suggestion would be, just to forget the implicit search paths (option nostdinc) and the popup which lets us choose the cross target, and use the much more elegant feature "source tree". So we can define the system headers and libs relative to a source tree, which might be a folder in /Developer/SDKs/


A similar error occurs regarding search paths for headers (at least with C++ headers), when indexing comes into play. C++ headers like vector, iostream, etc. will be located ALWAYS in <current SDK>/usr/include/gcc/darwin/3.1/g++-v3/ -- regardless of what compiler is used.
The compiler will choose the correct headers, though.


So, I'm left with the situation, that indexer and compiler will not choose the same headers - and the compiler will not choose the library which corresponds to the system headers included. So, I'm not surprised, when an app will crash.

I recently updated to v1.1 - but did not installed the full XCode 1.1 Tools CD.

Thanks for help.


Regards Andreas Grosam _______________________________________________ xcode-users mailing list | email@hidden Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: Xcode 1.1 Tools update
  • Next by Date: Christmas Wish
  • Previous by thread: Re: Putting resources in JAR archives
  • Next by thread: Christmas Wish
  • Index(es):
    • Date
    • Thread