From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V2] dvd+rw-tools: new package
Date: Sat, 17 Jan 2015 16:34:24 -0600 [thread overview]
Message-ID: <54BAE370.7060404@ou.edu> (raw)
In-Reply-To: <XnsA425C51B017E9berndkuhlsPkbjNfxxIA@bernd-kuhls.de>
On 01/17/2015 12:22 PM, Bernd Kuhls wrote:
> according to Beyond Linux From Scratch you need libisoburn or a similar
> package which provides xorrisofs, otherwise "the growisofs command will not
> function properly"
> http://www.linuxfromscratch.org/blfs/view/svn/multimedia/dvd-rw-tools.html
>
> Did your package work without xorrisofs during your tests?
>
> Regards, Bernd
I was working on xorriso, dvdauthor, dvd+rw-tools and mjpegtools simultaneously
for my embedded project. Once they all worked I cleaned them up for submission.
GNU Xorriso includes all the libburnia libraries as well as the xorriso burner program.
FYI - Xorriso and dvdauthor were just committed. I did not think to check for hidden runtime
dependencies when I was working up the submission for those four packages individually. I just
worked on getting each of them to build in a clean buildroot snapshot for both uClibc and glibc.
If it was not a feature that I needed for my project right then it probably did not get
run time tested. So I can well believe there may be other dependencies that I did not discover.
Thanks for the tip, I'll try it out stand-alone and see what I find.
Steve
next prev parent reply other threads:[~2015-01-17 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 1:14 [Buildroot] [PATCH V2] dvd+rw-tools: new package Steve Kenton
2015-01-17 18:22 ` Bernd Kuhls
2015-01-17 22:34 ` Steve Kenton [this message]
2015-01-18 4:23 ` Steve Kenton
2015-01-18 15:11 ` Yann E. MORIN
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=54BAE370.7060404@ou.edu \
--to=skenton@ou.edu \
--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