From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/openjpeg: bump to version 2.1
Date: Mon, 25 Apr 2016 22:14:55 +0200 [thread overview]
Message-ID: <20160425221455.36312295@free-electrons.com> (raw)
In-Reply-To: <CA+TH9Vkf-=t2iS7ep1J3ejZ+LREVprQ+AN6wNn39MDAYVV58uw@mail.gmail.com>
Hello,
On Mon, 25 Apr 2016 22:05:44 +0200, Angelo Compagnucci wrote:
> > What about those optional dependencies? They are no longer used?
>
> They are no longer present as cmake options, they are handled internally.
What do you mean by "internally"? They are still optional dependencies,
but there are no CMake options to enable/disable them? The libpng, tiff
and lcms2 code has been duplicated in the openjpeg project?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-25 20:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 15:20 [Buildroot] [PATCH 0/2] python-pillow: new package Angelo Compagnucci
2016-04-25 15:20 ` [Buildroot] [PATCH 1/2] package/openjpeg: bump to version 2.1 Angelo Compagnucci
2016-04-25 19:28 ` Thomas Petazzoni
2016-04-25 20:05 ` Angelo Compagnucci
2016-04-25 20:14 ` Thomas Petazzoni [this message]
2016-04-25 20:18 ` Samuel Martin
2016-04-25 20:43 ` Angelo Compagnucci
2016-04-25 20:53 ` Angelo Compagnucci
2016-04-25 20:56 ` Samuel Martin
2016-04-25 21:01 ` Angelo Compagnucci
2016-04-25 19:29 ` Peter Korsgaard
2016-04-25 20:06 ` Angelo Compagnucci
2016-04-25 21:19 ` Angelo Compagnucci
2016-04-25 15:20 ` [Buildroot] [PATCH 2/2] package/python-pillow: new package Angelo Compagnucci
2016-04-25 20:35 ` Thomas Petazzoni
2016-04-25 20:49 ` Angelo Compagnucci
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=20160425221455.36312295@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