WebSVN – gelsvn – Diff – /branches/MPC/MPC/README

 The Makefile, Project and Workspace Creator.
 Designed by Justin Michel (michel_j@ociweb.com) and Chad Elliott.
 Implemented by Chad Elliott (elliott_c@ociweb.com).
 A single tool (MPC) can be used to generate tool specific input (i.e.
 Makefile, dsp, vcproj, etc).  The generator takes platform and building
 tool generic files (mpc files) as input which describe basic information
 needed to generate a "project" file for various build tools.  These tools
 include Make, NMake, Visual C++ 6, Visual C++ 7, etc.
 sub-projects.  Things such as include paths, library paths and inter-project
 dependencies could be described in this base project and any project that
 inherits from it would contain this information as well.
 Another set of files, known as template input files (mpd files), provides
-the generator with the necessary information to fill platform and build
+the generator with the necessary information to fill platform and build tool
-tool specific information for dynamic and static library and binary
+specific information for dynamic and static library and binary executable
-executable projects.
+projects.
 Together, the generic input files and the template input files are applied
-toward a platform and build specific template (mpt file) to create the final
+toward a platform and build specific template (mpd file) to create the final
 product (a build tool specific input file).  These templates contain
 "variables" that are filled in by the project creator with information
 gathered through the mpc and mpd files and possibly by default values set
 within the template itself.
                 } else {
                   list_libs += c_other
                   ...
+                }
-                Due to limited parsing capabilities, the else is required to
+                If the else is provided, it is required to be on
-                be on the same line as the closing curly brace.
+                the same line as the closing curly brace.  You may
+                also negate the project type (using '!') which will cause
+                the specific to be evaluated for all types except the type
+                specified.
                 If a keyword is not recognized as a valid MPC keyword, it is
                 interpreted as a template value modifier.  In this
                 situation, this construct has the exact same restrictions as
                 the -value_template command line option.  See the USAGE file
                 } else {
                   source2.cpp
                   ...
+                }
-                Due to limited parsing capabilities, the else is required to
+                If the else is provided, it is required to be on
-                be on the same line as the closing curly brace.
+                the same line as the closing curly brace.  You may
+                also negate the project type (using '!') which will cause
+                the conditional to be evaluated for all types except the
+                type specified.
 requires        Specifies which features should be enabled in order to
                 generate the project file.
 avoids          Specifies which features should be disabled in order to
                 generate the project file.
 project {
   Define_Custom(MOC) {
     automatic        = 0
     command          = $(QTDIR)/bin/moc
-    postcommand      = echo "#include <some.h>" > <%temporary%> && \
+    postcommand      = echo <%quote%>#include <%lt%>some.h<%gt%><%quote%> <%gt%> <%temporary%> <%and%> \
-                       <%cat%> <%output%> >> <%temporary%> && \
+                       <%cat%> <%output%> <%gt%><%gt%> <%temporary%> <%and%> \
                        <%mv%> <%temporary%> <%output%>
     output_option    = -o
     inputext         = .h
     pre_extension    = _moc
     source_outputext = .cpp
                     that are automatic will have the side effect of possibly
                     adding files to Source_Files, Inline_Files, Header_Files
                     Template_Files, Resource_Files and Documentation_Files
                     depending on which extension types the command generates.
 dependent           If this is given a value, then a dependency upon that
-                    value will be placed upon all of the generated files.
+                    value will be given to all of the generated files.
                     The default for this is unset and no dependency will be
                     generated.
 command             The name of the command that should be used to process
                     the input files for the custom type.
 commandflags        Any options that should be passed to the command go here.
 If the custom output can not be represented with the above output extension
 keywords (*_outputext) and you have knowledge of the output files a priori,
 you can represent them with the '>>' construct.
 Below is an example that demonstrates the use of '>>'.  The command takes an
-input file name of foo.prp and produces two files that have a completely
+input file name of foo.prp and produces two files that have completely
-unrelated filename (i.e. foo !~ hello).
+unrelated filenames (i.e. foo !~ hello).
 project {
   Define_Custom(Quogen) {
-    automatic               = 0
+    automatic           = 0
-    command                 = perl quogen.pl
+    command             = perl quogen.pl
-    commandflags            = --debuglevel=1 --language=c++ \
+    commandflags        = --debuglevel=1 --language=c++ \
-                              --kernel_language=c++
+                          --kernel_language=c++
-    inputext                = .prp
+    inputext            = .prp
-    keyword quogenflags     = commandflags
+    keyword quogenflags = commandflags
+  }
   Quogen_Files {
     foo.prp >> hello.h hello.cpp
+  }
   Source_Files {
     hello.cpp
+  }
+}
+You can use the '<<' construct to represent dependencies for specific custom
+input file.  For instance, in the above example, assume that foo.prp depends
+upon foo.in, we would represent this by adding << foo.in as shown below.
+  Quogen_Files {
+    foo.prp >> hello.h hello.cpp << foo.in
+  }
-There is a new construct that can be used within a Define_Custom section.
+There is a construct that can be used within a Define_Custom section
-It is called 'optional' and can be used to represent optional custom output
+called 'optional' and can be used to represent optional custom output
 dependent upon particular command line parameters passed to the custom
 command.
 project {
   Define_Custom(TEST) {
 project: qt_specific {
   ...
+}
+Feature Files
+-------------
+Features are enabled and disable within feature files or through the use of
+the -features option (see USAGE for more details).  The first feature file
+read is always global.features found in the config directory.  The second
+feature file read is the project type name with .features appended
+(ex. vc71.features, make.features, etc.) which must be located in the same
+directory as the global.features file.  Lastly, the file specified by the
+-feature_file option is read if this option is used.
+Each successive feature file has precedence over the previous.  That is,
+if a feature has already been set previously it is overridden.  The
+-features option has precedence over feature files.
 Special Keywords Available to Templates
 ---------------------------------------
 project_name    This contains the name of the project.
 project_file    This contains the name of the output file.
 guid            This is used by the VC7 project and workspace creator.
 ) If a particular list is not specified (Source_Files, Header_Files, etc.)
    all of the files in the directory will be added to the corresponding list
    by extension
-) If custom files (ex. idl files) exist in the directory and
+) If the custom type is automatic and custom files (ex. idl files) exist in
-   the custom files components (ex. IDL_Files) are left defaulted (i.e. not
+   the directory and the custom files components (ex. IDL_Files) are left
-   listed) or the custom files components are specified and none of the
+   defaulted (i.e. not listed) or the custom files components are specified
-   custom generated files are listed in the corresponding lists
+   and none of the custom generated files are listed in the corresponding
+   lists
    the custom files are added to the custom files component list if they
    weren't specified and all of the (would be) generated files will be added
    to the front of the corresponding lists (source, inline and header lists)
-) If files are listed in the Source_Files list and
+) If files are listed in the Source_Files list and a corresponding header or
-   a corresponding header or inline file exists
+   inline file exists
    the corresponding file will be added to the corresponding list (if it
    isn't already there)
 ) If a sharedname is specified and staticname is not
    staticname is assigned the sharedname value (the same applies if
    staticname is specified and sharedname is not)
 ) If exename is specified then the project target is considered an
    executable.  If neither exename, sharedname or staticname are used and
-   any of the source files listed contains a "main", then the project target
+   any of the source files listed contains a language dependent "main", then
-   is considered an executable, otherwise it is considered a library.
+   the project target is considered an executable, otherwise it is considered
+   a library.
 ) If pch_header is not specified and a header file matches *_pch.h
    it is assumed to be the precompiled header file (the same applies to
    pch_source)

Subversion Repositories gelsvn

(root)/branches/MPC/MPC/README – Rev 68 → 71