Changes between Version 2 and Version 3 of MacBuild


Ignore:
Timestamp:
Apr 27, 2007, 3:34:07 PM (18 years ago)
Author:
charlief
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MacBuild

    v2 v3  
    2222== Important requirements for building BOINC software for the Mac ==
    2323
    24 All BOINC software for Power PC Macs must be built using GCC 3.3 and MacOS10.3.9 SDK to assure backward compatibility with OS 10.3. All BOINC software for Intel Macs must be built using GCC 4.0 and MacOS10.4.u SDK to allow cross-compiling. This includes not only BOINC itself, but also the !WxWidgets, JPEG and cURL libraries, as well as all project applications.
     24All BOINC software for Power PC Macs must be built using GCC 3.3 and MacOS10.3.9 SDK to assure backward compatibility with OS 10.3. All BOINC software for Intel Macs must be built using GCC 4.0 and MacOS10.4.u SDK to allow cross-compiling. '''This includes not only BOINC itself, but also the !WxWidgets, JPEG and cURL libraries, as well as all project applications.'''
    2525
    2626Beware of using the wrong compiler! Apple's release notes for GCC 4.0 say:
    … …  
    6262
    6363[http://prdownloads.sourceforge.net/wxwindows/wxMac-2.8.3.tar.gz]
     64
    6465[http://downloads.sourceforge.net/wxwindows/wxMac-2.8.3.tar.bz2]
    6566
    … …  
    7677[ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz]
    7778
    78 XCode 2.4.1 installs autoconf 2.59 and automake 1.63. To determine the version number, type 'autoconf --version' or 'automake --version'. Building wxMac-2.8.3 and curl-7.16.1 require autoconf 2.59 and automake 1.93 or later.
     79''XCode 2.4.1 installs autoconf 2.59 and automake 1.63. To determine the version number, type 'autoconf --version' or 'automake --version'. Building wxMac-2.8.3 and curl-7.16.1 require autoconf 2.59 and automake 1.93 or later.''
    7980
    8081Upgrades for autoconf and automake are available from www.gnu.org:
    … …  
    8485http://ftp.gnu.org/gnu/automake/automake-1.9.3.tar.gz
    8586
    86 XCode installed these utilities in the /usr/bin/ directory, but the upgrades by default will install in /usr/local/bin/. If you install there, you must also set your PATH environment variable to include that location. The scripts referenced below do this automatically.
     87''XCode installed these utilities in the /usr/bin/ directory, but the upgrades by default will install in /usr/local/bin/. If you install there, you must also set your PATH environment variable to include that location. The scripts referenced below do this automatically.''
    8788
    8889As stated above, all BOINC software for Power PC Macs must be built using GCC 3.3 and MacOS10.3.9 SDK to assure backward compatibility with OS 10.3. All BOINC software for Intel Macs must be built using GCC 4.0 and MacOS10.4.u SDK to allow cross-compiling.
    … …  
    155156Note: You may find three XCode projects in the BOINC_dev/boinc/mac_build/ directory:
    156157
    157     * boinc.pbproj is obsolete and should no longer be used.
    158     * wxMac-BOINC.xcodeproj was needed for building older versions of the wxMac library in conjunction with the older versions of the setupForBoinc.sh or buildWxMac.sh scripts. It is not used for BOINC 5.9.2 or later.
    159     * boinc.xcodeproj builds BOINC. It can be used either with the BuildMacBOINC.sh script or as a stand-alone project. It has two extra build configurations, i386-Deployment and ppc-Deployment, which can be used for testing only to build for just one architecture. The Development build configuration builds only the native architecture and is used for debugging. The Deployment build configuration builds a universal binary and is suitable for release builds.
     158    * '''boinc.pbproj''' is obsolete and should no longer be used.
     159    * '''wxMac-BOINC.xcodeproj''' was needed for building older versions of the wxMac library in conjunction with the older versions of the setupForBoinc.sh or buildWxMac.sh scripts. It is not used for BOINC 5.9.2 or later.
     160    * '''boinc.xcodeproj''' builds BOINC. It can be used either with the BuildMacBOINC.sh script or as a stand-alone project. It has two extra build configurations, i386-Deployment and ppc-Deployment, which can be used for testing only to build for just one architecture. The Development build configuration builds only the native architecture and is used for debugging. The Deployment build configuration builds a universal binary and is suitable for release builds.
    160161
    161162== Building BOINC Manager Installer ==
    … …  
    209210So BOINC treats Intel Macs as a new, separate platform. BOINC previously directly supported four platforms: PowerPC Macs (powerpc-apple-darwin), Intel Linux (i686-pc-linux-gnu), Windows (windows-intelx86) and Solaris (sparc-sun-solaris2.7).
    210211
    211 We have now added a fifth platform for Intel Macs (i686-apple-darwin).
    212 
    213 As a temporary measure, projects can set their servers to deliver a copy of their current PowerPC application (renamed for the new platform) under the new i686-apple-darwin platform. The OS will run it in compatibility mode, emulating a PowerPC. (Apple calls this compatibility mode Rosetta, which of course has nothing to do with the Rosetta BOINC project.)
     212'''We have now added a fifth platform for Intel Macs (i686-apple-darwin).'''
     213
     214As a '''temporary''' measure, projects can set their servers to deliver a copy of their current PowerPC application (renamed for the new platform) under the new i686-apple-darwin platform. The OS will run it in compatibility mode, emulating a PowerPC. (Apple calls this compatibility mode Rosetta, which of course has nothing to do with the Rosetta BOINC project.)
    214215
    215216If you do this, be sure to give your native Intel application a higher version number when you do release it, so that clients will download it.