From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: fbv neutered
Date: Thu, 20 Aug 2009 16:24:14 +0200 [thread overview]
Message-ID: <4A8D5C8E.8030806@atmel.com> (raw)
In-Reply-To: <20090820042324.GC4952@smtp.west.cox.net>
Tom Rini skrev:
> On Wed, Aug 19, 2009 at 11:31:57PM -0400, Denys Dmytriyenko wrote:
>
>> On Wed, Aug 19, 2009 at 05:48:07PM +0200, Ulf Samuelsson wrote:
>>> I added "fbv" "frame buffer viewer" to the file system,
>>> and happily tried to watch my Mustang rental car.
>>>
>>> -- fbv did not recognize the file format.
>>>
>>> Generated a nice bmp file and tried this...
>>>
>>> -- fbv did not recognize the file format.
>>>
>>> I then checked the recipe:
>>>
>>>
>>> ---------------------------------
>>> CC="${CC}" ./configure --without-libungif --without-bmp \
>>> --without-libjpeg
>>> ---------------------------------
>>>
>>> Beats me why someone would want to have it built this way.
>
> Yes, I pushed it that way as I only needed it as a png viewer (we needed
> a simple "can we display graphics?" test program) and someone on IRC
> also only needed PNGs, I guess.
>
> Of course, it'd be pretty easy to add ungif/bmp/jpeg to the dependancies
> list and recompile if you wanted more support.
>
Anyone mind if I make it the default?
ungif breaks, so I might skip this for simplicity right now.
>>> Is there another application one should use?
>> Try fbida - worked for me just fine
>
> It didn't when I tried, way way back when. It also wanted way more
> stuff :)
>
--
Best Regards
Ulf Samuelsson
prev parent reply other threads:[~2009-08-20 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 15:48 fbv neutered Ulf Samuelsson
2009-08-19 16:09 ` Leon Woestenberg
2009-08-20 3:31 ` Denys Dmytriyenko
2009-08-20 4:23 ` Tom Rini
2009-08-20 4:55 ` Denys Dmytriyenko
2009-08-20 14:24 ` Ulf Samuelsson [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=4A8D5C8E.8030806@atmel.com \
--to=ulf.samuelsson@atmel.com \
--cc=openembedded-devel@lists.openembedded.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