« Return to Thread: Bitbake and Git

Re: Bitbake and Git

by Jason C. Mecham :: Rate this Message:

Reply to Author | View in Thread

Update - I'm only using commits from http://gitorious.org/gumstix-oe/mainline/commits/overo

when checking out certain commit ID's it doesn't have the omap3-console-image.bb file

when checking out other ones it doesn't (like the merge branch ones don't seem to have it). I guess I'm confused as to why some of them don't have it.

Commit ID: 96ac811 doesn't have it.
Commit ID: e085d8d does

I could see the ones from org.openembedded.dev not having them, but within the overo branch?

I followed these commands when creating the directory

mkdir -p $OE_HOME
cd $OE_HOME
git clone git://gitorious.org/gumstix-oe/mainline.git org.openembedded.dev
cd org.openembedded.dev
git checkout --track -b overo origin/overo

I used git checkout -b newbranchname <commit-id> to create the branch based on a certain commit-id

I'm asking this because I'm in the process of learning git, and I thought I had it down. Obviously there is hole in my knowledge.



________________________________________
From: Jason C. Mecham [jason.mecham@...]
Sent: Monday, June 29, 2009 6:49 PM
To: General mailing list for gumstix users.
Subject: [Gumstix-users] Bitbake and Git

If I use the latest git commit for the Overo I'm able to build the OMAP3-console-image using bitbake

HOWEVER, if I try checking out an older git commit release the OMAP3-console-image.bb file disappears.  The omap3-console-image.bb had to have been in the previous releases (I just need to go back a month or so prior to a certain change). It could very well be something I'm doing wrong when checking out a different version (git checkout -b newbranchname commit-id). I've only recently become familiar with Git, but it seems to work beautifully when using just git repository and kernel images. I only run into issues when trying to use it in conjunction with bitbake/OE.

I also ran into into an issue where it forced me to delete the TMP directory (Error, DISTRO_PR has changed (.3 to .2) which means all packages need to rebuild. Please remove your TMPDIR so this can happen. For autobuilder setups you can avoid this by using a TMPDIR that include DISTRO_PR in the path.). I've seen messages on this board regarding that and its expected, but it seems like your REALLY NOT supposed to try to go back with.


------------------------------------------------------------------------------
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

------------------------------------------------------------------------------
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

 « Return to Thread: Bitbake and Git