Using Tools: 2 Typical Development Session

| Up: GEOS SDK TechDocs | Up | Prev: 1 Tools Summary | Next: 3 File Types

The Tutorial shows in detail how to write, compile, download, and debug an application. As a quick guide, however, the following list recaps the steps in a typical development session:

  1. On the development machine, use a text editor (perhaps the one that came with your compiler) to write or edit the source (.c and .goc files, perhaps .asm or .ui files if you have the Esp assembler), header (.h and .goh files, perhaps .def files if you have the Esp assembler), and Glue parameters (.gp files) for your geode.The source files for the geode should be arranged within your development directory.
  2. If you have never compiled the geode before or have added or included new files since the last compilation, you must run mkmf to create or update the MAKEFILE.
  3. If you have added or included new files since the last compilation, you should execute pmake depend so that the compiler will know which files need to be remade if one is altered.
  4. Run pmake . This compiles and links the geode's source files, using directions provided by the MAKEFILE.
  5. To test the geode, either run it on the target machine or run swat from the development machine to debug it.
| Up: GEOS SDK TechDocs | Up | Prev: 1 Tools Summary | Next: 3 File Types