20,741
edits
Building FlightGear - Cross Compiling: Difference between revisions
Jump to navigation
Jump to search
→Background
m (→Roadmap: virtual appliance via docker: https://github.com/mxe/mxe/issues/145#issuecomment-133776848) |
|||
| Line 201: | Line 201: | ||
== Background == | == Background == | ||
anyone who cares about [..] free-as-in-speech is invited and encouraged to work on mingw support, which used to work and James suspects is not so hard to get working again. But he asked several times in the last years and no-one ever offered to help with MinGW, so it seems is a small niche of people <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35131633/ | |||
|title = <nowiki> [Flightgear-devel] VisualStudio versions / support </nowiki> | |||
|author = <nowiki> James Turner </nowiki> | |||
|date = Jun 2nd, 2016 | |||
|added = Jun 2nd, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
{{FGCquote | {{FGCquote | ||
|Linux/Unix users are generally more accustomed to building software from source - on Unix-based platforms it isn't rare even for non-developers to regularly configure/compile and install software - whereas it is much less common on Windows, which is why you need to install a bunch of things to even end up with a working build environment, whereas a Unix-based system will often have everything pre-installed. In addition, FlightGear is a complex piece of software, especially in terms of build-time/run-time dependencies - so people entirely new to the whole process of building software from source are likely to find this pretty frustrating. Personally, I also find setting up a build environment on Linux much easier than doing the same on Windows, despite being pretty familiar with the required workflows - but that doesn't have to do much with FG - the superbuild should help automate most of the required steps these days.<br/> | |Linux/Unix users are generally more accustomed to building software from source - on Unix-based platforms it isn't rare even for non-developers to regularly configure/compile and install software - whereas it is much less common on Windows, which is why you need to install a bunch of things to even end up with a working build environment, whereas a Unix-based system will often have everything pre-installed. In addition, FlightGear is a complex piece of software, especially in terms of build-time/run-time dependencies - so people entirely new to the whole process of building software from source are likely to find this pretty frustrating. Personally, I also find setting up a build environment on Linux much easier than doing the same on Windows, despite being pretty familiar with the required workflows - but that doesn't have to do much with FG - the superbuild should help automate most of the required steps these days.<br/> | ||