Article # 169, added by Geoworks, historical record
| first |
previous |
index |
next |
last |
Using LOCAL_ROOT and ROOT_DIR to network your SDK
When using the SDK on a network or running multiple versions of the SDK (e.g., OmniGo, N9000, etc.) you can seperate your development directory from the rest of the SDK (tools, header files, symbol files, and such) by setting up the ROOT_DIR and LOCAL_ROOT environment variables. With these two environment variables setup, the SDK will look for files first in the development area defined by LOCAL_ROOT and, failing to find them, will look in ROOT_DIR. For example, if you have an environment like this: ROOT_DIR=S:\GEOSDK LOCAL_ROOT=C:\PCGEOS You can keep the SDK files (tools, headers, etc.) installed on the S: drive. The individual developer, though, can use source code on his PC. For example, if a developer has the above envariables set and does a pmake in C:\PCGeos\Appl\SDK_C\MyApp, pmake will compile the source code in the PC's local directory. If files are missing from the local PC directory (like the *.gp file), they will be taken from S:\30SDK\Appl\SDK_C\MyApp. If you are developing an application for several platforms (e.g., OmniGo and N9000), you can set up LOCAL_ROOT to point to the directory tree which contains your single set of source code and set ROOT_DIR to the SDK for which you want to compile the application. You can use the tools from the latest SDK for compiling. Otherwise you will have to modify your PATH environment variable to set the BIN directory to use. On caveat to using the same tools for different platforms is that you will have to delete the SYMDIR files that SWAT caches directories in. Otherwise, whenever you switch ROOT_DIR and run swat, it will read the wrong symbol files.