From: "Wiles, Keith" <keith.wiles@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Kevin Wilson <wkevils@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] dpdk 2.0 - how to build the documentation
Date: Sun, 2 Aug 2015 14:12:08 +0000 [thread overview]
Message-ID: <D1E372C8.257CC%keith.wiles@intel.com> (raw)
In-Reply-To: <1769062.Qdv563YfQL@xps13>
On 8/2/15, 12:41 AM, "dev on behalf of Thomas Monjalon"
<dev-bounces@dpdk.org on behalf of thomas.monjalon@6wind.com> wrote:
>2015-08-02 09:39, Kevin Wilson:
>> I have downloaded dpdk-2.0.0.tar.gz from dpdk.org
>> How do I build the documentation (pdf files)?
>
>They are available here:
> http://dpdk.org/doc/archives/dpdk-2.0/pdf/guides/
>If you want to build them:
> make doc-guides-pdf
>You'll need these packages:
> python-sphinx, inkscape, texlive-collection-latexextra,
>texlive-collection-fontsextra
Here is the command line I used for my Ubuntu install:
sudo apt-get install texlive-latex-extra texlive-fonts-extra python-sphinx
inkscape
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
Hope that help someone else
‹
Regards,
++Keith
Intel Corporation
prev parent reply other threads:[~2015-08-02 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 6:39 Kevin Wilson
2015-08-02 7:41 ` Thomas Monjalon
2015-08-02 14:12 ` Wiles, Keith [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=D1E372C8.257CC%keith.wiles@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=wkevils@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).