https://wiki.flightgear.org/w/api.php?action=feedcontributions&user=Daemonburrito&feedformat=atomFlightGear wiki - User contributions [en]2024-03-28T09:46:27ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=User_talk:Johan_G&diff=70951User talk:Johan G2014-05-10T23:04:43Z<p>Daemonburrito: /* Updated compile guide */</p>
<hr />
<div>== Swedish ==<br />
Hi Johan,<br />
<br />
thanks for starting translating articles to Swedish! Unfortunately, the wiki admin has to "add" this language to the system (therefore adding [[sv:Article]] does not work as of now). I've immediately asked him to do so, but it might take a while. In the meantime you can continue translating articles, it's just the linking that doesn't work.<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] 08:36, 3 July 2011 (EDT)<br />
<br />
:Ah, that explains why the language link doesn't seem to work. Thank you! I sent him a mail as well. Well, at least I can continue (in a slow pace). [[User:Johan G|Johan G]] 08:43, 3 July 2011 (EDT)<br />
<br />
== Don't be a stranger. ==<br />
Jag hoppas att du kommer tillbaka snart. {{Unsigned2|11:45, 11 October 2011|PH-JBO}}<br />
<br />
:Thank you for hoping for my return. Den som väntar på något gott... ''In other words, I'm back.'' [[User:Johan G|Johan G]] 09:59, 5 December 2011 (EST)<br />
::Du är inte ensam. Välkommen tillbaka! [[User:PH-JBO|PH-JBO]] 07:28, 6 December 2011 (EST)<br />
<br />
== Test ==<br />
A short thest to see if a new section added with the "+" tab is appended to the bottom of the page. [[User:Johan G|Johan G]] 07:32, 9 February 2012 (EST)<br />
<br />
== Discussing new main page/portals ==<br />
Hi,<br />
<br />
would be nice if you could come on [[IRC]] this week. I'd like to discuss the new main page/portals that I've been working on ;)<br />
You'll find me in [irc://#wiki@irc.flightgear.org #wiki@irc.flightgear.org]<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] 12:27, 19 March 2012 (EDT)<br />
<br />
: Hi, I should be in #wiki now as Johan_G. This will bee interesting. I have not used IRC before, and last time I watched it over someones shoulder was in <s>1999</s> 1998!<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:52, 19 March 2012 (EDT)<br />
<br />
== Infobox aircraft changes ==<br />
I thought, I'd better get in touch with the only wikimedia template guru that I know :-) I just added a handful of meta categories (inspired by [http://forum.flightgear.org/viewtopic.php?f=25&t=21431#p195109]), and now want to extend the infobox accordingly, including images for each supported features, see: http://wiki.flightgear.org/Template_talk:Infobox_aircraft Any ideas/preference how to implement this best? Images will probably be contributed by Michat. Thanks --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 18:33, 30 November 2013 (UTC)<br />
<br />
:It is low on my to-do list, but see my answer at [[Template talk:Infobox aircraft]].<br />
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:08, 1 December 2013 (UTC)<br />
<br />
== Yes/no template ==<br />
<br />
Hi Johan,<br />
<br />
the yes/no template doesn't seem to work well on [[Photoscenery]], everything says "yes" now. Another issue is that the 1m/pixel text is no longer centered, as if it only applies to "texture materials", while it's supposed to cover "3D model" as well. And to be honest, I prefer the more pronounced colours that we had before... I'm all in for a yes/no template though, don't get me wrong ;-)<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:43, 2 March 2014 (UTC)<br />
<br />
: Oops. I was updating the templates to be able to handle adding xhtml attributes and one the edits accidentally had "Yes instead of "No". Should already work as expected by now.<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:51, 2 March 2014 (UTC)<br />
<br />
: Made the colours quite a bit stronger, but black text should still be readable in the cells.<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:20, 2 March 2014 (UTC)<br />
<br />
== Thanks for appreciating ==<br />
Hi, thanks for appreciating [[Howto:Convert objects with ModelConverterX]]. I recently posted a howto on [http://forum.flightgear.org/viewtopic.php?f=5&t=22851 georeferencing OSM in WED], let me know if that could be added somewhere in the wiki, I'd be glad to, but I'm not sure if it's useful outside of Italy.--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 22:38, 26 April 2014 (UTC)<br />
<br />
:You are very welcome. :-)<br />
:About the howto, it could probably fit really well as an article on the wiki. My only concern there is using Google to check the taxiways. I am not sure or not that it is relevant, but Google's terms of use do not allow derivative works. Licenses can be a problem sometimes, and I am completely ignorant when it comes to Italian legislation on intellectual property, but I assume that most sources are copyrighted more or less automatically, but that there might be a few sources with less restrictive licenses.<br />
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:30, 27 April 2014 (UTC)<br />
:: I see. Well, in Italy (see elgaton's answer) we're allowed to trace over some nice aerial images in OSM, but that's all, so we have to go through OSM and its limitations (i.e. no Bezier). I can substitute that part with just a warning to check by other means what angles should be rounded, or suggest to make rounded corners stand out in OSM with more points. However blurry is the border with Google, I guess it could be considered as "getting the coordinates"* of rounded corners (*I've read it's considered ok here).<br />
::It jumps to my mind that Bing has allowed use of its aerial images for OSM tracing - worldwide. They have a good detail but are not very precise, yet that's something a mapper can fix. I guess this changes the usefulness of the howto :D Let me know if there's a particular page/category where I can put this. --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:43, 28 April 2014 (UTC)<br />
:::The juridical stuff can be a problematic at times. ;-)<br />
:::A fitting category would be [[:Category:Scenery enhancement]] I think.<br />
:::(On a side note that category page have turned into an article over time, which looks messy and wont turn up in a regular wiki search using the search box.)<br />
:::—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:03, 28 April 2014 (UTC)<br />
<br />
== A FlightGear help category ==<br />
<br />
Today [[Unexpected Crashes with Scenery ver.2]] was added to [[:Category:Help]]. There's lack indeed of a FlightGear help category (into FlightGear of course). That sounds like a good name (place), but I won't add it until I know your opinion.<br />
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:49, 10 May 2014 (UTC)<br />
<br />
: Ah, thanks for asking. There is indeed lack of a FlightGear help category, but I'll get to that. The help category seem to only have contained pages in the help namespace, i.e. articles with help about using the wiki (i think that category page even states that).<br />
<br />
: As for the FlightGear help pages, I have actually never really figured out if there originally was some kind of thought through structure there or if the whole thing was a bit haphazard turned into ad hoc. I.e. I have never really grasped how to use them in an intuitive way (for both me, other editors and the readers). There is a lot of categories that slightly overlap or are slightly vague, which does not help when trying to find articles or even categories. I think a lot of that mess should be discussed on the [[FlightGear wiki:Village pump|village pump]].<br />
<br />
: In addition there are lots of annoying little technicalities, like that the search box auto-complete function is case sensitive and that some editors are very much into Camel Case Titles, something for example Wikipedia is recommending their editors to avoid. Speaking of that, the wiki could need a style guide, but that would take some extra maintenance to enforce.<br />
<br />
: To be honest have been secretly wishing that you might be into trying to figure out a better structure and better category names, specially for the FlightGear related stuff. I have thought about it and figured that I would wish it would be better... but doesn't feel up to it. I spent most of my categorisation efforts on templates and images, unless pages was uncategorised.<br />
<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:30, 10 May 2014 (UTC)<br />
<br />
== Updated compile guide ==<br />
<br />
[[User:Daemonburrito/Building FlightGear - Linux]]<br />
<br />
Hello, Johan. As promised, a completely reworked compile guide. It makes a nice, clean, and safe environment. And it ''works''!<br />
<br />
But it is a pretty big change to drop in there, so I'm leaving it on my user page for comments for a bit. Let me know what you think. [[User:Daemonburrito|Daemonburrito]] ([[User talk:Daemonburrito|talk]]) 17:06, 10 May 2014 (UTC)<br />
<br />
: I am not really the right person to review it, except for copy editing (i.e. style/wiki markup) if that would be needed. In this case I think it might be better to mention it on the forum. I have very little experience with Linux, and on top of that it was quite some time ago (Red hat Linux, kernel 2.2 etc. on a ''way'' to weak box).<br />
<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:40, 10 May 2014 (UTC)<br />
<br />
:: Will do. Thanks! [[User:Daemonburrito|Daemonburrito]] ([[User talk:Daemonburrito|talk]]) 23:04, 10 May 2014 (UTC)</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User_talk:Johan_G&diff=70931User talk:Johan G2014-05-10T17:08:12Z<p>Daemonburrito: /* Updated compile guide */ forgot link</p>
<hr />
<div>== Swedish ==<br />
Hi Johan,<br />
<br />
thanks for starting translating articles to Swedish! Unfortunately, the wiki admin has to "add" this language to the system (therefore adding [[sv:Article]] does not work as of now). I've immediately asked him to do so, but it might take a while. In the meantime you can continue translating articles, it's just the linking that doesn't work.<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] 08:36, 3 July 2011 (EDT)<br />
<br />
:Ah, that explains why the language link doesn't seem to work. Thank you! I sent him a mail as well. Well, at least I can continue (in a slow pace). [[User:Johan G|Johan G]] 08:43, 3 July 2011 (EDT)<br />
<br />
== Don't be a stranger. ==<br />
Jag hoppas att du kommer tillbaka snart. {{Unsigned2|11:45, 11 October 2011|PH-JBO}}<br />
<br />
:Thank you for hoping for my return. Den som väntar på något gott... ''In other words, I'm back.'' [[User:Johan G|Johan G]] 09:59, 5 December 2011 (EST)<br />
::Du är inte ensam. Välkommen tillbaka! [[User:PH-JBO|PH-JBO]] 07:28, 6 December 2011 (EST)<br />
<br />
== Test ==<br />
A short thest to see if a new section added with the "+" tab is appended to the bottom of the page. [[User:Johan G|Johan G]] 07:32, 9 February 2012 (EST)<br />
<br />
== Discussing new main page/portals ==<br />
Hi,<br />
<br />
would be nice if you could come on [[IRC]] this week. I'd like to discuss the new main page/portals that I've been working on ;)<br />
You'll find me in [irc://#wiki@irc.flightgear.org #wiki@irc.flightgear.org]<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] 12:27, 19 March 2012 (EDT)<br />
<br />
: Hi, I should be in #wiki now as Johan_G. This will bee interesting. I have not used IRC before, and last time I watched it over someones shoulder was in <s>1999</s> 1998!<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:52, 19 March 2012 (EDT)<br />
<br />
== Infobox aircraft changes ==<br />
I thought, I'd better get in touch with the only wikimedia template guru that I know :-) I just added a handful of meta categories (inspired by [http://forum.flightgear.org/viewtopic.php?f=25&t=21431#p195109]), and now want to extend the infobox accordingly, including images for each supported features, see: http://wiki.flightgear.org/Template_talk:Infobox_aircraft Any ideas/preference how to implement this best? Images will probably be contributed by Michat. Thanks --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 18:33, 30 November 2013 (UTC)<br />
<br />
:It is low on my to-do list, but see my answer at [[Template talk:Infobox aircraft]].<br />
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:08, 1 December 2013 (UTC)<br />
<br />
== Yes/no template ==<br />
<br />
Hi Johan,<br />
<br />
the yes/no template doesn't seem to work well on [[Photoscenery]], everything says "yes" now. Another issue is that the 1m/pixel text is no longer centered, as if it only applies to "texture materials", while it's supposed to cover "3D model" as well. And to be honest, I prefer the more pronounced colours that we had before... I'm all in for a yes/no template though, don't get me wrong ;-)<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:43, 2 March 2014 (UTC)<br />
<br />
: Oops. I was updating the templates to be able to handle adding xhtml attributes and one the edits accidentally had "Yes instead of "No". Should already work as expected by now.<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:51, 2 March 2014 (UTC)<br />
<br />
: Made the colours quite a bit stronger, but black text should still be readable in the cells.<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:20, 2 March 2014 (UTC)<br />
<br />
== Thanks for appreciating ==<br />
Hi, thanks for appreciating [[Howto:Convert objects with ModelConverterX]]. I recently posted a howto on [http://forum.flightgear.org/viewtopic.php?f=5&t=22851 georeferencing OSM in WED], let me know if that could be added somewhere in the wiki, I'd be glad to, but I'm not sure if it's useful outside of Italy.--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 22:38, 26 April 2014 (UTC)<br />
<br />
:You are very welcome. :-)<br />
:About the howto, it could probably fit really well as an article on the wiki. My only concern there is using Google to check the taxiways. I am not sure or not that it is relevant, but Google's terms of use do not allow derivative works. Licenses can be a problem sometimes, and I am completely ignorant when it comes to Italian legislation on intellectual property, but I assume that most sources are copyrighted more or less automatically, but that there might be a few sources with less restrictive licenses.<br />
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:30, 27 April 2014 (UTC)<br />
:: I see. Well, in Italy (see elgaton's answer) we're allowed to trace over some nice aerial images in OSM, but that's all, so we have to go through OSM and its limitations (i.e. no Bezier). I can substitute that part with just a warning to check by other means what angles should be rounded, or suggest to make rounded corners stand out in OSM with more points. However blurry is the border with Google, I guess it could be considered as "getting the coordinates"* of rounded corners (*I've read it's considered ok here).<br />
::It jumps to my mind that Bing has allowed use of its aerial images for OSM tracing - worldwide. They have a good detail but are not very precise, yet that's something a mapper can fix. I guess this changes the usefulness of the howto :D Let me know if there's a particular page/category where I can put this. --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:43, 28 April 2014 (UTC)<br />
:::The juridical stuff can be a problematic at times. ;-)<br />
:::A fitting category would be [[:Category:Scenery enhancement]] I think.<br />
:::(On a side note that category page have turned into an article over time, which looks messy and wont turn up in a regular wiki search using the search box.)<br />
:::—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:03, 28 April 2014 (UTC)<br />
<br />
== A FlightGear help category ==<br />
<br />
Today [[Unexpected Crashes with Scenery ver.2]] was added to [[:Category:Help]]. There's lack indeed of a FlightGear help category (into FlightGear of course). That sounds like a good name (place), but I won't add it until I know your opinion.<br />
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:49, 10 May 2014 (UTC)<br />
<br />
== Updated compile guide ==<br />
<br />
http://wiki.flightgear.org/User:Daemonburrito/Building_FlightGear_-_Linux<br />
<br />
Hello, Johan. As promised, a completely reworked compile guide. It makes a nice, clean, and safe environment. And it ''works''!<br />
<br />
But it is a pretty big change to drop in there, so I'm leaving it on my user page for comments for a bit. Let me know what you think. [[User:Daemonburrito|Daemonburrito]] ([[User talk:Daemonburrito|talk]]) 17:06, 10 May 2014 (UTC)</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User_talk:Johan_G&diff=70930User talk:Johan G2014-05-10T17:06:35Z<p>Daemonburrito: Updated compile guide</p>
<hr />
<div>== Swedish ==<br />
Hi Johan,<br />
<br />
thanks for starting translating articles to Swedish! Unfortunately, the wiki admin has to "add" this language to the system (therefore adding [[sv:Article]] does not work as of now). I've immediately asked him to do so, but it might take a while. In the meantime you can continue translating articles, it's just the linking that doesn't work.<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] 08:36, 3 July 2011 (EDT)<br />
<br />
:Ah, that explains why the language link doesn't seem to work. Thank you! I sent him a mail as well. Well, at least I can continue (in a slow pace). [[User:Johan G|Johan G]] 08:43, 3 July 2011 (EDT)<br />
<br />
== Don't be a stranger. ==<br />
Jag hoppas att du kommer tillbaka snart. {{Unsigned2|11:45, 11 October 2011|PH-JBO}}<br />
<br />
:Thank you for hoping for my return. Den som väntar på något gott... ''In other words, I'm back.'' [[User:Johan G|Johan G]] 09:59, 5 December 2011 (EST)<br />
::Du är inte ensam. Välkommen tillbaka! [[User:PH-JBO|PH-JBO]] 07:28, 6 December 2011 (EST)<br />
<br />
== Test ==<br />
A short thest to see if a new section added with the "+" tab is appended to the bottom of the page. [[User:Johan G|Johan G]] 07:32, 9 February 2012 (EST)<br />
<br />
== Discussing new main page/portals ==<br />
Hi,<br />
<br />
would be nice if you could come on [[IRC]] this week. I'd like to discuss the new main page/portals that I've been working on ;)<br />
You'll find me in [irc://#wiki@irc.flightgear.org #wiki@irc.flightgear.org]<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] 12:27, 19 March 2012 (EDT)<br />
<br />
: Hi, I should be in #wiki now as Johan_G. This will bee interesting. I have not used IRC before, and last time I watched it over someones shoulder was in <s>1999</s> 1998!<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:52, 19 March 2012 (EDT)<br />
<br />
== Infobox aircraft changes ==<br />
I thought, I'd better get in touch with the only wikimedia template guru that I know :-) I just added a handful of meta categories (inspired by [http://forum.flightgear.org/viewtopic.php?f=25&t=21431#p195109]), and now want to extend the infobox accordingly, including images for each supported features, see: http://wiki.flightgear.org/Template_talk:Infobox_aircraft Any ideas/preference how to implement this best? Images will probably be contributed by Michat. Thanks --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 18:33, 30 November 2013 (UTC)<br />
<br />
:It is low on my to-do list, but see my answer at [[Template talk:Infobox aircraft]].<br />
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:08, 1 December 2013 (UTC)<br />
<br />
== Yes/no template ==<br />
<br />
Hi Johan,<br />
<br />
the yes/no template doesn't seem to work well on [[Photoscenery]], everything says "yes" now. Another issue is that the 1m/pixel text is no longer centered, as if it only applies to "texture materials", while it's supposed to cover "3D model" as well. And to be honest, I prefer the more pronounced colours that we had before... I'm all in for a yes/no template though, don't get me wrong ;-)<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:43, 2 March 2014 (UTC)<br />
<br />
: Oops. I was updating the templates to be able to handle adding xhtml attributes and one the edits accidentally had "Yes instead of "No". Should already work as expected by now.<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:51, 2 March 2014 (UTC)<br />
<br />
: Made the colours quite a bit stronger, but black text should still be readable in the cells.<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:20, 2 March 2014 (UTC)<br />
<br />
== Thanks for appreciating ==<br />
Hi, thanks for appreciating [[Howto:Convert objects with ModelConverterX]]. I recently posted a howto on [http://forum.flightgear.org/viewtopic.php?f=5&t=22851 georeferencing OSM in WED], let me know if that could be added somewhere in the wiki, I'd be glad to, but I'm not sure if it's useful outside of Italy.--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 22:38, 26 April 2014 (UTC)<br />
<br />
:You are very welcome. :-)<br />
:About the howto, it could probably fit really well as an article on the wiki. My only concern there is using Google to check the taxiways. I am not sure or not that it is relevant, but Google's terms of use do not allow derivative works. Licenses can be a problem sometimes, and I am completely ignorant when it comes to Italian legislation on intellectual property, but I assume that most sources are copyrighted more or less automatically, but that there might be a few sources with less restrictive licenses.<br />
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:30, 27 April 2014 (UTC)<br />
:: I see. Well, in Italy (see elgaton's answer) we're allowed to trace over some nice aerial images in OSM, but that's all, so we have to go through OSM and its limitations (i.e. no Bezier). I can substitute that part with just a warning to check by other means what angles should be rounded, or suggest to make rounded corners stand out in OSM with more points. However blurry is the border with Google, I guess it could be considered as "getting the coordinates"* of rounded corners (*I've read it's considered ok here).<br />
::It jumps to my mind that Bing has allowed use of its aerial images for OSM tracing - worldwide. They have a good detail but are not very precise, yet that's something a mapper can fix. I guess this changes the usefulness of the howto :D Let me know if there's a particular page/category where I can put this. --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:43, 28 April 2014 (UTC)<br />
:::The juridical stuff can be a problematic at times. ;-)<br />
:::A fitting category would be [[:Category:Scenery enhancement]] I think.<br />
:::(On a side note that category page have turned into an article over time, which looks messy and wont turn up in a regular wiki search using the search box.)<br />
:::—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:03, 28 April 2014 (UTC)<br />
<br />
== A FlightGear help category ==<br />
<br />
Today [[Unexpected Crashes with Scenery ver.2]] was added to [[:Category:Help]]. There's lack indeed of a FlightGear help category (into FlightGear of course). That sounds like a good name (place), but I won't add it until I know your opinion.<br />
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:49, 10 May 2014 (UTC)<br />
<br />
== Updated compile guide ==<br />
Hello, Johan. As promised, a completely reworked compile guide. It makes a nice, clean, and safe environment. And it ''works''!<br />
<br />
But it is a pretty big change to drop in there, so I'm leaving it on my user page for comments for a bit. Let me know what you think. [[User:Daemonburrito|Daemonburrito]] ([[User talk:Daemonburrito|talk]]) 17:06, 10 May 2014 (UTC)</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito/Building_FlightGear_-_Linux&diff=70929User:Daemonburrito/Building FlightGear - Linux2014-05-10T17:00:23Z<p>Daemonburrito: /* Compiling */ Flightgear and fgdata updated; symlink fgdata instead of mv</p>
<hr />
<div>== Compiling ==<br />
<br />
If you're compiling Flightgear, you are likely to attempt building the latest revision. It is unlikely that a Linux distro will have a version of OpenSceneGraph recent enough for the latest Flightgear. To make the process of building dependencies like OpenSceneGraph from source easier, these instructions will assume that you will be installing to a custom "prefix"; a tree separate from root (/usr/lib).<br />
<br />
This is advisable for the following reasons:<br />
<br />
* Builds can fail in mysterious ways if leftovers from older versions remain (common cause of build failures). You can safely delete your tree, without needing root.<br />
* If you're developing Flightgear, you are likely to need several variants available (e.g., "HEAD", Debug/Release).<br />
<br />
These instructions will use a Bash variable called "<tt>$PREFIX</tt>". You can assign this variable at the beginning to use the commands verbatim, or you can substitute your path by hand.<br />
<br />
=== Example: Setting <code>$PREFIX</code> ===<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export PREFIX="/home/me/projects/fg"<br />
</syntaxhighlight><br />
<br />
You can even use your "project" directory as the prefix. To do this cleanly, make a <tt>src/</tt> directory under the project directory. Download the git repositories into this directory. If you follow the rest of the instructions with <code>$PREFIX=$HOME/projects/flightgear</code>, you will end up with a tree like this (osg* include directories omitted for brevity):<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects $ tree -L 2 -d flightgear<br />
flightgear<br />
├── bin<br />
├── include<br />
│ ├── OpenThreads<br />
│ ├── osg<br />
│ └── simgear<br />
├── lib<br />
│ ├── FlightGear -> ../src/fgdata<br />
│ └── x86_64-linux-gnu<br />
├── lib64<br />
│ ├── osgPlugins-3.2.0<br />
│ └── pkgconfig<br />
├── share<br />
│ ├── flightgear -> ../src/fgdata<br />
│ └── man<br />
└── src<br />
├── build.flightgear<br />
├── build.osg<br />
├── build.simgear<br />
├── fgdata<br />
├── flightgear<br />
├── OpenSceneGraph<br />
└── simgear<br />
</syntaxhighlight><br />
<br />
=== CMake ===<br />
<br />
Flightgear, Simgear, and OpenSceneGraph now use <tt>cmake</tt>. See the [http://www.cmake.org/Wiki/CMake_Useful_Variables CMake wiki] for additional documentation.<br />
<br />
CMake allows users to create "out-of-source" builds, which means build files are created in a separate directory, and many variants can be maintained. To use out-of-source builds, simply create a new directory and pass the path to source to <code>cmake</code>.<br />
<br />
==== Example: "out-of-source" build with CMake ====<br />
<br />
<syntaxhighlight lang="bash"><br />
simgear $ mkdir ../build.simgear<br />
simgear $ cd ../build.simgear<br />
build.simgear $ cmake ../simgear<br />
</syntaxhighlight><br />
<br />
==== <tt>ccmake</tt> ====<br />
<br />
CMake build configuration files (<tt>CMakeCache.txt</tt>) are designed to be edited and generated. A GUI has been baked in since the beginning of the CMake project, which allows editing of configuration settings (like <tt>configure</tt> parameters).<br />
<br />
For Ubuntu, the package <tt>cmake-curses-gui</tt> needs to be install to use the <tt>ccmake</tt> GUI.<br />
<br />
==== Installation with CMake ====<br />
<br />
After CMake has run, you can <code>make && make install</code>.<br />
<br />
=== OpenSceneGraph ===<br />
<br />
Full article: [[OpenSceneGraph]]<br />
<br />
Using the <tt>build.*</tt> convention is advised.<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ svn checkout http://svn.openscenegraph.org/osg/OpenSceneGraph/tags/OpenSceneGraph-3.2.0 OpenSceneGraph<br />
~/projects/flightgear/src $ mkdir build.osg<br />
~/projects/flightgear/src $ cd build.osg<br />
~/projects/flightgear/src/build.osg $ cmake ../OpenSceneGraph -DCMAKE_INSTALL_PATH=$PREFIX<br />
~/projects/flightgear/src/build.osg $ make && make install<br />
</syntaxhighlight><br />
<br />
You can change build settings by editing <tt>build.osg/CMakeCache.txt</tt> or by running <tt>ccmake</tt>.<br />
<br />
=== SimGear ===<br />
<br />
SimGear is hosted on Gitorious: https://gitorious.org/fg/simgear<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ mkdir build.simgear<br />
~/projects/flightgear/src $ cd build.simgear<br />
~/projects/flightgear/src/build.simgear $ cmake ../simgear -DCMAKE_INSTALL_PATH=$PREFIX -DCMAKE_PREFIX_PATH=$PREFIX<br />
</syntaxhighlight><br />
<br />
You can change build settings by editing <tt>build.osg/CMakeCache.txt</tt> or by running <tt>ccmake</tt>.<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src/build.simgear $ make && make install<br />
</syntaxhighlight><br />
<br />
''Note:'' With <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: "<code>'<anonymous>' has incomplete type</code>". Take a look at http://bugs.gentoo.org/166723.<br />
<br />
=== FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ mkdir build.flightgear<br />
~/projects/flightgear/src $ cd build.flightgear<br />
~/projects/flightgear/src/build.flightgear $ cmake ../flightgear -DCMAKE_INSTALL_PATH=$PREFIX -DCMAKE_PREFIX_PATH=$PREFIX<br />
</syntaxhighlight><br />
<br />
You can change build settings by editing <tt>build.osg/CMakeCache.txt</tt> or by running <tt>ccmake</tt>.<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src/build.flightgear $ make && make install<br />
</syntaxhighlight><br />
<br />
=== <tt>fgdata</tt> ===<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
Symlink it to the expected location. Currently, it's <code>$PREFIX/lib</code>. Previously, it has been <code>$PREFIX/share</code>.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd $PREFIX/lib<br />
$ ln -s ../src/fgdata FlightGear<br />
</syntaxhighlight></div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito/Building_FlightGear_-_Linux&diff=70928User:Daemonburrito/Building FlightGear - Linux2014-05-10T16:46:47Z<p>Daemonburrito: /* Compiling */ SimGear cmake update, out-of-source build.</p>
<hr />
<div>== Compiling ==<br />
<br />
If you're compiling Flightgear, you are likely to attempt building the latest revision. It is unlikely that a Linux distro will have a version of OpenSceneGraph recent enough for the latest Flightgear. To make the process of building dependencies like OpenSceneGraph from source easier, these instructions will assume that you will be installing to a custom "prefix"; a tree separate from root (/usr/lib).<br />
<br />
This is advisable for the following reasons:<br />
<br />
* Builds can fail in mysterious ways if leftovers from older versions remain (common cause of build failures). You can safely delete your tree, without needing root.<br />
* If you're developing Flightgear, you are likely to need several variants available (e.g., "HEAD", Debug/Release).<br />
<br />
These instructions will use a Bash variable called "<tt>$PREFIX</tt>". You can assign this variable at the beginning to use the commands verbatim, or you can substitute your path by hand.<br />
<br />
=== Example: Setting <code>$PREFIX</code> ===<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export PREFIX="/home/me/projects/fg"<br />
</syntaxhighlight><br />
<br />
You can even use your "project" directory as the prefix. To do this cleanly, make a <tt>src/</tt> directory under the project directory. Download the git repositories into this directory. If you follow the rest of the instructions with <code>$PREFIX=$HOME/projects/flightgear</code>, you will end up with a tree like this (osg* include directories omitted for brevity):<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects $ tree -L 2 -d flightgear<br />
flightgear<br />
├── bin<br />
├── include<br />
│ ├── OpenThreads<br />
│ ├── osg<br />
│ └── simgear<br />
├── lib<br />
│ ├── FlightGear -> ../src/fgdata<br />
│ └── x86_64-linux-gnu<br />
├── lib64<br />
│ ├── osgPlugins-3.2.0<br />
│ └── pkgconfig<br />
├── share<br />
│ ├── flightgear -> ../src/fgdata<br />
│ └── man<br />
└── src<br />
├── build.flightgear<br />
├── build.osg<br />
├── build.simgear<br />
├── fgdata<br />
├── flightgear<br />
├── OpenSceneGraph<br />
└── simgear<br />
</syntaxhighlight><br />
<br />
=== CMake ===<br />
<br />
Flightgear, Simgear, and OpenSceneGraph now use <tt>cmake</tt>. See the [http://www.cmake.org/Wiki/CMake_Useful_Variables CMake wiki] for additional documentation.<br />
<br />
CMake allows users to create "out-of-source" builds, which means build files are created in a separate directory, and many variants can be maintained. To use out-of-source builds, simply create a new directory and pass the path to source to <code>cmake</code>.<br />
<br />
==== Example: "out-of-source" build with CMake ====<br />
<br />
<syntaxhighlight lang="bash"><br />
simgear $ mkdir ../build.simgear<br />
simgear $ cd ../build.simgear<br />
build.simgear $ cmake ../simgear<br />
</syntaxhighlight><br />
<br />
==== <tt>ccmake</tt> ====<br />
<br />
CMake build configuration files (<tt>CMakeCache.txt</tt>) are designed to be edited and generated. A GUI has been baked in since the beginning of the CMake project, which allows editing of configuration settings (like <tt>configure</tt> parameters).<br />
<br />
For Ubuntu, the package <tt>cmake-curses-gui</tt> needs to be install to use the <tt>ccmake</tt> GUI.<br />
<br />
==== Installation with CMake ====<br />
<br />
After CMake has run, you can <code>make && make install</code>.<br />
<br />
=== OpenSceneGraph ===<br />
<br />
Full article: [[OpenSceneGraph]]<br />
<br />
Using the <tt>build.*</tt> convention is advised.<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ svn checkout http://svn.openscenegraph.org/osg/OpenSceneGraph/tags/OpenSceneGraph-3.2.0 OpenSceneGraph<br />
~/projects/flightgear/src $ mkdir build.osg<br />
~/projects/flightgear/src $ cd build.osg<br />
~/projects/flightgear/src/build.osg $ cmake ../OpenSceneGraph -DCMAKE_INSTALL_PATH=$PREFIX<br />
~/projects/flightgear/src/build.osg $ make && make install<br />
</syntaxhighlight><br />
<br />
You can change build settings by editing <tt>build.osg/CMakeCache.txt</tt> or by running <tt>ccmake</tt>.<br />
<br />
=== SimGear ===<br />
<br />
SimGear is hosted on Gitorious: https://gitorious.org/fg/simgear<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ mkdir build.simgear<br />
~/projects/flightgear/src $ cd build.simgear<br />
~/projects/flightgear/src/build.simgear $ cmake ../simgear -DCMAKE_INSTALL_PATH=$PREFIX -DCMAKE_PREFIX_PATH=$PREFIX<br />
</syntaxhighlight><br />
<br />
You can change build settings by editing <tt>build.osg/CMakeCache.txt</tt> or by running <tt>ccmake</tt>.<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src/build.simgear $ make && make install<br />
</syntaxhighlight><br />
<br />
''Note:'' With <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: "<code>'<anonymous>' has incomplete type</code>". Take a look at http://bugs.gentoo.org/166723.<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight></div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito/Building_FlightGear_-_Linux&diff=70927User:Daemonburrito/Building FlightGear - Linux2014-05-10T16:29:14Z<p>Daemonburrito: /* Compiling */ OpenSceneGraph example</p>
<hr />
<div>== Compiling ==<br />
<br />
If you're compiling Flightgear, you are likely to attempt building the latest revision. It is unlikely that a Linux distro will have a version of OpenSceneGraph recent enough for the latest Flightgear. To make the process of building dependencies like OpenSceneGraph from source easier, these instructions will assume that you will be installing to a custom "prefix"; a tree separate from root (/usr/lib).<br />
<br />
This is advisable for the following reasons:<br />
<br />
* Builds can fail in mysterious ways if leftovers from older versions remain (common cause of build failures). You can safely delete your tree, without needing root.<br />
* If you're developing Flightgear, you are likely to need several variants available (e.g., "HEAD", Debug/Release).<br />
<br />
These instructions will use a Bash variable called "<tt>$PREFIX</tt>". You can assign this variable at the beginning to use the commands verbatim, or you can substitute your path by hand.<br />
<br />
=== Example: Setting <code>$PREFIX</code> ===<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export PREFIX="/home/me/projects/fg"<br />
</syntaxhighlight><br />
<br />
You can even use your "project" directory as the prefix. To do this cleanly, make a <tt>src/</tt> directory under the project directory. Download the git repositories into this directory. If you follow the rest of the instructions with <code>$PREFIX=$HOME/projects/flightgear</code>, you will end up with a tree like this (osg* include directories omitted for brevity):<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects $ tree -L 2 -d flightgear<br />
flightgear<br />
├── bin<br />
├── include<br />
│ ├── OpenThreads<br />
│ ├── osg<br />
│ └── simgear<br />
├── lib<br />
│ ├── FlightGear -> ../src/fgdata<br />
│ └── x86_64-linux-gnu<br />
├── lib64<br />
│ ├── osgPlugins-3.2.0<br />
│ └── pkgconfig<br />
├── share<br />
│ ├── flightgear -> ../src/fgdata<br />
│ └── man<br />
└── src<br />
├── build.flightgear<br />
├── build.osg<br />
├── build.simgear<br />
├── fgdata<br />
├── flightgear<br />
├── OpenSceneGraph<br />
└── simgear<br />
</syntaxhighlight><br />
<br />
=== CMake ===<br />
<br />
Flightgear, Simgear, and OpenSceneGraph now use <tt>cmake</tt>. See the [http://www.cmake.org/Wiki/CMake_Useful_Variables CMake wiki] for additional documentation.<br />
<br />
CMake allows users to create "out-of-source" builds, which means build files are created in a separate directory, and many variants can be maintained. To use out-of-source builds, simply create a new directory and pass the path to source to <code>cmake</code>.<br />
<br />
==== Example: "out-of-source" build with CMake ====<br />
<br />
<syntaxhighlight lang="bash"><br />
simgear $ mkdir ../build.simgear<br />
simgear $ cd ../build.simgear<br />
build.simgear $ cmake ../simgear<br />
</syntaxhighlight><br />
<br />
==== <tt>ccmake</tt> ====<br />
<br />
CMake build configuration files (<tt>CMakeCache.txt</tt>) are designed to be edited and generated. A GUI has been baked in since the beginning of the CMake project, which allows editing of configuration settings (like <tt>configure</tt> parameters).<br />
<br />
For Ubuntu, the package <tt>cmake-curses-gui</tt> needs to be install to use the <tt>ccmake</tt> GUI.<br />
<br />
==== Installation with CMake ====<br />
<br />
After CMake has run, you can <code>make && make install</code>.<br />
<br />
=== OpenSceneGraph ===<br />
<br />
Full article: [[OpenSceneGraph]]<br />
<br />
Using the <tt>build.*</tt> convention is advised.<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects/flightgear/src $ svn checkout http://svn.openscenegraph.org/osg/OpenSceneGraph/tags/OpenSceneGraph-3.2.0 OpenSceneGraph<br />
~/projects/flightgear/src $ mkdir build.osg<br />
~/projects/flightgear/src $ cd build.osg<br />
~/projects/flightgear/src/build.osg $ cmake ../OpenSceneGraph -DCMAKE_INSTALL_PATH=$PREFIX<br />
~/projects/flightgear/src/build.osg $ make && make install<br />
</syntaxhighlight><br />
<br />
You can change build settings by editing <tt>build.osg/CMakeCache.txt</tt> or by running <tt>ccmake</tt>.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install <tt>simgear</tt> globally on the system but in a specific directory, you can do so by adding <code>-DCMAKE_INSTALL_PREFIX==/path/to/your/fgInstallation</code> to the <code>cmake</code> command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight></div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito/Building_FlightGear_-_Linux&diff=70925User:Daemonburrito/Building FlightGear - Linux2014-05-10T16:15:30Z<p>Daemonburrito: /* Compiling */ Sample directory structure</p>
<hr />
<div>== Compiling ==<br />
<br />
If you're compiling Flightgear, you are likely to attempt building the latest revision. It is unlikely that a Linux distro will have a version of OpenSceneGraph recent enough for the latest Flightgear. To make the process of building dependencies like OpenSceneGraph from source easier, these instructions will assume that you will be installing to a custom "prefix"; a tree separate from root (/usr/lib).<br />
<br />
This is advisable for the following reasons:<br />
<br />
* Builds can fail in mysterious ways if leftovers from older versions remain (common cause of build failures). You can safely delete your tree, without needing root.<br />
* If you're developing Flightgear, you are likely to need several variants available (e.g., "HEAD", Debug/Release).<br />
<br />
These instructions will use a Bash variable called "<tt>$PREFIX</tt>". You can assign this variable at the beginning to use the commands verbatim, or you can substitute your path by hand.<br />
<br />
=== Example: Setting <code>$PREFIX</code> ===<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export PREFIX="/home/me/projects/fg"<br />
</syntaxhighlight><br />
<br />
You can even use your "project" directory as the prefix. To do this cleanly, make a <tt>src/</tt> directory under the project directory. Download the git repositories into this directory. If you follow the rest of the instructions with <code>$PREFIX=$HOME/projects/flightgear</code>, you will end up with a tree like this (osg* include directories omitted for brevity):<br />
<br />
<syntaxhighlight lang="bash"><br />
~/projects $ tree -L 2 -d flightgear<br />
flightgear<br />
├── bin<br />
├── include<br />
│ ├── OpenThreads<br />
│ ├── osg<br />
│ └── simgear<br />
├── lib<br />
│ ├── FlightGear -> ../src/fgdata<br />
│ └── x86_64-linux-gnu<br />
├── lib64<br />
│ ├── osgPlugins-3.2.0<br />
│ └── pkgconfig<br />
├── share<br />
│ ├── flightgear -> ../src/fgdata<br />
│ └── man<br />
└── src<br />
├── build.flightgear<br />
├── build.osg<br />
├── build.simgear<br />
├── fgdata<br />
├── flightgear<br />
├── OpenSceneGraph<br />
└── simgear<br />
</syntaxhighlight><br />
<br />
=== CMake ===<br />
<br />
Flightgear, Simgear, and OpenSceneGraph now use <tt>cmake</tt>. See the [http://www.cmake.org/Wiki/CMake_Useful_Variables CMake wiki] for additional documentation.<br />
<br />
CMake allows users to create "out-of-source" builds, which means build files are created in a separate directory, and many variants can be maintained. To use out-of-source builds, simply create a new directory and pass the path to source to <code>cmake</code>.<br />
<br />
==== Example: "out-of-source" build with CMake ====<br />
<br />
<syntaxhighlight lang="bash"><br />
simgear $ mkdir ../build.simgear<br />
simgear $ cd ../build.simgear<br />
build.simgear $ cmake ../simgear<br />
</syntaxhighlight><br />
<br />
==== <tt>ccmake</tt> ====<br />
<br />
CMake build configuration files (<tt>CMakeCache.txt</tt>) are designed to be edited and generated. A GUI has been baked in since the beginning of the CMake project, which allows editing of configuration settings (like <tt>configure</tt> parameters).<br />
<br />
For Ubuntu, the package <tt>cmake-curses-gui</tt> needs to be install to use the <tt>ccmake</tt> GUI.<br />
<br />
==== Installation with CMake ====<br />
<br />
After CMake has run, you can <code>make && make install</code>.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install <tt>simgear</tt> globally on the system but in a specific directory, you can do so by adding <code>-DCMAKE_INSTALL_PREFIX==/path/to/your/fgInstallation</code> to the <code>cmake</code> command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight></div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito/Building_FlightGear_-_Linux&diff=70924User:Daemonburrito/Building FlightGear - Linux2014-05-10T16:08:20Z<p>Daemonburrito: /* Compiling */ $PREFIX</p>
<hr />
<div>== Compiling ==<br />
<br />
If you're compiling Flightgear, you are likely to attempt building the latest revision. It is unlikely that a Linux distro will have a version of OpenSceneGraph recent enough for the latest Flightgear. To make the process of building dependencies like OpenSceneGraph from source easier, these instructions will assume that you will be installing to a custom "prefix"; a tree separate from root (/usr/lib).<br />
<br />
This is advisable for the following reasons:<br />
<br />
* Builds can fail in mysterious ways if leftovers from older versions remain (common cause of build failures). You can safely delete your tree, without needing root.<br />
* If you're developing Flightgear, you are likely to need several variants available (e.g., "HEAD", Debug/Release).<br />
<br />
These instructions will use a Bash variable called "<tt>$PREFIX</tt>". You can assign this variable at the beginning to use the commands verbatim, or you can substitute your path by hand.<br />
<br />
=== Example: Setting <code>$PREFIX</code> ===<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export PREFIX="/home/me/projects/fg"<br />
</syntaxhighlight><br />
<br />
You can even use your "project" directory as the prefix. To do this cleanly, make a <tt>src/</tt> directory under the project directory. Download the git repositories into this directory. You will end up with a tree like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
<br />
</syntaxhighlight><br />
<br />
=== CMake ===<br />
<br />
Flightgear, Simgear, and OpenSceneGraph now use <tt>cmake</tt>. See the [http://www.cmake.org/Wiki/CMake_Useful_Variables CMake wiki] for additional documentation.<br />
<br />
CMake allows users to create "out-of-source" builds, which means build files are created in a separate directory, and many variants can be maintained. To use out-of-source builds, simply create a new directory and pass the path to source to <code>cmake</code>.<br />
<br />
==== Example: "out-of-source" build with CMake ====<br />
<br />
<syntaxhighlight lang="bash"><br />
simgear $ mkdir ../build.simgear<br />
simgear $ cd ../build.simgear<br />
build.simgear $ cmake ../simgear<br />
</syntaxhighlight><br />
<br />
==== <tt>ccmake</tt> ====<br />
<br />
CMake build configuration files (<tt>CMakeCache.txt</tt>) are designed to be edited and generated. A GUI has been baked in since the beginning of the CMake project, which allows editing of configuration settings (like <tt>configure</tt> parameters).<br />
<br />
For Ubuntu, the package <tt>cmake-curses-gui</tt> needs to be install to use the <tt>ccmake</tt> GUI.<br />
<br />
==== Installation with CMake ====<br />
<br />
After CMake has run, you can <code>make && make install</code>.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install <tt>simgear</tt> globally on the system but in a specific directory, you can do so by adding <code>-DCMAKE_INSTALL_PREFIX==/path/to/your/fgInstallation</code> to the <code>cmake</code> command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight></div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito/Building_FlightGear_-_Linux&diff=70922User:Daemonburrito/Building FlightGear - Linux2014-05-10T15:37:24Z<p>Daemonburrito: /* Compiling */ More CMake background</p>
<hr />
<div>== Compiling ==<br />
<br />
=== CMake ===<br />
<br />
Flightgear, Simgear, and OpenSceneGraph now use <tt>cmake</tt>. See the [http://www.cmake.org/Wiki/CMake_Useful_Variables CMake wiki] for additional documentation.<br />
<br />
CMake allows users to create "out-of-source" builds, which means build files are created in a separate directory, and many variants can be maintained. To use out-of-source builds, simply create a new directory and pass the path to source to <code>cmake</code>.<br />
<br />
==== Example "out-of-source" build with CMake ====<br />
<br />
<syntaxhighlight lang="bash"><br />
simgear $ mkdir ../build.simgear<br />
simgear $ cd ../build.simgear<br />
build.simgear $ cmake ../simgear<br />
</syntaxhighlight><br />
<br />
==== <tt>ccmake</tt> ====<br />
<br />
CMake build configuration files (<tt>CMakeCache.txt</tt>) are designed to be edited and generated. A GUI has been baked in since the beginning of the CMake project, which allows editing of configuration settings (like <tt>configure</tt> parameters).<br />
<br />
For Ubuntu, the package <tt>cmake-curses-gui</tt> needs to be install to use the <tt>ccmake</tt> GUI.<br />
<br />
==== Installation with CMake ====<br />
<br />
After CMake has run, you can <code>make && make install</code>.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install <tt>simgear</tt> globally on the system but in a specific directory, you can do so by adding <code>-DCMAKE_INSTALL_PREFIX==/path/to/your/fgInstallation</code> to the <code>cmake</code> command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight></div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito/Building_FlightGear_-_Linux&diff=70884User:Daemonburrito/Building FlightGear - Linux2014-05-10T05:48:53Z<p>Daemonburrito: /* Compiling */ Out-of-source explanation and link to cmake wiki.</p>
<hr />
<div>== Compiling ==<br />
<br />
Flightgear, Simgear, and OpenSceneGraph now use <tt>cmake</tt>. See the [http://www.cmake.org/Wiki/CMake_Useful_Variables CMake wiki] for additional documentation.<br />
<br />
CMake allows users to create "out-of-source" builds, which means build files are created in a separate directory, and many variants can be maintained. To use out-of-source builds, simply create a new directory and pass the path to source to <code>cmake</code>.<br />
<br />
=== Example "out-of-source" build with CMake ===<br />
<br />
<syntaxhighlight lang="bash"><br />
simgear $ mkdir ../build.simgear<br />
simgear $ cd ../build.simgear<br />
build.simgear $ cmake ../simgear<br />
</syntaxhighlight><br />
<br />
After CMake has run, you can <code>make && make install</code>.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install <tt>simgear</tt> globally on the system but in a specific directory, you can do so by adding <code>-DCMAKE_INSTALL_PREFIX==/path/to/your/fgInstallation</code> to the <code>cmake</code> command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight></div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito/Building_FlightGear_-_Linux&diff=70634User:Daemonburrito/Building FlightGear - Linux2014-05-06T20:10:21Z<p>Daemonburrito: /* Compiling */</p>
<hr />
<div>== Compiling ==<br />
<br />
When tracking a fast changing software like FlightGear/Git it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.<br />
<br />
To install in a directory of your choice, add the <code>CMAKE_INSTALL_PREFIX</code> argument to <code>cmake</code>. E.g., <code>-DCMAKE_INSTALL_PREFIX==/path/to/your/fgInstallation</code>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install <tt>simgear</tt> globally on the system but in a specific directory, you can do so by adding <code>-DCMAKE_INSTALL_PREFIX==/path/to/your/fgInstallation</code> to the <code>cmake</code> command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight></div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User_talk:Daemonburrito&diff=70568User talk:Daemonburrito2014-05-05T15:44:17Z<p>Daemonburrito: /* Bash syntax highlighting */</p>
<hr />
<div>== Bash syntax highlighting ==<br />
<br />
[http://wiki.flightgear.org/index.php?title=Building_FlightGear_-_Linux&diff=next&oldid=70534 Good spotting]! I actually do not think that anyone else have thought of that before.<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:07, 5 May 2014 (UTC)<br />
<br />
: Thanks! It's been a couple of years since I hacked on Flightgear, and I wanted to get the ball rolling on something simple. I enjoy writing documentation, anyway.<br />
: I've got a bigger rewrite coming of the page, and I've got a [http://wiki.flightgear.org/User:Daemonburrito/Building_FlightGear_-_Linux preview] off of my user page. I plan to get rid of the "as root" stuff, update commmands for <tt>cmake</tt>, and end up with a typical dev setup (I hope my setup is pretty typical). Let me know if you have any thoughts. [[User:Daemonburrito|Daemonburrito]] ([[User talk:Daemonburrito|talk]]) 15:35, 5 May 2014 (UTC)</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User_talk:Daemonburrito&diff=70567User talk:Daemonburrito2014-05-05T15:35:36Z<p>Daemonburrito: /* Bash syntax highlighting */</p>
<hr />
<div>== Bash syntax highlighting ==<br />
<br />
[http://wiki.flightgear.org/index.php?title=Building_FlightGear_-_Linux&diff=next&oldid=70534 Good spotting]! I actually do not think that anyone else have thought of that before.<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:07, 5 May 2014 (UTC)<br />
<br />
: Thanks! It's been a couple of years since I hacked on Flightgear, and I wanted to get the ball rolling on something simple. I enjoy writing documentation, anyway.<br />
: I've got a bigger rewrite coming of the page, and I've got a [http://wiki.flightgear.org/User:Daemonburrito/Building_FlightGear_-_Linux preview] off of my user page. I plan to get rid of the "as root" stuff, and end up with a typical dev setup (I hope my setup is pretty typical). Let me know if you have any thoughts. [[User:Daemonburrito|Daemonburrito]] ([[User talk:Daemonburrito|talk]]) 15:35, 5 May 2014 (UTC)</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito/Building_FlightGear_-_Linux&diff=70543User:Daemonburrito/Building FlightGear - Linux2014-05-04T23:29:05Z<p>Daemonburrito: Created page with "== Compiling == Assuming you are root, do: <syntaxhighlight lang="bash"> # cd /usr/local/src </syntaxhighlight> '''Note:''' When tracking a fast changing software like Fligh..."</p>
<hr />
<div>== Compiling ==<br />
Assuming you are root, do:<br />
<br />
<syntaxhighlight lang="bash"><br />
# cd /usr/local/src<br />
</syntaxhighlight><br />
<br />
'''Note:''' When tracking a fast changing software like FlightGear/Git it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.<br />
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install <tt>simgear</tt> globally on the system but in a specific directory, you can do so by adding <code>-DCMAKE_INSTALL_PREFIX==/path/to/your/fgInstallation</code> to the <code>cmake</code> command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight></div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito&diff=70542User:Daemonburrito2014-05-04T23:17:16Z<p>Daemonburrito: </p>
<hr />
<div>== Proposed changes ==<br />
* [[User:Daemonburrito/Building_FlightGear_-_Linux]]</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=User:Daemonburrito&diff=70541User:Daemonburrito2014-05-04T23:16:01Z<p>Daemonburrito: Created page with "# Proposed changes * User:Daemonburrito/Building_FlightGear_-_Linux"</p>
<hr />
<div># Proposed changes<br />
* [[User:Daemonburrito/Building_FlightGear_-_Linux]]</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=Building_FlightGear_-_Linux&diff=70540Building FlightGear - Linux2014-05-04T22:15:43Z<p>Daemonburrito: /* Getting and compiling SimGear */ Using cmake args for instsall prefix.</p>
<hr />
<div>{{Main article|Building Flightgear}} <br />
<br />
This section describes how to build [[FlightGear]] on Linux system.<br />
<br />
Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.<br />
<br />
openSUSE also provides binary packages of the latest development version, which are continuously updated.<br />
Follow [http://software.opensuse.org/download.html?lang=en&project=games:FlightGear:Unstable&package=fgrun this link] to select your openSUSE version and install, or manually add ''games:FlightGear:Unstable'' to your ''YaST Software Repositories''.<br />
<br />
Or if you develop on Ubuntu or Debian, consider trying the script described in [[Scripted Compilation on Linux Debian/Ubuntu]].<br />
<br />
== Distro-specific instructions ==<br />
=== Debian/Ubuntu ===<br />
* You can use the [[Scripted Compilation on Linux Debian/Ubuntu]] script to have Flightgear compiled in one shot under both Ubuntu and Debian systems.<br />
* Debian users who prefer to build it without script may look at [[Building Flightgear - Debian]].<br />
* Hints for [[Ubuntu]] users.<br />
<br />
=== Gentoo ===<br />
* Gentoo users can also use overlays to build FlightGear without much hassle: [[Building Flightgear - Gentoo]].<br />
<br />
== Requirements ==<br />
Before you can compile FlightGear, you need to have the following installed on your computer:<br />
<br />
'''C++ compiler'''<br />
<br />
These are: c++, cpp, gcc, g++ found under the <code>/usr/bin</code> directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.<br />
<br />
'''GIT'''<br />
<br />
See [[FlightGear and Git]].<br />
<br />
'''[[OpenGL]] support'''<br />
<br />
More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running the following in a [[command line]]:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ glxinfo | grep direct<br />
</syntaxhighlight><br />
<br />
Note: To run the above command, you need to have the tool '''mesa-utils''' installed.<br />
<br />
You should then see:<br />
<br />
direct rendering: Yes<br />
<br />
This means you are good to go as far as OpenGL support is concerned.<br />
<br />
If you see:<br />
<br />
direct rendering: No<br />
<br />
Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing '''plib 1.8.5''' and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.<br />
<br />
== Dependencies ==<br />
<br />
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package <tt>plib1.8.5</tt> is <tt>plib1.8.5</tt>'''-dev'''.<br />
<br />
The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.<br />
<br />
* <tt>FlightGear</tt><br />
** [http://kcat.strangesoft.net/openal.html <tt>OpenAL</tt>]<br />
** <tt>SimGear</tt><br />
*** [http://plib.sourceforge.net/ <tt>PLIB</tt>]. Since March 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.<br />
**** For versions pre March 2008: (Free)<tt>GLUT</tt> or <tt>SDL</tt> (We recommend the use of <tt>SDL</tt> over <tt>Free/GLUT</tt>, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since March 2008, <tt>FreeGLUT</tt> as well as <tt>SDL</tt> are both considered deprecated], please only use <code>--enable-osgviewer</code> during configuration instead) <br />
*** <tt>[[OpenSceneGraph]]</tt> (check link for compatible versions)<br />
*** You also need the development files for several basic libraries to build the software, among them the following (the package names are for Debian and derivatives(?)):<br />
**** <tt>libfreetype6-dev</tt><br />
**** <tt>libjpeg62-dev</tt><br />
**** <tt>libungif4-dev</tt><br />
**** <tt>libtiff4-dev</tt><br />
**** <tt>libpng12-dev</tt><br />
**** <tt>libxmu-dev</tt><br />
**** <tt>libxi-dev</tt><br />
**** <tt>zlib1g-dev</tt><br />
**** <tt>libglut3-dev</tt><br />
<br />
If you attack the above dependencies in the order listed below, you should be good:<br />
<br />
# <tt>glut</tt> Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the <tt>glut</tt> and <tt>glut-devel</tt> packages, otherwise FlightGear may be able to compile but won't run correctly.<br />
# <tt>zlib</tt> Most distributions install the basic <tt>zlib</tt> libraries by default, but not the development portions. If you don't have <tt>zlib.h</tt>, you probably need to install the <tt>zlib-devel</tt> package for your distribution. <br />
# <tt>plib</tt> Portability libraries and scene graph. <br />
# <tt>[[OpenSceneGraph]]</tt> <br />
# <tt>simgear</tt> Simulation support libraries. If you are building FlightGear from Git, you need the Git version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.<br />
<br />
== Compiling ==<br />
Assuming you are root, do:<br />
<br />
<syntaxhighlight lang="bash"><br />
# cd /usr/local/src<br />
</syntaxhighlight><br />
<br />
'''Note:''' When tracking a fast changing software like FlightGear/Git it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.<br />
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install <tt>simgear</tt> globally on the system but in a specific directory, you can do so by adding <code>-DCMAKE_INSTALL_PREFIX==/path/to/your/fgInstallation</code> to the <code>cmake</code> command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight><br />
<br />
== External links ==<br />
=== Instructions ===<br />
* [[MSYS]] <br />
* [[MinGW/cross-compiler]] <br />
* [[CodeBlocks IDE]] <br />
* [[OpenSUSE 10.1 10.2]] <br />
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]<br />
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]<br />
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X]<br />
== Important note for GIT users ==<br />
As of latest development in GIT, only cmake is now required for building both SimGear and FlightGear. So if you build GIT (for what any reason) please don't try to use autogen.sh as it is removed from repository.<br />
<br />
For detailed instructions, see page [[Building_using_CMake|Building using cmake]].<br />
<br />
{{Building}}<br />
<br />
[[fr:Compiler FlightGear sous GNU/Linux]]</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=Building_FlightGear_-_Linux&diff=70539Building FlightGear - Linux2014-05-04T20:44:38Z<p>Daemonburrito: /* Getting and compiling SimGear */</p>
<hr />
<div>{{Main article|Building Flightgear}} <br />
<br />
This section describes how to build [[FlightGear]] on Linux system.<br />
<br />
Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.<br />
<br />
openSUSE also provides binary packages of the latest development version, which are continuously updated.<br />
Follow [http://software.opensuse.org/download.html?lang=en&project=games:FlightGear:Unstable&package=fgrun this link] to select your openSUSE version and install, or manually add ''games:FlightGear:Unstable'' to your ''YaST Software Repositories''.<br />
<br />
Or if you develop on Ubuntu or Debian, consider trying the script described in [[Scripted Compilation on Linux Debian/Ubuntu]].<br />
<br />
== Distro-specific instructions ==<br />
=== Debian/Ubuntu ===<br />
* You can use the [[Scripted Compilation on Linux Debian/Ubuntu]] script to have Flightgear compiled in one shot under both Ubuntu and Debian systems.<br />
* Debian users who prefer to build it without script may look at [[Building Flightgear - Debian]].<br />
* Hints for [[Ubuntu]] users.<br />
<br />
=== Gentoo ===<br />
* Gentoo users can also use overlays to build FlightGear without much hassle: [[Building Flightgear - Gentoo]].<br />
<br />
== Requirements ==<br />
Before you can compile FlightGear, you need to have the following installed on your computer:<br />
<br />
'''C++ compiler'''<br />
<br />
These are: c++, cpp, gcc, g++ found under the <code>/usr/bin</code> directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.<br />
<br />
'''GIT'''<br />
<br />
See [[FlightGear and Git]].<br />
<br />
'''[[OpenGL]] support'''<br />
<br />
More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running the following in a [[command line]]:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ glxinfo | grep direct<br />
</syntaxhighlight><br />
<br />
Note: To run the above command, you need to have the tool '''mesa-utils''' installed.<br />
<br />
You should then see:<br />
<br />
direct rendering: Yes<br />
<br />
This means you are good to go as far as OpenGL support is concerned.<br />
<br />
If you see:<br />
<br />
direct rendering: No<br />
<br />
Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing '''plib 1.8.5''' and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.<br />
<br />
== Dependencies ==<br />
<br />
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package <tt>plib1.8.5</tt> is <tt>plib1.8.5</tt>'''-dev'''.<br />
<br />
The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.<br />
<br />
* <tt>FlightGear</tt><br />
** [http://kcat.strangesoft.net/openal.html <tt>OpenAL</tt>]<br />
** <tt>SimGear</tt><br />
*** [http://plib.sourceforge.net/ <tt>PLIB</tt>]. Since March 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.<br />
**** For versions pre March 2008: (Free)<tt>GLUT</tt> or <tt>SDL</tt> (We recommend the use of <tt>SDL</tt> over <tt>Free/GLUT</tt>, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since March 2008, <tt>FreeGLUT</tt> as well as <tt>SDL</tt> are both considered deprecated], please only use <code>--enable-osgviewer</code> during configuration instead) <br />
*** <tt>[[OpenSceneGraph]]</tt> (check link for compatible versions)<br />
*** You also need the development files for several basic libraries to build the software, among them the following (the package names are for Debian and derivatives(?)):<br />
**** <tt>libfreetype6-dev</tt><br />
**** <tt>libjpeg62-dev</tt><br />
**** <tt>libungif4-dev</tt><br />
**** <tt>libtiff4-dev</tt><br />
**** <tt>libpng12-dev</tt><br />
**** <tt>libxmu-dev</tt><br />
**** <tt>libxi-dev</tt><br />
**** <tt>zlib1g-dev</tt><br />
**** <tt>libglut3-dev</tt><br />
<br />
If you attack the above dependencies in the order listed below, you should be good:<br />
<br />
# <tt>glut</tt> Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the <tt>glut</tt> and <tt>glut-devel</tt> packages, otherwise FlightGear may be able to compile but won't run correctly.<br />
# <tt>zlib</tt> Most distributions install the basic <tt>zlib</tt> libraries by default, but not the development portions. If you don't have <tt>zlib.h</tt>, you probably need to install the <tt>zlib-devel</tt> package for your distribution. <br />
# <tt>plib</tt> Portability libraries and scene graph. <br />
# <tt>[[OpenSceneGraph]]</tt> <br />
# <tt>simgear</tt> Simulation support libraries. If you are building FlightGear from Git, you need the Git version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.<br />
<br />
== Compiling ==<br />
Assuming you are root, do:<br />
<br />
<syntaxhighlight lang="bash"><br />
# cd /usr/local/src<br />
</syntaxhighlight><br />
<br />
'''Note:''' When tracking a fast changing software like FlightGear/Git it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.<br />
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install <tt>simgear</tt> globally on the system but in a specific directory, you can do so by adding <code>--prefix=/path/to/your/fgInstallation</code> to the <code>./configure</code> command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with <tt>gcc</tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h</tt> like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight><br />
<br />
== External links ==<br />
=== Instructions ===<br />
* [[MSYS]] <br />
* [[MinGW/cross-compiler]] <br />
* [[CodeBlocks IDE]] <br />
* [[OpenSUSE 10.1 10.2]] <br />
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]<br />
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]<br />
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X]<br />
== Important note for GIT users ==<br />
As of latest development in GIT, only cmake is now required for building both SimGear and FlightGear. So if you build GIT (for what any reason) please don't try to use autogen.sh as it is removed from repository.<br />
<br />
For detailed instructions, see page [[Building_using_CMake|Building using cmake]].<br />
<br />
{{Building}}<br />
<br />
[[fr:Compiler FlightGear sous GNU/Linux]]</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=Building_FlightGear_-_Linux&diff=70538Building FlightGear - Linux2014-05-04T20:37:34Z<p>Daemonburrito: /* Dependencies */ Typography and wikimarkup.</p>
<hr />
<div>{{Main article|Building Flightgear}} <br />
<br />
This section describes how to build [[FlightGear]] on Linux system.<br />
<br />
Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.<br />
<br />
openSUSE also provides binary packages of the latest development version, which are continuously updated.<br />
Follow [http://software.opensuse.org/download.html?lang=en&project=games:FlightGear:Unstable&package=fgrun this link] to select your openSUSE version and install, or manually add ''games:FlightGear:Unstable'' to your ''YaST Software Repositories''.<br />
<br />
Or if you develop on Ubuntu or Debian, consider trying the script described in [[Scripted Compilation on Linux Debian/Ubuntu]].<br />
<br />
== Distro-specific instructions ==<br />
=== Debian/Ubuntu ===<br />
* You can use the [[Scripted Compilation on Linux Debian/Ubuntu]] script to have Flightgear compiled in one shot under both Ubuntu and Debian systems.<br />
* Debian users who prefer to build it without script may look at [[Building Flightgear - Debian]].<br />
* Hints for [[Ubuntu]] users.<br />
<br />
=== Gentoo ===<br />
* Gentoo users can also use overlays to build FlightGear without much hassle: [[Building Flightgear - Gentoo]].<br />
<br />
== Requirements ==<br />
Before you can compile FlightGear, you need to have the following installed on your computer:<br />
<br />
'''C++ compiler'''<br />
<br />
These are: c++, cpp, gcc, g++ found under the <code>/usr/bin</code> directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.<br />
<br />
'''GIT'''<br />
<br />
See [[FlightGear and Git]].<br />
<br />
'''[[OpenGL]] support'''<br />
<br />
More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running the following in a [[command line]]:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ glxinfo | grep direct<br />
</syntaxhighlight><br />
<br />
Note: To run the above command, you need to have the tool '''mesa-utils''' installed.<br />
<br />
You should then see:<br />
<br />
direct rendering: Yes<br />
<br />
This means you are good to go as far as OpenGL support is concerned.<br />
<br />
If you see:<br />
<br />
direct rendering: No<br />
<br />
Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing '''plib 1.8.5''' and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.<br />
<br />
== Dependencies ==<br />
<br />
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package <tt>plib1.8.5</tt> is <tt>plib1.8.5</tt>'''-dev'''.<br />
<br />
The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.<br />
<br />
* <tt>FlightGear</tt><br />
** [http://kcat.strangesoft.net/openal.html <tt>OpenAL</tt>]<br />
** <tt>SimGear</tt><br />
*** [http://plib.sourceforge.net/ <tt>PLIB</tt>]. Since March 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.<br />
**** For versions pre March 2008: (Free)<tt>GLUT</tt> or <tt>SDL</tt> (We recommend the use of <tt>SDL</tt> over <tt>Free/GLUT</tt>, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since March 2008, <tt>FreeGLUT</tt> as well as <tt>SDL</tt> are both considered deprecated], please only use <code>--enable-osgviewer</code> during configuration instead) <br />
*** <tt>[[OpenSceneGraph]]</tt> (check link for compatible versions)<br />
*** You also need the development files for several basic libraries to build the software, among them the following (the package names are for Debian and derivatives(?)):<br />
**** <tt>libfreetype6-dev</tt><br />
**** <tt>libjpeg62-dev</tt><br />
**** <tt>libungif4-dev</tt><br />
**** <tt>libtiff4-dev</tt><br />
**** <tt>libpng12-dev</tt><br />
**** <tt>libxmu-dev</tt><br />
**** <tt>libxi-dev</tt><br />
**** <tt>zlib1g-dev</tt><br />
**** <tt>libglut3-dev</tt><br />
<br />
If you attack the above dependencies in the order listed below, you should be good:<br />
<br />
# <tt>glut</tt> Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the <tt>glut</tt> and <tt>glut-devel</tt> packages, otherwise FlightGear may be able to compile but won't run correctly.<br />
# <tt>zlib</tt> Most distributions install the basic <tt>zlib</tt> libraries by default, but not the development portions. If you don't have <tt>zlib.h</tt>, you probably need to install the <tt>zlib-devel</tt> package for your distribution. <br />
# <tt>plib</tt> Portability libraries and scene graph. <br />
# <tt>[[OpenSceneGraph]]</tt> <br />
# <tt>simgear</tt> Simulation support libraries. If you are building FlightGear from Git, you need the Git version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.<br />
<br />
== Compiling ==<br />
Assuming you are root, do:<br />
<br />
<syntaxhighlight lang="bash"><br />
# cd /usr/local/src<br />
</syntaxhighlight><br />
<br />
'''Note:''' When tracking a fast changing software like FlightGear/Git it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.<br />
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight><br />
<br />
== External links ==<br />
=== Instructions ===<br />
* [[MSYS]] <br />
* [[MinGW/cross-compiler]] <br />
* [[CodeBlocks IDE]] <br />
* [[OpenSUSE 10.1 10.2]] <br />
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]<br />
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]<br />
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X]<br />
== Important note for GIT users ==<br />
As of latest development in GIT, only cmake is now required for building both SimGear and FlightGear. So if you build GIT (for what any reason) please don't try to use autogen.sh as it is removed from repository.<br />
<br />
For detailed instructions, see page [[Building_using_CMake|Building using cmake]].<br />
<br />
{{Building}}<br />
<br />
[[fr:Compiler FlightGear sous GNU/Linux]]</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=Building_FlightGear_-_Linux&diff=70537Building FlightGear - Linux2014-05-04T20:22:27Z<p>Daemonburrito: /* Requirements */</p>
<hr />
<div>{{Main article|Building Flightgear}} <br />
<br />
This section describes how to build [[FlightGear]] on Linux system.<br />
<br />
Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.<br />
<br />
openSUSE also provides binary packages of the latest development version, which are continuously updated.<br />
Follow [http://software.opensuse.org/download.html?lang=en&project=games:FlightGear:Unstable&package=fgrun this link] to select your openSUSE version and install, or manually add ''games:FlightGear:Unstable'' to your ''YaST Software Repositories''.<br />
<br />
Or if you develop on Ubuntu or Debian, consider trying the script described in [[Scripted Compilation on Linux Debian/Ubuntu]].<br />
<br />
== Distro-specific instructions ==<br />
=== Debian/Ubuntu ===<br />
* You can use the [[Scripted Compilation on Linux Debian/Ubuntu]] script to have Flightgear compiled in one shot under both Ubuntu and Debian systems.<br />
* Debian users who prefer to build it without script may look at [[Building Flightgear - Debian]].<br />
* Hints for [[Ubuntu]] users.<br />
<br />
=== Gentoo ===<br />
* Gentoo users can also use overlays to build FlightGear without much hassle: [[Building Flightgear - Gentoo]].<br />
<br />
== Requirements ==<br />
Before you can compile FlightGear, you need to have the following installed on your computer:<br />
<br />
'''C++ compiler'''<br />
<br />
These are: c++, cpp, gcc, g++ found under the <code>/usr/bin</code> directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.<br />
<br />
'''GIT'''<br />
<br />
See [[FlightGear and Git]].<br />
<br />
'''[[OpenGL]] support'''<br />
<br />
More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running the following in a [[command line]]:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ glxinfo | grep direct<br />
</syntaxhighlight><br />
<br />
Note: To run the above command, you need to have the tool '''mesa-utils''' installed.<br />
<br />
You should then see:<br />
<br />
direct rendering: Yes<br />
<br />
This means you are good to go as far as OpenGL support is concerned.<br />
<br />
If you see:<br />
<br />
direct rendering: No<br />
<br />
Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing '''plib 1.8.5''' and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.<br />
<br />
== Dependencies ==<br />
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package plib1.8.5 is plib1.8.5'''-dev'''.<br />
<br />
The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.<br />
<br />
* FlightGear<br />
** [http://kcat.strangesoft.net/openal.html OpenAL]<br />
** SimGear<br />
*** [http://plib.sourceforge.net/ PLIB]. Since March 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.<br />
**** For versions pre March 2008: (Free)GLUT or SDL (We recommend the use of SDL over Free/GLUT, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since March 2008, FreeGLUT as well as SDL are both considered deprecated, please only use --enable-osgviewer during configuration instead]) <br />
*** [[OpenSceneGraph]] (check link for compatible versions)<br />
*** You also need the development files for several basic libraries to build the software, among them the following (the package names are for Debian and derivatives(?)):<br />
**** libfreetype6-dev<br />
**** libjpeg62-dev<br />
**** libungif4-dev<br />
**** libtiff4-dev<br />
**** libpng12-dev<br />
**** libxmu-dev<br />
**** libxi-dev<br />
**** zlib1g-dev<br />
**** libglut3-dev<br />
<br />
If you attack the above dependencies in the order listed below, you should be good:<br />
<br />
1. Glut. Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the glut and glut-devel packages, otherwise FlightGear may be able to compile but won't run correctly.<br />
<br />
2. Zlib. Most distributions install the basic zlib libraries by default, but not the development portions. If you don't have zlib.h, you probably need to install the zlib-devel package for your distribution. <br />
<br />
3. Plib - portability libraries and scene graph. <br />
<br />
4. [[OpenSceneGraph]] <br />
<br />
5. SimGear - Simulation support libraries. If you are building FlightGear from Git, you need the Git version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.<br />
<br />
== Compiling ==<br />
Assuming you are root, do:<br />
<br />
<syntaxhighlight lang="bash"><br />
# cd /usr/local/src<br />
</syntaxhighlight><br />
<br />
'''Note:''' When tracking a fast changing software like FlightGear/Git it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.<br />
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight><br />
<br />
== External links ==<br />
=== Instructions ===<br />
* [[MSYS]] <br />
* [[MinGW/cross-compiler]] <br />
* [[CodeBlocks IDE]] <br />
* [[OpenSUSE 10.1 10.2]] <br />
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]<br />
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]<br />
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X]<br />
== Important note for GIT users ==<br />
As of latest development in GIT, only cmake is now required for building both SimGear and FlightGear. So if you build GIT (for what any reason) please don't try to use autogen.sh as it is removed from repository.<br />
<br />
For detailed instructions, see page [[Building_using_CMake|Building using cmake]].<br />
<br />
{{Building}}<br />
<br />
[[fr:Compiler FlightGear sous GNU/Linux]]</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=Building_FlightGear_-_Linux&diff=70536Building FlightGear - Linux2014-05-04T20:14:15Z<p>Daemonburrito: /* Compiling */ We seem to have Geshi installed; using it for bash.</p>
<hr />
<div>{{Main article|Building Flightgear}} <br />
<br />
This section describes how to build [[FlightGear]] on Linux system.<br />
<br />
Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.<br />
<br />
openSUSE also provides binary packages of the latest development version, which are continuously updated.<br />
Follow [http://software.opensuse.org/download.html?lang=en&project=games:FlightGear:Unstable&package=fgrun this link] to select your openSUSE version and install, or manually add ''games:FlightGear:Unstable'' to your ''YaST Software Repositories''.<br />
<br />
Or if you develop on Ubuntu or Debian, consider trying the script described in [[Scripted Compilation on Linux Debian/Ubuntu]].<br />
<br />
== Distro-specific instructions ==<br />
=== Debian/Ubuntu ===<br />
* You can use the [[Scripted Compilation on Linux Debian/Ubuntu]] script to have Flightgear compiled in one shot under both Ubuntu and Debian systems.<br />
* Debian users who prefer to build it without script may look at [[Building Flightgear - Debian]].<br />
* Hints for [[Ubuntu]] users.<br />
<br />
=== Gentoo ===<br />
* Gentoo users can also use overlays to build FlightGear without much hassle: [[Building Flightgear - Gentoo]].<br />
<br />
== Requirements ==<br />
Before you can compile FlightGear, you need to have the following installed on your computer:<br />
<br />
'''C++ compiler'''<br />
<br />
These are: c++, cpp, gcc, g++ found under the /usr/bin directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.<br />
<br />
'''GIT'''<br />
<br />
See [[FlightGear and Git]].<br />
<br />
'''[[OpenGL]] support'''<br />
<br />
More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running the following in a [[command line]]:<br />
<br />
glxinfo | grep direct<br />
<br />
Note: To run the above command, you need to have the tool '''mesa-utils''' installed.<br />
<br />
You should then see:<br />
<br />
direct rendering: Yes<br />
<br />
This means you are good to go as far as OpenGL support is concerned.<br />
<br />
If you see:<br />
<br />
direct rendering: No<br />
<br />
Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing plib 1.8.5 and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.<br />
<br />
== Dependencies ==<br />
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package plib1.8.5 is plib1.8.5'''-dev'''.<br />
<br />
The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.<br />
<br />
* FlightGear<br />
** [http://kcat.strangesoft.net/openal.html OpenAL]<br />
** SimGear<br />
*** [http://plib.sourceforge.net/ PLIB]. Since March 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.<br />
**** For versions pre March 2008: (Free)GLUT or SDL (We recommend the use of SDL over Free/GLUT, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since March 2008, FreeGLUT as well as SDL are both considered deprecated, please only use --enable-osgviewer during configuration instead]) <br />
*** [[OpenSceneGraph]] (check link for compatible versions)<br />
*** You also need the development files for several basic libraries to build the software, among them the following (the package names are for Debian and derivatives(?)):<br />
**** libfreetype6-dev<br />
**** libjpeg62-dev<br />
**** libungif4-dev<br />
**** libtiff4-dev<br />
**** libpng12-dev<br />
**** libxmu-dev<br />
**** libxi-dev<br />
**** zlib1g-dev<br />
**** libglut3-dev<br />
<br />
If you attack the above dependencies in the order listed below, you should be good:<br />
<br />
1. Glut. Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the glut and glut-devel packages, otherwise FlightGear may be able to compile but won't run correctly.<br />
<br />
2. Zlib. Most distributions install the basic zlib libraries by default, but not the development portions. If you don't have zlib.h, you probably need to install the zlib-devel package for your distribution. <br />
<br />
3. Plib - portability libraries and scene graph. <br />
<br />
4. [[OpenSceneGraph]] <br />
<br />
5. SimGear - Simulation support libraries. If you are building FlightGear from Git, you need the Git version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.<br />
<br />
== Compiling ==<br />
Assuming you are root, do:<br />
<br />
<syntaxhighlight lang="bash"><br />
# cd /usr/local/src<br />
</syntaxhighlight><br />
<br />
'''Note:''' When tracking a fast changing software like FlightGear/Git it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.<br />
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone http://gitorious.org/fg/simgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd simgear<br />
$ cmake .<br />
</syntaxhighlight><br />
<br />
'''Note''' that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/flightgear.git<br />
</syntaxhighlight><br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd flightgear<br />
$ ./autogen.sh<br />
$ ./configure<br />
</syntaxhighlight><br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
</syntaxhighlight><br />
<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
</syntaxhighlight><br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ make; make install<br />
</syntaxhighlight><br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://gitorious.org/fg/fgdata.git<br />
</syntaxhighlight><br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
<br />
<syntaxhighlight lang="bash"><br />
$ git clone git://mapserver.flightgear.org/fgdata<br />
</syntaxhighlight><br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
<br />
<syntaxhighlight lang="bash"><br />
$ mv fgdata /usr/local/share/flightgear<br />
</syntaxhighlight><br />
<br />
== External links ==<br />
=== Instructions ===<br />
* [[MSYS]] <br />
* [[MinGW/cross-compiler]] <br />
* [[CodeBlocks IDE]] <br />
* [[OpenSUSE 10.1 10.2]] <br />
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]<br />
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]<br />
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X]<br />
== Important note for GIT users ==<br />
As of latest development in GIT, only cmake is now required for building both SimGear and FlightGear. So if you build GIT (for what any reason) please don't try to use autogen.sh as it is removed from repository.<br />
<br />
For detailed instructions, see page [[Building_using_CMake|Building using cmake]].<br />
<br />
{{Building}}<br />
<br />
[[fr:Compiler FlightGear sous GNU/Linux]]</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=Talk:Building_FlightGear_-_Linux&diff=70535Talk:Building FlightGear - Linux2014-05-04T20:05:22Z<p>Daemonburrito: /* mapserver vs. gitorious */ new section</p>
<hr />
<div>== 06/2010: Update required WRT CVS vs. GIT use==<br />
There are a number of articles which still refer to CVS instead of GIT, so there should probably be a new category added to such pages to indicate that these pages need to be updated accordingly.<br />
<br />
== TODO: introduce and discuss fgfs-builder ==<br />
ftp://ftp.uni-duisburg.de/FlightGear/Misc_rag/fgfs-builder<br />
<br />
== proposal about building FG and OSG related items ==<br />
<br />
- First change the obsoletes references to Plib<br />
(do we need to keep them somewhere because of the remaining plib branch ?)<br />
--> done<br />
<br />
- Give some explanation about what we win with OSG.<br />
<br />
- Gather some help tips on how to get and build the FG patched OSG.<br />
<br />
- List the more common problems encountered when running FG with OSG, mark them as fixed when done.<br />
<br />
- A link is given to gdb, some examples and associated context would be great.<br />
<br />
== Windows? ==<br />
<br />
Any chance of getting a thorough guide on how to set up a dev environment for Flight Gear in Windows? I'm attempting to right now, but I'm already on day 2 with no luck, and apparently according to this site: http://www.geoffmclane.com/fg/ it's not even possible on my current system set-up, as I have MSVC6, and it would extremely nice to know for sure. <br />
<br />
If I can get this to work in the end I'll post something, but until then ...<br />
<br />
FG will not compile with msvc6, it was allready a lot of work to adapt the code a few years ago (declaration of indices in a for statement, some templates could not compile as is, etc). Now that FG uses OSG wich is very C++, it's harder to use VC6. The best is surely to use the free version of msvc 2005.<br />
<br />
== using script for ubuntu/debian ==<br />
<br />
may I add the download_and_compile.sh script to the page for the Ubuntu (And soon even Debian) users ? I have well tested it on 8.04 and 8.10 both 32 and 64 bits<br />
<br />
Now it automatically compiles:<br />
<br />
* plib 1.8.5<br />
* osg from svn<br />
* simgear from cvs<br />
* FlighGear from cvs<br />
* fgrun from svn<br />
* fgcom from svn<br />
* atlas from cvs<br />
<br />
script can downloaded [http://brisa.homelinux.net/fgfs/download_and_compile.sh here].<br />
<br />
If you agree I can make a section under this article explaining the usage.<br />
<br />
== mapserver vs. gitorious ==<br />
<br />
The git mirror for simgear at mapserver.flightgear.org seemed to be down.<br />
<br />
I got this:<br />
fatal: remote error: access denied or repository not exported: /git/simgear<br />
<br />
The gitorious repo works fine, so I edited this page to reflect that.</div>Daemonburritohttps://wiki.flightgear.org/w/index.php?title=Building_FlightGear_-_Linux&diff=70534Building FlightGear - Linux2014-05-04T19:41:30Z<p>Daemonburrito: /* Getting and compiling SimGear */ Use Gitorious for simgear (mapserver mirror down).</p>
<hr />
<div>{{Main article|Building Flightgear}} <br />
<br />
This section describes how to build [[FlightGear]] on Linux system.<br />
<br />
Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.<br />
<br />
openSUSE also provides binary packages of the latest development version, which are continuously updated.<br />
Follow [http://software.opensuse.org/download.html?lang=en&project=games:FlightGear:Unstable&package=fgrun this link] to select your openSUSE version and install, or manually add ''games:FlightGear:Unstable'' to your ''YaST Software Repositories''.<br />
<br />
Or if you develop on Ubuntu or Debian, consider trying the script described in [[Scripted Compilation on Linux Debian/Ubuntu]].<br />
<br />
== Distro-specific instructions ==<br />
=== Debian/Ubuntu ===<br />
* You can use the [[Scripted Compilation on Linux Debian/Ubuntu]] script to have Flightgear compiled in one shot under both Ubuntu and Debian systems.<br />
* Debian users who prefer to build it without script may look at [[Building Flightgear - Debian]].<br />
* Hints for [[Ubuntu]] users.<br />
<br />
=== Gentoo ===<br />
* Gentoo users can also use overlays to build FlightGear without much hassle: [[Building Flightgear - Gentoo]].<br />
<br />
== Requirements ==<br />
Before you can compile FlightGear, you need to have the following installed on your computer:<br />
<br />
'''C++ compiler'''<br />
<br />
These are: c++, cpp, gcc, g++ found under the /usr/bin directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.<br />
<br />
'''GIT'''<br />
<br />
See [[FlightGear and Git]].<br />
<br />
'''[[OpenGL]] support'''<br />
<br />
More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running the following in a [[command line]]:<br />
<br />
glxinfo | grep direct<br />
<br />
Note: To run the above command, you need to have the tool '''mesa-utils''' installed.<br />
<br />
You should then see:<br />
<br />
direct rendering: Yes<br />
<br />
This means you are good to go as far as OpenGL support is concerned.<br />
<br />
If you see:<br />
<br />
direct rendering: No<br />
<br />
Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing plib 1.8.5 and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.<br />
<br />
== Dependencies ==<br />
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package plib1.8.5 is plib1.8.5'''-dev'''.<br />
<br />
The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.<br />
<br />
* FlightGear<br />
** [http://kcat.strangesoft.net/openal.html OpenAL]<br />
** SimGear<br />
*** [http://plib.sourceforge.net/ PLIB]. Since March 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.<br />
**** For versions pre March 2008: (Free)GLUT or SDL (We recommend the use of SDL over Free/GLUT, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since March 2008, FreeGLUT as well as SDL are both considered deprecated, please only use --enable-osgviewer during configuration instead]) <br />
*** [[OpenSceneGraph]] (check link for compatible versions)<br />
*** You also need the development files for several basic libraries to build the software, among them the following (the package names are for Debian and derivatives(?)):<br />
**** libfreetype6-dev<br />
**** libjpeg62-dev<br />
**** libungif4-dev<br />
**** libtiff4-dev<br />
**** libpng12-dev<br />
**** libxmu-dev<br />
**** libxi-dev<br />
**** zlib1g-dev<br />
**** libglut3-dev<br />
<br />
If you attack the above dependencies in the order listed below, you should be good:<br />
<br />
1. Glut. Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the glut and glut-devel packages, otherwise FlightGear may be able to compile but won't run correctly.<br />
<br />
2. Zlib. Most distributions install the basic zlib libraries by default, but not the development portions. If you don't have zlib.h, you probably need to install the zlib-devel package for your distribution. <br />
<br />
3. Plib - portability libraries and scene graph. <br />
<br />
4. [[OpenSceneGraph]] <br />
<br />
5. SimGear - Simulation support libraries. If you are building FlightGear from Git, you need the Git version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.<br />
<br />
== Compiling ==<br />
Assuming you are root, do:<br />
cd /usr/local/src<br />
<br />
'''Note:''' When tracking a fast changing software like FlightGear/Git it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.<br />
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.<br />
<br />
=== Getting and compiling SimGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the SimGear git repository and set it up to track the 'next' branch.<br />
<br />
git clone git://gitorious.org/fg/simgear.git<br />
<br />
or if the git port is firewalled on you network, use the http transport<br />
<br />
git clone http://gitorious.org/fg/simgear.git<br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
The source code will be downloaded into a directory called '''simgear'''.<br />
<br />
Next, go into the directory and make preparations for the compilation:<br />
cd simgear<br />
cmake .<br />
<br />
'''Note''' that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command<br />
<br />
'''Step 3:'''<br />
<br />
Compile and install SimGear by doing:<br />
make; make install<br />
<br />
<br />
''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like: <br />
<br />
'<anonymous>' has incomplete type <br />
take a look at http://bugs.gentoo.org/166723<br />
<br />
=== Getting and compiling FlightGear ===<br />
<br />
'''Step 1:'''<br />
<br />
Clone the FlightGear git repository and set it up to track the 'next' branch.<br />
git clone git://gitorious.org/fg/flightgear.git<br />
<br />
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.<br />
<br />
'''Step 2:'''<br />
<br />
Next, go into the folder and make preparations for the compilation:<br />
cd flightgear<br />
''./autogen.sh''<br />
./configure<br />
<br />
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.<br />
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:<br />
./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer<br />
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:<br />
export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH<br />
<br />
'''Step 3:'''<br />
<br />
Now you can compile and install Flightgear by:<br />
make; make install<br />
<br />
'''Step 4:'''<br />
<br />
Clone the data directory:<br />
git clone git://gitorious.org/fg/fgdata.git<br />
<br />
The data directory is large (almost 2.5GB) so it will take considerable time to download.<br />
There mirror of fgdata that might be faster to download from:<br />
git clone git://mapserver.flightgear.org/fgdata<br />
<br />
The mirror is synchronized with the master so either will do.<br />
<br />
And install it in (or as) /usr/local/share/FlightGear<br />
mv fgdata /usr/local/share/flightgear<br />
<br />
<br />
<br />
== External links ==<br />
=== Instructions ===<br />
* [[MSYS]] <br />
* [[MinGW/cross-compiler]] <br />
* [[CodeBlocks IDE]] <br />
* [[OpenSUSE 10.1 10.2]] <br />
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]<br />
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]<br />
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X]<br />
== Important note for GIT users ==<br />
As of latest development in GIT, only cmake is now required for building both SimGear and FlightGear. So if you build GIT (for what any reason) please don't try to use autogen.sh as it is removed from repository.<br />
<br />
For detailed instructions, see page [[Building_using_CMake|Building using cmake]].<br />
<br />
{{Building}}<br />
<br />
[[fr:Compiler FlightGear sous GNU/Linux]]</div>Daemonburrito