982
edits
Talk:Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions
Jump to navigation
Jump to search
m
Talk:Scripted Compilation on Linux Debian/Ubuntu (view source)
Revision as of 11:21, 8 August 2013
, 8 August 2013→General Thoughts on download_and_compile.sh
| Line 274: | Line 274: | ||
* installing | * installing | ||
* reporting results | * reporting results | ||
What could change: | |||
* Its possible to separate the logic that decides what steps to take from the actual execution. The logic decides what commands to execute and sets up the command list, then a simple process just executes the commands. This could make a log easier to read. | * Its possible to separate the logic that decides what steps to take from the actual execution. The logic decides what commands to execute and sets up the command list, then a simple process just executes the commands. This could make a log easier to read. | ||
| Line 281: | Line 281: | ||
* You might be in the process of updating a file in one of the components. How would the build need to change to avoid overwriting your change. | * You might be in the process of updating a file in one of the components. How would the build need to change to avoid overwriting your change. | ||
* We currently use the main flightgear git archives for sources. Its possible to use personal or team clones for one or more components instead? | * We currently use the main flightgear git archives for sources. Its possible to use personal or team clones for one or more components instead? | ||
* Do we need better reporting of the results of the build? | |||
* what can we do with cmake to reduce the bash code used to make decisions about what steps need to be done? | |||
* how much of the scripts logic can we delegate to cmake? | |||
* should we add a flightgear test run to the script? | |||