diff options
Diffstat (limited to 'README.macosx')
-rw-r--r-- | README.macosx | 65 |
1 files changed, 0 insertions, 65 deletions
diff --git a/README.macosx b/README.macosx deleted file mode 100644 index 15e1c71..0000000 --- a/README.macosx +++ /dev/null | |||
@@ -1,65 +0,0 @@ | |||
1 | libextractor on Mac OS X | ||
2 | ======================== | ||
3 | |||
4 | libextractor has two installation methods on Mac OS X: it can be installed | ||
5 | as a Mac OS X framework or with the standard `./configure; make; make install' | ||
6 | shell commands. The framework package is self-contained, but currently omits | ||
7 | some of the extractor plugins that can be compiled in if libextractor is | ||
8 | installed with ./configure; make; make install' (provided that the required | ||
9 | dependencies exist.) | ||
10 | |||
11 | Installing and uninstalling the framework | ||
12 | ========================================= | ||
13 | |||
14 | The binary framework is distributed as a disk image (Extractor-x.x.xx.dmg). | ||
15 | Installation is done by opening the disk image and clicking Extractor.pkg | ||
16 | inside it. The Mac OS X installer application will then run. The framework | ||
17 | is installed to the root volume's /Library/Frameworks folder and installing | ||
18 | will require admin privileges. | ||
19 | |||
20 | The framework can be uninstalled by dragging | ||
21 | /Library/Frameworks/Extractor.framework to Trash. | ||
22 | |||
23 | Using the framework | ||
24 | =================== | ||
25 | |||
26 | In the framework, the 'extract' command line tool can be found at | ||
27 | /Library/Frameworks/Extractor.framework/Versions/Current/bin/extract | ||
28 | |||
29 | The framework can be used in software projects as a framework or as a dynamic | ||
30 | library. | ||
31 | Framework usage: | ||
32 | >>> hello.c | ||
33 | #include <Extractor/extractor.h> | ||
34 | |||
35 | int main() | ||
36 | { | ||
37 | EXTRACTOR_ExtractorList *el; | ||
38 | el = EXTRACTOR_loadDefaultLibraries (); | ||
39 | EXTRACTOR_removeAll (el); | ||
40 | return 0; | ||
41 | } | ||
42 | gcc -o hello hello.c -framework Extractor | ||
43 | |||
44 | Dynamic library usage: | ||
45 | >>> hello.c | ||
46 | #include <extractor.h> | ||
47 | |||
48 | int main() | ||
49 | { | ||
50 | EXTRACTOR_ExtractorList *el; | ||
51 | el = EXTRACTOR_loadDefaultLibraries (); | ||
52 | EXTRACTOR_removeAll (el); | ||
53 | return 0; | ||
54 | } | ||
55 | gcc -I/Library/Frameworks/Extractor.framework/Versions/Current/include -o hello hello.c -L/Library/Frameworks/Extractor.framework/Versions/Current/lib -lextractor | ||
56 | |||
57 | Notice the difference in the #include line. | ||
58 | |||
59 | When using the framework as a dynamic library in projects using autotools, | ||
60 | one would most likely want to add | ||
61 | "-I/Library/Frameworks/Extractor.framework/Versions/Current/include" | ||
62 | to CPPFLAGS and | ||
63 | "-L/Library/Frameworks/Extractor.framework/Versions/Current/lib" | ||
64 | to LDFLAGS. | ||
65 | |||