| •1 |
USUAL AUTOTOOLS-BASED INSTALLATION |
| 2 |
__________________ |
| 3 |
|
| 4 |
Check that development package of libtiff is installed. |
| •5 |
Run: |
| 6 |
autoreconf --install |
| 7 |
./configure |
| 8 |
make |
| 9 |
make install |
| 10 |
Will install minidjvu executable into /usr/local/bin/, as well as |
| 11 |
various support files, documentation, development files, etc. |
| 12 |
|
| 13 |
|
| 14 |
|
| 15 |
BLOODSHED DEV-C++ |
| 16 |
_________________ |
| 17 |
|
| 18 |
In case if you want to compile it for Windows, there's a project |
| 19 |
file for Bloodshed Dev-C++. You will also need Libtiff for Windows, |
| 20 |
which may be found here: |
| 21 |
http://gnuwin32.sourceforge.net/packages/tiff.htm |
| 22 |
|
| 23 |
|
| 24 |
|
| 25 |
CUSTOM COMPILATION |
| 26 |
__________________ |
| 27 |
|
| 28 |
If you want to compile it all manually, read this. |
| 29 |
|
| 30 |
The release directory should be treated as an include directory |
| 31 |
(usually -I or /I option). That applies both to the library and the program. |
| 32 |
|
| 33 |
The library is built from sources in `minidjvu' subdirectory. |
| 34 |
The program is built from sources in `src' subdirectory. |
| 35 |
|
| •36 |
To enable TIFF support, define HAVE_LIBTIFF to 1, add libtiff include directory |
| 37 |
to the include path, then link against libtiff. |
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
OTHERWISE |
| 42 |
_________ |
| 43 |
|
| 44 |
Under Linux, you can always try something like |
| 45 |
|
| •46 |
g++ -Iinclude `find -name "*.c*"` -O2 -o minidjvu |
| 47 |
|
| 48 |
or, if you want TIFF support, |
| 49 |
|
| •50 |
g++ -DHAVE_LIBTIFF=1 -Iinclude `find -name "*.c*"` -O2 -ltiff -o minidjvu |
| 51 |
|
| 52 |
Under MSVC, watch for those __declspec directives in |
| 53 |
`minidjvu/base/0porting/0porting.h' - if you wish a DLL, turn them on. |
| 54 |
|
| 55 |
|
| 56 |
|
| 57 |
COMPILING ON MAC |
| 58 |
________________ |
| 59 |
|
| 60 |
That instruction was useful when there were configure scripts (are they |
| 61 |
really useful if they can't handle the Mac stuff?). |
| 62 |
|
| 63 |
/* This instructions were kindly sent to me by Alejandro David Weil. |
| 64 |
* Apparently, there are some problems with Macs, but I don't know why. |
| 65 |
*/ |
| 66 |
|
| 67 |
After some tries I got minidjvu built and running on mac os X panther. |
| 68 |
I had to make this: |
| 69 |
|
| 70 |
1. setup: |
| 71 |
export MACOSX_DEPLOYMENT_TARGET=10.3 |
| 72 |
|
| 73 |
2. run configure in this way: |
| 74 |
LDFLAGS="-L/sw/lib" ./configure |
| 75 |
|
| 76 |
3.before compile, modify file libtool changing the allow_undefined_flag to: |
| 77 |
allow_undefined_flag="-undefined dynamic_lookup" |
| 78 |
|
| 79 |
4. now run: |
| 80 |
make |
| 81 |
|
| 82 |
|
| 83 |
|
| 84 |
PORTING |
| 85 |
_______ |
| 86 |
|
| 87 |
Browse through `minidjvu/base/0porting.h' to see if it needs changing. |
| 88 |
What next, I don't know :) |