From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] turbovnc: new package
Date: Wed, 1 Nov 2017 10:53:05 +0100 [thread overview]
Message-ID: <20171101105305.1cd82e60@windsurf> (raw)
In-Reply-To: <20171101060657.tzjnt4ceb25irb3o@sapphire.tkos.co.il>
Hello,
On Wed, 1 Nov 2017 08:06:57 +0200, Baruch Siach wrote:
> > +config BR2_PACKAGE_TURBOVNC
> > + bool "turbovnc"
> > + select BR2_PACKAGE_JPEG_TURBO
>
> You also need to select BR2_PACKAGE_JPEG because BR2_PACKAGE_JPEG_TURBO
> depends on BR2_PACKAGE_JPEG.
No, you cannot do that, because BR2_PACKAGE_JPEG_TURBO is part of a
choice, and you cannot select options in a choice.
I don't see why TurboVNC would need jpeg-turbo specifically, as it's
API compatible with libjpeg. Therefore, please select BR2_PACKAGE_JPEG
here, and let the user decide whether jpeg-turbo or libjpeg should be
used.
> > + select BR2_PACKAGE_OPENSSL
> > + select BR2_PACKAGE_XLIB_LIBICE
> > + select BR2_PACKAGE_XLIB_LIBSM
> > + select BR2_PACKAGE_XLIB_LIBX11
> > + select BR2_PACKAGE_XLIB_LIBXEXT
> > + select BR2_PACKAGE_XLIB_LIBXAU
> > + select BR2_PACKAGE_XLIB_LIBXDMCP
If you select those libraries, you need to add a:
depends on BR2_PACKAGE_XORG7
> Since the license files hashes are locally calculated, having only sha256 for
> each file should be enough.
Agreed.
> > +TURBOVNC_VERSION = 2.1.2
> > +TURBOVNC_SOURCE = turbovnc-$(TURBOVNC_VERSION).tar.gz
> > +TURBOVNC_SITE = https://downloads.sourceforge.net/project/turbovnc/$(TURBOVNC_VERSION)
> > +TURBOVNC_DEPENDENCIES = jpeg-turbo openssl xlib_libICE xlib_libSM xlib_libX11 \
> > + xlib_libXext xlib_libXau xlib_libXdmcp
> > +TURBOVNC_LICENSE = GPL-2.0, MIT (putty), Dual FTL/GPL-2.0+ (freetype) \
Missing comma at the end of this line.
Why does it bundle freetype? Can it use an external Freetype instead?
> > + bzip2 license (bzip2), Zlib (zlib)
The SPDX license code for bzip2 license is bzip2-1.0.5 or bzip2-1.0.6,
see https://spdx.org/licenses/.
Also, why does it bundle Zlib ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-01 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 12:40 [Buildroot] [PATCH v2 1/1] turbovnc: new package Stefan Fröberg
2017-11-01 6:06 ` Baruch Siach
2017-11-01 9:53 ` Thomas Petazzoni [this message]
2017-11-02 21:21 ` Stefan Fröberg
2017-11-02 21:28 ` Thomas Petazzoni
2017-11-02 23:20 ` Stefan Fröberg
2017-11-03 22:17 ` Stefan Fröberg
2017-11-06 13:13 ` Stefan Fröberg
2017-11-06 19:59 ` Baruch Siach
2017-11-06 20:05 ` Thomas Petazzoni
2017-11-06 22:19 ` Arnout Vandecappelle
2017-11-06 22:38 ` Thomas Petazzoni
2017-11-07 13:28 ` Stefan Fröberg
2017-11-01 19:18 ` Stefan Fröberg
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=20171101105305.1cd82e60@windsurf \
--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