982
edits
Talk:Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions
Jump to navigation
Jump to search
Talk:Scripted Compilation on Linux Debian/Ubuntu (view source)
Revision as of 13:13, 1 February 2014
, 1 February 2014→Current Status of development
| Line 12: | Line 12: | ||
1.9.15 will contain one or more of the following: | 1.9.15 will contain one or more of the following: | ||
*** version number comparison. is version 3.10.0 higher than 3.9.0 or lower? this is needed to allow version to be specified as "3.9.0 or higher". | |||
*** cleanup task: for some reason, the local .git repostiories and sources are placed in directories such as simgear/simgear, fgfs/flightgear, openrti/openrti. Why? Why not just simgear, flightgear and openrti? | |||
*** cleanup task: the script uses cd to move up and down the source/build/install directories as an alternative, define variable values containing full paths and cd only to the specific directory needed to do a particular task. plib and osg have gotten this treatment already. | |||
*** cleanup task: lowercase all variables that are not used as environment variables. This is the current accepted practice for bash scripts. | *** cleanup task: lowercase all variables that are not used as environment variables. This is the current accepted practice for bash scripts. | ||
*** cleanup task: use a "Here Document" for help | *** cleanup task: use a "Here Document" for help | ||
*** cleanup task: get rid of all that my_slash stuff in the fgx section | *** cleanup task: get rid of all that my_slash stuff in the fgx section | ||
*** cleanup task: in the component build sections use cd to move between directories using full path names where needed. remove relative cd commands. remove necessity to return to current build directory at the end of each component. | *** cleanup task: in the component build sections use cd to move between directories using full path names where needed. remove relative cd commands. remove necessity to return to current build directory at the end of each component. | ||
*** | *** Default versions of OSG for each version of flightgear | ||
** feature_modify_fltk. produce a script to modify the paths in ~/fltk/flightgear/org/fgrun.prefs to point to the current directory | ** feature_modify_fltk. produce a script to modify the paths in ~/fltk/flightgear/org/fgrun.prefs to point to the current directory | ||
** feature_symlinks | ** feature_symlinks | ||
*** | *** use installed OSG or plib | ||
*** allow use of specified boost or fltk library version | |||
*** allow use of a specified version of just about anything. | |||
*** Allow a single downloaded set of sources and fgdata to support multiple builds. There are two ways to do this: Keep a single .git and checkout directory for each component, using them one at a time or keep a single .git and checkout version per branch. The second option allows work on more than one branch at a time. | |||
*** Eclipse integration | |||
*** Netbeans integration | |||
*** Codeblocks integration | |||
*** Your favorite IDE integration | |||
** feature_fgmeta_cmake | ** feature_fgmeta_cmake | ||