What's wrong?Ī: Incredibuild is notifying you of an #import directive that was found in the precompiled header source file, without the "no_implementation" keyword. See FAQ section in documentation for more details.". Q: I'm getting the following warning: "Incredibuild: build system warning: #import directives in the precompiled header should use the no_implementation attribute. You can also override this setting for a particular project when building a project from the Batch Build dialog. This can be set from the " Build System" tab in the Agent Settings dialog. Why?Ī: Incredibuild keeps a global setting to determine whether to generate browse information or not. Q: Browse information is not generated when building a project with Incredibuild, although it is generated when building with MSVC. 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. If only the toolbar is missing, the explanation could be that it is simply hidden. Note that the MSVC 6.0 add-in requires the add-in to be installed separately for each user using the machine. Q: I can't see the Incredibuild menu/toolbar in Microsoft Studio! Where's it gone?Ī: 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. 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. How do I restore it?Ī: From the Start menu, select Programs files-> Incredibuild-> Incredibuild Agent Tray-Icon to restore the tray-icon display. Q: I can't see the Incredibuild tray-icon display. Your trial period for using Incredibuild has expired. Network security restrictions are blocking TCP/IP access from your machine to either the Coordinator machine or the Agent machines in the network. Your machine is disconnected from the network. 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. The Coordinator name or port set in the Agent Settings dialog in your machine is incorrect. The project contains a very small amount of files, and therefore they do not get distributed between the Agents. Check with your system administrator to see if your license allows allocation of the required extension package to your machine. Allocating build system packages is done from the Coordinator Monitor. The extension package required for building the project is not allocated to your Agent. Check with your system administrator to see if your license allows adding your machine to the list of subscribed Agents. The Agent on your machine is not subscribed on the Coordinator machine. Q: When building projects, only my machine's Agent participates in the build!Ī: This can be due to a number of reasons: Note that you can only use BuildConsole in computers that have Microsoft Visual Studio installed. Why?Ī: The PATH environment variable is not set to the Incredibuild installation folder. 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. This can also be done remotely from the Coordinator Monitor. Q: How can a user disable an Agent temporarily to make sure Incredibuild does not use the machine's CPU?Ī: By right-clicking the Incredibuild tray-icon and selecting Disable Agent. This is normal and does not affect the application's behavior. Why?Ī: 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. Q: I'm comparing OBJ/EXE files that MSVC created to those of Incredibuild – and they're not the same. idb files for each of the Agents participating in the build, and these are stored in the intermediate folder. Incredibuild generates separate debug information and. 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. If you do not find an answer here or in the Knowledge Base website page, please let us know by opening a ticket in our Support Center and we will try to respond as promptly as possible. We do our best to try and answer the most frequently asked questions in this section.
0 Comments
Leave a Reply. |