Changes between Version 44 and Version 45 of BuildMacApp

Timestamp:

Feb 13, 2013, 10:28:54 AM (11 years ago)

Author:

Christian Beer

Comment:

changed link and instructions for new git repo

BuildMacApp

@@ -32 +32 @@
 '''Note:''' This issue applies mainly to Mac-specific APIs; support for standard UNIX functions rarely changes over different Mac OS versions.  However, the version numbers of some UNIX libraries do change over time, and applications which dynamically link to them may fail to load on older systems if they are built on a newer system.  If this happens, the best solution is to build a static version of the UNIX library yourself and static link it to your application.  Most UNIX libraries are open source, so you can get the source files and build them yourself.  Many are available from http://opensource.apple.com/.
 
-You will also need to build the BOINC libraries on each platform and any other libraries your application needs.  You can use the Makefiles supplied in the BOINC Subversion tree to build the BOINC libraries with this approach, or build them as Universal Binaries using the BOINC XCode project, as described later in this document.
+You will also need to build the BOINC libraries on each platform and any other libraries your application needs.  You can use the Makefiles supplied in the BOINC source repository to build the BOINC libraries with this approach, or build them as Universal Binaries using the BOINC XCode project, as described later in this document.
 
 == Cross-Platform Development ==
@@ -67 +67 @@
 These specify that the executable should be able to run on systems back to OS 10.4 and OS 10.5, respectively.
 
-You can find examples in the following files in the BOINC SVN trunk:[[BR]] `boinc/mac_build/buildc-ares.sh`[[BR]] `boinc/mac_build/buildcurl.sh`[[BR]] `boinc/mac_build/buildopenssl.sh`[[BR]] `boinc/samples/example_app/MakeMacExample.sh`[[BR]] `boinc/samples/example_app/Makefile_mac2`[[BR]] `boinc/samples/example_app/Makefile_mac`[[BR]] `boinc/samples/wrapper/Makefile_mac`[[BR]] `boinc/samples/vboxwrapper/Makefile_mac`[[BR]] `boinc/samples/vboxwrapper/BuildMacVboxWrapper.sh`[[BR]] `boinc/samples/vboxwrapper/Makefile_mac`[[BR]]
+You can find examples in the following files in the [source:boinc BOINC sourcecode]:[[BR]] `boinc/mac_build/buildc-ares.sh`[[BR]] `boinc/mac_build/buildcurl.sh`[[BR]] `boinc/mac_build/buildopenssl.sh`[[BR]] `boinc/samples/example_app/MakeMacExample.sh`[[BR]] `boinc/samples/example_app/Makefile_mac2`[[BR]] `boinc/samples/example_app/Makefile_mac`[[BR]] `boinc/samples/wrapper/Makefile_mac`[[BR]] `boinc/samples/vboxwrapper/Makefile_mac`[[BR]] `boinc/samples/vboxwrapper/BuildMacVboxWrapper.sh`[[BR]] `boinc/samples/vboxwrapper/Makefile_mac`[[BR]]
 
 == Preparing To Build ==
 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.  This parent directory will contain the BOINC source files, your application project, and any other library projects you will use.
 
-Source files are now archived using Subversion. You can download svnX, a free GUI application for running Subversion from either [http://www.apple.com/downloads/macosx/development_tools/svnx.html] or [http://www.lachoseinteractive.net/en/community/subversion/svnx/].
-
-If you installed the developer command line (CLI) tools from Xcode, then a recent version of Subversion is already installed in `/usr/bin/`.  To copy it into `/usr/local/bin/` (where svnX expects to find it), enter the following in the Terminal utility application:
-
-{{{
-cd /usr/bin
-sudo cp -p svn* /usr/local/bin
-}}}
-Get the BOINC source tree from SVN, and put it in the same BOINC_dev folder. To do this, type the following in Terminal:
+Source files are archived in the [SourceCodeGit BOINC repository].
+
+Get the BOINC source from the repository, and put it in the same BOINC_dev folder. To do this, type the following in Terminal:
 
 {{{
 cd {path}/BOINC_dev/
-svn co http://boinc.berkeley.edu/svn/trunk/boinc
-}}}
-(You may change the name of the boinc directory to anything you wish.)  Hint: if you have trouble getting this to work, try using `https` instead of `http`.
-
-The command above retrieves the source code from the HEAD or development branch of the SVN repository. See more information on [wiki:SourceCode getting the BOINC source code].
+git clone git://boinc.berkeley.edu/boinc.git boinc
+}}}
+(You may change the name of the boinc directory to anything you wish.) See more information on [SourceCode getting the BOINC source code].
 
 Build the BOINC libraries as follows: