On Tuesday 15 January 2013 15:28:25 Rudolf Streif wrote:
What are you exactly referring to as new version? The package version
that bitbake builds is defined by the recipe, through the version
designation in the recipe's file name or through explicitly setting PV.
I think what you are trying
On Tue, Jan 15, 2013 at 6:57 PM, Brian Smucker b...@bsmucker.eu.org wrote:
Hi Rudolf,
On 1/15/2013 3:28 PM, Rudolf Streif wrote:
Brian,
What are you exactly referring to as new version? The package version
that bitbake builds is defined by the recipe, through the version
designation in
Hi,
The version of busybox is the same. I've just temporarily done a
bitbake -c menuconfig to change one of the options, recompiled using the
custom config that's generated, and now I want to force its inclusion
into core-image-minimal.
Thanks,
Brian
On 1/16/2013 6:13 AM, Autif Khan
On Wed, Jan 16, 2013 at 10:23 AM, Brian Smucker b...@bsmucker.eu.org wrote:
Hi,
The version of busybox is the same. I've just temporarily done a bitbake -c
menuconfig to change one of the options, recompiled using the custom config
that's generated, and now I want to force its inclusion into
Hello All,
I'm a relative newbie to yocto/oe, but have got a ways down the road to
understanding, but the gaps in my understanding cause me great grief at
times.
I think this probably is a simple question, but somehow I'm doing
something wrong.
I recompile busybox with a new config:
Brian,
What are you exactly referring to as new version? The package version
that bitbake builds is defined by the recipe, through the version
designation in the recipe's file name or through explicitly setting PV.
I think what you are trying to do is to modify the busybox configuration
and then
Hi Rudolf,
On 1/15/2013 3:28 PM, Rudolf Streif wrote:
Brian,
What are you exactly referring to as new version? The package
version that bitbake builds is defined by the recipe, through the
version designation in the recipe's file name or through explicitly
setting PV.
I think what you
