Changes between Version 10 and Version 11 of MacBuild
- Timestamp:
- Aug 2, 2007, 8:35:05 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MacBuild
v10 v11 89 89 1. Create a parent directory within which to work. In this description , we will call it BOINC_dev, but you can name it anything you wish. 90 90 2. Put the following 3 directories inside the BOINC_dev folder (omit any you don't need): 91 92 91 {{{ 93 92 curl-7.16.4 … … 95 94 wxMac-2.8.0 96 95 }}} 97 98 96 Important: do not change the names of any of these 3 directories. 99 97 3. Get the BOINC source tree from SVN, and put it in the same BOINC_dev folder. To do this, type the following in Terminal: 100 101 98 {{{ 102 99 cd {path}/BOINC_dev/ 103 100 svn co http://boinc.berkeley.edu/svn/trunk/boinc 104 101 }}} 105 106 102 (You may change the name of the boinc directory to anything you wish.) 107 103 108 The command above retrieves the source code from the HEAD or development branch of the SVN repository. For more information on getting the BOINC source code, see [SourceCode here].104 The command above retrieves the source code from the HEAD or development branch of the SVN repository. See more information on [SourceCode getting the BOINC source code]. 109 105 4. Run the script to build the curl, jpeg and wxMac libraries as follows: 110 111 106 {{{ 112 107 cd {path}/BOINC_dev/boinc/mac_build/ 113 108 source setupForBoinc.sh -clean 114 109 }}} 115 116 110 If you don't wish to force a full rebuild of everything, omit the -clean argument. 117 111 118 112 Note: this script builds curl first, followed by jpeg and finally wxMac. If you haven't downloaded wxMac because you aren't building the BOINC Manager, the script will build curl and jpeg. Likewise, if you only downloaded curl because you need neither graphics nor the BOINC Manager, the script will build curl before quitting. 119 113 5. Build BOINC as follows: 120 121 114 {{{ 122 115 cd {path}/BOINC_dev/boinc/mac_build/ … … 124 117 }}} 125 118 126 119 The complete syntax for this script is 127 120 128 121 {{{ … … 130 123 }}} 131 124 132 125 The options for BuildMacBOINC.sh are: 133 126 134 127 -dev:: … … 137 130 don't do a 'clean' of each target before building. default is to clean all first. 138 131 139 132 The following arguments determine which targets to build 140 133 141 134 -all:: … … 146 139 build two targets: BOINC client and command-line utility [BoincCmd boinc_cmd] (also builds libboinc.a, since boinc_cmd requires it.) 147 140 148 141 Both -lib and -client may be specified to build five targets (no BOINC Manager.) 149 142 150 143 Note: You may find three XCode projects in the BOINC_dev/boinc/mac_build/ directory: … … 182 175 == Debugging and BOINC security == 183 176 184 Version 5.5.4 of BOINC Manager for the Macintosh introduced new, stricter security measures. For details, please see the file [source:trunk/boinc/mac_installer/Readme.rtf Readme.rtf] and web pages [ http://boinc.berkeley.edu/sandbox.php Sandbox Design] and [SandboxUser Sandbox User].177 Version 5.5.4 of BOINC Manager for the Macintosh introduced new, stricter security measures. For details, please see the file [source:trunk/boinc/mac_installer/Readme.rtf Readme.rtf] and web pages [/sandbox.php Sandbox Design] and [SandboxUser Sandbox User]. 185 178 186 179 The GDB debugger can't attach to applications which are running as a different user or group so it ignores the S_ISUID and S_ISGID permission bits when launching an application. To work around this, BOINC does not use the special boinc_master or boinc_project users or groups when run from XCode. … … 206 199 '''We have now added a fifth platform for Intel Macs (i686-apple-darwin).''' 207 200 208 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.)201 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.) 209 202 210 203 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.