-
Notifications
You must be signed in to change notification settings - Fork 5
MonoGame Content Builder
NOTE: This is preliminary documentation of a feature in progress.
The MonoGame Content Builder (MGCB.exe) is a command line tool for building content on Windows, Mac, and Linux desktop systems.
Typically it is executed indirectly by VisualStudio or MonoDevelop when building content for MonoGame. Alternatively you can use it directly from the command line for specialized build pipelines or for debugging content processing.
The options are processed "left to right". When an option is repeated the last option is always wins.
/outputDir:<directory_path>
This is a required parameter when building content. It specifies the directory where all content is written.
/intermediateDir:<directory_path>
This is a required parameter when building content. It specifies the directory where all intermediate files are written.
/rebuild
An optional parameter which forces a full rebuild of all content.
/reference:<assembly_path>
An optional parameter which adds an assembly reference which contains importers, processors, or writers needed during content building.
/importer:<class_name>
An optional parameter which defines the class name of the content importer for reading source content. If the option is omitted or used without a class name the default content importer for the source type is used.
/processor:<class_name>
An optional parameter which defines the class name of the content processor for processing imported content. If the option is omitted used without a class name the default content processor for the imported content is used.
/processorParam:<name>=<value>
An optional parameter which defines a parameter name and value to set on a content processor.
/build:<content_filepath>
Instructs the content builder to build the specified content file using the previously set switches and options.
/@:<response_filepath>
This defines a text response file (sometimes called a command file) that contains the same options and switches you would normally find on the command line.
Each switch is specified on a new line. Comment lines are prefixed with #. You can specify multiple response files or mix normal command line switches with response files.
An example response file could look like this:
# Directories
/outputDir:bin/foo
/intermediateDir:obj/foo
/rebuild
# Build a texture
/importer:TextureImporter
/processor:TextureProcessor
/processorParam:ColorKeyEnabled=false
/build:Textures\wood.png
/build:Textures\metal.png
/build:Textures\plastic.png