Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] rpi-userland: new package
Date: Sun, 06 Jan 2013 23:09:38 +0100	[thread overview]
Message-ID: <87ehhyc6al.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <175bbe60c696b921f074714aac68427ae0561b22.1357505417.git.maxime.hadjinlian@gmail.com> (Maxime Hadjinlian's message of "Sun, 6 Jan 2013 21:56:21 +0100")

>>>>> "Maxime" == Maxime Hadjinlian <maxime.hadjinlian@gmail.com> writes:

 Maxime> Introducing a package to build the userland part of the Raspberry,
 Maxime> needed by anyone who would want to build a rootfs for a RaspberryPi.

Presumably it isn't REALLY needed, right? Only if you want to use the
GPU?

 Maxime> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
 Maxime> ---
 Maxime>  package/Config.in                                  |    1 +
 Maxime>  package/rpi-userland/Config.in                     |   18 +++++
 Maxime>  ...0002-Test-for-the-existence-of-execinfo-h.patch |   69 ++++++++++++++++++++
 Maxime>  ...make-vmcs.cmake-allow-to-override-VMCS_IN.patch |   26 ++++++++
 Maxime>  package/rpi-userland/rpi-userland.mk               |   20 ++++++
 Maxime>  5 files changed, 134 insertions(+)
 Maxime>  create mode 100644 package/rpi-userland/Config.in
 Maxime>  create mode 100644 package/rpi-userland/rpi-userland-0002-Test-for-the-existence-of-execinfo-h.patch
 Maxime>  create mode 100644 package/rpi-userland/rpi-userland-makefiles-0001-cmake-vmcs.cmake-allow-to-override-VMCS_IN.patch
 Maxime>  create mode 100644 package/rpi-userland/rpi-userland.mk

 Maxime> diff --git a/package/Config.in b/package/Config.in
 Maxime> index 9b50f4b..17205fe 100644
 Maxime> --- a/package/Config.in
 Maxime> +++ b/package/Config.in
 Maxime> @@ -580,6 +580,7 @@ source "package/collectd/Config.in"
 Maxime>  source "package/empty/Config.in"
 Maxime>  source "package/googlefontdirectory/Config.in"
 Maxime>  source "package/mobile-broadband-provider-info/Config.in"
 Maxime> +source "package/rpi-userland/Config.in"

I think 'hardware handling' makes more sense, so I've moved it there
instead.

 Maxime>  source "package/shared-mime-info/Config.in"
 Maxime>  source "package/snowball-init/Config.in"
 Maxime>  source "package/sound-theme-borealis/Config.in"
 Maxime> diff --git a/package/rpi-userland/Config.in b/package/rpi-userland/Config.in
 Maxime> new file mode 100644
 Maxime> index 0000000..646d74e
 Maxime> --- /dev/null
 Maxime> +++ b/package/rpi-userland/Config.in
 Maxime> @@ -0,0 +1,18 @@
 Maxime> +config BR2_PACKAGE_RPI_USERLAND
 Maxime> +	bool "RaspberryPi userland"

We normally keep the name short and lower case, so I've renamed to
'rpi-userland'.

 Maxime> +	depends on BR2_INSTALL_LIBSTDCPP
 Maxime> +	depends on BR2_LARGEFILE
 Maxime> +	help
 Maxime> +	  Raspberry Pi Userland contains the necessary library to use the
 Maxime> +	  VideoCore driver.
 Maxime> +
 Maxime> +	  Includes source for the ARM side code to interface to: 

Trailing spaces.

 Maxime> +	  EGL, mmal, GLESv2, vcos, openmaxil, vchiq_arm, bcm_host, WFC, OpenVG.
 Maxime> +
 Maxime> +	  https://github.com/raspberrypi/userland/
 Maxime> +
 Maxime> +comment "RaspberryPi userland requires a toolchain with C++ support enabled"
 Maxime> +	depends on !BR2_INSTALL_LIBSTDCPP
 Maxime> +
 Maxime> +comment "RaspberryPi userland requires a toolchain with LARGEFILE support"
 Maxime> +	depends on !BR2_LARGEFILE

I've merged these two comments.

Committed with those changes, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-01-06 22:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06 20:56 [Buildroot] [pull request] Pull request for branch rpi-support Maxime Hadjinlian
2013-01-06 20:56 ` [Buildroot] [PATCH 1/3] libcofi: new package Maxime Hadjinlian
2013-01-06 21:02   ` Peter Korsgaard
2013-01-06 21:13     ` Maxime Hadjinlian
2013-01-06 21:18       ` Peter Korsgaard
2013-01-06 21:21         ` Maxime Hadjinlian
2013-01-06 22:02   ` Peter Korsgaard
2013-01-06 20:56 ` [Buildroot] [PATCH 2/3] rpi-userland: " Maxime Hadjinlian
2013-01-06 22:09   ` Peter Korsgaard [this message]
2013-01-06 22:13     ` Maxime Hadjinlian
2013-01-06 22:17       ` Yann E. MORIN
2013-01-06 22:22         ` Maxime Hadjinlian
2013-01-06 23:37       ` Floris Bos
2013-01-06 22:10   ` Peter Korsgaard
2013-01-06 22:14     ` Maxime Hadjinlian
2013-01-06 20:56 ` [Buildroot] [PATCH 3/3] rpi-firmware: New package Maxime Hadjinlian
2013-01-06 22:12   ` Peter Korsgaard
2013-01-06 22:15     ` Maxime Hadjinlian
  -- strict thread matches above, loose matches on Subject: below --
2013-01-05 22:55 [Buildroot] [pull request] Pull request for branch rpi-support Maxime Hadjinlian
2013-01-05 22:55 ` [Buildroot] [PATCH 2/3] rpi-userland: new package Maxime Hadjinlian
2013-01-05 14:10 [Buildroot] [pull request] Pull request for branch rpi-support Maxime Hadjinlian
2013-01-05 14:10 ` [Buildroot] [PATCH 2/3] rpi-userland: new package Maxime Hadjinlian
2013-01-05 15:18   ` Samuel Martin
2013-01-05 16:23     ` Maxime Hadjinlian
2013-01-05 16:33       ` Samuel Martin
2013-01-05 17:39     ` Thomas Petazzoni
2013-01-05 20:12       ` Maxime Hadjinlian
2013-01-05 20:21         ` Samuel Martin
2013-01-05 15:23   ` Yann E. MORIN
2013-01-05 15:41   ` Alex Bradbury
2013-01-05 16:27     ` Maxime Hadjinlian
2013-01-06  2:26   ` Floris Bos
2013-01-06 10:28     ` Maxime Hadjinlian
2013-01-06 13:50       ` Floris Bos

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=87ehhyc6al.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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