From: Alfonso Sabato Siciliano <alf.siciliano@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@edbrowse.org
Subject: Re: [edbrowse-dev] tidySetOptBool vs tidySetOptInt on debian
Date: Sun, 8 Dec 2019 09:08:08 +0100 [thread overview]
Message-ID: <CA+nKRKD-kzaEedXd0P7U2Qi6gvVmMk+EO0b9SGsGBZSVR48Kmg@mail.gmail.com> (raw)
In-Reply-To: <20191107225601.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
Now it's obvious: my problem (and solution) with FreeBSD and Adam's problem
with
debian are different; so FreeBSD is off-topc here.
Anyway I seem
if (${CMAKE_SYSTEM_NAME} STREQUAL "FreeBSD")
set(TIDY_NAMES tidy5)
is a normal solution when an OS manages some different version of a library
renaming it.
In this specific case, it fixes incompatibility between headers and linked
library. Properly:
/usr/local/include/tidy/tidy.h and tidy.so are libtidy.0.99 (www/tidy-lib
port)
while the right is
/usr/local/include/tidy.h and tidy5.so (www/tidy-html5 port)
cmake finds the correct tidy.h but it cannot find the right ".so" without:
set(TIDY_NAMES tidy5), of course a better solution is welcome.
Alfonso
[-- Attachment #2: Type: text/html, Size: 883 bytes --]
next prev parent reply other threads:[~2019-12-08 8:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 17:15 Adam Thompson
2019-12-07 18:43 ` Dominique Martinet
2019-12-07 19:01 ` Alfonso S. Siciliano
2019-12-07 19:34 ` Dominique Martinet
2019-12-07 19:49 ` Adam Thompson
2019-12-07 21:45 ` alf.siciliano
2019-12-07 22:16 ` Dominique Martinet
2019-12-08 2:29 ` Geoff McLane
2019-12-08 3:56 ` Karl Dahlke
2019-12-08 8:08 ` Alfonso Sabato Siciliano [this message]
2019-12-08 8:07 ` Dominique Martinet
2019-12-08 13:22 ` Adam Thompson
2019-12-08 21:22 ` Geoff McLane
2019-12-07 19:44 ` Adam Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+nKRKD-kzaEedXd0P7U2Qi6gvVmMk+EO0b9SGsGBZSVR48Kmg@mail.gmail.com \
--to=alf.siciliano@gmail.com \
--cc=edbrowse-dev@edbrowse.org \
--cc=eklhad@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).