All of lore.kernel.org
 help / color / mirror / Atom feed
From: Volker Vogelhuber <v.vogelhuber@digitalendoscopy.de>
To: <yocto@yoctoproject.org>
Subject: building yocto image from git always switches branch
Date: Tue, 12 Mar 2013 17:34:02 +0100	[thread overview]
Message-ID: <513F58FA.3080808@digitalendoscopy.de> (raw)

I currently try to create a kernel and rootfs image based on yocto 1.3.
I cloned the poky git repository and switched to danny branch.

For some reason during the bitbake run for creating the image the branch 
of my local git repository is always switched to master, which of course 
won't match with the other layers I checked out for danny.

Currently I do the following:

#!/bin/bash

if [ ! -e poky ]; then
   git clone git://git.yoctoproject.org/poky.git
   cd poky
   git checkout -b danny remotes/origin/danny
   cd ..
fi
if [ ! -e poky/meta-ti ]; then
   git clone -b danny git://git.yoctoproject.org/meta-ti poky/meta-ti
fi

After the checkout I copy some configuration files to the build/conf 
directory within the poky directory (bblayers.conf, local.conf) and an 
additional layer for our specific hardware module.

When I change to the build directory and start building the image using 
bitbake, there seems to be a git call somewhere in the recipes that 
switches the branch of the poky git checkout back to master. Of course 
that results in a total misbehaviour of the build process, as the 
underlaying recipes changes during the build.

Can someone explain that behaviour? Is that a bug or is there something 
I'm doing wrong.

Kind regards,
     Volker


             reply	other threads:[~2013-03-12 16:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 16:34 Volker Vogelhuber [this message]
2013-03-15  9:02 ` building yocto image from git always switches branch Volker Vogelhuber
2013-03-15 14:34   ` Bruce Ashfield
2013-03-15 15:04     ` Volker Vogelhuber
2013-03-15 16:00       ` Bruce Ashfield

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=513F58FA.3080808@digitalendoscopy.de \
    --to=v.vogelhuber@digitalendoscopy.de \
    --cc=yocto@yoctoproject.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.