These switches can be used together with /build and/or /buildall as described below.
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.
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.
When this switch is used, BuildPlus will not launch Hyperview to display the newest project file at the end of the build. Also, BuildPlus will close after it is finished, even if there are errors.
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.
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).
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.
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.
For information on cleaning up temporary files when not running BuildPlus from the command line, see Cleaning up temporary/intermediate files.
With this switch, BuildPlus will use the DBDOC components in the Overrides directory, even if the overrides are turned off in Build Root Options. This does not change the saved setting in Build Root 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 Build Root Options so that it will always be used.
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.
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):
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:
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:
With /nominimize, BuildPlus will not be automatically minimized during the buildall.
DBDOC ©1996 - 2019 G. Michaels Consulting Ltd., all rights reserved. All other trademarks and registered trademarks are the property of their respective holders. Website source largely available under the terms of the AGPLv3.