These switches can be used together with /build and/or /buildall as described below.

Preventing automatic renaming of project (.dbdoc) files

/noren

• can be used with /build or /buildall

Usually, BuildPlus creates project files called Snapshot.DBDOC for each project, then automatically renames them to <Project Name>_<Build Date>.dbdoc. Using this switch stops the automatic renaming of project files.

“C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe” /build /noren

“C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe” /buildall /noren

For information on changing how new project files are named when not running BuildPlus from the command line, see Changing how project files will be named.

Preventing automatic launching of new project files

/noview

• can be used with /build (has no effect with /buildall)

When this switch is used, BuildPlus will close after it is finished, even if there are errors. As of 11.3 BuildPlus will by default not launch Hyperview to display the newest project file at the end of the build.

“C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe” /build /noview

If you use this switch with /nomsg, you will need to check occasionally that your builds are completing, since there will be no visible indicator of errors.

Automatic launching of new project files

/launch_hv

• can be used with /build (has no effect with /buildall)

When this switch is used, BuildPlus will launch Hyperview to display the newest project file at the end of the build.

“C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe” /build /launch_hv

Suppressing BuildPlus message boxes

/nomsg

• can be used with /build

By default, only message boxes indicating errors are shown, and non-error messages are suppressed. With this switch, error messages are also suppressed. For buildalls, no messages will ever appear (the /nomsg switch is automatically applied).

“C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe” /build /nomsg

If you use this switch with /noview, you will need to check occasionally that your builds are completing, since there will be no visible indicator of errors.

Preventing clean up of temporary files

/noclean

• can be used with /build or /buildall

During a build, many temporary files are created by Hyperlink. At the end of the build, BuildPlus usually deletes these. Using this switch will stop BuildPlus from deleting them.

"C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe” /build /noclean

"C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe” /buildall /noclean

For information on cleaning up temporary files when not running BuildPlus from the command line, see Cleaning up temporary/intermediate files.

Using programs from the overrides folder

/override

• can be used with /build or /buildall

With this switch, BuildPlus will use the DBDOC components in the Overrides directory, even if the overrides are turned off in BuildRoot Options. This does not change the saved setting in BuildRoot Options.

In general, you should not use this option unless you have been instructed to by GMCL. If you always need this option, you should turn it on in BuildRoot Options so that it will always be used.

“C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe” /build /override

“C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe” /buildall /override

For more information about using Overrides when not running BuildPlus from the command line, see Choosing to use programs in the Overrides directory for builds.

Excluding projects from a buildall

/exclude

• can be used with /buildall

Use this switch to specify projects that should be excluded from a buildall

Example: To build all the projects in the build roots C:\DBDOC_BUILDS and C:\test builds, except for B Mill (in C:\DBDOC_BUILDS) and Demo project (in C:\TEST_BUILDS):

"C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe" /buildall C:\DBDOC_BUILDS "C:\test builds" /exclude "C:\DBDOC_BUILDS\B Mill","C:\test builds\Demo Project"

Starting a buildall with a specific project

/start

• can be used with /buildall

With this switch, BuildPlus will begin with the project you specify and build all the projects that are after it alphabetically within the specified build root(s).

Example: The build root C:\DBDOC_BUILDS contains 20 projects, Project01 through Project20. To build Project07 through Project20:

"C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus" /buildall "C:\DBDOC_BUILDS" /start "C:\DBDOC_BUILDS\Project07"

Completing all builds when using /start

/fullcycle

• can be used with /buildall

With both /start and /fullcycle, BuildPlus will begin with the project specified, build every project in order through to the last project, then build the remaining projects, beginning with the first project.

Example: The build root C:\DBDOC_BUILDS contains 20 projects, Project01 through Project20. To build Project07 through Project20, and then Project01 through Project06:

"C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus" /buildall "C:\DBDOC_BUILDS" /start "C:\DBDOC_BUILDS\Project07" /fullcycle

Preventing minimizing of BuildPlus window

/nominimize

• can be used with /buildall (has no effect with /build)

With /nominimize, BuildPlus will not be automatically minimized during the buildall.

“C:\Program Files (x86)\GMCL\DBDOC\Programs\BuildPlus.exe” /buildall /nominimize

See also

• Importing BPI files via the command line
• Running BuildPlus with command line switch /build
• Running buildalls with command line switch /buildall
• Using command line switch /MOC