Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
To: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe-core] THISDIR usage
Date: Wed, 11 Apr 2012 15:25:07 +0200	[thread overview]
Message-ID: <940168466624837829@unknownmsgid> (raw)
In-Reply-To: <CA+chaQfoxtqA5QgaCy6cgaf27MsMLCLXc=5MO-Dj9263scEeeQ@mail.gmail.com>

No FILESPATH in the log after bitbake -e <recipe> command.
But... it's ok running scripts/bitbake instead of the binary one as I'm doing?

Il giorno 11/apr/2012, alle ore 15:07, Martin Jansa
<martin.jansa@gmail.com> ha scritto:

> Use bitbake -e your_recipe and check FILESPATH variable.
>
>
> On Wed, Apr 11, 2012 at 12:52 PM, Giuseppe Condorelli
> <giuseppe.condorelli@gmail.com> wrote:
>> Many thanks for the reply, I tried the suggestion but I obtained this:
>>
>> "Unable to fetch URL file://myfile.tar.gz from any source"
>>
>> What's happening?
>> Thanks,
>> Giuseppe
>>
>> Il giorno mercoledì 11 aprile 2012, Gary Thomas ha scritto:
>>
>>> On 2012-04-11 04:23, Giuseppe Condorelli wrote:
>>>
>>>> Hi, I moved to OE-Core (working on stable version dowloaded as tar file
>>>> from cgit.openembedded.org).
>>>> I'm in trouble trying to include a source through .bbappend file, located
>>>> under my meta-<personal>  subtree.
>>>>
>>>> FILESPATHBASE_prepend := "${THISDIR}/files:"
>>>> SRC_URI += "file://myfile.tar.gz"
>>>>
>>>> results in a no such file or directory. Please can you tell me if I'm
>>>> missing anything?
>>>>
>>>
>>> Assuming your tree looks something like this [partial]:
>>>
>>>  meta-giuseppe:
>>>    recipes:
>>>      some-recipe:
>>>        some-recipe_1.2.3.bbappend
>>>        files:
>>>          myfile.tar.gz
>>>
>>> Try using this instead
>>>  FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>>>
>>> --
>>> ------------------------------**------------------------------
>>> Gary Thomas                 |  Consulting for the
>>> MLB Associates              |    Embedded world
>>> ------------------------------**------------------------------
>>>
>>> ______________________________**_________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/**cgi-bin/mailman/listinfo/**openembedded-devel<http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel>
>>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2012-04-11 13:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 10:23 [oe-core] THISDIR usage Giuseppe Condorelli
2012-04-11 10:33 ` Giuseppe Condorelli
2012-04-11 10:38 ` Gary Thomas
2012-04-11 10:52   ` Giuseppe Condorelli
2012-04-11 11:05     ` Gary Thomas
2012-04-11 13:06     ` Martin Jansa
2012-04-11 13:25       ` Giuseppe Condorelli [this message]
2012-04-28 20:57 ` Khem Raj
2012-04-28 23:44   ` Giuseppe Condorelli
     [not found] <005901cd17e1$3b9a2290$b2ce67b0$@st.com>
2012-04-11 12:49 ` Giuseppe Condorelli
2012-04-11 13:01   ` Jaap de Jong
2012-04-11 13:06     ` Giuseppe Condorelli

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=940168466624837829@unknownmsgid \
    --to=giuseppe.condorelli@gmail.com \
    --cc=openembedded-devel@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