Hello all,
How do I force a particular task to run every time while building an
image? At present in my custom image recipe I've added the following
lines
SOME_VARIABLE = "Blah"
do_bootimg[depends] += "base-files:do_install"
But the contents of ${SOME_VARIA
On 30/01/12 15:32, jfabernathy wrote:
On 01/30/2012 06:15 PM, Joshua Lock wrote:
On 30/01/12 15:05, jfabernathy wrote:
On 01/30/2012 05:58 PM, Joshua Lock wrote:
It's beginning to sound like we've caught some folks off guard by
pushing changes to the edison branch of the poky repository in
pre
On 30/01/12 14:51, jfabernathy wrote:
Could my having a local download directory that is used on all bakes
cause this problem???
Not at all, that's fully supported.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
We are pleased to announce the second milestone of the coming release
of Yocto 1.2. This milestone release is available at:
http://downloads.yoctoproject.org/releases/yocto/milestones/poky-edison-6.1.0-m2.tar.bz2
or
http://mirrors.kernel.org/yoc
On 01/30/2012 06:15 PM, Joshua Lock wrote:
On 30/01/12 15:05, jfabernathy wrote:
On 01/30/2012 05:58 PM, Joshua Lock wrote:
It's beginning to sound like we've caught some folks off guard by
pushing changes to the edison branch of the poky repository in
preparation for an upcoming edison point r
On 30/01/12 15:05, jfabernathy wrote:
On 01/30/2012 05:58 PM, Joshua Lock wrote:
It's beginning to sound like we've caught some folks off guard by
pushing changes to the edison branch of the poky repository in
preparation for an upcoming edison point release.
The named branches are development
On Mon, Jan 30, 2012 at 5:05 PM, jfabernathy wrote:
> On 01/30/2012 05:58 PM, Joshua Lock wrote:
>
> It's beginning to sound like we've caught some folks off guard by pushing
> changes to the edison branch of the poky repository in preparation for an
> upcoming edison point release.
>
> The named
On 01/30/2012 05:58 PM, Joshua Lock wrote:
It's beginning to sound like we've caught some folks off guard by
pushing changes to the edison branch of the poky repository in
preparation for an upcoming edison point release.
The named branches are development branches for the release, stable
rel
It's beginning to sound like we've caught some folks off guard by
pushing changes to the edison branch of the poky repository in
preparation for an upcoming edison point release.
The named branches are development branches for the release, stable
release development will be done in the named b
On 30/01/12 14:47, jfabernathy wrote:
On 01/30/2012 05:43 PM, Joshua Lock wrote:
On 30/01/12 14:33, jfabernathy wrote:
On 01/30/2012 05:12 PM, Joshua Lock wrote:
On 30/01/12 13:54, jfabernathy wrote:
On 01/30/2012 04:51 PM, Bruce Ashfield wrote:
On Mon, Jan 30, 2012 at 4:47 PM, jfabernathy
On 01/30/2012 05:43 PM, Joshua Lock wrote:
On 30/01/12 14:33, jfabernathy wrote:
On 01/30/2012 05:12 PM, Joshua Lock wrote:
On 30/01/12 13:54, jfabernathy wrote:
On 01/30/2012 04:51 PM, Bruce Ashfield wrote:
On Mon, Jan 30, 2012 at 4:47 PM, jfabernathy
wrote:
It seems that something happen
On 01/30/2012 05:43 PM, Joshua Lock wrote:
On 30/01/12 14:33, jfabernathy wrote:
On 01/30/2012 05:12 PM, Joshua Lock wrote:
On 30/01/12 13:54, jfabernathy wrote:
On 01/30/2012 04:51 PM, Bruce Ashfield wrote:
On Mon, Jan 30, 2012 at 4:47 PM, jfabernathy
wrote:
It seems that something happen
Agenda:
* Opens collection - 5 min (Song)
* Yocto 1.1.1 point release update - 10 min (Josh/Beth)
* Yocto 1.2 M3 status - 10 min (Song/Team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.2_Status
* Opens - 10 min
* Team Sharing - 20 min
-Original Appointment-
Conference det
On 30/01/12 14:33, jfabernathy wrote:
On 01/30/2012 05:12 PM, Joshua Lock wrote:
On 30/01/12 13:54, jfabernathy wrote:
On 01/30/2012 04:51 PM, Bruce Ashfield wrote:
On Mon, Jan 30, 2012 at 4:47 PM, jfabernathy
wrote:
It seems that something happened today. I could not complete a
build on
ed
On 01/30/2012 05:12 PM, Joshua Lock wrote:
On 30/01/12 13:54, jfabernathy wrote:
On 01/30/2012 04:51 PM, Bruce Ashfield wrote:
On Mon, Jan 30, 2012 at 4:47 PM, jfabernathy
wrote:
It seems that something happened today. I could not complete a
build on
edison branch for meta-cedartrail. I copied
On 30/01/12 13:54, jfabernathy wrote:
On 01/30/2012 04:51 PM, Bruce Ashfield wrote:
On Mon, Jan 30, 2012 at 4:47 PM, jfabernathy
wrote:
It seems that something happened today. I could not complete a build on
edison branch for meta-cedartrail. I copied it to meta-mycdv, but other
than that same,
On 01/30/2012 04:51 PM, Bruce Ashfield wrote:
On Mon, Jan 30, 2012 at 4:47 PM, jfabernathy wrote:
It seems that something happened today. I could not complete a build on
edison branch for meta-cedartrail. I copied it to meta-mycdv, but other
than that same, old same old. I tried the standard
On Mon, Jan 30, 2012 at 4:47 PM, jfabernathy wrote:
> It seems that something happened today. I could not complete a build on
> edison branch for meta-cedartrail. I copied it to meta-mycdv, but other
> than that same, old same old. I tried the standard unchanged SRCREV and
> also tried the lates
It seems that something happened today. I could not complete a build on
edison branch for meta-cedartrail. I copied it to meta-mycdv, but other
than that same, old same old. I tried the standard unchanged SRCREV and
also tried the latest.
Error below:
ERROR: Function 'do_validate_branches'
On Mon, 2012-01-30 at 08:34 -0800, paul_nat...@selinc.com wrote:
> I am investigating Yocto for a build system here. Part of my
> requirements for a build system is auditable/traceable builds that can
> be replicated long into the future (our company has a 10 year warranty
> on our products, and we
On 30 Jan 2012, at 18:34, Flanagan, Elizabeth wrote:
On Mon, Jan 30, 2012 at 8:34 AM, wrote:
Hi,
I am investigating Yocto for a build system here. Part of my
requirements
for a build system is auditable/traceable builds that can be
replicated long
into the future (our company has a 10 ye
On Mon, Jan 30, 2012 at 8:34 AM, wrote:
> Hi,
>
> I am investigating Yocto for a build system here. Part of my requirements
> for a build system is auditable/traceable builds that can be replicated long
> into the future (our company has a 10 year warranty on our products, and we
> build products
To all users of the Yocto Project bug tracker, we are about to upgrade
our Bugzilla install to the newest version and we need your help.
At https://dev.yoctoproject.org/ you will find two copies of Bugzilla:
our attempt at upgrading to the newest version 4.0.3
and a copy of our current 3.6.1 v
2012/1/30
> Hi,
>
> I am investigating Yocto for a build system here. Part of my requirements
> for a build system is auditable/traceable builds that can be replicated
> long into the future (our company has a 10 year warranty on our products,
> and we build products for the multidecade term). In
On 2012-01-30 10:37, Khem Raj wrote:
On Mon, Jan 30, 2012 at 8:34 AM, wrote:
Hi,
I am investigating Yocto for a build system here. Part of my requirements
for a build system is auditable/traceable builds that can be replicated long
into the future (our company has a 10 year warranty on our pro
On Mon, Jan 30, 2012 at 8:34 AM, wrote:
> Hi,
>
> I am investigating Yocto for a build system here. Part of my requirements
> for a build system is auditable/traceable builds that can be replicated long
> into the future (our company has a 10 year warranty on our products, and we
> build products
Hi,
I am investigating Yocto for a build system here. Part of my requirements
for a build system is auditable/traceable builds that can be replicated
long into the future (our company has a 10 year warranty on our products,
and we build products for the multidecade term). Initial examination of
On 01/28/2012 10:22 AM, Michael Halstead wrote:
On 01/28/2012 10:13 AM, Khem Raj wrote:
On Thu, Jan 26, 2012 at 2:59 PM, Saul Wold wrote:
We will make this change next week barring any major objections.
its a good idea infact. will you do svn2git conversion as well. ?
I converted from svn to
Hello Darren, Martin,
Thanks for the reply.
On Fri, 2012-01-27 at 09:13 -0800, Darren Hart wrote:
> > Why not .bbappend base-files and customize fstab there?
>
> This is how I am modifying /etc/network/interfaces and this is working
> fine for me. Joshua, I'd second Martin's suggestion.
As you
On 28/01/12 02:16, McClintock Matthew-B29882 wrote:
On Wed, Jan 25, 2012 at 7:36 AM, Brian Hutchinson wrote:
On Wed, Jan 25, 2012 at 9:48 AM, Jack Mitchell wrote:
Hi Brian,
Your best bet is to adapt the one from meta-oe here:
http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recip
Hello,
I found a minor typo mistake in ix86-common file which causes the
guile-native package to fail for unsigned int size. So, I am including a
patch for it. I am not sure about the patch sending guidelines. Anyways
here is the patch for it.
diff --git a/meta/site/ix86-common b/meta/site/ix86-c
31 matches
Mail list logo
