Debugging is an important skill to have when developing large, complex pieces of software. The ReactOS project has a variety of resources and tools to help its developers identify problems. Several different debuggers are supported by the project and the operating system also generates debug messages that can be captured and viewed using a variety of methods. The below guides will show you how to set up ReactOS and the platform it is installed on to receive debug output as well as how to use a debugger to examine the executing code.
The Project provides a package of customized compilers and tools to help quickly set up everything needed to build ReactOS called the ReactOS Build Environment (RosBE) for both Windows and Unix. The BE includes: CMake 220.127.116.11 MinGW GCC 4.7.2 ninja Command-line SVN Client 1.8.5 Note that if one wishes to use Microsoft's toolchain either from the command line or Visual Studio, simply make sure the bin directory of RosBE is in the path.
This guide is intended to help new developers setup and familiarize themselves with the tools needed to obtain, compile, and work with the ReactOS source code, along with a few tips and best practices for the required tools if new developers are unsure what is the best approach to use. This guide does not provide a walkthrough of the ReactOS code base nor does it present an introduction to the NT architecture.
Revision control for the ReactOS source code is managed using Subversion. As such, users will need a SVN client. Developers working on Windows are encouraged to use TortoiseSVN as it helps simplify many of the tasks associated with managing source code. Source CodeThe ReactOS project's source code is split into several different folders. ReactOS: The operating system itself with required base components. svn://svn.reactos.org/reactos/trunk/reactos/Applications: Additional applications developed for use with ReactOS and bundled with each point release.