edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Karl Dahlke <eklhad@comcast.net>, Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] edbrowse and edbrowse-js not communicating
Date: Tue, 15 Dec 2015 12:58:27 +0000	[thread overview]
Message-ID: <20151215125827.GA702@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <87d1u8mhtt.fsf@mushroom.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]

On Mon, Dec 14, 2015 at 08:55:26PM -0800, Chris Brannon wrote:
> Karl Dahlke <eklhad@comcast.net> writes:
> 
> > is it possible to have edbrowse check at run time
> > whether it has the correct and latest tidy, and issue a warning message if it does not?
> 
> Here's the problem.
> The old tidy code defined tidyReleaseDate.
> tidy-html5 defines tidyLibraryVersion and tidyReleaseDate, but they
> claim that tidyReleaseDate is deprecated.  So I don't know how long that
> will be available.
> For now, tidy-html5 is a drop-in replacement for the original tidy, so I
> suppose I could look at tidyReleaseDate to determine whether we're using
> old tidy code.
> A better solution would be to check at build time.
> That's quite doable with cmake, and I'm starting to get a handle on how
> to use it, so maybe that's the way to go.

Definitely, otherwise we leave ourselves open to all sorts of strangeness in the future.

> That begs a question.  At some point, should we consider deprecating all
> of our makefiles?

I was actually planning to send an email asking this,
particularly as I've now been successfully building with cmake on a bunch of
Debian machines. On the subject of cmake,
is there any chance we could add an install (and even uninstall)
rule just to make everything a bit more standard and in case we ever need to
compile parts of the code as shared objects?

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-12-15 12:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 15:32 Chuck Hallenbeck
2015-12-14 18:04 ` Chris Brannon
2015-12-14 18:12   ` Karl Dahlke
2015-12-15  4:55     ` Chris Brannon
2015-12-15 12:58       ` Adam Thompson [this message]
2015-12-17 10:44         ` Chris Brannon
2015-12-19 12:37           ` Adam Thompson
2015-12-19 12:58             ` Chris Brannon

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=20151215125827.GA702@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=chris@the-brannons.com \
    --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).