Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mjpegtools: new package
Date: Sun, 18 Jan 2015 16:36:37 +0100	[thread overview]
Message-ID: <20150118153637.GL4275@free.fr> (raw)
In-Reply-To: <54B954C0.4010503@ou.edu>

Steve, All,

On 2015-01-16 12:13 -0600, Steve Kenton spake thusly:
> The mjpegtools programs are a set of tools
> that can do recording of videos and playback,
> simple cut-and-paste editing and the MPEG
> compression of audio and video under Linux.
> 
> http://mjpeg.sourceforge.net
> 
> Signed-off-by Stephen M. Kenton <skenton@ou.edu>
> ---
> Build tested with both uClibc and glibc against last nights snapshot
> 
> Every buildroot patch I generate turns out to be a learning experience
> So, let's see what I don't know this time ...

We were all learners at tsome point! ;-)

> Finding the higher level dependencies is still beyond me,

We basically have a set of toolchains for various presets, like with or
without threads, with or withour locales, with glibc or uclibc, on
different architectures, and we have some autobuilders that constantly
build random package selections with a randomly choosen toolchain:

    http://autobuild.buildroot.org/
    http://autobuild.buildroot.org/toolchains/

It is interesting to test with at least uClibc and glibc (like you did),
but also with a very "light" toolchain that has no fancy stuff: no
threads, no IPv6, no locales... such as this one:
    http://autobuild.buildroot.org/toolchains/configs/br-arm-basic.config

Use it as thus:

    wget -O defconfig http://autobuild.buildroot.org/toolchains/configs/br-arm-basic.config
    make BR2_DEFCONFIG=$(pwd)/defconfig defconfig
    make menuconfig    (select whatever package you want to test)
    make

It helps find the obvious basic requirements.

Then, for the not-so-obvious requirements, we have the autobuilders to
do all the testing. ;-)

> so I think
> I'll concentrate on learning to use git as a next step. Thanks for
> all the help getting these packages in shape.

Cheers! Thanks for the submissions! :-)

> Obviously I'm working
> on multi-media stuff. If there is a wish list for other related
> packages let me know and I'll try and work them up for submission.

Well, you can have a look at the Patchwork, there are quite a few
multi-media related patches pending:

    http://patchwork.ozlabs.org/project/buildroot/list/

[--SNIP--]

I did not find anything highly suspicious in that patch. Good. :-)

However, we now like to store hashes for the tarballs we download, so we
can test for integrity :

    http://buildroot.net/downloads/manual/manual.html#adding-packages-hash

Sourceforget provides SHA1 hashes when you click on the (i) button next
to the file you want to download.

Care to respin with that file added, please?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2015-01-18 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 18:13 [Buildroot] [PATCH] mjpegtools: new package Steve Kenton
2015-01-18 15:36 ` Yann E. MORIN [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=20150118153637.GL4275@free.fr \
    --to=yann.morin.1998@free.fr \
    --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