All of lore.kernel.org
 help / color / mirror / Atom feed
From: hallerHarry@gmx.de
To: bitbake-devel@lists.openembedded.org
Subject: bitbake DEPENDS problem
Date: Thu, 17 Jan 2013 19:50:45 +0100	[thread overview]
Message-ID: <20130117185045.24970@gmx.net> (raw)

Hi,

I've got the below described minimalistic bitbake setup. There are two recipes where one recipe (mySecPkg.bb) DEPENDS on the other (myPkg.bb).
According to the OpenEmbedded User Manual [1] and the Yocto Pokey Manual Section 2.3 [2] I would have expected if I run build against mySecPkg that bitbake obeys inter-package dependencies and also builds myPkg since mySecPkg DEPENDS on it.
But this is not the case. Bitbake only builds mySecPkg. Is there something wrong with my assumption or setup? I would appreciate if someone could shed some light on that.

Thanks in advance for any assistance provided!

$ env -i PATH=$PATH:./bitbake-1.17.0/bin bitbake -DDD mySecPkg
...
DEBUG: providers for myPkg are: ['myPkg']
...
DEBUG: Resolved 0 extra dependencies
...
NOTE: Pruned 1 inactive tasks, 1 left

Here is the setup:

|-- bitbake
|   |-- bin
|   |   `-- bitbake
|   `-- ...
|
|-- conf
|   |-- bblayers.conf
|   |      BBPATH = "${TOPDIR}"
|   |      BBFILES ?= ""
|   |      BBLAYERS ?= "meta"
|   |
|   `-- local.conf
|          BB_NUMBER_THREADS = "2"
|          PARALLEL_MAKE = "-j 2"
|
`-- meta
    |-- conf
    |   |-- layer.conf
    |   |      BBPATH := "${LAYERDIR}:${BBPATH}"
    |   |      BBFILES := "${BBFILES} ${LAYERDIR}/recipes/*.bb"
    |   |
    |   `-- bitbake.conf
    |          ...
    |          require local.conf
    |
    |-- classes
    |   |-- base.bbclass
    |   |      bbnote() {
    |   |         echo "NOTE:" "$*"
    |   |      }
    |   |
    |   |      addtask build
    |   |      do_build[dirs] = "${TOPDIR}"
    |   |      #do_build[nostamp] = "1"
    |   |      python base_do_build () {
    |   |         bb.note("The included,...")
    |   |      }
    |   |
    |   |      EXPORT_FUNCTIONS do_build
    |   |
    |   `-- myBaseClass.bbclass
    |          addtask do_build
    |          do_build() {
    |             bbnote "*** myBaseClass::do_build()"
    |          }
    |
    `-- recipes
        |-- myPkg_0.1.bb
        |      PN = "myPkg"
        |      PV = "0.1"
        |
        |      inherit myBaseClass
        |
        |      do_build() {
        |         bbnote "*** myPkg::do_build()"
        |      }
        |
        `-- mySecPkg_0.1.bb
               PN = "mySecPkg"
               PV = "0.1"
               DEPENDS = "myPkg"

               inherit myBaseClass

               do_build() {
                  bbnote "*** mySecPkg::do_build()"
                  return 0
               }
 
[1] http://docs.openembedded.org/usermanual/usermanual.html
[2] http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.html

Regards
 HH




             reply	other threads:[~2013-01-17 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 18:50 hallerHarry [this message]
2013-01-18 12:00 ` bitbake DEPENDS problem Richard Purdie

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=20130117185045.24970@gmx.net \
    --to=hallerharry@gmx.de \
    --cc=bitbake-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.