Q: I’ve noticed some files with the “vcx0_ib_” prefix (x can be “6”, “7”, or “8”) appear in the intermediate directory of my project during Incredibuild operation. Why does this occur?
A: This is normal. Incredibuild generates separate debug information and .idb files for each of the Agents participating in the build, and these are stored in the intermediate folder.Q: I’m comparing OBJ/EXE files that MSVC created to those of Incredibuild – and they’re not the same. Why?
A: There are some differences between Incredibuild and MSVC output, caused by debug information placement, timestamps in the binary files, OBJ file order in the linking phase, and so on. This is normal and does not affect the application’s behavior.Q: How can a user disable an Agent temporarily to make sure Incredibuild does not use the machine’s CPU?
A: By right-clicking the Incredibuild tray-icon and selecting Disable Agent. This can also be done remotely from the Coordinator Monitor.Q: I’m trying to run BuildConsole from the command line but keep getting the “‘BuildConsole’ is not recognized as an internal or external command, operable program or batch file.” error. Why?
A: The PATH environment variable is not set to the Incredibuild installation folder. Note that you can only use BuildConsole in computers that have Microsoft Visual Studio installed.Q: When building projects, only my machine’s Agent participates in the build!
A: This can be due to a number of reasons:- The Agent on your machine is not subscribed on the Coordinator machine. Check with your system administrator to see if your license allows adding your machine to the list of subscribed Agents.
- The extension package required for building the project is not allocated to your Agent. Allocating build system packages is done from the Coordinator Monitor. Check with your system administrator to see if your license allows allocation of the required extension package to your machine.
- The project contains a very small amount of files, and therefore they do not get distributed between the Agents.
- The Coordinator name or port set in the Agent Settings dialog in your machine is incorrect.
- The Coordinator is currently unavailable, either because the machine it is running on is shut down or disconnected from the network, or because the Coordinator service is not active.
- Your machine is disconnected from the network. Check network cable and settings.
- Network security restrictions are blocking TCP/IP access from your machine to either the Coordinator machine or the Agent machines in the network.
- Your trial period for using Incredibuild has expired.
Q: I can’t see the Incredibuild tray-icon display. How do I restore it?
A: From the Start menu, select Programs files->Incredibuild->Incredibuild Agent Tray-Icon to restore the tray-icon display. If you wish the Incredibuild tray-icon to always be displayed, verify that the Enable tray-icon display on system start-up option is selected in the Agent Settings dialog “Tray-Icon” page.Q: I can’t see the Incredibuild menu/toolbar in Microsoft Studio! Where’s it gone?
A: Use the “Visual Studio Add-in” section in the Agent Settings dialog to restore the menu and toolbar, using either the “Add-in Installation removal’ section or, for MSVC 6.0, the “Fix menu” and “Fix Toolbar” buttons. Note that the MSVC 6.0 add-in requires the add-in to be installed separately for each user using the machine. This can be done using this dialog. If only the toolbar is missing, the explanation could be that it is simply hidden. To check if this is the case, right-click on the toolbar section in Microsoft Studio and verify that all listed toolbars beginning with the word “Toolbar” are selected.Q: Browse information is not generated when building a project with Incredibuild, although it is generated when building with MSVC. Why?
A: Incredibuild keeps a global setting to determine whether to generate browse information or not. This can be set from the “Build System” tab in the Agent Settings dialog. You can also override this setting for a particular project when building a project from the Batch Build dialog.Q: I’m getting the following warning: “Incredibuild: build system warning: #import directives in the precompiled header should use the no_implementation attribute. See FAQ section in documentation for more details.”. What’s wrong?
A: Incredibuild is notifying you of an #import directive that was found in the precompiled header source file, without the “no_implementation” keyword. This is problematic for two reasons: You may get “file not found” compilation errors when a source file #includes a .TLI file that was generated by this PCH. Using #import with the “no_implementation” flag in the PCH file, as described below, will solve this.Not using this keyword may slow down compilation as a result of larger PCH files.The following excerpt is from the MSDN Library “#import” topic:“The implementation_only attribute is intended for use in conjunction with the no_implementation attribute as a way of keeping the implementations out of the precompiled header (PCH) file. An #import statement with the no_implementation attribute is placed in the source region used to create the PCH. The resulting PCH is used by a number of source files. An #import statement with the implementation_only attribute is then used outside the PCH region. You are required to use this statement only once in one of the source files. This will generate all the required wrapper member functions without additional recompilation for each source file.”Q: When compiling, I get a “No such file or directory” error on a header file/type library file.
A: Check if this file is generated by a custom build step or an MIDL step in another project in the workspace. If so, this may be caused by a missing inter-project dependency definition in the workspace. See the documentation section on “Dependency Issues” (under “Advanced Topics”) for more information.Q: When compiling, it seems that the compiler is using a different/out-of-date version of a header file/type library file.
A: See the answer in the previous question.Q: Looking at the Output view in the Build Monitor, it looks like the display is missing output for many files that have already been compiled. What’s wrong?
A: During compilation, Incredibuild buffers the build output for some of the configurations to make sure that different configurations’ outputs do not mix with each other. To view all output messages for each configuration, use the Projects view. The output display will gradually contain the entire build output.Q: When running an incremental build with MSVC after building with Incredibuild, I get the following build warning: “warning C4652: compiler option ‘Generate Browser Info’ inconsistent with precompiled header; current command-line option will override that defined in the precompiled header”. What is wrong?
A: There is a conflict between Incredibuild’s browse information creation options and the way MSVC handles browse information for that project. To overcome this, do one of the following:- If you wish to use browse information:
- Set the configuration’s project settings to generate browse information (this is done by selecting the browse info check boxes on both the C/C++ page and the Browse info page in MSVC’s project settings dialog).
- Set Incredibuild’s browse information creation settings (in the Agent Settings dialog) to create browse information for this configuration (this can be done by selecting “Always” or “According to ‘Generate browse info’ project setting”, or by using a matching search phrase).
- Rebuild the project.
- If you do not wish to use browse information:
- Set the configuration’s project settings NOT to generate browse information.
- Set Incredibuild’s browse information creation settings (in the Agent Settings dialog) NOT to create browse information for this configuration (this can be done by selecting “Never” or “According to ‘Generate browse info’ project setting”, or by using a matching search phrase).
- Rebuild the project.
Q: The Incredibuild Agent fails to start on my machine. What’s wrong?
A: This could be happening for a number of reasons. Here are some initial steps to help understand the cause of this:- If the Incredibuild Agent tray-icon display indicates an error graphic, click the tray-icon once to display the last error encountered by the Incredibuild Agent service, and see if this leads to the source of the problem.
- Try replacing the following files, which should appear in your Windows/System32 folder, by copying them from another machine, with the same operating system that has a working Agent installed:perfc009.datperfd009.dat If not, run the Windows setup installation to restore these system files.
- Contact Incredibuild Support and provide as much detail as you can about the problem.
Q: When running a build, some Agents start compiling files, but stop before the compilation is finished, causing the file’s compilation bar to disappear. What’s wrong?
A: This could be happening because of a network configuration error. For Incredibuild to operate properly, all of the following tests should work:- Ping the problem Agent from the building machine, using its IP address.
- Ping the problem Agent from the building machine, using its network name.
- Ping the building machine from the problem Agent, using its IP address.
- Ping the building machine from the problem Agent, using its network name.
Q: I’ve installed a permanent/temporary Incredibuild license, but when trying to build, I get a message saying my build will run in standalone mode. What am I doing wrong?
A: Either your Agent is unsubscribed, or the required build system extension package has not been allocated to your Agent. To correct this, do the following:- Open the Coordinator Monitor.
- Locate your Agent in the Agent list.
- If the ‘Status’ column specifies ‘Unsubscribed’, right-click the Agent and select Subscribe.
- If the ‘Subscribe’ option is grayed out, your license has reached its limit of subscribed Agents and you must first unsubscribe an Agent.
- If the ‘Packages’ column specifies ‘Helper’ or a different MSVC version from the one you are using to build your project, right-click the Agent and use the ‘Allocate Package’ option to allocate the appropriate build system extension package to your Agent.
Q: I’ve installed a permanent/temporary Incredibuild license supporting multiple CPUs/cores, but only one processor is used in builds. What should I do?
A: Your Agent is probably missing the “Multiple CPU(s)/Core(s)” extension package. To correct this, do the following:- Open the Coordinator Monitor.
- Locate your Agent in the Agent list.
- Right-click the Agent and select Allocate Package->Multiple CPU(s)/Core(s).
- If this option is grayed out, your license has used up all of its “Multiple CPU(s)/Core(s)” extension packages, and you must first deallocate this package from one of the other Agents.