Using Tools: 13 pmake

Up: GEOS SDK TechDocs | Up | Down | Prev: 12 pcsend | Next: 14 Swat Stub

The pmake program is a make utility. This means that it takes a directory of sources and a makefile which contains knowledge of how to turn these sources into geodes. If there were no pmake , then you would have to type goc, bcc, and glue each time.

The pmake program will work correctly if you have set up your files correctly. This means that you must have a makefile. You should run mkmf to generate a makefile that knows how to generate geodes. If you are an experienced C programmer, you may have come up with some customizations that you use with your make utility. We still suggest that you work from a standard makefile (which knows about Goc and Glue), but include your customizations in a local.mk file (see How to Customize pmake ).

When you have just added or removed source files from a geode, you will have to generate new dependency information, which pmake will use when doing other makes. You can use pmake to generate this information (it will make an appropriate call to the makedpnd program; it will store the result in depends.mk ):

 pmake depend

Once you have created your source and make files, all you need to do to invoke pmake is type

pmake

The pmake tool can be used to construct a specific target. Thus, if you need to generate an .OBJ file but do not need the rest of the geode, you may type something like:

pmake sdtrk.obj

The system makefiles have been set up with knowledge of some special targets. If you are making a library and wish to install it in the proper directory so that all applications may use it, then signal this to pmake :

 pmake lib

The pmake program does have command-line arguments, but these are used only rarely; they are detailed below.


Up: GEOS SDK TechDocs | Up | Down | Prev: 12 pcsend | Next: 14 Swat Stub