For executables, if you plan to distribute compiled versions, you should generally create universal binaries for convenience. For example, libraries should generally be compiled as universal binaries even if you are exclusively targeting an Intel-based Macintosh computer, as your library may be used by a PowerPC binary running under Rosetta. Compiling for Multiple CPU Architecturesīecause the Macintosh platform includes more than one processor family, it is often important to compile software for multiple processor architectures. Do not attempt to replace the version installed in /usr/.įor additional information about using the GNU autotoolset, see and the manual pages autoconf, automake, and autoheader. Note that autoconf, by default, installs in /usr/local/, so you may need to modify your PATH environment variable to use the newly updated version. However, if you find it necessary to upgrade autoconf, you can get a current version from. In general, most projects include a prebuilt configure script with releases, so this is usually not necessary unless you are building an open source project using sources obtained from CVS or from a daily source snapshot. Because autoconf changes periodically, you may actually need to get a new version of autoconf if you need to build the very latest sources for some projects. Some programs may use autoconf macros that are not supported by the version of autoconf that shipped with OS X.
After you do that, more extensive refactoring may be required. Beyond these basics, if the project does not build, you may need to modify your makefile using some of the tips provided in the following sections. OS X includes autoconf in the BSD tools package. If that still fails, you may need to run /usr/bin/autoconf on your project to rebuild the configure script before it works. If you are distributing applications that use autoconf, you should include an up-to-date version of config.sub and config.guess so that OS X users don’t have to do anything extra to build your project. If running the configure script fails because it doesn’t understand the architecture, try replacing the project’s config.sub and config.guess files with those available in /usr/share/automake-1.6.
Just run configure and make as you would on any other UNIX-based system. If you are bringing a preexisting command-line utility to OS X that uses GNU autoconf, automake, or autoheader, you will probably find that it configures itself without modification (though the resulting configuration may be insufficient). Using GNU Autoconf, Automake, and Autoheader These issues apply largely without regard to what type of development you are doing. This section covers some of the more common issues that you may encounter in bringing your UNIX application to OS X. Now that you have the basic pieces in place, it is time to build your application. Next Previous Compiling Your Code in OS X
0 kommentar(er)
