From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] libvncserver: add config option for tightpng encoding support
Date: Sat, 27 Dec 2014 14:51:32 +0100 [thread overview]
Message-ID: <20141227145132.1c48523a@free-electrons.com> (raw)
In-Reply-To: <b66fd2b4894b872b928f81fdf13998ec@to-the-max.net>
Dear Floris Bos,
On Fri, 26 Dec 2014 18:37:15 +0100, Floris Bos wrote:
> JPEG and PNG are both necesarry.
>
> Libvncserver will only compile tight.c if HAVE_LIBJPEG
>
> https://github.com/LibVNC/libvncserver/blob/master/libvncserver/Makefile.am#L49
>
> And inside tight.c png is optional, jpeg is not.
Ok, so I believe we should rather do:
+config BR2_PACKAGE_LIBVNCSERVER_TIGHTPNG
+ bool "TightPNG encoding support"
+ select BR2_PACKAGE_JPEG
+ select BR2_PACKAGE_LIBPNG
+ help
+ TightPNG encoding speeds up HTML5 based VNC clients like noVNC.
+
+ http://wiki.qemu.org/VNC_Tight_PNG
in Config.in (i.e as you did)
And then in libvncserver.mk, do:
ifeq ($(BR2_PACKAGE_LIBPNG),y)
LIBVNCSERVER_DEPENDENCIES += libpng
else
LIBVNCSERVER_CONF_OPTS += --without-png
endif
This way, people not using tightpng support but having libpng enabled
will have PNG support in libvncserver.
Can you rework your patch in this direction?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-27 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 0:46 [Buildroot] [PATCH 1/2] libvncserver: bump version to 0.9.10 Floris Bos
2014-12-26 0:46 ` [Buildroot] [PATCH 2/2] libvncserver: add config option for tightpng encoding support Floris Bos
2014-12-26 17:08 ` Thomas Petazzoni
2014-12-26 17:37 ` Floris Bos
2014-12-27 13:51 ` Thomas Petazzoni [this message]
2014-12-27 17:43 ` Floris Bos
2014-12-27 18:07 ` Thomas Petazzoni
2014-12-26 4:40 ` [Buildroot] [PATCH 1/2] libvncserver: bump version to 0.9.10 Baruch Siach
2014-12-26 15:03 ` Floris Bos
2014-12-26 15:16 ` Yann E. MORIN
2014-12-26 17:07 ` Thomas Petazzoni
2014-12-27 13:52 ` Thomas Petazzoni
2014-12-27 17:01 ` Floris Bos
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=20141227145132.1c48523a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox