Fr/FlightGear Git sur Mac OS X: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with "{{FlightGearGitOn}} == Important à lire! == Cette page est en grand développement ! Cela prouve que vous pouvez probablement réussir à installer votre version de développ...")
 
No edit summary
Line 7: Line 7:
The build system for FlightGear changed 2011 to cmake. When you want to follow this wiki and get a new clean install you should remove all former installs of plib, PLIB.Framework, OpenSceneGraph, simgear and flightgear. Depending on location where you installed FlightGear GIT version (NOT MacFlightGear!), you have to remove a lot of stuff i.e. in /usr/include, /usr/lib, /usr/local/lib, /usr/local/include etc. (depends where you installed before, but default is /usr/local/...). It is probably better NOT TO DELETE this stuff, keep the content in a safe place, but out of system root.
The build system for FlightGear changed 2011 to cmake. When you want to follow this wiki and get a new clean install you should remove all former installs of plib, PLIB.Framework, OpenSceneGraph, simgear and flightgear. Depending on location where you installed FlightGear GIT version (NOT MacFlightGear!), you have to remove a lot of stuff i.e. in /usr/include, /usr/lib, /usr/local/lib, /usr/local/include etc. (depends where you installed before, but default is /usr/local/...). It is probably better NOT TO DELETE this stuff, keep the content in a safe place, but out of system root.


== Default installing locations ==
== Endroits d'installation par défaut ==
This guide installs the software with default paths on your system (MacPorts in /opt/local/ - other parts in /usr and /usr/local). There is only one framework (to be placed manually) in /Library/Frameworks. '''Use your own configuration options to get your preferred locations!'''. Do not post linking errors in the forum or the lists when you decide to use your own search paths.
This guide installs the software with default paths on your system (MacPorts in /opt/local/ - other parts in /usr and /usr/local). There is only one framework (to be placed manually) in /Library/Frameworks. '''Use your own configuration options to get your preferred locations!'''. Do not post linking errors in the forum or the lists when you decide to use your own search paths.


== Requirements ==
== Systèmes requis ==
System Requirements: OSX 10.5.8 (Leopard) or higher, and an Intel Mac.
System Requirements: OSX 10.5.8 (Leopard) or higher, and an Intel Mac.
Other requirements: Basic knowledge of using Terminal on OSX, Xcode Dev Tools, MacPorts
Other requirements: Basic knowledge of using Terminal on OSX, Xcode Dev Tools, MacPorts
Line 18: Line 18:
'''This action will take more than 2 hours!'''
'''This action will take more than 2 hours!'''


== Install ==
== Installation ==


=== Install Xcode Developer Tools ===
=== Installation des outils Xcode Developer ===
Download and install Xcode Dev Tools for OSX<br />
Download and install Xcode Dev Tools for OSX<br />
for OSX 10.5.8 you need Dev Tools 3.1.4 [http://meandmark.com/blog/2009/10/downloading-older-versions-of-xcode How to get older dev tools versions]<br />  
for OSX 10.5.8 you need Dev Tools 3.1.4 [http://meandmark.com/blog/2009/10/downloading-older-versions-of-xcode How to get older dev tools versions]<br />  
Line 27: Line 27:
Note that apple charges for version 4.0 and later and it is hard to find the links for older versions. However you can still use the required version for flightgear [3.2 or later] for free and you don’t need Dev Tools >= 4 [http://meandmark.com/blog/2009/10/downloading-older-versions-of-xcode How to get older dev tools versions]
Note that apple charges for version 4.0 and later and it is hard to find the links for older versions. However you can still use the required version for flightgear [3.2 or later] for free and you don’t need Dev Tools >= 4 [http://meandmark.com/blog/2009/10/downloading-older-versions-of-xcode How to get older dev tools versions]


=== Install MacPorts ===
=== Installation des ports Mac ===
Download and install [http://www.macports.org/install.php MacPorts]<br />
Download and install [http://www.macports.org/install.php MacPorts]<br />
Note: With already installed MacPorts it could be a good idea to first decactivate all other ports for this wiki. More information: http://guide.macports.org/#installing.macports.upgrade.
Note: With already installed MacPorts it could be a good idea to first decactivate all other ports for this wiki. More information: http://guide.macports.org/#installing.macports.upgrade.


=== Update MacPorts ===
=== Mise à jour des Ports Mac ===
In terminal type
In terminal type
  sudo port selfupdate
  sudo port selfupdate
Line 41: Line 41:
  sudo port upgrade outdated
  sudo port upgrade outdated


=== Download and Install GIT ===
=== Télécharger et installer GIT ===
There are different possibilities to install GIT.  
There are different possibilities to install GIT.  
  Option 1: install via MacPorts in Terminal with "sudo port install git-core"
  Option 1: install via MacPorts in Terminal with "sudo port install git-core"
Line 48: Line 48:
  [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/]
  [http://code.google.com/p/git-osx-installer/ http://code.google.com/p/git-osx-installer/]


=== Install ''boost'' (1.47.0) with MacPorts ===
=== Installer  ''boost'' (1.47.0) avec les Ports Mac ===
  sudo port install boost +universal
  sudo port install boost +universal
Note: this step can take more than 30 minutes! Boost is made for drinking more tea.
Note: this step can take more than 30 minutes! Boost is made for drinking more tea.


=== Install ''cmake'' (2.8.6) with MacPorts ===
=== Installer ''cmake'' (2.8.6) avec les Ports Mac===
  sudo port install cmake +universal
  sudo port install cmake +universal


=== Install '''plib''' (1.8.5) +universal ===
=== Installer '''plib''' (1.8.5) +universal ===
just install plib via MacPorts
just install plib via MacPorts
  sudo port install plib +universal
  sudo port install plib +universal


=== Install the ALUT.framework ===
=== Installer le ALUT.framework ===
Note: This framework is provided by James T. This is not official! James posted this download link in the develist and the link to the framework can change. Linking to the OpenAL/alut.h header and compilation of official freealut fails on my OSX 10.5.8 with FlightGear, and there is also no port avaiable at the moment. Big thanks to James for providing this framework (universal).
Note: Ce cadre is provided by James T. This is not official! James posted this download link in the develist and the link to the framework can change. Linking to the OpenAL/alut.h header and compilation of official freealut fails on my OSX 10.5.8 with FlightGear, and there is also no port avaiable at the moment. Big thanks to James for providing this framework (universal).
Download here '''(temporary location!)''': [http://files.goneabitbursar.com/fg/alut-osx-universal.zip]<br />
Download here '''(temporary location!)''': [http://files.goneabitbursar.com/fg/alut-osx-universal.zip]<br />
Unzip and move the ALUT.framework folder to /Library/Frameworks
Unzip and move the ALUT.framework folder to /Library/Frameworks


=== Download and install OpenSceneGraph trunk ===
=== Téléchargez et installez  le tronc OpenSceneGraph ===


'''Remark 1:''' This is the most complicated part. Be sure you have all deps for OpenSceneGraph installed when you change some cmake settings like cocoa/ioimage (32/64-bit) instead of quicktime/carbon (32-bit only). Maybe you will need ''tiff'', ''jpeg'' and ''libpng'' installed to get some OSG Plug-ins compiled correctly. All this libs are available trough macports i.e. with "sudo port install tiff jpeg libpng" etc. Dont forget to add "+universal" port variant when you want to compile for more than one target ("i386;x86_64").
'''Remark 1:''' This is the most complicated part. Be sure you have all deps for OpenSceneGraph installed when you change some cmake settings like cocoa/ioimage (32/64-bit) instead of quicktime/carbon (32-bit only). Maybe you will need ''tiff'', ''jpeg'' and ''libpng'' installed to get some OSG Plug-ins compiled correctly. All this libs are available trough macports i.e. with "sudo port install tiff jpeg libpng" etc. Dont forget to add "+universal" port variant when you want to compile for more than one target ("i386;x86_64").
Line 106: Line 106:
The fgdata is about 4 GB! You can clone this repo once and later you use ''git pull''. There is other page [[FlightGear and Git]] about using the FlightGear Gitorious GIT Repos. There is also an alternate GIT repo on mapserver.flightgear.org: http://mapserver.flightgear.org/git/.
The fgdata is about 4 GB! You can clone this repo once and later you use ''git pull''. There is other page [[FlightGear and Git]] about using the FlightGear Gitorious GIT Repos. There is also an alternate GIT repo on mapserver.flightgear.org: http://mapserver.flightgear.org/git/.


=== Install SimGear (!new since nov 2011: cmake build) ===
=== Installez SimGear (!nouveau depuis nov 2011: cmake build) ===
cd to the simgear directory and type
cd to the simgear directory and type
   export CFLAGS="-g -O2 -fPIC -arch i386 -arch x86_64"
   export CFLAGS="-g -O2 -fPIC -arch i386 -arch x86_64"
88

edits

Navigation menu