DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] docs: convert from using inkscape to ImageMagick tools
Date: Fri, 24 Apr 2015 09:23:09 -0400	[thread overview]
Message-ID: <1429881789-16060-1-git-send-email-nhorman@tuxdriver.com> (raw)

Requiring inkscape to convert svg files to png/pdf files, while functional is
difficult for ephemeral build environments (i.e. build systems in which a new
build root is setup for each build), as inkscape and its dependencies typically
totals over 128Mb of code.  Instead, lets use ImageMagick tools.  It gives you
the same output in a much more compact tool suite (512k).

Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
---
 mk/rte.sdkdoc.mk | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/mk/rte.sdkdoc.mk b/mk/rte.sdkdoc.mk
index 9952f25..b03bca5 100644
--- a/mk/rte.sdkdoc.mk
+++ b/mk/rte.sdkdoc.mk
@@ -47,7 +47,7 @@ endif
 ifeq '$V' '0'
 RTE_SPHINX_VERBOSE := -q
 RTE_PDFLATEX_VERBOSE := --interaction=batchmode
-RTE_INKSCAPE_VERBOSE := >/dev/null 2>&1
+RTE_CONVERT_VERBOSE := >/dev/null 2>&1
 endif
 
 RTE_PDF_DPI ?= 300
@@ -116,4 +116,5 @@ guides-%:
 $(foreach guide, $(RTE_GUIDES), $(foreach img, $(wildcard $(guide)img/*.svg), \
 	$(eval guides-pdf-$(notdir $(guide:/=)): $(img:svg=pdf))))
 %.pdf: %.svg
-	$(Q)inkscape -d $(RTE_PDF_DPI) -D -f $< -A $@ $(RTE_INKSCAPE_VERBOSE)
+	$(Q)convert -units PixelsPerInch $< -density 300 $@ $(RTE_CONVERT_VERBOSE)
+#	$(Q)inkscape -d $(RTE_PDF_DPI) -D -f $< -A $@ $(RTE_INKSCAPE_VERBOSE)
-- 
2.1.0

             reply	other threads:[~2015-04-24 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-24 13:23 Neil Horman [this message]
2015-04-27 11:01 ` Mcnamara, John

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=1429881789-16060-1-git-send-email-nhorman@tuxdriver.com \
    --to=nhorman@tuxdriver.com \
    --cc=dev@dpdk.org \
    /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).