All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Frost <tsmrnd0@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] add ghostscript to buildroot
Date: Wed, 23 Apr 2014 16:11:54 +0900	[thread overview]
Message-ID: <6387189.ReKiMDKImK@linux-qsenn> (raw)

Hi everyone,

I have been working with buildroot for little more than one year. I think is 
great tool. Some months ago I needed to cross-compile DCMTK library (it is not 
included in buildroot) for DICOM image file management and PACS connectivity. 
By following your online help I managed to add this package and successfully 
cross-compile and use it (if needed I can provide the files just let me know 
how).

Anyway, at this moment I need to cross-compile GhostScript (any version is 
good enough for me). But this is really complicated, I'm getting errors every 
where. I notice that openwrt has already included GhostScript 
(https://code.google.com/p/wl500g-repo/source/browse/feeds/rtndev/ghostscript/Makefile?r=1336
) so at this moment I'm trying to port this package to buildroot. Buildroot 
and ?openwrt buildroot? are similar tools so I guess that with some 
modifications it can be added to Buildroot. But my Buildroot knowledge it not 
that good (I hope with more time and practice it gets better ;)).

I need GhostScript to convert ps files to the file that will be sent to the 
printer (I don?t know this format name). I already have a ppd parser, so I 
just need to convert the ps file to the other format to open ?/dev/usb/lp0? and 
write it inside. 

Question:

Is there any interest in adding Ghostscript package to buildroot in the near 
future?
Does anyone has some hints about porting packages from openwrt to buildroot 
that I can use as guide?

Thank you very much for your attention.
William Frost

             reply	other threads:[~2014-04-23  7:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23  7:11 William Frost [this message]
2014-04-24  6:53 ` [Buildroot] add ghostscript to buildroot Thomas De Schampheleire

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=6387189.ReKiMDKImK@linux-qsenn \
    --to=tsmrnd0@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.