Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Is it possible for a recipe to include/require something from a subdirectory?
Date: Thu, 20 Aug 2009 16:31:19 +0200	[thread overview]
Message-ID: <4A8D5E37.5010806@atmel.com> (raw)

I just finished a nice gnome script which allows me to automatically
generate SRC_URI_append's

I select the files[1-4] in <recipy-dir>/<recipy>/<xxx>/<yyy>",
and then run the script

result is:

SRC_URI_append_<board> = "\
	file://<file1>	\
	file://<file2>	\
	file://<file3>	\
	file://<file4>	\
	"

Now, in <recipy-dir>/<recipy>.bb I want to include the file using

require <xxx>/<yyy>/SRC_URI_append

This did not work, so I tried symlinking - bad move...
I'd hate having to move it to the top directory of the recipe.

Any ideas?

-- 
Best Regards
Ulf Samuelsson




             reply	other threads:[~2009-08-20 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20 14:31 Ulf Samuelsson [this message]
2009-08-20 15:26 ` Is it possible for a recipe to include/require something from a subdirectory? Chris Larson
2009-08-22  8:13   ` Ulf Samuelsson

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=4A8D5E37.5010806@atmel.com \
    --to=ulf.samuelsson@atmel.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