建立ReactOS你需要一个合适的构建环境。 目前ReactOS源代码是能够使用这两种编译开源(gcc,mingw…),和微软的编译器工具,与官方ReactOS构建环境(RosBE)推荐。 如果你想要报告问题,请首先确保您使用最新版本的ReactOS构建环境。

下载构建环境

ReactOS构建环境有两个,一个版本的Windows NT-compatible操作系统(Windows XP、Vista、7,等等)和Unix-compatible版本操作系统(Linux、FreeBSD、等等)。

窗户


RosBE.pngReactOS Windows NT-compatible OS的构建环境2.1.3版本


Unix和Linux


RosBE.pngReactOS Unix-compatible操作系统的构建环境2.1.2版本


下一个步骤

一个颠覆客户需要获得的电流源ReactOS Subversion存储库(阅读页面获取更多信息)。 的RosBe 0.3.7在Windows上,包括:一个SVN客户机 进入空”。 \ ssvn创建“目录并输入来源下载ReactOS来源。

设置构建环境后,明白了建筑ReactOS为进一步的信息。

包括公用事业

所有这些信息可以发现在RosBE通过输入帮助

BASEDIR

小命令,立即让你回到ReactOS源代码库目录。

CHARCH

改变ReactOS架构建设,对当前RosBE会话。 现在可能的架构:

  • i386

  • amd64

CHDEFDIR

改变ReactOS源目录为当前RosBE会话。

  • 以前的:切换到先前ReactOS源目录。

CHDEFGCC

用法:chdefgcc(路径)(类型)MinGW / GCC目录更改为当前RosBE会话。

  • 路径:路径设置主机或目标GCC。

  • 类型:设置为“目标”或“主机”

RADDR2LINE

主要文章:调试——翻译地址

用法:raddr2line[文件][地址)将程序地址转换为文件名和行号在ReactOS协助开发人员发现特定的bug。 如果选择不给你会提示。

  • 文件:这可以是一个全限定路径或者文件名(即可以使用部分的名字。 ntdll *]的可执行文件进行分析。 当仅使用一个文件搜索当前目录及其所有子目录。

  • 地址:地址翻译。

可鄙的人

简单的工具来管理不同的目录位置。 可鄙的人可以用来迅速改变从一个目录到另一个内部的提示,使其更容易去源在另一个目录。 包含在Windows和Unix的寻欢作乐。 可鄙的人可以通过以下参数:

  • 列表目前:列出所有的快捷方式。

  • 添加:添加一个快捷方式列表。

  • 编辑:编辑一个快捷方式列表。

  • 快速眼动:从列表中删除一个快捷方式。

  • def:切换到默认的目录位置,在每个RosBE开始启用。

如果你想使用一个目录快捷方式,例如一个名字树干,就进入短尾箱和程序将切换到目录设置快捷键。

SSVN

仅Windows。 创建、更新或清理你的ReactOS源代码树或显示本地和在线的修订号树。

  • 更新:更新修订或特定的一个当第二个参数指定一个。

  • 创建:创建一个新的ReactOS源代码树。

  • rosapps:创建/更新ReactOS RosApps源代码树。

  • rostests:创建/更新ReactOS RosTests源代码树。

  • 清理:清理和修复源树中的错误。

  • 状态:显示当前本地和在线修改数字。

更新

仅Windows。 更新所有文件的RosBE最近的文件。

  • 删除X:删除更新Nr X。

  • 信息X:显示信息更新Nr X。

  • nr X:Re / Nr X安装更新。

  • 重置:删除更新缓存。 不推荐。

  • 状态:显示最近的状态可用,不安装更新。





To build ReactOS you will need a suitable build environment. Currently ReactOS Source Code is able to be compiled using both open source (gcc, mingw, …), and Microsoft's compiler tools, with the official ReactOS Build Environment (RosBE) being recommended. If you want to report problems, please first make sure that you use the latest version of the ReactOS Build Environment.

Contents

1 Download the Build Environment

1.1 Windows

1.2 Unix and Linux

2 Next Steps

3 Included Utilities

3.1 BASEDIR

3.2 CHARCH

3.3 CHDEFDIR

3.4 CHDEFGCC

3.5 RADDR2LINE

3.6 SCUT

3.7 SSVN

3.8 UPDATE

4 Questions or Problems?

Download the Build Environment

There are two ReactOS Build Environments available, a version for Windows NT-compatible operating systems (Windows XP, Windows Vista, 7, etc.) and a version for Unix-compatible operating systems (Linux, FreeBSD, etc.).

Windows

ReactOS Build Environment for Windows NT-compatible OS Version 2.1.3

For older versions, please have a look at our ReactOS SourceForge project page

Unix and Linux

ReactOS Build Environment for Unix-compatible Operating Systems Version 2.1.2

For older versions, please have a look at our ReactOS SourceForge project page

System Requirements: Please look at the README file for detailed information about the needed packages and other requirements.

Next Steps

A Subversion client is needed to obtain the current source from the ReactOS Subversion repository (read that page for more information). As of RosBe 0.3.7 on Windows, an SVN client is included: Go into the empty ".\Source" directory and type "ssvn create" to download the ReactOS source.

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

Included Utilities

All these Information can be found in RosBE, too by typing help.

BASEDIR

Small command which immediately sets you back to the ReactOS Source Base Directory.

CHARCH

Change the Architecture to build ReactOS for, for the current RosBE session. Possible Architectures are right now:

i386

amd64

CHDEFDIR

Change the ReactOS source directory for the current RosBE session.

previous: Switch to the previous ReactOS source directory.

CHDEFGCC

Usage: chdefgcc [PATH] [TYPE]Change the MinGW/GCC directory for the current RosBE session.

Path: Path to set the Host or Target GCC to.

Type: Set it to "target" or "host"

RADDR2LINE

Main article: Debugging – Translating Addresses

Usage: raddr2line [FILE] [ADDRESS]Translates program addresses into file names and line numbers to assist developers with finding specific bugs in ReactOS. If either of the options is not given you will be prompted for it.

FILE: This can be either a fully specified path or just the file name [you can use a partial name ie. ntdll*] of the executable to be analyzed. When using just a file the current directory and all sub-directories are searched.

ADDRESS: The address to be translated.

SCUT

Simple utility for managing different directory locations. SCUT can be used to quickly change from one directory to another inside the BE prompt, making it easier to go to source in another directory. Included in both the Windows and Unix BEs. You can pass the following parameters to scut:

list: Lists all shortcuts currently available.

add: Adds a shortcut to the list.

edit: Edits a shortcut on the list.

rem: Removes a shortcut from the list.

def: Switches to the default directory location, which is enabled on every start of RosBE.

If you want to use a directory shortcut, for example one with the name trunk, just enter scut trunk and the program will switch to the directory you set for this shortcut.

SSVN

Windows ONLY. Creates, updates or cleans up your ReactOS source tree or shows the revision number of the local and online trees.

update: Updates to HEAD revision or to a specific one when the second parameter specifies one.

create: Creates a new ReactOS source tree.

rosapps: Creates/Updates a ReactOS RosApps source tree.

rostests: Creates/Updates a ReactOS RosTests source tree.

cleanup: Cleans up and fixes errors in the source tree.

status: Show the current local and online revision numbers.

UPDATE

Windows ONLY. Updates all files of RosBE to the most recent files.

delete X: Deletes Update Nr X.

info X: Shows info about Update Nr X.

nr X: Re/Installs Update Nr X.

reset: Removes the Updates Cache. Not recommended.

status: Shows the recent status of available, non installed updates.

Questions or Problems?

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

Otherwise you can also try to contact Daniel Reimer (Windows version), Colin Finck (Unix version) directly.