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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |