From: Tadek D <tdr...@ta...> - 2009-02-05 22:25:21
|
Hi, Based on gumstix-basic-image.bb, I have created my own image with extra one package (xxx) and I call this recipe gumstix-xxx-image.bb. This extra package has two recipes: xxx_1.0.0.bb and xxx_1.0.1.bb which I used during development. When I build root file system image using following sequence: bitbake -c rebuild xxx bitbake -c task-base-gumstix bitbake -c gumstix-xxx-image the bitbake correctly used xxx_1.0.1.bb recipe and the root file system contain correct version of xxx. My question is how to rebuild root file system corresponding to recipe xxx_1.0.0.bb ? When I tried following sequence: bitbake -c rebuild -b xxx_1.0.0.bb bitbake -c task-base-gumstix bitbake -c gumstix-xxx-image the resulting file system did not change (i.e. it contains newer version of xxx corresponding to 1.0.1 recipe). It must be fancy caching but I can't figure it out... Tad -- View this message in context: http://www.nabble.com/rebuilding-root-file-system-image-tp21862475p21862475.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Chris D. <chr...@gm...> - 2009-02-05 23:37:10
|
Hi Tad, > bitbake -c rebuild -b xxx_1.0.0.bb > bitbake -c task-base-gumstix > bitbake -c gumstix-xxx-image > the resulting file system did not change (i.e. it contains newer version of > xxx corresponding to 1.0.1 recipe). > That should be: bitbake -c rebuild -b xxx_1.0.0.bb bitbake -c rebuild gumstix-xxx-image Note the '-c rebuild' part for the image. Also, you only need to rebuild task-base-gumstix (which would also be 'bitbake -c rebuild task-base-gumstix') if you change settings such as MACHINE_FEATURES in gumstix-custom-<connex/verdex>.conf Chris |
From: Tadek D <tdr...@ta...> - 2009-02-06 04:22:58
|
Hi Chris, My typo and apology. I had (-c rebuild) bitbake -c rebuild -b xxx_1.0.0.bb bitbake -c rebuild gumstix-xxx-image but the binary for xxx application still corresponds to the newer one i.e. 1.0.1 and not to 1.0.0. :( Any clue? Tad PS Thank you for the note on task-base-gumstix bitbaking Chris Dollar wrote: > > Hi Tad, > >> bitbake -c rebuild -b xxx_1.0.0.bb >> bitbake -c task-base-gumstix >> bitbake -c gumstix-xxx-image >> the resulting file system did not change (i.e. it contains newer version >> of >> xxx corresponding to 1.0.1 recipe). >> > That should be: > bitbake -c rebuild -b xxx_1.0.0.bb > bitbake -c rebuild gumstix-xxx-image > > Note the '-c rebuild' part for the image. Also, you only need to > rebuild task-base-gumstix (which would also be 'bitbake -c rebuild > task-base-gumstix') if you change settings such as MACHINE_FEATURES in > gumstix-custom-<connex/verdex>.conf > > Chris > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with > Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code > to > build responsive, highly engaging applications that combine the power of > local > resources and data with the reach of the web. Download the Adobe AIR SDK > and > Ajax docs to start building applications > today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/rebuilding-root-file-system-image-tp21862475p21866362.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Chris D. <chr...@gm...> - 2009-02-06 14:52:41
|
Oh... I wasn't reading close enough either :) Bitbake will always prefer the newest version of any given package unless you explicitly tell it not to. There are a couple of ways to do this. If you look in <gum-oe>/com.gumstix.collection/conf/machine/include/gumstix.inc you'll see a number of PREFERRED_VERSION_xxx lines -- you could add a line like that for your package specifying the 1.0.0 version. Another way is to add the line DEFAULT_PREFERENCE = "-1" to the 1.0.1 recipe which will tell bitbake basically the same thing. Chris On Thu, Feb 5, 2009 at 9:22 PM, Tadek D <tdr...@ta...> wrote: > > Hi Chris, > My typo and apology. I had (-c rebuild) > bitbake -c rebuild -b xxx_1.0.0.bb > bitbake -c rebuild gumstix-xxx-image > but the binary for xxx application still corresponds to the newer one i.e. > 1.0.1 and not to 1.0.0. :( > Any clue? > Tad > PS Thank you for the note on task-base-gumstix bitbaking > > > Chris Dollar wrote: >> >> Hi Tad, >> >>> bitbake -c rebuild -b xxx_1.0.0.bb >>> bitbake -c task-base-gumstix >>> bitbake -c gumstix-xxx-image >>> the resulting file system did not change (i.e. it contains newer version >>> of >>> xxx corresponding to 1.0.1 recipe). >>> >> That should be: >> bitbake -c rebuild -b xxx_1.0.0.bb >> bitbake -c rebuild gumstix-xxx-image >> >> Note the '-c rebuild' part for the image. Also, you only need to >> rebuild task-base-gumstix (which would also be 'bitbake -c rebuild >> task-base-gumstix') if you change settings such as MACHINE_FEATURES in >> gumstix-custom-<connex/verdex>.conf >> >> Chris >> >> ------------------------------------------------------------------------------ >> Create and Deploy Rich Internet Apps outside the browser with >> Adobe(R)AIR(TM) >> software. With Adobe AIR, Ajax developers can use existing skills and code >> to >> build responsive, highly engaging applications that combine the power of >> local >> resources and data with the reach of the web. Download the Adobe AIR SDK >> and >> Ajax docs to start building applications >> today-http://p.sf.net/sfu/adobe-com >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- > View this message in context: http://www.nabble.com/rebuilding-root-file-system-image-tp21862475p21866362.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code to > build responsive, highly engaging applications that combine the power of local > resources and data with the reach of the web. Download the Adobe AIR SDK and > Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Tadek D <tdr...@ta...> - 2009-02-06 16:42:30
|
Chris, Ok. I tried DEFAULT_PREFERENCE = "-1" in 1.0.1 recipe. When bitbake -c rebuild xxx it as expected used my previous recipe. But when bitbake -c rebuild gumstix-xxx-image in the directory <gum-oe>/tmp/rootfs newer version of xxx appeared. I even tried to deleting <gum-oe>/tmp/work/armv5te-angstrom-linux-gnueabi/xxx-1.0.1-r1. Magically 1.0.0 keep re-appearing. I also tried modifying gumstix.inc (but in <gum-oe>/user.collection/conf/machine/include/gumstix.inc) by adding PREFERRED_VERSION_xxx lines = "1.0.0" . It effects bitbaking xxx, but not rootfs image I desperately trying to bake :( My gumstix-xxx-image.bb looks like this: # basic gumstix image require ${GUMSTIXTOP}/user.collection/packages/images/gumstix-minimal-image.bb IMAGE_INSTALL += " \ busybox \ cron \ ntp \ ntpdate \ motd \ mtd-utils \ iptables \ kernel-modules \ xxx \ " Chris Dollar wrote: > > Oh... I wasn't reading close enough either :) Bitbake will always > prefer the newest version of any given package unless you explicitly > tell it not to. There are a couple of ways to do this. If you look in > <gum-oe>/com.gumstix.collection/conf/machine/include/gumstix.inc > you'll see a number of PREFERRED_VERSION_xxx lines -- you could add a > line like that for your package specifying the 1.0.0 version. Another > way is to add the line DEFAULT_PREFERENCE = "-1" to the 1.0.1 recipe > which will tell bitbake basically the same thing. > > Chris > > On Thu, Feb 5, 2009 at 9:22 PM, Tadek D <tdr...@ta...> wrote: >> >> Hi Chris, >> My typo and apology. I had (-c rebuild) >> bitbake -c rebuild -b xxx_1.0.0.bb >> bitbake -c rebuild gumstix-xxx-image >> but the binary for xxx application still corresponds to the newer one >> i.e. >> 1.0.1 and not to 1.0.0. :( >> Any clue? >> Tad >> PS Thank you for the note on task-base-gumstix bitbaking >> >> >> Chris Dollar wrote: >>> >>> Hi Tad, >>> >>>> bitbake -c rebuild -b xxx_1.0.0.bb >>>> bitbake -c task-base-gumstix >>>> bitbake -c gumstix-xxx-image >>>> the resulting file system did not change (i.e. it contains newer >>>> version >>>> of >>>> xxx corresponding to 1.0.1 recipe). >>>> >>> That should be: >>> bitbake -c rebuild -b xxx_1.0.0.bb >>> bitbake -c rebuild gumstix-xxx-image >>> >>> Note the '-c rebuild' part for the image. Also, you only need to >>> rebuild task-base-gumstix (which would also be 'bitbake -c rebuild >>> task-base-gumstix') if you change settings such as MACHINE_FEATURES in >>> gumstix-custom-<connex/verdex>.conf >>> >>> Chris >>> >>> ------------------------------------------------------------------------------ >>> Create and Deploy Rich Internet Apps outside the browser with >>> Adobe(R)AIR(TM) >>> software. With Adobe AIR, Ajax developers can use existing skills and >>> code >>> to >>> build responsive, highly engaging applications that combine the power of >>> local >>> resources and data with the reach of the web. Download the Adobe AIR SDK >>> and >>> Ajax docs to start building applications >>> today-http://p.sf.net/sfu/adobe-com >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/rebuilding-root-file-system-image-tp21862475p21866362.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> Create and Deploy Rich Internet Apps outside the browser with >> Adobe(R)AIR(TM) >> software. With Adobe AIR, Ajax developers can use existing skills and >> code to >> build responsive, highly engaging applications that combine the power of >> local >> resources and data with the reach of the web. Download the Adobe AIR SDK >> and >> Ajax docs to start building applications >> today-http://p.sf.net/sfu/adobe-com >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with > Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code > to > build responsive, highly engaging applications that combine the power of > local > resources and data with the reach of the web. Download the Adobe AIR SDK > and > Ajax docs to start building applications > today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/rebuilding-root-file-system-image-tp21862475p21876158.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Tadek D <tdr...@ta...> - 2009-02-09 23:12:57
|
Chris, OK - I think I have a solution. It is slightly more complicated: 1) DEFAULT_PREFERENCE = "-1" inserted into xxx-1.0.1.bb causes that bitbake -c rebuild xxx will be using 1.0.0 and not 1.0.1. But if I bitbaked xxx 1.0.0 and 1.0.1 in the past I will end up with two ipk entries in tmp/deploy/glibc/glibc/ipk/armv5te/: xxx_1.0.0-r1_arm5te.ipk abd xxx_1.0.1-r1_arm5te.ipk 2) if I now bitbake -c gumstix-xxx-image, bitbake will use the newest xxx_1.0.1-r1_arm5te.ipk and the only way to produce rootfs corresponding to xxx 1.0.0 is to manually delete ipk corresponding to xxx 1.0.1 package from tmp/deploy directory Tad Oh... I wasn't reading close enough either :) Bitbake will always prefer the newest version of any given package unless you explicitly tell it not to. There are a couple of ways to do this. If you look in <gum-oe>/com.gumstix.collection/conf/machine/include/gumstix.inc you'll see a number of PREFERRED_VERSION_xxx lines -- you could add a line like that for your package specifying the 1.0.0 version. Another way is to add the line DEFAULT_PREFERENCE = "-1" to the 1.0.1 recipe which will tell bitbake basically the same thing. Chris -- View this message in context: http://www.nabble.com/rebuilding-root-file-system-image-tp21862475p21924300.html Sent from the Gumstix mailing list archive at Nabble.com. |