Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andreas Mueller <schnitzeltony@gmx.de>
To: openembedded-core@lists.openembedded.org
Subject: How to reuse code in oe-core environment
Date: Thu, 30 Jun 2011 01:02:16 +0200	[thread overview]
Message-ID: <201106300102.16411.schnitzeltony@gmx.de> (raw)

Hi,

I am playing around with oe-core try to find a way of reusing code for multiple 
recipes. In oe I did create foo.inc with

foo() {
	# code to reuse
}

and called foo from several recipes. In oe-core the run.* scripts are much more 
stripped of unnecessary.  All the code included by 'require' seems to miss, so 
the function foo() will not be found. 

My searches for examples did not lead to a hook so what is the suggested 
solution for reusing code for multiple recipes in oe-core?

regards

Andreas



             reply	other threads:[~2011-06-29 23:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 23:02 Andreas Mueller [this message]
2011-06-29 23:57 ` How to reuse code in oe-core environment Khem Raj
2011-06-29 23:59 ` Chris Larson
2011-06-30  0:32   ` Mark Hatle
2011-06-30  0:42     ` Andreas Mueller
2011-06-30  0:39   ` Andreas Mueller

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=201106300102.16411.schnitzeltony@gmx.de \
    --to=schnitzeltony@gmx.de \
    --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