-
Notifications
You must be signed in to change notification settings - Fork 27
/
README.dll
executable file
·118 lines (90 loc) · 4.37 KB
/
README.dll
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
Creating and using a DLL
* Creating a DLL
* Using the DLL
Creating a DLL
There are multiple methods of creating a DLL:
* using CodeGear
* using Cygwin
* using Microsoft Visual Studio C++
* using MingW
Creating a DLL using CodeGear
To create a DLL using CodeGear you'll need:
* Embarcadero CodeGear C++ Builder
The provided CodeGear project files were created using the 2009
version. Note that some version of CodeGear have a broken
compiler/linker and you'll need to turn off code optimization
to be able to build libewf.
* The latest zlib source package including from the zlib project site:
http://www.gzip.org/zlib/
* The latest bzip2 source package including from the bzip2 project site:
http://www.bzip.org/
Extract the contents of the zlib source package to the directory containing the extracted libewf source.
Normally the extracted zlib source directory will have a version number e.g. zlib-1.2.7, to remain
version independent rename the directory to zlib.
Extract the contents of the bzip2 source package to the directory containing the extracted libewf source.
Normally the extracted bzip2 source directory will have a version number e.g. bzip2-1.0.6, to remain
version independent rename the directory to bzip2.
Make sure to check if your build environment defines the correct WINVER for your build.
The code uses WINAPI version specific functions based on WINVER.
You can define a custom WINVER in the CodeGear project files or in libewf-<version>/common/config_borlandc.h
You should be able to build the DLL using the provided project files.
Creating a DLL using Cygwin
To create a DLL using Cygwin you'll need:
Cygwin with the following packages:
* binutils
* gcc-core
* bison (for libodraw)
* flex (for libodraw)
* autoconf
* automake
* make
* libtool
* gettext
* libiconv
* zlib-devel
* bzip2-devel (optional but recommended)
* openssl-devel (optional but recommended)
* libuuid-devel (optional but recommended)
Building the library:
./configure
make library
You should end up with the following DLL:
libewf-<version>/libewf/.libs/cygewf-0.dll
Older versions of Cygwin might require e2fsprogs for libuuid support
Install the e2fsprogs package and run the commands as following:
LDFLAGS=-L/usr/lib/e2fsprogs ./configure
make library
Creating a DLL using Microsoft Visual Studio C++
To create a DLL using Microsoft Visual Studio C++ you'll need:
* Microsoft Visual Studio C++
The provided Visual Studio project files were created using
the 2008 express version. The express verion is available on the
Microsoft website
* Microsoft Windows SDK (if not already included) for the Windows Crypto API
The Windows SDK is available on the Microsoft website
* The latest zlib source package including from the zlib project site:
http://www.gzip.org/zlib/
* The latest bzip2 source package including from the bzip2 project site:
http://www.bzip.org/
Extract the contents of the zlib source package to the directory containing the extracted libewf source.
Normally the extracted zlib source directory will have a version number e.g. zlib-1.2.7, to remain
version independent rename the directory to zlib.
Extract the contents of the bzip2 source package to the directory containing the extracted libewf source.
Normally the extracted bzip2 source directory will have a version number e.g. bzip2-1.0.6, to remain
version independent rename the directory to bzip2.
Make sure to check if your build environment defines the correct WINVER for your build.
The code uses WINAPI version specific functions based on WINVER.
You can define a custom WINVER in the Microsoft Visual Studio C++ project files or in libewf-<version>/common/config_msc.h
You should be able to build the DLL using the provided project files.
Note that the project files contain a Release and VSDebug configuration.
If you want to create your own Microsoft Visual Studio project files note that libewf needs
to be compiled with the parameter /MD, because stderr is passed from the executables.
Creating a DLL using MingW
To create a DLL using MingW see README.mingw
You should end up with the following DLL:
libewf/.libs/libewf-2.dll
Using the DLL
Make sure you use define LIBEWF_DLL_IMPORT before including <libewf.h>,
During runtime the libewf DLL also needs the zlib DLL.
When the DLL was build with Microsoft Visual Studio, you'll also need the Microsoft Visual Studio redistributable DLLs
to run on other platforms than the build platform.