20,741
edits
| Line 147: | Line 147: | ||
== makeffile and cmake idea (needs discussion) == | == makeffile and cmake idea (needs discussion) == | ||
{{cquote|<nowiki>I also did some work (and pushed it) to support CMake superbuilds using fgmeta. It works on Mac and Windows, and probably on Linux with some small tweaks, so this might be a way to simplify future versions of the download_and_compile script, since most of the steps (download & build OSG, download and build PLIB) are handled by the super-build.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40142.html|title=<nowiki>Re: [Flightgear-devel] new team clone on gitorious.org specifically for download_and_compile.</nowiki>|author=<nowiki>James Turner</nowiki>|date=<nowiki>Sat, 01 Jun 2013 02:16:43 -0700</nowiki>}}</ref>|<nowiki>James Turner</nowiki>}} | |||
# use of makefile or cmake as a basis for or as part of the script. | # use of makefile or cmake as a basis for or as part of the script. | ||
| Line 163: | Line 165: | ||
# This is a great idea, Should it be a separate alternative script? [[User:Callahanp|Callahanp]] 11:34, 31 May 2013 (UTC) | # This is a great idea, Should it be a separate alternative script? [[User:Callahanp|Callahanp]] 11:34, 31 May 2013 (UTC) | ||
: Agreed, the cmake-based approach sounds really sensible, and would also help unify the build infrastructure,i.e. regarding the [[FlightGear Build Server]], to make the setup better reproducable, but also allow CI to be set up locally, i.e. as part of NetBeans or Eclipse. The question is which parts of the script could be reasonably moved into some form of CMake/superbuild script - certain things are highly distro/OS/platform specific. And I'm not sure just how flexible cmake is here ? | |||
== Clear description of what is being built in the log file == | == Clear description of what is being built in the log file == | ||