Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] How to figure out what a package is?
Date: Fri, 06 Nov 2009 19:57:12 +0100	[thread overview]
Message-ID: <87zl6zv5vb.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <hd1mof$7qt$1@ger.gmane.org> (Grant Edwards's message of "Fri\, 6 Nov 2009 17\:35\:12 +0000 \(UTC\)")

>>>>> "Grant" == Grant Edwards <grant.b.edwards@gmail.com> writes:

Hi,

 Grant> This sounds a bit stupid, but where do you find a description
 Grant> of what a given package is?

Normally the help text should say so.

 Grant> I've got a list of packages supported by buildroot.

 Grant> How do I know what, for example, the package named "lite" is?

By reading the help text of the package in 'make menuconfig'
(and optionally visiting the URL):

config BR2_PACKAGE_LITE
	bool "LiTE (toolbox engine)"
	depends on BR2_PACKAGE_DIRECTFB
	help
	   LiTE stands for LiTE is a Toolbox Engine. 
	   Its role is to facilitate the functions of DirectFB so that a
	   toolbox could be written on top of DirectFB with less effort.
	   As such LiTE has abstractions for the underlying graphics and
	   event systems.

	   See http://www.directfb.org/wiki/index.php/LiTE:Architecture

Is there anything in the above that isn't clear to you?

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2009-11-06 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 17:35 [Buildroot] How to figure out what a package is? Grant Edwards
2009-11-06 18:02 ` H Hartley Sweeten
2009-11-06 18:12   ` Grant Edwards
2009-11-06 18:24     ` Thiago A. Corrêa
2009-11-06 18:37       ` Grant Edwards
2009-11-06 19:00         ` Peter Korsgaard
2009-11-07 14:57           ` Thiago A. Corrêa
2009-11-06 18:57 ` Peter Korsgaard [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=87zl6zv5vb.fsf@macbook.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