[yocto] Whitelist gdbserver

[Jeremy Overesch]

Thanks!

I searched for "whitelist" in the documentation, but it didn't list anything about whitelisting a package even though I knew it was possible. (libidn was being whitelisted.)  Also, it turns out I had to whitelist "gdb" not just "gdbserver", because gdbserver is part of the gdb recipe.

Thanks again,
Jeremy

-----Original Message-----
From: Andre McCurdy <armccurdy at gmail.com>
Sent: Thursday, September 13, 2018 4:51 PM
To: Jeremy Overesch <Jeremy.Overesch at millerwelds.com>
Cc: yocto at yoctoproject.org
Subject: Re: [yocto] Whitelist gdbserver

On Thu, Sep 13, 2018 at 8:42 AM, Jeremy Overesch
<Jeremy.Overesch at millerwelds.com> wrote:
> HI all,
>
> I’m attempting to whitelist gdbserver just for SDK purposes, while keeping
> all other GPLv3 code as incompatible (therefore unbuilt).  However,
> everything I’ve tried still results in gdbserver being removed from my SDK
> and therefore failing to build.
>
> In my local.conf, I have the following line:
>
> INCOMPATIBLE_LICENSE = "GPLv3 LGPLv3 AGPLv3"
>
> Through the yocto documentation
> (https://www.yoctoproject.org/docs/2.4/mega-manual/mega-manual.html#license-flag-matching),
> it appears that adding the following *should* work, yet it doesn’t:

I think you are mixing up "LICENSE" and "LICENSE_FLAGS". The two don't
really work together. It's partly explained in:

  https://www.yoctoproject.org/docs/2.4/mega-manual/mega-manual.html#var-LICENSE_FLAGS

See the LICENSE_FLAGS comment which says "This value is independent of
LICENSE and is typically used to mark recipes that might require
additional licenses in order to be used in a commercial product. For
more information, see the "Enabling Commercially Licensed Recipes"
section."

To whitelist a recipe which is being excluded due to
INCOMPATIBLE_LICENSE, use WHITELIST_GPL-3.0. For example for
gdbserver, try the following:

  WHITELIST_GPL-3.0 += "gdbserver"

________________________________

This message (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. If you are not the intended recipient of this message, you are hereby notified that you must delete the message without disseminating, copying or taking any action in reliance upon it. If you have received this message in error, please notify the sender via return e-mail. Thank you.