mirror of
https://github.com/reactos/reactos.git
synced 2025-01-05 22:12:46 +00:00
cae19acb7a
Let's add hacks to glue hacks together: In case rosvboxmgmt is started with its current directory not being the directory where it is along with hackssign_client.exe, then autoassign fails finding the hackssign client executable and thus, fails assigning drive letter. This is what happens when you starts rosvboxmgmt on boot with shell. So, when using autoassign, first look for the location of rosvboxmgmt and set our current directory there. This fixes rosvboxmgmt autoassign not working on boot. CORE-10032 ROSAPPS-303 svn path=/trunk/; revision=70578 |
||
---|---|---|
.. | ||
applications | ||
demos | ||
drivers | ||
lib | ||
nukecamp | ||
templates | ||
CMakeLists.txt | ||
COPYING | ||
Doxyfile | ||
readme.txt |
==================== ReactOS Applications ==================== This directory contains extra applicatons 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 "rosapps" in your build folder: 1. Copy the rosapps folder into the reactos\modules folder, or 2. Link reactos/modules/rosapps to rosapps # For Windows users cd %%_ROSSOURCEDIR%%\reactos\modules mklink /j rosapps %%_ROSSOURCEDIR%%\rosapps # For UNIX users cd \$$_ROSSOURCEDIR/reactos/modules ln -s \$$_ROSSOURCEDIR/rosapps rosapps