From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] package/duktape/duktape.pc.in: New file
Date: Sat, 17 Jul 2021 10:12:55 +0200 [thread overview]
Message-ID: <20210717101255.3dca9281@windsurf> (raw)
In-Reply-To: <20210705054100.2857251-2-aduskett@gmail.com>
On Sun, 4 Jul 2021 22:40:56 -0700
Adam Duskett <aduskett@gmail.com> wrote:
> Most distributions include a duktape.pc file bundled with the duktape
> development package. As the duktape source does not include a .pc file,
> add one to the package/duktape directory and install it to the staging
> directory. This is used by the polkit duktape patch later in the series.
>
> Signed-off-by: Adam Duskett <aduskett@gmail.com>
> ---
> package/duktape/duktape.mk | 4 ++++
> package/duktape/duktape.pc.in | 10 ++++++++++
> 2 files changed, 14 insertions(+)
> create mode 100644 package/duktape/duktape.pc.in
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-07-17 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 5:40 [Buildroot] [PATCH 0/5] Polkit: bump version to 0.119 and use duktape Adam Duskett
2021-07-05 5:40 ` [Buildroot] [PATCH 1/5] package/duktape/duktape.pc.in: New file Adam Duskett
2021-07-17 8:12 ` Thomas Petazzoni [this message]
2021-07-05 5:40 ` [Buildroot] [PATCH 2/5] package/polkit: bump version to 0.119 and use duktape Adam Duskett
2021-07-17 8:26 ` Thomas Petazzoni
2021-07-20 14:46 ` Adam Duskett
2021-07-20 14:54 ` Thomas Petazzoni
2021-07-20 15:18 ` Adam Duskett
2021-07-05 5:40 ` [Buildroot] [PATCH 3/5] package/polkit/S50polkit: new file Adam Duskett
2021-07-05 5:40 ` [Buildroot] [PATCH 4/5] support/testing: add polkit tests Adam Duskett
2021-07-05 5:41 ` [Buildroot] [PATCH 5/5] package/spidermonkey: drop package Adam Duskett
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=20210717101255.3dca9281@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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