936
edits
Avoiding multiple downloads of FGData on Linux: Difference between revisions
Jump to navigation
Jump to search
Avoiding multiple downloads of FGData on Linux (view source)
Revision as of 17:11, 25 May 2013
, 25 May 2013cleanup and final wording edits.
(wikified. but not yet pretty.) |
(cleanup and final wording edits.) |
||
| Line 6: | Line 6: | ||
The instructions below tell how to do this for existing or new uses of download_and_compile.sh. The tecnical details are not dependent on where you put your builds. You can use the directory scheme I use or your own existing scheme. | The instructions below tell how to do this for existing or new uses of download_and_compile.sh. The tecnical details are not dependent on where you put your builds. You can use the directory scheme I use or your own existing scheme. | ||
The concept as a whole works great. I've been using it for months. The instructions are a work in progress and have yet to be fully tested. The initial use case may have a bug related to allowing fgdata to be created through a link. I'm not sure that will work. I may need to tweak the initial directions. | |||
====The main ideas==== | ====The main ideas==== | ||
| Line 12: | Line 14: | ||
* install/fgdata can be a symbolic link to fgdata's real directory location | * install/fgdata can be a symbolic link to fgdata's real directory location | ||
====Technical Points==== | ====Technical Points and command examples==== | ||
* mkdir -p install/fgfs will create the install directory and subdirectory if either does not yet exist | |||
* mv can move a directory | |||
* cp -R will copy a directory recursively. | |||
* ln -s targetname linkname creates linkname as a symbolic link to the target. The target may or may not yet exist and that's ok. | |||
* Important: You can move the flightgear source directories and download_and_compile.sh to different folders at will. Git will not care. All the git specific files move right along with the sources. Its the same for svn. However, the same does not hold true for the files created during a build by cmake. The build and install folders cannot be moved because the files in them have hard coded paths in some cases. They'll need to be deleted and rebuilt. | * Important: You can move the flightgear source directories and download_and_compile.sh to different folders at will. Git will not care. All the git specific files move right along with the sources. Its the same for svn. However, the same does not hold true for the files created during a build by cmake. The build and install folders cannot be moved because the files in them have hard coded paths in some cases. They'll need to be deleted and rebuilt. | ||