1 *********************************************************************************************
\r
2 ******************************************************* 1) License information
\r
3 *********************************************************************************************
\r
5 EasyHook - The reinvention of Windows API hooking
\r
7 Copyright (C) 2009 Christoph Husse
\r
9 This library is free software; you can redistribute it and/or
\r
10 modify it under the terms of the GNU Lesser General Public
\r
11 License as published by the Free Software Foundation; either
\r
12 version 2.1 of the License, or (at your option) any later version.
\r
14 This library is distributed in the hope that it will be useful,
\r
15 but WITHOUT ANY WARRANTY; without even the implied warranty of
\r
16 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
\r
17 Lesser General Public License for more details.
\r
19 You should have received a copy of the GNU Lesser General Public
\r
20 License along with this library; if not, write to the Free Software
\r
21 Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
\r
23 Please visit http://www.codeplex.com/easyhook for more information
\r
24 about the project and latest updates.
\r
29 Reporting bugs is the only chance to get them fixed! Don't consider your
\r
30 report useless... I will fix any serious bug within a short time! Bugs with
\r
31 lower priority will always be fixed in the next release...
\r
34 Please notice that you should always look into the application event log
\r
35 if something goes wrong, because EasyHook will often output extended error
\r
36 information there...
\r
38 *********************************************************************************************
\r
39 ***************************************************** 2) How to compile
\r
40 *********************************************************************************************
\r
42 Since EasyHook 2.5, compilation is dramatically simplified. Just compile once
\r
43 for "x64" and once for "x86". The native EasyHook DLLs will automatically be
\r
44 copied into their counterpart arch directory.
\r
46 The you will have to copy the following files into any desired "Deploy" directory:
\r
48 "Debug\x64\EasyHook64.dll" -> "Deploy\EasyHook64.dll"
\r
49 "Debug\x64\EasyHook64Svc.dll" -> "Deploy\EasyHook64Svc.dll"
\r
50 "Debug\x86\EasyHook32.dll" -> "Deploy\EasyHook32.dll"
\r
51 "Debug\x86\EasyHook32Svc.dll" -> "Deploy\EasyHook32Svc.dll"
\r
52 "Debug\x64\EasyHook.dll" -> "Deploy\EasyHook.dll"
\r
53 "Debug\x64\EasyHook.dll.xml" -> "Deploy\EasyHook.dll.xml"
\r
55 (optional; only required for kernel hooking)
\r
56 "Debug\x86\EasyHook32Drv.sys" -> "Deploy\EasyHook32Drv.sys"
\r
57 "Debug\x64\EasyHook64Drv.sys" -> "Deploy\EasyHook64Drv.sys"
\r
60 Of course this is not necessary for testing purposes. As long as you keep
\r
61 all test applications in either the "x86" or "x64" directory, they will
\r
62 run properly. The "Deploy" directory is meant to contain all files necessary
\r
63 to ship an application based on EasyHook. This is what you get with the
\r
64 "Binaries Only" package.
\r
67 *********************************************************************************************
\r
68 ***************************************************** 3) Prerequisites
\r
69 *********************************************************************************************
\r
71 Since the CRT is now statically compiled, you won't need the Visual Studio Redistributable
\r
72 package anymore. For testing purposes I would always recommend to use the DEBUG version...
\r