From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: 18926@debbugs.gnu.org
Subject: bug#18926: cmake-build-system should set CMAKE_INSTALL_LIBDIR and CMAKE_PREFIX_PATH
Date: Sun, 01 Mar 2015 15:35:51 +0100 [thread overview]
Message-ID: <87r3t8g4zc.fsf@gnu.org> (raw)
In-Reply-To: <20150301095847.GA28759@debian> (Andreas Enge's message of "Sun, 1 Mar 2015 10:58:47 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> What would be desirable is the following:
> In the definition of a search path, we need an additional transformation
> (if it is not already there). We need to look for the regular expression
> (.+)/(lib|lib64|share)/.+\.cmake$
> or maybe
> (.+)/(lib|lib/[^/]+|share)/.+\.cmake$
> and put
> \1
> into CMAKE_PREFIX_PATH.
That’s not currently possible using the search path mechanism (and I
can’t imagine such weird semantics.)
I can imagine two solutions, in order of preference:
1. Find CMAKE_ environment variables that can be set using the search
path mechanism. Many environment variables are documented, is
there really none that we can use?
2. Add custom code to cmake-build-system.scm instead of using the
search path mechanism.
WDYT?
Thanks for taking the time to investigate!
Ludo’.
next prev parent reply other threads:[~2015-03-01 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 13:24 bug#18926: cmake-build-system should set CMAKE_INSTALL_LIBDIR and CMAKE_PREFIX_PATH 宋文武
2014-11-02 22:55 ` Ludovic Courtès
2014-11-03 13:44 ` 宋文武
2014-11-03 16:53 ` Ludovic Courtès
2014-11-04 12:42 ` 宋文武
2015-01-04 17:06 ` Ludovic Courtès
2015-02-08 18:14 ` Ludovic Courtès
2015-03-01 9:58 ` Andreas Enge
2015-03-01 14:35 ` Ludovic Courtès [this message]
2015-03-01 20:11 ` Andreas Enge
2015-03-14 15:11 ` Andreas Enge
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=87r3t8g4zc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=18926@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.