On Tue, 5 Dec 2017, Geoff McLane wrote:
Hi all,
Hi Jeff,
Sorry for the problems here, at least as far as HTML Tidy is concerned...
1. Yes, for some period recently, tidy.h was being installed in a
sub-directory,
'tidy'... That is into /usr/include/tidy/, or /usr/local/include/tidy/...
However the FindTidy.cmake also accounted for this... But this has been
**fixed** in the latest 5.6
The cmake default is /usr/local/include unless you add the cmake option -
$ cmake ../.. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Release
The second option is to ensure you are building the 'release' library. Some
cmake versions default to 'debug' unless this is specified...
I refreshed my download of tidy 5.6.0, and tried compiling it using your
suggested options (cutting and pasting), with the same result. "the
option -c is invalid in cpp" etc., etc.
Bummer.
But where ever it got installed to, you should be able to add -
$ export TIDY_ROOT=/path/to/tidy/install
when doing the edbrowse $ cmake .. [options]
Or even add it as a cmake option, -DTIDY_ROOT=/path/to/tidy/install
The CMakeFiles/FindTidy.cmake I supplied supports using this 'TIDY_ROOT'
define... either in environment or as an option...
This is so people like me, or Karl, and others, can build even later
versions of Tidy, and install them local to the build for testing edbrowse
with that version without disturbing the global release install of Tidy...
2. Yes, it takes time, too long in my book, for the latest tidy releases to
show
up in distributions. And my searching showed Debian is still back at 5.2
release.
There has been a 5.4 and now a 5.6 release since then...
And AFAIK Tidy has never been separated into 'tidy' and 'tidy-dev' packages,
but
that would not stop some distributions doing that... in most cases the needed
headers and libraries were included in the quite small 'tidy' package...
3. Not sure I agree cpp/c++ are preprocessors packages... running either of
them with --help shows -c is a valid option, but maybe that is beside the
point...
As I first stated tidy is also a pure C package, and adding that to the
CMakeLists.txt, like project(tidy C) will tell cmake to not look for
a cpp/c++ compiler... and should allow latest 5.6 tidy to be built, and
installed... from the zip, or repo...
And likewise for edbrowse CMakeLists.txt, like project (edbrowse C),
if edbrowse also only uses C...
And I too can not understand why g++/cpp/c++ would be broken in
Debian sid... That is a real puzzle... but as stated not required
for tidy, nor edbrowse... just change the project (...) lines...
HTH, Geoff.
--
Here In Northeast Ohio, The Moon is Waning Gibbous (93% of Full)
When your only tool is a hammer, everything looks like a nail.
Sent from Emil's iPhone.
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
