reactos/reactos
Johannes Anderwald 2066acf1fa * remove unused export
svn path=/trunk/; revision=23550
2006-08-12 14:22:40 +00:00
..
base * allocate a terminating zero for every parsed argument 2006-08-12 14:17:44 +00:00
boot Computer name must always be uppercased, even despite it is an example 2006-08-11 09:05:24 +00:00
dll * remove unused export 2006-08-12 14:22:40 +00:00
drivers Skip first call to AddDevice 2006-08-07 11:03:35 +00:00
hal
include - DrawCaption 2006-08-08 20:00:53 +00:00
lib - Change DbgPrint prototype back to Alex's fix. His change was correct and my commit was wrong. 2006-08-06 19:57:24 +00:00
media Updated information about widl. 2006-07-30 13:39:42 +00:00
modules
ntoskrnl A thread may exit with a status code of 0. 2006-08-09 12:46:41 +00:00
regtests - Change DbgPrint prototype back to Alex's fix. His change was correct and my commit was wrong. 2006-08-06 19:57:24 +00:00
subsystems Fix build, for NDEBUG. 2006-08-08 20:51:59 +00:00
tools Force -fno-sibling-call-optimisation to every module's CFLAGs. This fixes *numerous* bugs (thanks to a bug in GCC itself), even in DBG=1 builds! 2006-08-08 12:41:56 +00:00
apistatus.lst
baseaddress.rbuild
config-ppc.template.rbuild Add software patent setting to build config template. 2006-07-22 19:38:18 +00:00
config.template.rbuild Add software patent setting to build config template. 2006-07-22 19:38:18 +00:00
COPYING
CREDITS
Doxyfile
INSTALL
LGPL.txt
Makefile
proxy.mak
ReactOS-ppc.rbuild
ReactOS.rbuild
README

========================
ReactOS Version 0.2.x
Updated June 23rd, 2004
========================

1. What is ReactOS?

   ReactOS is an Open Source effort to develop a quality operating system
that is compatible with Windows NT applications and drivers.

   The ReactOS project, although currently focused on Windows NT 4.0
compatibility, is always keeping an eye toward compatibility with
future Windows NT releases, that is, Windows 2000 (NT 5.0) and
Windows XP (NT 5.1).

More information is available at http://www.reactos.org/.

2. Building ReactOS

See the INSTALL file for more details.

3. More information

See the doc subdirectory for some sparse notes

4. Who is responsible

See the CREDITS file