[docs] winedev: Update 'kernel' paths

Frédéric Delanoy frederic.delanoy at gmail.com
Thu Aug 15 14:48:35 CDT 2013

 en/winedev-coding.sgml  | 4 ++--
 en/winedev-kernel.sgml  | 4 ++--
 en/winedev-testing.sgml | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/en/winedev-coding.sgml b/en/winedev-coding.sgml
index a2d5daf..5cd7290 100644
--- a/en/winedev-coding.sgml
+++ b/en/winedev-coding.sgml
@@ -489,8 +489,8 @@ AC_CHECK_HEADER(foo.h, AC_DEFINE(HAVE_FOO_H))
-      When adding a new language, also make sure the parameters 
-      defined in  <filename>./dlls/kernel/nls/*.nls</filename> 
+      When adding a new language, also make sure the parameters
+      defined in <filename>dlls/kernel32/nls/*.nls</filename>
       fit your local habits and language.
diff --git a/en/winedev-kernel.sgml b/en/winedev-kernel.sgml
index cab6883..c787ff6 100644
--- a/en/winedev-kernel.sgml
+++ b/en/winedev-kernel.sgml
@@ -2178,7 +2178,7 @@ if (res != ERROR_SUCCESS) return res;
 	    which is called, hence using the default console's code page.  There
 	    are some other spots affected, but you can look in
-	    <filename>dlls/kernel</filename> to find them all.  All of this is
+            <filename>dlls/kernel32</filename> to find them all.  All of this is
 	    implemented in Wine.
@@ -2394,7 +2394,7 @@ if (res != ERROR_SUCCESS) return res;
 	    When entering a syslevel, the code (in
-	    <filename>dlls/kernel/syslevel.c</filename>) will check that a
+            <filename>dlls/krnl386.exe16/syslevel.c</filename>) will check that a
 	    higher syslevel is not already held and produce an error if so. This
 	    is because it's not legal to enter level 2 while holding level 3 -
 	    first, you must leave level 3.
diff --git a/en/winedev-testing.sgml b/en/winedev-testing.sgml
index 9f2d785..7581ef6 100644
--- a/en/winedev-testing.sgml
+++ b/en/winedev-testing.sgml
@@ -140,7 +140,7 @@
         The tests for a specific Wine library are located in a 'tests'
         subdirectory of the library directory. Each test is contained in a
-        file (e.g. <filename>dlls/kernel/tests/thread.c</filename>). Each
+        file (e.g. <filename>dlls/kernel32/tests/thread.c</filename>). Each
         file itself contains many checks concerning one or more related APIs.
@@ -151,7 +151,7 @@
         run the tests contained in the <filename>thread.c</filename> file of the
         kernel library, you would do:
-<prompt>$ </prompt>cd dlls/kernel/tests
+<prompt>$ </prompt>cd dlls/kernel32/tests
 <prompt>$ </prompt>make thread.ok

More information about the wine-patches mailing list