Maptitude GISDK Help

Compiling with the Stand-Alone Resource Compiler

 

Resources can be compiled from the DOS command line or from the Windows Program Manager using the stand-alone version of the resource compiler (rscc.exe). This program accepts a command line of the following form:

 

rscc {-c} -u uidbname fname1.rsc fname2.rsc...

 

where:

If you do not use the -c command line option, compiled resources will replace any existing resources that come from a file with the same name. If you compile a file called test.rsc, any resources from a previous version of test.rsc are removed from the UI Database before the new test.rsc is compiled.

 

A group of resource files can be compiled in one step using a list file as follows:

 

rscc {-c} -u uidbname @listfile1 @listfile2...

 

where listfile1, listfile2, etc. are names of list files, as described above. Note that the optional -c command line option speeds up compilation by quite a bit when you are compiling a large number of resource files.

 

You can also combine list files and resource files in the command line, as in the following example:

 

rscc -c -u myxfac menus.rsc macros.rsc @rsc_list.txt

 

You cannot use the stand-alone version of the resource compiler while the UI Database is in use by the platform. For example, if you are working on a custom application that is stored in a UI Database named my_app, you cannot run the resource compiler using that same UI Database while the custom application is running.

 

You can call the stand-alone version of the resource compiler from within a GISDK macro by calling RunProgram(). For example, the following statement would compile utils.rsc in the gisdk\samples folder into a new UI Database called newtest.dbd:

 

RunProgram('rscc -c -u "c:\\temp\\newtest.dbd" "c:\\Program Files\\Maptitude\\GISDK\\Samples\\utils.rsc" ', )

 

 

©2025 Caliper Corporation www.caliper.com