(file) Return to MOFcompiler.dxx CVS log (file) (dir) Up to [Pegasus] / pegasus / doc / DevManual

Diff for /pegasus/doc/DevManual/MOFcompiler.dxx between version 1.1 and 1.4

version 1.1, 2001/02/25 15:01:40 version 1.4, 2005/12/14 18:38:54
Line 1 
Line 1 
 /* /*
         $Log$  
         Revision 1.1  2001/02/25 15:01:40  karl  
         Add frames to manual  
   
 The file documents the Pegasus MOF compiler. The file documents the Pegasus MOF compiler.
 */ */
  
Line 24 
Line 20 
 Pegasus libraries when compiling into a Pegasus respository. Pegasus libraries when compiling into a Pegasus respository.
  
 The compiler requires that the input MOF files be in the current directory The compiler requires that the input MOF files be in the current directory
 unless TBD  or that a fully qualified path be given.  MOF files included using
   #pragma include must be in the current directory or in a directory specified
   by a -I command line switch.
  
 The compiler assumes that the file extension is .mof it is not specified. The compiler assumes that the file extension is .mof it is not specified.
   (This feature is not yet implemented.)
   
   The actual configuration and type of repository created depends on the
   characteristics of the repository implemented in Pegasus.
   See the description of the Pegasus repositories for more information.
  
 The actual configuration and type of repository created depends on the characteristics of the repository implemented in Pegasus. See the description of the Pegasus repositories for more information.  There are actually two compiler executable files.
   
   cimof.exe - This file operates through the client interface and acts as a
   remote compiler against an active CIM Repository
   cimmofl.exe - This file operates locally and directly against the repository.
  
 <B>EXAMPLE</B> <B>EXAMPLE</B>
  
 <PRE> <PRE>
        cimmof -w -Rtestrepository -IMOF MOF/CIMSchema25.mof         cimmof -w -Rtestrepository -I./MOF MOF/CIMSchema25.mof
 </PRE> </PRE>
  
 Compile the mof file defined in the directory MOF with the name CIMSchema25.mof Compile the mof file defined in the directory MOF with the name CIMSchema25.mof
Line 60 
Line 67 
 <LI>-h, --help  Print out usage message with command line definitions. <LI>-h, --help  Print out usage message with command line definitions.
  
  
 <LI>-E -                Perform only a syntax check on the input and creates no                                         repository.  Inthis mode, the compiler does not do the sematic checks that are done when MOFis added to a repository  <LI>-E -                Perform only a syntax check on the input and creates no                                         repository.  Inthis mode, the compiler does not do the sematic checks that are done when a CIM object is\
    added to a repository
  
 -w -- Suppresses ??? warnings.  -w -- Suppresses warning messages.
  
 <LI>-R<path> -  Specifies the path to the repository to be written. This is an <LI>-R<path> -  Specifies the path to the repository to be written. This is an
 alternative to the PEGASUS_HOME environment variable. If PEGASUS_HOME is set alternative to the PEGASUS_HOME environment variable. If PEGASUS_HOME is set
 the repository gets written to $PEGASUS_HOME/repository. The -R flag one the the repository gets written to $PEGASUS_HOME/repository. The -R flag one the
 command line overrides this with <path> specified in the directive. command line overrides this with <path> specified in the directive.
   Specify an absolute path.
   
 ?? relative or absolute???  
  
 <LI>--CIMRepository=<path> <LI>--CIMRepository=<path>
  
Line 78 
Line 84 
  
         cimmof -I~/testfiles ~/testfiles/main.mof         cimmof -I~/testfiles ~/testfiles/main.mof
  
 ?? relative or absolute ??  The path may be relative or absolute.
  
 </UL> </UL>
  
 Limitations of the current version  
   
 <EM>See the README in the COMPILER section of the Pegasus code tree for up-to-date  
 information on both the current Limitations and the current TODOs.</EM>  
   
   The compiler does not handle missing include files very sanely  
        right now.  It just skips them.  
   
 TODOs  
   
 <UL>  
   
 <LI>  - Parse and store references correctly  
   
 <LI> - Test parsing and storage of instances.  They probably don't work now.  
   
 <LI> - Rationalize the error logging scheme.  Things are spit randomly to  
     sterr now.  
   
 <LI>  - Extend error detection and handling.  
   
 </UL>  
 */ */
  


Legend:
Removed from v.1.1  
changed lines
  Added in v.1.4

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2