1 ReactOS Build System Documentation
2 ==================================
6 To generate GNU make makefiles and building ReactOS do the following:
8 1) Go to the top-level reactos directory
9 2) Run the command: mingw32-make
11 This will start building ReactOS.
13 To build a bootable CD run the following command:
17 This will create ReactOS.iso in the top-level reactos directory.
20 Top-level XML Build File
21 ------------------------
22 The top-level xml build file (ReactOS.xml) is processed by rbuild. The following is an example of how it could look like:
25 <!DOCTYPE project SYSTEM "tools/rbuild/project.dtd">
26 <project name="ReactOS" makefile="Makefile.auto" xmlns:xi="http://www.w3.org/2001/XInclude">
27 <xi:include href="config.xml">
29 <xi:include href="config.template.xml" />
33 <define name="_M_IX86" />
34 <if property="DBG" value="1">
35 <define name="DBG" value="1" />
36 <property name="DBG_OR_KDBG" value="true" />
39 <include base="ReactOS">include</include>
41 <directory name="boot">
42 <xi:include href="boot/boot.xml" />
45 <module name="bootcd" type="iso">
52 It is possible to split an xml build file over several files. The include element in the xi namespace is used to accomplish this.
55 <xi:include href="config.xml">
57 <xi:include href="config.template.xml" />
62 href - Name of xml build file to include. The filename is relative to the location of the current xml build file.
73 This element is used to provide the name of an alternate file that is to be included if the first include file did not exists.
87 There can be one project per top-level XML build file. A project can only be defined in a top-level xml build file.
90 <project name="ReactOS" makefile="Makefile.auto" xmlns:xi="http://www.w3.org/2001/XInclude">
95 name - Name of the project.
96 makefile - Filename of the GNU makefile that is to be created.
102 define, directory, if, include, module, property
107 There can be zero or more modules per xml build file.
110 <module name="msvcrt" type="win32dll" extension=".dll" entrypoint="_DllMain@12" baseaddress="0x70000000" mangledsymbols="true">
115 name - Name of the module. Also the base name of the generated file if such file is generated for the particular module type.
116 type - Type of module. See below for an explanation of module types.
117 extension - Extension of the generated file if such file is generated for the particular module type.
118 entrypoint - Entrypoint symbol of the generated file if such file is generated for the particular module type.
119 baseaddress - Base address of the generated file if such file is generated for the particular module type.
120 mangledsymbols - Controls wether or not to pass --kill-at to dlltool. If this attribute has the value false then --kill-at is passed to dlltool. If the value is true, then --kill-at is not passed to dlltool. If the generated file exports C++ classes then this need to be true.
126 bootstrap, define, dependency, directory, file, if, importlibrary, include, invoke, library, property.
131 The module type determines the actions that is to be carried out to process the module. The defined module types are seen below:
132 buildtool - Builds a tool that can be run (invoked) when building ReactOS. Default extension is .exe when building on Windows and nothing when building on Linux. The entrypoint, baseaddress, and mangledsymbols module attributes are not applicable for this module type.
133 staticlibrary - Builds a static library containing object files that can be linked together with other modules. Default extension is .a. The entrypoint, baseaddress, and mangledsymbols module attributes are not applicable for this module type.
134 objectlibrary - Builds object files that can be linked together with other modules. Default extension is .o. The entrypoint, baseaddress, and mangledsymbols module attributes are not applicable for this module type.
135 kernel - Builds ntoskrnl.exe. Default extension is .exe. Default entrypoint is _NtProcessStartup.
136 kernelmodedll - Builds a kernel-mode DLL. Default extension is .dll. Default entrypoint is _DriverEntry@8.
137 kernelmodedriver - Builds a kernel-mode driver. Default extension is .sys. Default entrypoint is _DriverEntry@8.
138 nativedll - Builds a native DLL. Default extension is .dll. Default entrypoint is _DllMainCRTStartup@12.
139 win32dll - Builds a Win32 DLL. Default extension is .dll. Default entrypoint is _DllMain@12.
140 win32gui - Builds a Win32 GUI executable. Default extension is .exe. Default entrypoint is _WinMainCRTStartup. The baseaddress module attribute is not applicable for this module type.
141 bootloader - Builds a bootloader. The entrypoint, baseaddress, and mangledsymbols module attributes are not applicable for this module type.
142 bootsector - Builds one or more bootsector binaries. The entrypoint, baseaddress, and mangledsymbols module attributes are not applicable for this module type.
143 iso - Builds a bootable CD. The entrypoint, baseaddress, and mangledsymbols module attributes are not applicable for this module type.
148 A bootstrap element specifies that the generated file should be put on the bootable CD as a bootstrap file.
151 <bootstrap base="reactos" nameoncd="halmp.dll" />
154 base - Put file in this directory on the bootable CD. This attribute is optional.
155 nameoncd - Name of file on the bootable CD. This attribute is optional.
166 A define element specifies the name and (optionally) value of a define for the C/C++ compiler and resource compiler.
169 <define name="WINVER">0x501</define>
172 name - Name of define.
175 Value of define. The value is optional.
183 A dependency element specifies the name of a module (usually of type buildtool) that is to be processed before the current module.
186 <dependency>OtherModule</dependency>
200 A directory element specifies the name of a subdirectory.
203 <directory name="MyDirectory">
208 name - Name of directory.
214 directory, file, if, property.
219 A file element specifies the name of a file that is to be processed.
222 <file>MyFile.c</file>
236 An if element allows for conditional processing of other elements.
239 <if property="DBG" value="1">
244 property - Name of the property that is to be evaluated.
245 value - Value to compare to the value of the property. If the property has the specified value, then the subelements are processed.
251 define, directory, file, if, include, property.
254 Importlibrary element
255 ---------------------
256 An importlibrary element specifies that an import library should be generated which other modules can use to link with the current module.
259 <importlibrary definition="MyModule.def" />
262 definition - Filename of definition file (.def) used to generate the import library. The filename is relative to the current module.
273 An include element specifies an include directory for the C/C++ compiler and resource compiler.
276 <include base="MyLibraryModule">include</include>
279 base - Module or project which the value of this element is relative to. This attribute is optional. If left out, the include directory is relative to the position of the top-level xml build file.
282 Relative include directory.
290 An invoke element specifies the name of a module which is to be executed before the current module is processed.
293 <invoke module="wmc">
295 <inputfile>ntoskrnl.mc</inputfile>
298 <outputfile switches="-H">../include/reactos/bugcodes.h</outputfile>
299 <outputfile switches="-o">bugcodes.rc</outputfile>
307 Name of the module to execute.
315 An input element specifies a group of filenames that is to be passed as parameters to a build tool. Input filename parameters are located after output filename parameters on the command line.
329 An inputfile element specifies a filename that is to be passed as a parameter to a build tool.
332 switches - Switches that is passed as parameters just before the filename. This attribute is optional.
335 Name of file that is to be passed as a parameter to the build tool.
343 An output element specifies a group of filenames that is to be passed as parameters to a build tool. Output filename parameters are located before input filename parameters on the command line.
357 An outputfile element specifies a filename that is to be passed as a parameter to a build tool.
360 switches - Switches that is passed as parameters just before the filename. This attribute is optional.
363 Name of file that is to be passed as a parameter to the build tool.
371 An importlibrary element specifies the name of another module which is to be linked with the current module.
374 <library>MyLibraryModule</library>
380 Name of the module to link with.
388 A property element specifies the name and value of a property that can be used for conditional processing of the xml build file.
391 <property name="mypropertyname" value="mypropertyvalue" />
394 name - Name of property.
395 value - Value of property.