Changes between Version 22 and Version 23 of MacBuild

Timestamp:

Dec 6, 2007, 3:54:55 AM (17 years ago)

Author:

charlief

Comment:

--

MacBuild

@@ -211 +211 @@
 However, participants do not manually download project applications; this is done automatically by BOINC. So there would be no advantage to combining the 32-bit Intel, 64-bit Intel and PowerPC versions in a single 'universal binary' file, but doing so would triple the size of the download.
 
+So BOINC treats Intel Macs as 2 new, separate platforms: `i686-apple-darwin` and `x86_64-apple-darwin`, in addition to the PowerPC Mac platform (`powerpc-apple-darwin`).   
+
 Starting with BOINC 5.9.7, the Intel BOINC Client accepts powerpc-apple-darwin applications if no i686-apple-darwin is available.   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.)  
 
-The x86_64 BOINC Client requests x86_64-apple-darwin applications from BOINC servers as its first choice, i686-apple-darwin as a second choice, and finally powerpc-apple-darwin if no Intel applications are available.
-
-However, older Intel Mac clients will not get any work unless the server offers i686-apple-darwin applications. 
-
-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 i686-apple-darwin platform for older BOINC Clients. 
+The x86_64 BOINC Client requests `x86_64-apple-darwin` applications from BOINC servers as its first choice, `i686-apple-darwin` as a second choice, and finally `powerpc-apple-darwin` if no Intel applications are available.
+
+However, older Intel Mac clients will not get any work unless the server offers i686-apple-darwin applications.  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 i686-apple-darwin platform for older BOINC Clients. 
 
 If 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.
@@ -224 +224 @@
 
     * Screensaver graphics do not work.
-    * Since it is running under emulation, your application will run at reduced efficiency. But the benchmarks are based on running native Intel applications. This may cause scheduler problems, such as uncompleted deadlines and inadequate credit for participants.
+    * Since it is running under emulation, your application will run at reduced efficiency. But the benchmarks are based on running native Intel applications. This may cause scheduler problems, such as missed deadlines and inadequate credit for participants.
 
 So it is important to make a native Intel application available as soon as possible. It is very easy to add a new [BoincPlatforms platform] to your server with the [XaddTool xadd utility].
 
-BOINC supports all PowerPC Macs running OS 10.3.0 or later, and all Intel Macs. (The Intel Macs themselves require OS 10.4.4 or later.)
-
-The easiest way to build your application for these two platforms is to build each one on its native platform. In other words, do your `powerpc-apple-darwin` build on a PowerPC Mac running OS 10.3.9, and your i686-apple-darwin build on an Intel Mac.
+BOINC 6.1 supports all PowerPC Macs running OS 10.3.9 or later, and all Intel Macs, but older versions of BOINC supported OS 10.3.0 or later for PowerPC Macs.  (The Intel Macs themselves require OS 10.4.4 or later.)
+
+The easiest way to build your application for these two platforms is to build each one on its native platform. In other words, do your `powerpc-apple-darwin` build on a PowerPC Mac running OS 10.3.9, and your `i686-apple-darwin` build on an Intel Mac.
 
 But Apple provides the tools to allow you to cross-compile your application on any Mac (PowerPC or Intel) running OS 10.4 or later. Here is how: