[M3devel] cm3.cfg variables for IDE

[Randy Coleburn]

Jay:
 
I thought I should let you know what I understand to be the variables that the IDE is looking to find in cm3.cfg.  That way, as you work through any changes to the various cm3.cfg, you can make sure these requirements are met.
 
INSTALL_ROOT   (e.g., c:\cm3)
BUILD_DIR   (e.g., NT386)
PKG_USE   (e.g., c:\cm3\pkg)

DOC_INSTALL  (e.g., c:\cm3\doc)
INITIAL_CM3_IDE_BROWSER   (e.g., c:\progra~1\intern~1\iexplore.exe)
INITIAL_CM3_IDE_EDITOR   (e.g.,   c:\progra~1\window~1\accessories\wordpad.exe)
 
Now, of these 6 listed above, the first three: INSTALL_ROOT, BUILD_DIR and PKG_USE, are the most critical for the IDE.
 
DOC_INSTALL can be omitted, in which case the IDE will substitute INSTALL_ROOT\doc
 
If INITIAL_CM3_IDE_BROWSER and/or INITIAL_CM3_IDE_EDITOR are not defined, the IDE will prompt the user via its console log window for the complete paths to these two programs; thus their definition can be omitted from the cm3.cfg.  The IDE will store the user's input for subsequent reuse in its own private cfg file.  This file is stored in the user's home folder or as specified in the optional CM3_IDE_HOME environment variable.  The CM3_IDE_HOME environment variable should point to the path of the user's primary private package repository.  CM3_IDE_HOME should NOT be defined in cm3.cfg.
 
If anyone wants to keep the cminstall program up-to-date, they should 
replace INITIAL_REACTOR_BROWSER and INITIAL_REACTOR_EDITOR 
with INITIAL_CM3_IDE_BROWSER and/or INITIAL_CM3_IDE_EDITOR .
 
Regards,
Randy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080128/3e892867/attachment-0002.html>