FileVerifier v0.2.0 beta
(C) 2007 Tom Bramer
FileVerifier comes with ABSOLUTELY NO WARRANTY. This is free software
and you are welcome to distribute and modify it under certain conditions.
See COPYING.txt for license agreement details.
This is a beta release. Not all features have been implemented or finalized.
The program may even crash or behave unexpectedly in certain instances.
With that said, the program should be quite usable. I have not tested the
binaries on many systems yet, so I don't know of any incompatability issues
yet. In general, the program requires at least Windows 2000. This release may
run on NT 4.0 with upgrades, but testing needs to be done to determine this
(it hasn't even been tested on Windows 2000 yet).
The binary distribution is compiled with Unicode support, and will definitely not
run on systems not supporting this (Windows 9x). However, the program can be
built as an ANSI version (Microsoft's terminology there), so it may be possible
to adapt the program to run on such operating systems.
INSTRUCTIONS FOR USE:
Extract binaries into a directory of your choice. Make sure your archiver
extracts using directory names or else the program won't start (in other
words, there should be a "Modules" subdirectory under the main program
directory). Just run fv.exe to start the program. The program has a menu
item that allows one to associate .FVA and .FVB files with the application
in Windows Explorer if desired. This is only registered for the currently
logged in user.
* The program crashes when trying to read Macintosh (CR line ending) text
files. This is to be fixed before the final release.
If you want to compile this, you are pretty much on your own on this one, but
if you REALLY want to do it, here's what you should need to do:
MINGW and MSYS (or possibly Cygwin tools pointing to the MINGW compilers).
Boost development libraries.
STLPort (any recent version, with extensions turned on (this is the default)).
Expat (again, probably any recent version).
UPX for compressing the executable.
1.) Edit the configuration file "config.mk" to set the location and names of the required
libraries as previously mentioned. Other tweaks may be necessary depending on
your build environment configuration (whether or not you have msys installed, etc.).
2.) Determine what type of build that you would like. There are currently four configurations:
For release builds, provide the make command with the "RELEASE=1" parameter, or for debug builds,
provide "DEBUG=1". For ANSI builds, provide "ANSI=1", and for unicode builds, "UNICODE=1" should
suffice. For example, if I want to build the release-unicode configuration, use:
make RELEASE=1 UNICODE=1
3.) Issue the "make" command in the root directory, using the parameters determined in the previous step.
This should build the program in two forms, fv.exe (uncompressed) and fv-release.exe (compressed and
stripped of extraneous symbols), both which reside in the build directory. Do a "make obj-clean" to
remove the intermediate files in build directory.
AUTHOR CONTACT INFO:
Tom Bramer <firstname.lastname@example.org>