edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Adam Thompson <arthompson1990@gmail.com>
Cc: edbrowse-dev@edbrowse.org
Subject: Re: [edbrowse-dev] documentation respecting install prefix in cmake
Date: Wed, 25 Dec 2019 17:29:52 +0100	[thread overview]
Message-ID: <20191225162952.GA2846@nautica> (raw)
In-Reply-To: <20191225140551.GB93806@toaster>

Adam Thompson wrote on Wed, Dec 25, 2019:
> I think we do something like this for install prefix.  I'd write the patch
> but, as I said, my cmake knowledge is rather close to non-existent
> unfortunately.

I don't know much either, but it's always possible to test.

It looks like CMAKE_INSTALL_PREFIX is always defined (at least on my
version of cmake, 3.14.5), so I have submitted a patch in my cmake
branch https://github.com/martinetd/edbrowse/tree/cmake

Someone with an older version might want to check, but their
documentation does not say anything about it having changed recently so
it probably is ok:

They do talk about GNUInstallDirs though which has MANDIR and DOCDIR
variables we could use. That might be a better fix...


  reply	other threads:[~2019-12-25 16:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25 13:36 Adam Thompson
2019-12-25 13:47 ` Dominique Martinet
2019-12-25 14:05   ` Adam Thompson
2019-12-25 16:29     ` Dominique Martinet [this message]
2019-12-25 17:42       ` Geoff McLane
2019-12-26 18:43         ` Adam Thompson
2019-12-26 20:31           ` Geoff McLane
2019-12-26 20:51             ` Dominique Martinet
2019-12-27 15:58               ` alf.siciliano
2019-12-27 20:26                 ` Geoff McLane
2020-01-16 20:28                   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191225162952.GA2846@nautica \
    --to=asmadeus@codewreck.org \
    --cc=arthompson1990@gmail.com \
    --cc=edbrowse-dev@edbrowse.org \


* 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).