From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
Cc: Marcus Hoffmann <buildroot@bubu1.eu>
Subject: Re: [Buildroot] [PATCH v2 1/2] package/pico-sdk: new package
Date: Mon, 15 Jul 2024 21:44:14 +0200 [thread overview]
Message-ID: <20240715214414.4c4f2e96@windsurf> (raw)
In-Reply-To: <20240228202414.719244-1-buildroot@bubu1.eu>
Hello,
On Wed, 28 Feb 2024 21:24:12 +0100
Marcus Hoffmann via buildroot <buildroot@buildroot.org> wrote:
> package/Config.in | 1 +
> package/pico-sdk/Config.in | 9 +++++++++
> package/pico-sdk/pico-sdk.hash | 3 +++
> package/pico-sdk/pico-sdk.mk | 20 ++++++++++++++++++++
> 4 files changed, 33 insertions(+)
> create mode 100644 package/pico-sdk/Config.in
> create mode 100644 package/pico-sdk/pico-sdk.hash
> create mode 100644 package/pico-sdk/pico-sdk.mk
Entry in DEVELOPERS file was missing, so I added one.
> +define PICO_SDK_INSTALL_STAGING_CMDS
> + mkdir -p $(STAGING_DIR)/usr/include/pico-sdk
> + cp -r $(@D)/* $(STAGING_DIR)/usr/include/pico-sdk
Since it's not just headers, but a big pile of stuff, I changed to
install it to usr/share/pico-sdk instead.
Applied with those changes. Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-15 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 20:24 [Buildroot] [PATCH v2 1/2] package/pico-sdk: new package Marcus Hoffmann via buildroot
2024-02-28 20:24 ` [Buildroot] [PATCH v2 2/2] package/picotool: " Marcus Hoffmann via buildroot
2024-07-12 13:28 ` Thomas Petazzoni via buildroot
2024-07-15 18:31 ` Marcus Hoffmann via buildroot
2024-07-15 19:45 ` Thomas Petazzoni via buildroot
2024-07-15 19:44 ` Thomas Petazzoni via buildroot [this message]
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=20240715214414.4c4f2e96@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@bubu1.eu \
--cc=thomas.petazzoni@bootlin.com \
/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