From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] unbound: new package
Date: Fri, 12 Jan 2018 16:00:27 +0200 [thread overview]
Message-ID: <5990987d-da1e-ec22-738b-6747bd6819cb@petroprogram.com> (raw)
In-Reply-To: <20180112120803.0ddb7b6d@windsurf.lan>
Hi
Thomas Petazzoni kirjoitti 12.01.2018 klo 13:08:
> Hello,
>
> On Fri, 12 Jan 2018 12:45:06 +0200, Stefan Fr?berg wrote:
>
>>> Why not "select BR2_PACKAGE_OPENSSL"?
>>> Did you test with libressl as well?
>>>
>> That cannot be select because it's a choise and if I remember buildroot
>> manual and
>> what Thomas said, you can't (or actually shouldn't) select from choice
>> unless
>> absolutely necessary (like, for example, in my turbovnc patch...have to
>> remember update that too...)
> It is correct that regular virtual packages cannot be selected.
>
> But openssl (like jpeg) is special, and you can select
> BR2_PACKAGE_OPENSSL. BR2_PACKAGE_OPENSSL is not part of a choice.
>
> The case of turbovnc is different: you wanted to select jpeg-turbo
> specifically, which is one jpeg implementation. And this is not
> possible.
>
> See the difference ? BR2_PACKAGE_OPENSSL is the virtual package itself,
> which has two implementations: libopenssl and libressl, selectable
> through a choice.
>
> BR2_PACKAGE_JPEG_TURBO is one implementation of the BR2_PACKAGE_JPEG
> virtual package. Selecting BR2_PACKAGE_JPEG is OK (just like selecting
> BR2_PACKAGE_OPENSSL is OK), but selecting BR2_PACKAGE_JPEG_TURBO
> doesn't work.
>
>
Ah, okay.
But Thomas, I can't use BR2_PACKAGE_JPEG for turbovnc because it uses
specific ABI (the so called TurboJPEG ABI)
from libjpeg-turbo package and vanilla jpeg does not provide it.
https://libjpeg-turbo.org/About/TurboJPEG
At least, *if* I remember correctly, turbovnc nagged something about
missing function when I tried to compile against vanilla jpeg.
Regards
Stefan
next prev parent reply other threads:[~2018-01-12 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 23:20 [Buildroot] [PATCH 1/1] unbound: new package Stefan Fröberg
2018-01-12 6:41 ` Bernd Kuhls
2018-01-12 10:34 ` Stefan Fröberg
2018-01-12 10:45 ` Stefan Fröberg
2018-01-12 11:08 ` Thomas Petazzoni
2018-01-12 14:00 ` Stefan Fröberg [this message]
2018-01-12 15:23 ` Thomas Petazzoni
2018-01-12 16:19 ` Stefan Fröberg
-- strict thread matches above, loose matches on Subject: below --
2020-03-21 0:57 Stefan Ott
2020-03-21 6:42 ` Yegor Yefremov
2020-03-29 16:53 ` Stefan Ott
2020-03-21 8:27 ` Thomas Petazzoni
2020-03-21 12:37 ` Yann E. MORIN
2020-03-29 17:00 ` Stefan Ott
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=5990987d-da1e-ec22-738b-6747bd6819cb@petroprogram.com \
--to=stefan.froberg@petroprogram.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.