【正文】 atform configuration and build tool that works with the native piler toolchains on Microsoft Windows, Mac OS X, Linux and other platforms that the tool supports. However, the only supported build system for mobile applications in Qt Creator is qmake. Qt Creator also supports generic projects, where developers either use an unsupported build system, or do not want to associate a build system with their project at all. In cases like these, Qt Creator works as a code editor, and build settings can be manually specified for the project. Debugging Qt Creator is integrated with several external native debuggers: GNU Symbolic Debugger (gdb), Microsoft Console Debugger (CDB) and an internal JavaScript debugger. The following figure shows Qt Creator in Debug mode with the debugging tools pane below the code editor. In Debug mode, developers can perform mon debugging tasks, including the following: ? Interrupt program execution. ? Step through the program linebyline or instructionbyinstruction. ? Set breakpoints. ? Examine call stack contents. ? Examine and modify registers and memory contents of the debugged program. ? Examine and modify registers and memory contents of local and global variables. ? Examine the list of loaded shared libraries. ? Create snapshots of the current state of the debugged program and reexamine them later. Qt Creator displays the raw information provided by the native debuggers in a clear and concise manner. This simplifies the debugging process as much as possible without losing the power of the native debuggers. In addition to the generic IDE functionality provided by stack view, views for locals and expressions, registers, and so on, Qt Creator includes features to make debugging Qtbased applications easy. The debugger plugin understands the internal layout of several Qt classes, as well as most containers of the C++ Standard Library and some gcc and Symbian extensions. This deeper understanding is used to present objects of such classes in a useful way. If Qt Creator is installed as part of a Qt SDK, the GNU Symbolic Debugger is installed automatically and developers should be ready to start debugging after they create a new project. However, they can change the setup to use debugging tools for Windows, for example. Developers can connect mobile devices to the development PC and debug processes running on the devices. 7 Analyzing Code The memory available on devices is limited and you should use it carefully. Qt Creator integrates Valgrind code analysis tools for detecting memory leaks and profiling function execution. You must download and install the Valgrind tools separately to use them from Qt Creator. The QML Profiler is installed as part of Qt Creator. It allows you to profile your Qt Quick applications. Using Version Control Systems The remended way to set up a project is to use a version control system. Only project source files should be stored. Files generated by the build system or Qt Creator should not be stored. Other approaches are possible, but we do not remend using work resources, for example. Qt Creator supports a number of version control systems, integrating their use into the working environment. Supported systems include Bazaar, CVS, Git, Mercurial, Perforce, and Subversion. Configuration is straightforward, with mon settings for version control located together and features for specific version control systems located in Tools submenus. Output for each system is shown in the Version Control output pane. User interface elements for displaying mits and managing repositories are also provided for some systems. Getting Help From time to time,