Difference between revisions of "Build Environment"

From ReactOS Wiki
Jump to: navigation, search
m
Line 11: Line 11:
  
 
[[Image:RosBE.png|64px|left]]
 
[[Image:RosBE.png|64px|left]]
<span style="font-size: 12pt; font-weight: bold;">[http://downloads.sourceforge.net/reactos/RosBE-0.3.6.exe ReactOS Build Environment for Windows NT-compatible Operating Systems]</span>
+
<span style="font-size: 12pt; font-weight: bold;">[http://downloads.sourceforge.net/reactos/RosBE-0.3.7.exe ReactOS Build Environment for Windows NT-compatible Operating Systems]</span>
  
''Version 0.3.6''
+
''Version 0.3.7''
 
<p style="margin-bottom: 10px;">&nbsp;</p>
 
<p style="margin-bottom: 10px;">&nbsp;</p>
  

Revision as of 03:30, 29 July 2007

Introduction

To build ReactOS, you will need a suitable Build Environment.

As the current ReactOS Source Code is only compatible with specific versions of the compiler tools, only the official ReactOS Build Environment (RosBE) is supported by us.

So if you want to report problems, please first make sure that you use the latest version of the ReactOS Build Environment.

Download the Build Environment

There are two ReactOS Build Environments available, a version for Windows NT-compatible Operating Systems (Windows 2000, XP, Server 2003, ...) and a version for Unix-compatible operating systems (Linux, FreeBSD, ...).


RosBE.png

ReactOS Build Environment for Windows NT-compatible Operating Systems

Version 0.3.7

 

RosBE.png

ReactOS Build Environment for Unix-compatible Operating Systems

Version 0.3.6

Next Steps

Additionally, a Subversion (SVN) Client is needed to obtain the current source from the ReactOS Subversion repository. The current repository URL is svn://svn.reactos.org/reactos/trunk/reactos.

After setting up your build environment, see Building ReactOS for futher information.

You may want to use an IDE, so refer to this page.

Questions or Problems?

If you have problems or questions concerning the Build Environment, it's the best to ask in the #reactos-rosbe Chat channel.

Otherwise you can also try to contact Daniel Reimer or Colin Finck directly.