Difference between revisions of "Compiling the viewer (Mac OS X)"

From Second Life Wiki
Jump to: navigation, search
(Fmod: mention STORM-406 & OPEN-6)
m (Where's the built viewer?: streamlined language a little)
Line 32: Line 32:
 
== Where's the built viewer? ==
 
== Where's the built viewer? ==
  
On OS X, your viewer build will be in  "build-darwin-i386/newview/RelWithDebInfo/Second Life.app" depending on which branch you built.
+
Assuming you build the RelWithDebug branch (the default), the viewer build will be in  <code>build-darwin-i386/newview/RelWithDebInfo/Second Life.app</code> .
  
The easiest way to launch your compiled viewer is to simply navigate under the Finder to that folder and double click the application.
+
One way to launch your newly compiled viewer is to   use the Finder to navigate  to that folder and double click the application.  Another way is to create an alias for it.  Then you can put the alias wherever you find convenient.
  
Note:
+
Note: If you change the build configuration you use, the intermediate directory will also change, e.g. from <code>RelWithDebInfo</code> to <code>Release</code>.  The files for the two configurations will not interfere with one another.
* If you change the build configuration you use, the intermediate directory will also change, e.g. from <code>RelWithDebInfo</code> to <code>Release</code>.
+
  
 
= Building the Unit Tests =
 
= Building the Unit Tests =

Revision as of 09:08, 6 April 2011

For recent information check the Project Snowstorm page.

Getting Development Tools

  • Xcode: Most Lindens use Xcode 3.2 on Snow Leopard (OS X 10.6) for building on Macintosh computers. For simplicity, we suggest installing everything from the mpkg. Note that later versions of Xcode have build options to be backwards compatible to 3.1. (See Talk:Compiling_the_viewer_(Mac_OS_X)#Trying_newer_versions_of_tools. Later versions of Xcode (3.2.4) work fine.)
  • CMake: Install CMake from cmake.org, or using MacPorts with 'port install cmake'. You will need at least CMake 2.6; CMake 2.8 may be required in the future.
  • Command line Makefiles: These are included in Apple's Xcode product. Download and install Xcode from Apple.

Downloading Source Code

Linden Lab Project Snowstorm uses Mercurial and Bit Bucket for the version control repository. The repository is here. Look vor viewer-development, viewer-beta, viewer-release, and others, as your needs dictate. If you're just starting out, it's probably best to get viewer-release or viewer-beta , because viewer-developer gets updated several times per week. But if you would rather work with the latest code, look for the latest builds on Project Snowstorm and viewer-developer on bitbucket.


Installing Proprietary Libraries

Some builds of the the Viewer depends on proprietary libraries (alternative open source libraries are also provided for developers who prefer or are not licensed to use the proprietary libraries). Lindens do not distribute these libraries, so you will need to fetch and install these even if you download the libraries packages. (This is due to licensing restrictions. Don't ask, Lindens already did, and can't get permission. So you do have to get them yourself.)

Fmod

(instructions needed, see STORM-406 and OPEN-6)

Build the viewer with autobuild

Configuring and building with autobuild works the same on all platforms. Full instructions may be found at Build_Viewer_With_Autobuild.

Xcode

If you have followed the configure instructions from Build_Viewer_With_Autobuild, the directory build-darwin-i386 will have been created in the root of your source distribution. Inside that directory you will find the SecondLife.xcodeproj project file which can be used with Xcode. When opened it should be configured correctly to build, so just Build and Run.

Where's the built viewer?

Assuming you build the RelWithDebug branch (the default), the viewer build will be in build-darwin-i386/newview/RelWithDebInfo/Second Life.app .

One way to launch your newly compiled viewer is to use the Finder to navigate to that folder and double click the application. Another way is to create an alias for it. Then you can put the alias wherever you find convenient.

Note: If you change the build configuration you use, the intermediate directory will also change, e.g. from RelWithDebInfo to Release. The files for the two configurations will not interfere with one another.

Building the Unit Tests

From Xcode, open the project 'linden/indra/test/MacTester.xcodeproj', set 'MacTester' as the active target, and build.

What to do if it doesn't work for you

Submitting Patches

This is probably far down the road, but if you make changes to the source and want to submit them, see the page about submitting patches.