From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 03/11] manual: update prerequisite.txt
Date: Wed, 21 Mar 2012 00:29:24 +0100 [thread overview]
Message-ID: <20120321002924.064d044a@skate> (raw)
In-Reply-To: <1332285001-12881-4-git-send-email-s.martin49@gmail.com>
Hello Samuel,
Good work. I'll try to reply to your introduction e-mail soon with
general comments. Below some specific comments on this patch.
Le Wed, 21 Mar 2012 00:09:53 +0100,
Samuel MARTIN <s.martin49@gmail.com> a ?crit :
> +Mandatory packages
> +~~~~~~~~~~~~~~~~~~
> +
> +* Build tools:
> +** +build-essential+ (only for Debian based system)
> +** +gcc+
> +** +g+++
> +** +autoconf+
> +** +automake+
> +** +libtool+
autoconf/automake/libtool are not needed.
> +** +bison+
> +** +flex+
> +** +gettext+
> +** +patch+
> +** +gawk+
gawk is not in the list of mandatory dependencies. For example, the
crosstool-ng package builds host-gawk because it needs gawk. So this
tool is not current part of the mandatory dependencies.
> +* Source fetching tools:
> +** +curl+
curl is not needed.
> +** +wget+
> +** +cvs+
> +** +git+
> +** +mercurial+
> +** +subversion+
None of the version control systems are part of the mandatory
dependencies. They will only be needed if the user has selected only
one package that needs to be fetched from one of those version control
system.
I know it's nitpicking, but I think that one of the good thing with
Buildroot is that the amount of mandatory dependencies on the host is
relatively small, so it would be a shame to mark all those tools are
mandatory even though they are not.
> +* Development libraries:
> +** +ncurses5+
> +** +lzo2+
> +** +lzma+
> +** +zlib1+
> +** +acl1+
> +** +uuid+
Except ncurses5, none of these libraries should be needed, I think. We
build host-zlib when needed, and I don't see where the other libraries
are coming from.
> +* Documentation generation tools:
> +** +asciidoc+
This one should be part of the optional dependencies, people /using/
Buildroot will not need to re-generate the documentation.
> +** +texinfo+
> +
> +[[requirement-optional]]
> +
> +Optional packages
> +~~~~~~~~~~~~~~~~~
> +
> +* Interface dependencies (requires development libraries):
s/Interface/Configuration interface/
> +** +ncurses5+ to use the 'menuconfig' interface
This one is already listed above as a mandatory dependency.
> +** +qt4+ to use the 'xconfig' interface
> +** +glib2+, +gtk2+ and +glade2+ to use the 'gconfig' interface
> +
> +* Development libraries:
> +** +glib2+
> +** +netpbm10+ (for +fbtest+)
> +** +python-xcbgen+ (for +Matchbox+ on Debian based system)
Huh, why?!? We build host-libglib2 when needed, and the other ones
should be fixed if they don't build correctly without those host
components installed.
> +** +jdk+ and and depending on the host system +gcj-compat+ for Java
> +development (for +java+, +jamvm+ and +gnu-classpath+)
We don't have Java packages anymore in Buildroot, at least at the
moment.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-20 23:29 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 23:09 [Buildroot] [PATCH 00/11] RFC: Manual content reorganization Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 01/11] manual: rework the whole documentation stub Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 02/11] manual: rework introduction.txt and update embedded-basics.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 03/11] manual: update prerequisite.txt Samuel MARTIN
2012-03-20 23:29 ` Thomas Petazzoni [this message]
2012-03-20 23:09 ` [Buildroot] [PATCH 04/11] manual: rework using.txt and update common-usage.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 05/11] manual: update make-tips.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 06/11] manual: update working-with.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 07/11] manual: update troubleshooting.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 08/11] manual: rework the intro of customize-rootfs.txt Samuel MARTIN
2012-03-20 23:09 ` [Buildroot] [PATCH 09/11] manual: update writing-rules.txt Samuel MARTIN
2012-03-20 23:10 ` [Buildroot] [PATCH 10/11] manual: update get-involved.txt Samuel MARTIN
2012-03-20 23:10 ` [Buildroot] [PATCH 11/11] manual: update contribute.txt Samuel MARTIN
2012-03-25 21:50 ` [Buildroot] [PATCH 00/11] RFC: Manual content reorganization Arnout Vandecappelle
2012-04-15 10:56 ` Samuel Martin
2012-04-25 20:23 ` Samuel Martin
2012-04-28 14:41 ` Arnout Vandecappelle
2012-05-06 21:04 ` Peter Korsgaard
2012-05-07 15:39 ` Samuel Martin
2012-05-12 23:18 ` Arnout Vandecappelle
2012-05-13 10:38 ` [Buildroot] [PATCH v2 " Samuel Martin
2012-05-13 10:38 ` [Buildroot] [PATCH v2 01/11] manual: rework the whole documentation stub Samuel Martin
2012-05-16 11:45 ` Thomas De Schampheleire
2012-05-13 10:38 ` [Buildroot] [PATCH v2 02/11] manual: rework introduction.txt and add embedded-basics.txt Samuel Martin
2012-05-16 11:50 ` Thomas De Schampheleire
2012-05-13 10:38 ` [Buildroot] [PATCH v2 03/11] manual: add prerequisite.txt Samuel Martin
2012-05-16 16:32 ` Thomas De Schampheleire
2012-05-16 21:45 ` Samuel Martin
2012-05-17 6:53 ` Thomas De Schampheleire
2012-05-13 10:38 ` [Buildroot] [PATCH v2 04/11] manual: rework using.txt and update common-usage.txt Samuel Martin
2012-05-16 16:47 ` Thomas De Schampheleire
2012-05-13 10:38 ` [Buildroot] [PATCH v2 05/11] manual: add make-tips.txt Samuel Martin
2012-05-16 16:55 ` Thomas De Schampheleire
2012-05-13 10:38 ` [Buildroot] [PATCH v2 06/11] manual: update working-with.txt Samuel Martin
2012-05-16 17:00 ` Thomas De Schampheleire
2012-05-17 10:02 ` Samuel Martin
2012-05-13 10:38 ` [Buildroot] [PATCH v2 07/11] manual: rework the intro of customize-rootfs.txt Samuel Martin
2012-05-16 17:02 ` Thomas De Schampheleire
2012-05-13 10:38 ` [Buildroot] [PATCH v2 08/11] manual: add troubleshooting.txt Samuel Martin
2012-05-16 17:04 ` Thomas De Schampheleire
2012-05-13 10:38 ` [Buildroot] [PATCH v2 09/11] manual: add writing-rules.txt Samuel Martin
2012-05-13 14:12 ` Yegor Yefremov
2012-05-16 17:15 ` Thomas De Schampheleire
2012-05-13 10:38 ` [Buildroot] [PATCH v2 10/11] manual: add get-involved.txt Samuel Martin
2012-05-13 11:25 ` Yegor Yefremov
2012-05-16 17:21 ` Thomas De Schampheleire
2012-05-13 10:38 ` [Buildroot] [PATCH v2 11/11] manual: add contribute.txt Samuel Martin
2012-05-13 12:16 ` Yegor Yefremov
2012-05-16 17:24 ` Thomas De Schampheleire
2012-08-01 20:43 ` [Buildroot] [PATCH 00/11] RFC: Manual content reorganization Thomas Petazzoni
2012-08-05 14:59 ` Samuel Martin
2012-11-09 21:25 ` Arnout Vandecappelle
2012-11-09 22:45 ` Samuel Martin
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=20120321002924.064d044a@skate \
--to=thomas.petazzoni@free-electrons.com \
--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