272
edits
m (→Contributing) |
Hamzaalloush (talk | contribs) m (→osg-earth compilation trouble: will report soon) |
||
| Line 709: | Line 709: | ||
* We keep seeing people asking for ways to have an entirely self-contained FlightGear setup that doesn't require any installation (e.g. either all files residing in a single folder or the whole binary linked statically) - we used to support this a few years go, and we even had people using FG on a USB drive, or on boot-able drives - and we commonly suggest that people first try running FG on computers before purchasing any new hardware - so it would make sense to look at what's needed to still support static builds using the mxe tool chain. This may involve making the static/dynamic configuration options configurable in the corresponding *.mk files. | * We keep seeing people asking for ways to have an entirely self-contained FlightGear setup that doesn't require any installation (e.g. either all files residing in a single folder or the whole binary linked statically) - we used to support this a few years go, and we even had people using FG on a USB drive, or on boot-able drives - and we commonly suggest that people first try running FG on computers before purchasing any new hardware - so it would make sense to look at what's needed to still support static builds using the mxe tool chain. This may involve making the static/dynamic configuration options configurable in the corresponding *.mk files. | ||
=== osg-earth compilation trouble === | === osg-earth compilation trouble === 'SOLVED' | ||
osg-earth has both CMake and autotools generators provided by source, i'm using a basic CMake config: | osg-earth has both CMake and autotools generators provided by source, i'm using a basic CMake config: | ||
edits