From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V3] sdl2: new package
Date: Tue, 30 Jun 2015 00:22:42 +0200 [thread overview]
Message-ID: <20150629222241.GF3669@free.fr> (raw)
In-Reply-To: <1435609819-22256-1-git-send-email-guillaume.gardet@oliseo.fr>
Guillaume, All,
On 2015-06-29 22:30 +0200, Guillaume GARDET spake thusly:
> Signed-off-by: Guillaume GARDET <guillaume.gardet@oliseo.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Romain Naour <romain.naour@openwide.fr>
[--SNIP--]
> diff --git a/package/sdl2/Config.in b/package/sdl2/Config.in
> new file mode 100644
> index 0000000..c3f61f5
> --- /dev/null
> +++ b/package/sdl2/Config.in
> @@ -0,0 +1,32 @@
> +config BR2_PACKAGE_SDL2
> + depends on !BR2_STATIC_LIBS
> + bool "sdl2"
> + help
> + Simple DirectMedia Layer 2 - SDL2 is a library that allows
> + programs portable low level access to a video framebuffer,
> + audio output, mouse, and keyboard. It is not compatible with SDL1.
> +
> + http://www.libsdl.org/
> +
> +comment "sdl2 needs a toolchain w/ dynamic library"
> + depends on BR2_STATIC_LIBS
Either you put that comment at the beginning of the file, or at the end,
not in the middle.
The reason is that Kconfig, when it detects a dependnecy chain between
two adjacent symbols, will render the second symbol indented below the
first, like so:
config FOO
bool "foo"
config BAR
boll "bar'
depends on FOO
will be render in the menuconfig as:
[*] foo
[ ] bar
To show that 'bar' is a sub-option of 'foo'.
If you put the comment in between FOO nad BAR, then you break the
"dependency chain" and the symbols will be rendred as:
[*] foo
[ ] bar
which is less than ideal.
[I haven't looked at the rest of the file, as I know about nothing about
sdl2]
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-06-29 22:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 9:47 [Buildroot] [PATCH] sdl2: new package Guillaume GARDET
2015-03-13 10:39 ` Guillaume GARDET - Oliséo
2015-03-13 16:14 ` Thomas Petazzoni
2015-03-30 9:33 ` Guillaume GARDET - Oliséo
2015-03-30 12:50 ` Guillaume GARDET - Oliséo
2015-03-30 12:59 ` Thomas Petazzoni
2015-03-30 13:14 ` [Buildroot] [PATCH V2] " Guillaume GARDET
2015-04-22 8:35 ` Guillaume GARDET - Oliséo
2015-04-22 22:11 ` Romain Naour
2015-06-29 20:30 ` [Buildroot] [PATCH V3] " Guillaume GARDET
2015-06-29 22:22 ` Yann E. MORIN [this message]
2015-07-02 8:16 ` [Buildroot] [PATCH V4] " Guillaume GARDET
2015-07-05 18:21 ` Romain Naour
2015-07-06 12:17 ` Guillaume GARDET - Oliséo
2015-07-06 12:26 ` Thomas Petazzoni
2015-07-06 13:23 ` Guillaume GARDET - Oliséo
2015-07-06 13:34 ` Thomas Petazzoni
2015-07-07 22:19 ` Arnout Vandecappelle
2015-07-18 18:57 ` Romain Naour
2015-10-19 13:45 ` Vincent Stehlé
2015-10-21 20:56 ` Romain Naour
2015-10-21 21:09 ` Romain Naour
2015-10-21 21:22 ` Thomas Petazzoni
2015-10-21 21:25 ` Romain Naour
2015-07-07 22:22 ` Arnout Vandecappelle
2015-05-03 15:03 ` [Buildroot] [PATCH V2] " Bernd Kuhls
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=20150629222241.GF3669@free.fr \
--to=yann.morin.1998@free.fr \
--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