From: Erik Schilling <erik.schilling@linaro.org>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: Linux-GPIO <linux-gpio@vger.kernel.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH libgpiod RFC 0/3] bindings: rust: allow packaging of libgpiod-sys
Date: Fri, 26 May 2023 10:30:32 +0200 [thread overview]
Message-ID: <1b9968c1-77f3-6525-af57-a6c7808adb59@linaro.org> (raw)
In-Reply-To: <5f782ccd-ccff-67f8-22cf-7b9b1c7e2e3a@linaro.org>
>>> I am not exactly sure if I understood the above comment correctly. But
>>> if we want to eventually be able to consume gpiosim-sys via crates.io
>>> (or any packaging mechanism that relies on cargo package), then we will
>>> need to decouple the header and .so file referencing in a similar way.
>>> The easiest solution for me seems to be to just add a pkg-config file
>>> for gpiosim and use the same mechanism that I sketched for libgpiod-sys
>>> here.
>>
>> Yes we would like to get gpiosim via crates.io as well.
>
> Would simply adding a pkg-config for the gpiosim C lib be desirable?
> Then we can use the same mechanism. There is none existing at the
> moment. I am not sure whether that is intentional or just not done yet.
@Bartosz: Viresh said on IRC that I should ask you about this :). Shall
I just add a pkg-config for gpiosim? Or is that not desired for some reason?
- Erik
next prev parent reply other threads:[~2023-05-26 8:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 11:25 [PATCH libgpiod RFC 0/3] bindings: rust: allow packaging of libgpiod-sys Erik Schilling
2023-05-23 11:25 ` [PATCH libgpiod RFC 1/3] bindings: rust: drop legacy extern crate syntax Erik Schilling
2023-05-24 4:36 ` Viresh Kumar
2023-05-23 11:25 ` [PATCH libgpiod RFC 2/3] bindings: rust: remove unneeded cc dependency Erik Schilling
2023-05-24 4:36 ` Viresh Kumar
2023-05-23 11:25 ` [PATCH libgpiod RFC 3/3] bindings: rust: build against pkg-config info Erik Schilling
2023-05-24 5:01 ` Erik Schilling
2023-05-24 6:03 ` [PATCH libgpiod RFC 0/3] bindings: rust: allow packaging of libgpiod-sys Viresh Kumar
2023-05-24 8:09 ` Erik Schilling
2023-05-24 8:14 ` Viresh Kumar
2023-05-24 10:53 ` Erik Schilling
2023-05-26 8:30 ` Erik Schilling [this message]
2023-05-26 8:36 ` Bartosz Golaszewski
2023-05-26 8:59 ` Erik Schilling
2023-05-26 9:31 ` Viresh Kumar
2023-05-26 9:44 ` Erik Schilling
2023-05-24 9:17 ` Bartosz Golaszewski
2023-05-26 9:45 ` Erik Schilling
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=1b9968c1-77f3-6525-af57-a6c7808adb59@linaro.org \
--to=erik.schilling@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=viresh.kumar@linaro.org \
/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).