- #Flightgear on mac how to#
- #Flightgear on mac for mac os x#
- #Flightgear on mac install#
Launch FlightGear.app at FlightGearOSX/build/Deployment. This is because Apple's amework contains ALUT implementation so linker complains the duplicated symbols (but no alut.h inside framework). In this case, specify linker to link amework before amework.
Using your own amework (if you build FlightGear without using my Xcode project files) might get linker error. However, specifying SDKROOT=MacOSX10.5.sdk and TARGET_MAC_OSX=10.4 can build a binary for both Tiger and Leopard. #Flightgear on mac for mac os x#
Moreover, gcc 4.2 doesn't contain SDKs for Mac OS X 10.4. In this case, you need to edit SDK's OpenAL/alc.h and alut.h to change both ALCvoid and ALvoid to void if it is the only argument of a prototype declaration.
Using gcc 4.2 on Xcode will give you some compilation errors around ALUT or OpenAL/alc.h. You can also use gcc 4.2 for enabling full optimization. edit build.sh and change GCC_OPTIMIZATION_LEVEL to 0 or 1. Do not use these optimization flags for FlightGear. Using -O2, -O3, or -Os with gcc4.0 (comes with Xcode 3.1/3.1.1) causes FlightGear crash. mtune=core2, -mfpmath=sse) and try again. 
If you get this type of error, clear the optimization flag (e.g. This is caused by either wrong optimization flags for you CPU or a bug in Mac OS kernel (darwin).
Optimization flags may cause Illegal operation exceptions. Specifying this flag makes FlightGear run only on Core 2 Duo Macs and Mac Pros so it's better not distribute it. I haven't trid it so give me your feedback. It enables you to use ssse3 extension + 64bit extension. Core 2 Duo users can use -mtune=core2 instread of prescott. patch -N -p0 "Edit Project Settings" -> "Customized Options" for Deployment (or one of FlightGear, SimGear, or Release) configuration. when asked cvs password, type 'guest' or 'cvsguest' as requested. run download.sh - fetches everything you need. Add the following lines to ~/.bashrc (only for those who installed svn from ):. #Flightgear on mac install#
Download and install subversion (only if you don't have one. I use svn that comes with Leopard (as of June 18, 2009). If you don't have a subversion client, download a binary package from Subversion Project. You can download the latest project files with: Xcode project files and patches (Mac OS X specific). F.Y.I., This page also shows the required files as of June 17th, 2009. Most recent information about required source files are listed here so keep an eye on that page. However, required files can be frequently changed so it's good to know where you can get those. Mac OS X project files contains shell scripts that semi-automatically download all required files so you don't have to find these files. 
Here is the step-by-step instruction of building FlightGear. Please DO NOT ask project members about the use of these tools. If you are not familiar with the tools above, we highly recommend you consult some web articles and/or books about these before you get started.
terminal (/Applications/Utilities/Terminal.app) - must. We assume you have some basic knowledge about using: 
FYI, It takes approximately 45 mins to compile everything on MacBook Pro 2.33GHz. Compiling all the files may also take hours in slower G4 machines.
#Flightgear on mac how to#
This document illustrates how to build OS X Bundle ( FlightGear.app) with cvs-head on Mac OS 10.4.x/10.5.x with Xcode 3.0 or later Requirements System Requirementsįaster machine (G5 or Intel) is recommended as FlightGear-cvs with OSG is heavier than 0.9.9 or 0.9.10.
0 kommentar(er)
