2,561
edits
Simplifying Aircraft Deployment: Difference between revisions
Jump to navigation
Jump to search
m
adding library notes WRT accessing archives like directories to facilitate running aircraft w/o having to install them in the first place
m (adding library notes WRT accessing archives like directories to facilitate running aircraft w/o having to install them in the first place) |
|||
| Line 23: | Line 23: | ||
* allow aircraft to be used without requiring an installation | * allow aircraft to be used without requiring an installation | ||
* allow aircraft to be installed in and used from custom directories (i.e. non-base package, as in ~/.fgfs/Aircraft or support something like --user-aircraft=/folder/with/non-base-package-aircraft) | * allow aircraft to be installed in and used from custom directories (i.e. non-base package, as in ~/.fgfs/Aircraft or support something like --user-aircraft=/folder/with/non-base-package-aircraft) | ||
* allow aircraft to be run from tarballs to allow users to test aircraft easily | * allow aircraft to be run from tarballs/archives to allow users to test aircraft easily (Libraries to transparently access archives likes directories: [http://zziplib.sourceforge.net/ ZZIPLIB] [http://icculus.org/physfs/]) | ||
* provide support for proper dependency tracking between aircraft and common resources [http://www.flightgear.org/forums/viewtopic.php?t=1135] | * provide support for proper dependency tracking between aircraft and common resources [http://www.flightgear.org/forums/viewtopic.php?t=1135] | ||