936
edits
(Big correction. You have to have run download_and_compile.sh before you can use this technique. Directions are still untested.) |
mNo edit summary |
||
Line 7: | Line 7: | ||
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 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 main ideas==== | ====The main ideas==== | ||
* you may only need one copy of each version of fgdata you are working with | * you may only need one copy of each version of fgdata you are working with | ||
* fgdata normally lives as a sub-directory in install/fgfs/ | * fgdata normally lives as a sub-directory in install/fgfs/ | ||
* once it exists, install/fgdata can moved and replaced by a symbolic link to fgdata's real directory location | * once it exists, install/fgdata can moved and replaced by a symbolic link to fgdata's real directory location |
edits