From: "Léo Le Bouter via Guix-patches via" <guix-patches@gnu.org>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Cc: "47187@debbugs.gnu.org" <47187@debbugs.gnu.org>
Subject: [bug#47187] [PATCH] gnu: Add c-lightning.
Date: Sun, 21 Mar 2021 22:42:08 +0100 [thread overview]
Message-ID: <2e63a42572d05d3b3b0ecadfb3bf214c719ab560.camel@zaclys.net> (raw)
In-Reply-To: <SjeqBINTOoa3n9VqlQfXDB9T1V9IuwwKMATmcslp8baQBPODyoG4WdWDe6p9EgD9tORixvYDjBJ6XEG3y3_gpxhaC6_V_c6O69i8M3KLVTI=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
Hello!
> Okay.
>
> It is somewhat unclear to me however how to discover where the
> library is located.
> As far as I understand how autotools does it, it looks at some
> standard locations on `/`, but I am uncertain if that is how it
> actually works.
>
> For example if `libwally-core` is separately packaged, obviously it
> would install into a `/gnu/store/*` via a `--prefix` override.
> And if the dependent package were using autotools, it is somehow able
> to magically find where the `lib*.a` file is.
> However, C-Lightning does not actually use autotools (its build
> system predated my participation, I offered to port to autotools but
> this was declined), so I somehow need to emulate what autotools does
> in `--use-system-libraries` mode.
>
> I probably have to go hack some autotools package that trivially
> depends on `libwally-core` and see what the exact shell script is
> generated.
pkg-config if your deps provide .pc files! Otherwise I am actually not
sure of the lookup strategies.
> Note that AFAIK the Python bindings do not actually invoke any of the
> C-Lightning binaries, they just open the UNIX socket to the c-
> lightning daemon, so I think there is no need for `c-lightning`
> itself as an input.
Alright!
> Regards,
> ZmnSCPxj
Léo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-21 21:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 8:40 [bug#47187] [PATCH] gnu: Add c-lightning ZmnSCPxj via Guix-patches via
2021-03-16 9:13 ` Léo Le Bouter via Guix-patches via
2021-03-16 9:17 ` Léo Le Bouter via Guix-patches via
2021-03-16 11:27 ` ZmnSCPxj via Guix-patches via
2021-03-16 12:46 ` Léo Le Bouter via Guix-patches via
2021-03-17 3:42 ` ZmnSCPxj via Guix-patches via
2021-03-18 6:33 ` Léo Le Bouter via Guix-patches via
2021-03-18 16:54 ` ZmnSCPxj via Guix-patches via
2021-03-19 9:09 ` Léo Le Bouter via Guix-patches via
2021-03-19 19:31 ` ZmnSCPxj via Guix-patches via
2021-03-21 21:42 ` Léo Le Bouter via Guix-patches via [this message]
2021-03-26 18:13 ` Léo Le Bouter via Guix-patches via
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=2e63a42572d05d3b3b0ecadfb3bf214c719ab560.camel@zaclys.net \
--to=guix-patches@gnu.org \
--cc=47187@debbugs.gnu.org \
--cc=ZmnSCPxj@protonmail.com \
--cc=lle-bout@zaclys.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.
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.