Building FlightGear - Cross Compiling: Difference between revisions

Jump to navigation Jump to search
fill up gallery, also clean up more qouting, TODO: "news"
(→‎Status: new updates!)
(fill up gallery, also clean up more qouting, TODO: "news")
Line 20: Line 20:


== News ==
== News ==
{{Note| examples and the osgviewer in action recorded, was using Wine at the time, but i tried it on Windows dual booted to same machine and it worked! -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 13:25, 28 May 2015 (EDT) }}


{{#ev:youtube|ddYyH5CYhAo|400|left}}{{#ev:youtube|mTHhHMlTSAo|400|center}}
 


== Gallery ==
== Gallery ==
<gallery mode=packed widths=230px heights=230px>
<gallery mode=packed widths=230px heights=230px>
OSG Earth.png|showing the symbolic osg earth :)
OSG Earth.png|showing the symbolic osg earth :)
OSGEarth Boston Baseball.png|example what OSM buildings look like with OSG textures
</gallery>
</gallery>


Line 217: Line 217:
     |author=<nowiki>elgaton</nowiki>
     |author=<nowiki>elgaton</nowiki>
     |date=<nowiki>Thu Apr 09</nowiki>
     |date=<nowiki>Thu Apr 09</nowiki>
  }}
}}
== Idea ==
{{FGCquote
  |do we really need Windows SDK's? can't we find a similar toolchain like Mingw using GCC for example? i think VS support non-native compilers as well? we can then skip this whole thing and probebly even adopt a modified version of the debian build script
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=238158#p238158
    |title=<nowiki>Re: Help me! Install osgEarth feature on Win7 64b with FG gi</nowiki>
    |author=<nowiki>hamzaalloush</nowiki>
    |date=<nowiki>Wed Apr 08</nowiki>
  }}
}}
{{FGCquote
  |I also think is better using free software tools to compile it and incidentally make it easier
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=238176#p238176
    |title=<nowiki>Re: Help me! Install osgEarth feature on Win7 64b with FG gi</nowiki>
    |author=<nowiki>Catalanoic</nowiki>
    |date=<nowiki>Wed Apr 08</nowiki>
   }}
   }}
}}
}}
Line 763: Line 744:


=== Thursday, May 28, 2015 : OSG Applications/Examples built and tested working. ===
=== Thursday, May 28, 2015 : OSG Applications/Examples built and tested working. ===
{{Note| examples and the osgviewer in action recorded, was using Wine at the time, but i tried it on Windows dual booted to same machine and it worked! -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 13:25, 28 May 2015 (EDT) }}
{{#ev:youtube|ddYyH5CYhAo|400}}


=== Wednesday, May 29, 2015 : Simgear Shared support done (Thanks to {{usr|Flyhigh}}!) ===
=== Wednesday, May 29, 2015 : Simgear Shared support done (Thanks to {{usr|Flyhigh}}!) ===
Line 780: Line 763:


=== Sunday, May 31, 2015 : OSG-Earth built and examples tested. ===
=== Sunday, May 31, 2015 : OSG-Earth built and examples tested. ===
{{#ev:youtube|mTHhHMlTSAo|400|left}} {{#ev:youtube|sfWVo5u_7lw|400|center}}


<syntaxhighlight lang=bash>optirun ./osgearth_version.exe --caps
<syntaxhighlight lang=bash>optirun ./osgearth_version.exe --caps
Line 811: Line 796:
[osgEarth]  [Capabilities]  NPOT textures = yes
[osgEarth]  [Capabilities]  NPOT textures = yes
[osgEarth]  [Capabilities]  Compression = ARB S3 RG</syntaxhighlight>
[osgEarth]  [Capabilities]  Compression = ARB S3 RG</syntaxhighlight>
{{#ev:youtube|sfWVo5u_7lw|400|left}} [[File:OSGEarth Boston Baseball.png|400px|center]]


=== Wednesday, June 9, 2015 : Shared FGViewer working ===
=== Wednesday, June 9, 2015 : Shared FGViewer working ===
Line 819: Line 801:
{{Note|I've uploaded the fgfs.log file, the command I ran, and the wine memory dump to a Github Gist. As for fgviewer, after including the path to the data directory, fgviewer works correctly. -- [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 11:38, 9 June 2015 (EDT)}}
{{Note|I've uploaded the fgfs.log file, the command I ran, and the wine memory dump to a Github Gist. As for fgviewer, after including the path to the data directory, fgviewer works correctly. -- [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 11:38, 9 June 2015 (EDT)}}


[[File:Fgviewer under wine.png|600px|left|Screenshot of running FGViewer under Wine]]
[[File:Fgviewer under wine.png|400px|Screenshot of running FGViewer under Wine]]


== Issues ==
== Issues ==
Line 832: Line 814:


* As request for custom scenery generation arises among end-users/data developers, we see the need for a cross-platform ready set of tools handy. since then the effort started for providing Terragear on Windows(initially by {{usr|Hamzaalloush}}). It was expected that Terragear, as a scenery generation tool, that was made to deployed on a Linux server, would have portability problems. this effort would at least pinpoint issues with portability for the underlying structure of FlightGear.
* As request for custom scenery generation arises among end-users/data developers, we see the need for a cross-platform ready set of tools handy. since then the effort started for providing Terragear on Windows(initially by {{usr|Hamzaalloush}}). It was expected that Terragear, as a scenery generation tool, that was made to deployed on a Linux server, would have portability problems. this effort would at least pinpoint issues with portability for the underlying structure of FlightGear.
 
* The Terragear tools for scenery generation would be the ideal environment on which to bring"Small, stable, incremental changes which are preferable to larger monolithic changes to ease review", adhering to the FG roadmap for development, since we are mainly dealing with the basic building blocks for Flightgear, where a Simgear based environment is the only prerequisite. the SG abstraction layer for threading, as well as for maths are good points to investigate in this setup(as it is used throughly), as well as providing small patches upstream towards getting Simgear, Mingw64 compatible as the end-goal.
 
* The Terragear tools for scenery generation would be the ideal environment on which to bring: {{FGCquote  |Small, stable, incremental changes are preferable to larger monolithic changes to ease review.  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/34183645/    |title=<nowiki>[Flightgear-devel] Policy Document and V4.X Roadmap</nowiki>    |author=<nowiki>Stuart Buchanan</nowiki>    |date=Jun 7th, 2015  }}}}, adhering to the FG Global roadmap for development, since we are mainly dealing with the basic building blocks for Flightgear, where a Simgear based environment is the only prerequisite. the SG abstraction layer for threading, as well as for maths are good points to investigate in this setup(as it is used throughly), as well as providing small patches upstream towards getting Simgear, Mingw64 compatible as the end-goal.
 
 
* The relatively smaller number of static symbols collected from such an effort, is a good basis for investigating debugging facilities on cross-compiled binaries.
* The relatively smaller number of static symbols collected from such an effort, is a good basis for investigating debugging facilities on cross-compiled binaries.
272

edits

Navigation menu