There was an idea to mark this function deprecated, such that if used the
developer would see a warning. But this was never implemented in a cross
platform way.
So for now revert to circa Jan 2015 when Jim added a build date to the
version.txt file. And now both LIBTIDY_VERSION and RELEASE_DATE macros are
established in CMakeLists.txt, and picked up in version.h.
The idea is the date will now march forward with the version number, side
by side in version.txt. Although have left tidy.c only emitting the
version on the --version command.
After this function has been marked deprecated for several release periods,
only then should consideration be given to potentially removing it.
First many other projects do this, and it seems a good choice.
Due mainly to windows where the static and shared libraries have the same
name, appended an 's' to the static library.
The tidy console app will use the static library, since to build the man
page tidy may need to be run before the shared libraries are installed.
And this makes the windows tidy exe a stand-alone app. No DLL install
issue.
This addresses issue #194, and possibly #190
The recommended place to run cmake is in the build/cmake directory,
but have changed a relative path to an absolute path which should
allow cmake to be run ANYWHERE!. See bottom of Issue #193
Also a few other minor tweak to CMakeLists.txt
Need to be able to clearly separate versions as we move forward towards
the final 5.0.0 release... Will try to remember to bump the point
as each fix is added so issue reports can be clear in which
version the problem exists.
Geoff McLane
Jim Derry
Pedro
Geoff McLane