mirror of
https://github.com/reactos/reactos.git
synced 2025-02-24 17:34:57 +00:00
![]() Indeed the RTL/NDK/whatever always explicitely uses ANSI and/or UNICODE string types where needed (and do not depend on tchar.h stuff). It is up to the given application to explicitely specify (in its CMakeLists.txt or elsewhere) whether it wants to define UNICODE or not. --> Fix the problem of having the UNICODE define magically being defined after including some NDK header. [DNSAPI][USER32_APITEST]: Explicitely use UNICODE functions where needed (and as was already done in other parts of the code). svn path=/trunk/; revision=74172 |
||
---|---|---|
.. | ||
apitests | ||
dibtests | ||
drivers | ||
dxtest | ||
kmtests | ||
regtests | ||
rosautotest | ||
testdata | ||
tests | ||
win32 | ||
winetests | ||
.gitignore | ||
CMakeLists.txt | ||
COPYING | ||
readme.txt |
==================== ReactOS Tests ==================== This directory contains various tests for ReactOS. Make sure you also have a copy of the rest of the ReactOS source before you attempt to build anything in this module. It is to be placed under "modules" subdirectory of a trunk checkout. No additional changes to build files are necessary, it'll be picked up automatically. To include "rostests" in your build folder: 1. Copy the rostests folder into the reactos\modules folder, or 2. Link reactos/modules/rostests to rostests # For Windows users cd %%_ROSSOURCEDIR%%\reactos\modules mklink /j rostests %%_ROSSOURCEDIR%%\rostests # For UNIX users cd \$$_ROSSOURCEDIR/reactos/modules ln -s \$$_ROSSOURCEDIR/rostests rostests