About Developer Tools

 About Mac OS X Developer Tools Compatibility and Installation December 2002 Release for Mac OS X version 10.2 Contents Introduction Compatibility of the Tools with Mac OS X Versions Compatibility of Built Binaries Use of the Developer Tools with WebObjects Developer Installing the Mac OS X Developer Tools Installing the Older ProjectBuilderWO IDE (DevPBWO.pkg) Possible Installation Problems and Workarounds Introduction The Mac OS X Developer Tools includes everything you need to write software for Mac OS X, including the programming tools, system API documentation, and Mac OS X interfaces, libraries and example source code. For the latest information and updates to Mac OS X Developer Tools, documentation, code samples, and technical notes, please visit the Apple Developer Connection’s Mac OS X pages, starting at http://developer.apple.com/macosx. We encourage developers to join the Apple Developer Connection which provides the most convenient access to Mac OS X development resources, including technical support and pre-release software. For information, visit http://www.apple.com/developer. Please read the separate “What’s New” document for information on what has changed since the July 2002 Developer Tools release. Compatibility of the Tools with Mac OS X Versions The December 2002 release of the Developer Tools is intended for use only on systems running the Mac OS X version 10.2 operating system or later, and vice versa. It has been tested on the Mac OS X versions 10.2, 10.2.1, 10.2.2 and 10.2.3, at the time of this writing. For development on Mac OS X v10.1 to v10.1.5, use the April 2002 Mac OS X Developer Tools release. Compatibility of Built Binaries With the December 2002 Developer Tools release, you can build two-level namespace binaries which run on Mac OS X 10.1 and later. Those two-level namespace binaries will also run on systems earlier than Mac OS X 10.1, provided that: - those binaries do not require new APIs which did not exist on earlier systems. Instead, at runtime you can check for the existence of APIs and dynamically load the necessary symbols if you are running on a system where they are available. - those binaries do not reference symbols of the same name from more than one shared library (or your application). While systems earlier than Mac OS X 10.1 can run two-level namespace binaries, those systems cannot properly resolve multiple symbols of the same name. The gcc compiler’s ABI (Application Binary Interface) for C++ programs has been changing as the compiler’s support for the full C++ language has become more complete. As a result of these changes, C++ code that is bound together must be created by the same version of the compiler in order to be guaranteed to work. Consequently, it is a bad idea to create libraries with C++ interfaces that are built (or distributed) independently of the code that uses those libraries. Speci…