Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Getting rid of "The license listed internal was not in the licenses collected" warnings?
Date: Mon, 07 Sep 2015 18:38:07 +0200	[thread overview]
Message-ID: <55EDBD6F.7090900@topic.nl> (raw)
In-Reply-To: <CAHiDW_GfhUoDMBtwbj2G8RbRnA7OWR_3b_M_tDc-hEz8g4NqYw@mail.gmail.com>

On 07-09-15 13:56, Jussi Kukkonen wrote:
> On 7 September 2015 at 13:14, Mike Looijmans <mike.looijmans@topic.nl
> <mailto:mike.looijmans@topic.nl>> wrote:
>
>     Just sped another hour or so trying to pinpoint this, but I cannot
>     wrap my head around it. What do I have to do to add a license to a
>     layer without these annoying warnings?
>
>
> I just tried this (with master branch) and it seems to work fine
> here...  Are you using master or something older?

Did you try that in a separate, empty layer? I suspect I'm missing a 
variable or directive of some kind which cause it to miss the license file.

> Do you not get a "${DEPLOY_DIR}/licenses/${BPN}/generic_internal" file
> when you build the recipe for BPN?

Nope.


>
>   - Jussi
>
>     Mike.
>
>
>     On 03-07-15 09:23, Mike Looijmans wrote:
>
>         In my layer.conf I have:
>
>         LICENSE_PATH += "${LAYERDIR}/licenses"
>
>
>         In that path, there's a license file called "internal"
>         containing the
>         following short text:
>
>         For TOPIC internal use only.
>         Do not distribute.
>
>
>         Now on each build I get warnings like this for every recipe that
>         refers to
>         this license:
>         "WARNING: The license listed internal was not in the licenses
>         collected for
>         recipe ..."
>
>
>         As far as I know, I did everything right, but I can't figure out
>         what else I
>         need to do here. How do I get this license into the "license
>         collected"?
>
>
>
>
>
>     Kind regards,
>
>     Mike Looijmans
>     System Expert
>
>     TOPIC Embedded Products
>     Eindhovenseweg 32-C, NL-5683 KH Best
>     Postbus 440, NL-5680 AK Best
>     Telefoon: +31 (0) 499 33 69 79
>     <tel:%2B31%20%280%29%20499%2033%2069%2079>
>     Telefax: +31 (0) 499 33 69 70 <tel:%2B31%20%280%29%20499%2033%2069%2070>
>     E-mail: mike.looijmans@topicproducts.com
>     <mailto:mike.looijmans@topicproducts.com>
>     Website: www.topicproducts.com <http://www.topicproducts.com>
>
>     Please consider the environment before printing this e-mail
>
>
>
>
>
>     --
>     _______________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.openembedded.org
>     <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


-- 
Mike Looijmans


  reply	other threads:[~2015-09-07 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  7:23 Getting rid of "The license listed internal was not in the licenses collected" warnings? Mike Looijmans
2015-09-07 10:14 ` Mike Looijmans
2015-09-07 11:56   ` Jussi Kukkonen
2015-09-07 16:38     ` Mike Looijmans [this message]
2015-09-08  8:44       ` Jussi Kukkonen
2015-09-08 10:19         ` Mike Looijmans
2015-09-08 10:39           ` Mikko.Rapeli

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=55EDBD6F.7090900@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=jussi.kukkonen@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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