Latest Mass-Distributed Version
- Version 5.2.4 was distributed on 8 December, 2006
- Errata (with fixes) for this version:
1) For unix/linux builds of the "managed" libraries, the "args.o" target was accidentally left undefined in each of
the makefiles in "managed/make". To correct this, add the
following 3 lines to the make files of interest to you. I
put them right before the line beginning "jp2.o ::". Be
sure to preserve the initial tab characters on the second
and third of these lines.
args.o :: ../../apps/args/args.cpp
$(CC) $(CFLAGS) -I../../coresys/common \
-c ../../apps/args/args.cpp -o args.o
Also, in the "kdu_hyperdoc" target, change the line:
$(CC) $(C_OPT) -I../../coresys/common \
to read (again, remember not to remove any tabs from makefiles):
$(CC) $(C_OPT) -I../../coresys/common -I../../apps/args \
2) For some reason, the "settings.cs" file was lost from the "KduRender" C# demo project in "managed/managed_2005.sln" for
VS2005 builds. This is trivial to fix: just right click
on the project and select "Properties"; then select the "Settings" tab on the left hand side of the properties page
and follow the instructions (i.e., just click to create a
settings file).
3) A second problem with the "KduRender" and "KduRender2"
C# demo applications manifests itself on Win64 operating
systems. The problem here is that the build configurations
which shipped with version 5.2.4 were for "Any CPU". This
causes the 64-bit loader to be invoked, which cannot load
the 32-bit DLL, "kdu_mni". One solution would be to add a
64-bit build configuration for "kdu_mni", but the best
solution is to explicitly build an "x86" build configuration,
causing everything to run under WOW64 with the 32-bit loader.
To do this, click "Build->Configuration Manager", click <New> in the "Active Solution Platform" box and select an
"x86" configuration. Once you have done this, you can use <Edit> in the "Active Solution Platform" box to access a
dialog from which all the other configurations can be deleted,
leaving you just with the "x86" configuration. You can now
rebuild everything for this configuration and it should run
fine on both WIN32 and WIN64 systems.
4) For those who still build with Microsoft Visual Studio 6, a
minor backward compatibility problem was accidentally introduced
into the "kdu_show" demo application. To fix this, open the"kdu_show.cpp" file and locate the two lines beginning:
ON_COMMAND(ID_MODES_RECOMMENDED_THREADS, &CKdu_showApp::On...
and
ON_UPDATE_COMMAND_UI(ID_MODES_RECOMMENDED_THREADS, &CKdu_showApp::On...
Simply remove the prefix "&CKdu_showApp::" from each of these two
lines, since this qualifier is not backward compatible with VC6.
5) A minor bug exists in the "kdu_stripe_compressor" and "kdu_stripe_decompressor" objects, which occurs if an application
asks for recommended stripe heights without wanting to know about
the maximum stripe heights. In case this causes problems for one
of your own applications, the fix is easy. In each of the files "kdu_stripe_compressor.cpp" and "kdu_stripe_decompressor.cpp",
locate the line beginning
if ((comp_states[0].max_recommended_stripe_height==0) && ...
and remove the second condition, leaving it as
if (comp_states[0].max_recommended_stripe_height==0)
