Command Line Options
|-cache[read|write]||Use the build cache.|
|-cacheinfo||Emit summary of objects in the cache.|
|-cachetrim [sizeMiB]||Reduce the size of the cache.|
|-cacheverbose||Provide additional information about cache interactions.|
|-clean||Force a clean build.|
|-compdb||Generate JSON compilation database for the specified targets.|
|-config [path]||Explicity specify the config file to use.|
|-dist||Enable distributed compilation.|
|-distverbose||Enable detailed logging for distributed compilation.|
|-fastcancel||[Experimental] Active fast cancellation on build failure.|
|-fixuperrorpaths||Reformat GCC/SNC/Clang error messages in Visual Studio format.|
|-forceremote||Force distributable jobs to only be built remotely.|
|-help||Show usage help.|
|-ide||Enable multiple options for IDE integration.|
|-j[x]||Explicitly set local worker thread count.|
|-monitor||Output a machine readable file for use by 3rd party tools.|
|-noprogress||Don't show the progress bar while building.|
|-nostoponerror||Don't stop building on first error.|
|-nosummaryonerror||Don't print the -summary output if there is an error.|
|-nounity||[Experimental] Individually build all files normally built in Unity.|
|-progress||Show the build progress bar even if it would otherwise be disabled.|
|-quiet||Don't show build output.|
|-report||Output a report at build termination.|
|-showcmds||Show command lines used to launch external processes.|
|-showdeps||Show known dependency tree for specified targets.|
|-showtargets||Show primary targets defined in build configuration.|
|-summary||Show a summary at the end of the build.|
|-verbose||Show detailed diagnostic information for debugging.|
|-version||Print version and exit.|
|-vs||[Deprecated] Same as -ide.|
|-wait||Wait for a previous build to complete before starting.|
|-wrapper||Wrapper mode for Visual Studio. (Windows only)|
|-console||Disable UI. (Windows Only)|
|-cpus=[n|-n|n%]||Control worker CPUs allocation.|
|-mode=[disabled|idle|dedicated]||Control worker availability.|
|-nosubprocess||Don't spawn as a sub-process.|
Enable usage of the build cache. The cache options need to be configured in the build configuration file.
The cache can be enabled as read only or write only with '-cacheread' or '-cachewrite'. This can be useful for automated build systems, where you might like one machine to populate the cache for read-only use by other users.
Use of '-cache' is equivalent to '-cachread' and '-cachewrite' together.
Emit summary of objects in the cache. This can be used to understand the total size of the cache and how quickly it is growing. (See the related -cachetrim)
Reduce the size of the cache to the specified size in MiB. This will delete items in the cache (oldest first) until under the requested size. (See the related -cacheinfo)
Provide additional information about cache interactions, including cache keys, explicit hit/miss/store information and performance metrics. This can be used to assist troubleshooting.
Force a clean build. The build configuration file is re-parsed and all exsiting dependency information is discarded. A build is performed as if building for the first time with no built files present.
Instead of building specified targets generate a JSON compilation database for them. Resulting compilation database will include entries for all source files from ObjectList and Library nodes that are dependencies of the specified targets.
Explicity specify the config file to use. By default, FASTBuild looks for "fbuild.bff" in the current directory. This options allows a file to be explicitly specified instead.
Enable distributed compilation. Requires some build configuration.
Print detailed information about distributed compilation. This can help when investigating connectivity issues. Activates -dist if not already specified.
[Experimental] Activate fast cancellation on build failure.
Normally, when a build fails, FASTBuild will stop spawning new tasks, but will allow any other concurrently running processes to complete. In some cases, these tasks can take a long time to complete. When activated, the -fastcancel option will allow FASTBuild to instead terminate those concurrent jobs.
Enables re-formatting of warnings, errors and notes for GCC/SNC & Clang to Visual Studio format. Additionally, relative paths are expanded to full paths. This allows these errors to be double-clickable inside Visual Studio.
Enabled automatically when '-vs' is used.
Prevents all local compilation of distributable jobs.
FASTBuild will normally utilize local CPU resources to compile distributable jobs in several situations, in order to improve performance:
- When there are no remote workers available (otherwise build would not complete)
- When all remote workers are busy and local CPUs would be idle
- When blocked on remote work
This option prevents local consumption of distributable jobs in all these cases. This will generally result in slower builds and may even prevent the build completing entirely. As such, this options should generally only be used for troubleshooting.
Additionally, this option disabled use of the cache.
NOTE: This option can prevent builds from completing (if no workers are available for example).
NOTE: This option will generally degrade build performance.
Prints command line usage information, as per the summary at the top of this page.
IDE integration mode. Enables several options that are commonly desired when running from within an IDE such as VisualStudio, XCode or kDevelop. The following options are enabled:
Generally, the default behaviour will give best performance, and this option should only be used in very specific situations.
The -j[x] option allows you to artificially control local parallelism by modifying the local thread pool size.
FASTBuild will normally determine the optimal number of local threads to use by detecting the number of hardware cores present on the host. The -j option allows you to override this.
Positive values for x can be used to set the number of tasks which can be performed locally in parallel. This can be used to limit CPU usage on a machine that needs to perform other work while compilation is in progress. Values greater than the number of physical processors are also accepted, but will almost always result in degraded performance.
A value of 0 for x indicates that no additional threads should be spawned, and build graph processing and compilation should occur on the same thread. This can be useful for build process debugging, especially when combined with the '-verbose' option.
This option has no direct bearing on distributed compilation, but modifying local parallelism will reduce the ability of FASTBuild to distribute work efficiently.
Output a machine readable file for use by 3rd party tools.
A machine readable file is written to %TEMP%/FastBuild/FastBuildLog.log and updated throughout the build. This file can be monitored by 3rd party applications to provide enhanced visualization of the build state.
Suppresses the progress bar that is normally shown while compiling.
This should be used when targetting compilation from within Visual Studio or another IDE. (or use -vs)
When encountering build errors, FASTBuild will normally stop as quickly as possible.
-nostoponerror instructs FASTBuild to instead build as much as possible before stopping when failures occur. This is useful if you want to see as many errors as possible in your compilation output.
NOTE: When specifying multiple targets to compile on the command line, -nostoponerror is implied.
The -nosummaryonerror option instructs FASTBuild to only print the -summary overview if the build completes successfully.
NOTE: When specifying -nosummaryonerror, -summary is implied if not already specified.
[Experimental] Individually build all files normally in Unity.
NOTE: When alternating between specifying -nounity and not, libraries may not relink when they should. The resulting executables are valid, but may contain the previous unity objects instead of the loose objects
Show the build progress bar even if it would otherwise be disabled.
FASTBuild shows a build progress bar unless it detects that the stdout has been redirected (indicating that it's not being run from a command prompt). You can override this behavior and force the progress bar to be enabled using -progress.
Don't show build output. Information about which items are being built and the overall state of the build will be suppressed.
Output a detailed report at the end of the build. The report is written to report.html in the current directory.
The build report contains details of:
- The build environment (version, cmd line used etc.)
- All items built.
- Cache utilization.
- Include file usage.
NOTE: This option will lengthen the total build time, depending on the complexity of the build.
Displays the full command lines passed to external tools as they are invoked.
This option is useful for debugging build configurations, where the -verbose mode is too spammy.
NOTE: This option may have an impact on build performance.
Displays the hierearchy of dependencies for the specified target(s). This can be useful for debugging build configurations.
If no target is specified, "all" is used.
NOTE: The dependencies shown will refelect the state as of the last completed build. i.e. dependencies that would be discovered during the next build will not be shown.
Displays the list of targets defined in the bff configuration file.
Displays a summary upon build completion.
Show detailed diagnostic information for debugging.
This can be used to provide more information when debugging a build configuration problem. It will display detailed information as the build configuration is parsed, as well as detailed information during the build, including full command line arguments passed to external executables.
It is usually useful to combine this flag with -j0 to serialize the build process and output (avoiding the output of different threads being mixed together).
Prints executable version information and exits. No configuration parsing or building is performed.
Queue build after an already running build completes.
Only one instance of FASTBuild can run at a time within the same root working directory. If you launch another FASTBuild while one is already running, the error "Another FASTBuild is already running." will be emitted.
If you wish to build multiple targets, you should specify them together on the command line. This allows for paralellization across both targets.
Alternatively, the -wait command line arg allows you to queue the second build, so instead of failing, it will start after the first build completes. This will be slower than if both targets were invoked together on the original command line.
Spawns FASTBuild via an intermediate sub-process to be able to cleanly terminate a build from Visual Studio.
When cancelling a build in Visual Studio, the FASTBuild process will be killed, with no opportunity to save the build database, resulting in lost compilation work. Specifying this option spawns an orpaphaned child process to do the actual work. When the parent process is terminated by Visual Studio, the child process detects this and cleanly shuts down.
If a subsequent "wrapper mode" build is initiated before the first terminates, FASTBuild will wait for this first process to complete.
Disable worker UI.
The FBuildWorker can run in a UI-less mode on Windows. (On OSX and Linux, the worker currently always runs in UI-less mode)
Control worker CPUs allocation.
The number of workers available is normally controlled through the UI of the FBuildWorker.exe. The "-cpus" command line option will override this as follows:
|-cpus=n||Value n will be used.|
|-cpus=-n||Value of NUMBER_OF_PROCESSORS-n will be used.|
|-cpus=n%||Specify number of CPUs as a percentage of NUMBER_OF_PROCESSORS.|
In all cases, the number used will be clamped between 1 and the NUMBER_OF_PROCESSORS environment variable.
NOTE: The newly overridden options will be saved and used on subsequent restarts of the worker.
Control worker availability.
The FBuildWorker.exe mode is normally controlled through the UI. The "-mode" command line option will override this as follows:
|-mode=disabled||Worker will accept no tasks.|
|-mode=idle||Worker will accept tasks when PC is considerd idle.|
|-mode=dedicated||Worker will accept tasks regardless of PC state.|
NOTE: The newly overridden options will be saved and used on subsequent restarts of the worker.
Don't spawn a sub-process copy of the worker.
By default, when the FBuildWorker is launched, it makes a copy of itself (FBuildWorker.exe.copy), launches the copy and terminates. The duplicate process monitors the original executable file for changes, and re-launches itself if the file is updated. In this way, the FBuildWorker.exe can be kept under revision control, and when synchronized to a new version, will automatically re-start.
The "-nosubprocess" option supresses this behaviour.