Regarding this and your earlier message about VC6 compilation.
At the moment we recommend compiling djvulibre for windows
with MSVC 2008 express, which can be downloaded for
free from microsoft. Since I do not use windows for anything
but compiling djvulibre once a year, I have no reason to
purchase anything more than that.
I believe that MSVC 2008 can export dsw files,
but I do not know if the free version can.
Regarding the dll dependence.
The djvulibre executables also depend on translation files
to produce meaningful error messages. Dll-independent
versions are not really standalone either.
The best way to use these tools is to install them with the installer
and change the search path to include the djvulibre directory as well.
I use the thing in the control panel (system->advanced->environment variables) and that makes all the djvulibre program available all the time.
My suggestion is for you to download MSVC 2008 Express
and follow directions from the README_win32 files to
compile djvulibre yourself. Then you can change djvulibre
from dll to static library and do exactly what you want.
- L.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Leon. I don't know if your message helped Monday2000, but I was happy to learn MSVC 2008 Express is free. I had not known that. I am actually surprised you don't use mingw to compile for Windows from Linux:
Hi,
I downloaded djvulibre-3.5.21 and sadly discovered that its command-line utilities depend now on libdjvulibre.dll etc.
But I need also these command-line utilities in a dll-independent form - as it was always earlier.
Please, in future make 2 packages of Win32-DjVuLibre:
1. dll-dependent (as now)
2. dll-independent (as earlier)
Developers, you should now mention in the html documentation the exact dll-dependencies - for every Win32 DjVuLibre console utility.
Regarding this and your earlier message about VC6 compilation.
At the moment we recommend compiling djvulibre for windows
with MSVC 2008 express, which can be downloaded for
free from microsoft. Since I do not use windows for anything
but compiling djvulibre once a year, I have no reason to
purchase anything more than that.
I believe that MSVC 2008 can export dsw files,
but I do not know if the free version can.
Regarding the dll dependence.
The djvulibre executables also depend on translation files
to produce meaningful error messages. Dll-independent
versions are not really standalone either.
The best way to use these tools is to install them with the installer
and change the search path to include the djvulibre directory as well.
I use the thing in the control panel (system->advanced->environment variables) and that makes all the djvulibre program available all the time.
My suggestion is for you to download MSVC 2008 Express
and follow directions from the README_win32 files to
compile djvulibre yourself. Then you can change djvulibre
from dll to static library and do exactly what you want.
- L.
Thanks Leon. I don't know if your message helped Monday2000, but I was happy to learn MSVC 2008 Express is free. I had not known that. I am actually surprised you don't use mingw to compile for Windows from Linux:
http://camltastic.blogspot.com/2008/10/mingw-compile-software-for-windows.html
But I suppose compiling under windows gives better compatibility for the DLL and allows you to test the build right away.
Bill
Can this instructions be easily adapted to crosscompiling DjVuLibre with mingw on Debian? At the moment I have no time to check it myself...
Best regards
Janusz