Difference between revisions of "Build Environment"

From ReactOS Wiki
Jump to: navigation, search
m
(Added old RosBE link back, noted new RosBE has had issues reported.)
Line 15: Line 15:
  
 
Instead of individually downloading all of the above you can also try the ReactOS Build Environment Setup - it includes everything which is needed to build ReactOS:
 
Instead of individually downloading all of the above you can also try the ReactOS Build Environment Setup - it includes everything which is needed to build ReactOS:
* [http://blight.reactos.at/reactos-be/ReactOS%20Build%20Environment%200.2-3.4.4.exe ReactOS Build Environment 0.2-3.4.4.exe]
+
* [http://blight.reactos.at/reactos-be/ReactOS%20Build%20Environment%200.1-3.4.2.exe ReactOS Build Environment 0.1-3.4.2.exe] - preferred.
 +
* [http://blight.reactos.at/reactos-be/ReactOS%20Build%20Environment%200.2-3.4.4.exe ReactOS Build Environment 0.2-3.4.4.exe] - beta, some issues.
  
 
== Building ReactOS ==
 
== Building ReactOS ==

Revision as of 02:41, 5 October 2005

Required files

For Windows

For latest releases go to http://www.mingw.org/download.shtml and download the following files:

For latest releases go to http://www.kernel.org/pub/software/devel/nasm/binaries/win32/ and download the following files:

Instead of individually downloading all of the above you can also try the ReactOS Build Environment Setup - it includes everything which is needed to build ReactOS:

Building ReactOS

Run the make file from the root directory of ReactOS. In order to build a bootable ISO image, you must first build freeldr then run "make install" ; next you must run "make bootcd" from the root ReactOS directory. The ISO image will be located in the root ReactOS directory when it is finsihed.

In a reactos/windows build environment mingw32-make must be used instead of make

Installation

First run MinGW-3.1.0-1.exe then unpack the other tarballs into the directory which you had installed MinGW.

Build Options

See the top-level Makefile for documentation on the build targets and environment variables available to configure desired build options.

Optional stuff

Subversion Client

Get yourself a Subversion client and download the sources from the Subversion repository.

Patching

You can use WinMerge to see changes in source code visually. This is particularly useful for submitting and reviewing patches.

  1. Create a new directory. For example C:\mingw.
  2. Extract the files mentioned above in the directory you just created. It is important that you extract gcc-update.zip last because it overwrites the buggy gcc.exe from gcc-2.95.3-fastcall.zip.
  3. In your install directory (C:\mingw in this example), you fill find the file mingw32.bat. Change the line that updates the PATH variable according to your install directory (add C:\mingw\bin in this example).
  4. Run mingw32.bat before you want to use mingw. You can call it from autoexec.bat or you can call it whenever you open a shell window.

See also