From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package/links: enable building graphics mode with only fb driver
Date: Mon, 07 Jun 2021 15:17:46 -0000 [thread overview]
Message-ID: <20210607144654.5220A8B398@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=4cf6c02fb0b8b216e446c1230cb8f1eb61763211
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
The "fb" framebuffer driver needs GPM (mouse support) to compile,
but not DirectFB or Xorg.
The .mk file already has an optional dependency on GPM, so it doesn't
need to be added there.
Also added a Kconfig comment for easier discovery of the GPM
requirement.
Signed-off-by: Urja Rannikko <urjaman@gmail.com>
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
package/links/Config.in | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/package/links/Config.in b/package/links/Config.in
index 713f53da4e..cc2389c9f1 100644
--- a/package/links/Config.in
+++ b/package/links/Config.in
@@ -10,11 +10,15 @@ if BR2_PACKAGE_LINKS
config BR2_PACKAGE_LINKS_GRAPHICS
bool "use graphics"
- depends on BR2_PACKAGE_DIRECTFB || BR2_PACKAGE_XORG7
+ depends on BR2_PACKAGE_GPM || BR2_PACKAGE_DIRECTFB || BR2_PACKAGE_XORG7
select BR2_PACKAGE_XLIB_LIBXT if BR2_PACKAGE_XORG7
select BR2_PACKAGE_LIBPNG
help
- Enable graphics output for DirectFB or X11.
+ Enable graphics output for framebuffer, DirectFB or X11.
+ Framebuffer output requires GPM (console mouse).
Otherwise links will be text-mode only.
+comment "links graphics needs GPM, DirectFB or X11"
+ depends on !BR2_PACKAGE_GPM && !BR2_PACKAGE_DIRECTFB && !BR2_PACKAGE_XORG7
+
endif
reply other threads:[~2021-06-07 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210607144654.5220A8B398@busybox.osuosl.org \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.