From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building Manual Errors
Date: Thu, 12 Sep 2013 18:37:45 +0200 [thread overview]
Message-ID: <20130912183745.64503913@skate> (raw)
In-Reply-To: <OF56171A80.616C14AA-ON86257BE4.0059D6AD-86257BE4.005A710F@rockwellcollins.com>
Dear Ryan Barnett,
On Thu, 12 Sep 2013 11:27:51 -0500, Ryan Barnett wrote:
> > Samuel: shouldn't we check the dependencies for building the manual
> > before someone attemps to do that? On my Linux Mint system
> > (=Ubuntu-based) I had to install asciidoc (which pulled in a lot of
> > tex deps) and w3m.
>
> One I idea I had to solve these dependancies issues between specific
> versions and packages for all the different distro's is to add all
> of the packages that are needed for building manual or any other
> buildroot maintenance script (stuff that is in support/scripts) to
> buildroot as host packages and then put together a
> buildroot_maintenance_defconfig that will build all of the packages
> need for the host system to run this scripts. Let me know what
> you think about that and we can maybe continue this discussion
> in a different thread.
My understanding is that asciidoc requires a very large number of TeX /
LaTeX dependencies which I really don't think we want to package in
Buildroot, so I believe doing this is not such a good idea.
Normal users shouldn't need to build the manual, since it's available
online for reading. Only developers will care about this, and I believe
installing asciidoc is a reasonable requirement for developers.
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:[~2013-09-12 16:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 23:49 [Buildroot] Building Manual Errors rjbarnet at rockwellcollins.com
2013-09-11 9:14 ` Samuel Martin
2013-09-11 11:13 ` Peter Korsgaard
2013-09-11 16:25 ` Ryan Barnett
2013-09-12 16:18 ` Thomas De Schampheleire
2013-09-12 16:27 ` Ryan Barnett
2013-09-12 16:37 ` Thomas Petazzoni [this message]
2013-09-12 16:51 ` Thomas De Schampheleire
2013-09-12 16:56 ` Thomas Petazzoni
2013-09-12 17:02 ` Thomas De Schampheleire
2013-09-12 17:54 ` Ryan Barnett
2013-09-19 15:03 ` Thomas De Schampheleire
2013-09-19 15:12 ` Ryan Barnett
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=20130912183745.64503913@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