20,741
edits
FlightGear Newsletter January 2018: Difference between revisions
Jump to navigation
Jump to search
m
FlightGear Newsletter January 2018 (view source)
Revision as of 15:15, 30 January 2018
, 30 January 2018→Docker-based scenery toolchain
| Line 69: | Line 69: | ||
* Run ogr-decode against local shapefiles or perform direct queries to a postgres database | * Run ogr-decode against local shapefiles or perform direct queries to a postgres database | ||
Torsten has sucessfully created the elevation data from SRTM1/3 for the entire globe and created a few random airports with this image. Currently, he is playing with integrating ogr-decode. The docker image gets automatically built, including building latest simgear & terragear from GIT. This build process runs directly at the docker hub: https://hub.docker.com/r/flightgear/terragear/builds/ (Yes: docker hub compiles simgear and terragear for us, amazing, | Torsten has sucessfully created the elevation data from SRTM1/3 for the entire globe and created a few random airports with this image. Currently, he is playing with integrating ogr-decode. The docker image gets automatically built, including building latest simgear & terragear from GIT. This build process runs directly at the docker hub: https://hub.docker.com/r/flightgear/terragear/builds/ (Yes: docker hub compiles simgear and terragear for us, amazing, isn't it?) Torsten hopes to be able to compile the a first chunk of scenery within the next couple of weeks.<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/36209739/ | |url = https://sourceforge.net/p/flightgear/mailman/message/36209739/ | ||
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery | |||
goes docker </nowiki> | |||
|author = <nowiki> Torsten Dreyer </nowiki> | |||
|date = Jan 30th, 2018 | |||
|added = Jan 30th, 2018 | |||
|script_version = 0.36 | |||
}}</ref> | |||
That means, if someone wants to generate scenery in the future they will simply be able to download the latest docker image, start it up on Docker CE and run the commands. No compilation required. Which is quite amaing, and could massively reduce the effort required to work on scenery.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/36209758/ | |||
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery | |||
goes docker </nowiki> | |||
|author = <nowiki> Stuart Buchanan </nowiki> | |||
|date = Jan 30th, 2018 | |||
|added = Jan 30th, 2018 | |||
|script_version = 0.36 | |||
}}</ref> | |||
In other words, Build once, run anywhere - thats what docker is made for. (caveat: anywhere means "any Linux flavor or MacOS on x86-64 architecture and eventually Windows64, too.)<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/36209773/ | |||
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery | |title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery | ||
goes docker </nowiki> | goes docker </nowiki> | ||