On 12/11/14 12:14, Paul Eggleton wrote:
>> It's not supposed to behave this way, although I have reproduced it here - I
>> think I hadn't actually tested rebuilding an image with a recipe in the
>> workspace added to the image. The problem is that the do_compile task is
>> being marked as nostamp,
On Thu, Dec 11, 2014 at 7:35 PM, Paul Eggleton
wrote:
> On Thursday 11 December 2014 14:43:40 Trevor Woerner wrote:
>> On 12/11/14 14:16, Trevor Woerner wrote:
>> > Oops! (this worked before the "git pull")
>> >
>> > $ devtool add xannounce ~/devel/yocto/build/workflow/xannounce/
>> > NOTE
On Thursday 11 December 2014 18:10:57 Trevor Woerner wrote:
> I think *this* thread (and question) got lost in the shuffle...
>
> On 12/09/14 10:47, Trevor Woerner wrote:
> > On 12/02/14 09:01, Paul Eggleton wrote:
> >> On Monday 01 December 2014 23:54:03 Trevor Woerner wrote:
> >>> On 11/25/14 12
On 12/11/14 16:35, Paul Eggleton wrote:
> Thanks for the quick bisect - I've fixed it so that wrapper is only used when
> running bitbake through "devtool build", and now "devtool add" works properly
> again. This is why I should probably write some proper tests before trying to
> do anything f
I think *this* thread (and question) got lost in the shuffle...
On 12/09/14 10:47, Trevor Woerner wrote:
> On 12/02/14 09:01, Paul Eggleton wrote:
>> On Monday 01 December 2014 23:54:03 Trevor Woerner wrote:
>>> On 11/25/14 12:28, Paul Eggleton wrote:
I've then added a new recipe auto-creatio
On Thursday 11 December 2014 14:43:40 Trevor Woerner wrote:
> On 12/11/14 14:16, Trevor Woerner wrote:
> > Oops! (this worked before the "git pull")
> >
> > $ devtool add xannounce ~/devel/yocto/build/workflow/xannounce/
> > NOTE: Creating workspace layer in
> > /home/trevor/devel/yoct
bisecting (manually) leads to this commit being safe:
ea50ec527483eb3a094588858baebd5fb23f71c6 devtool: rename deploy/undeploy
to deploy-target/undeploy-target
and this one introducing the problem:
770f203f73f358ce3c6c5ac12fe2775b812bdc6b devtool: fool bitbake into
thinking it's outputting to a
Oops! (this worked before the "git pull")
$ devtool add xannounce ~/devel/yocto/build/workflow/xannounce/
NOTE: Creating workspace layer in
/home/trevor/devel/yocto/build/workflow/build/workspace
NOTE: Recipe
/home/trevor/devel/yocto/build/workflow/build/workspace/recipes/xann
On Thursday 11 December 2014 13:30:01 Trevor Woerner wrote:
> Awesome!! I'm giving this update a whirl right now...
>
> ...just one small nit... in commit
> 7d2c6430131ccf94b8bdc185b8cd849fe479d552 the warning message says:
>
> +lines_before.append('# NOTE: LICENSE is being set to "CLOSED
Awesome!! I'm giving this update a whirl right now...
...just one small nit... in commit
7d2c6430131ccf94b8bdc185b8cd849fe479d552 the warning message says:
+lines_before.append('# NOTE: LICENSE is being set to "CLOSED"
to allow you to at least start building - if')
+lines_before.a
On Wednesday 10 December 2014 17:51:16 Paul Eggleton wrote:
> On Tuesday 09 December 2014 13:58:02 Trevor Woerner wrote:
> > On 12/09/14 11:08, Paul Eggleton wrote:
> > > "devtool build" isn't strictly required in this phase, I added it
> > > primarily to support future usage in the SDK where the i
On Tuesday 09 December 2014 13:58:02 Trevor Woerner wrote:
> On 12/09/14 11:08, Paul Eggleton wrote:
> > On Tuesday 09 December 2014 10:39:05 Trevor Woerner wrote:
> >> Okay. Maybe it'd be best to just revert to bitbake? IOW, does the
> >> devtool tool need its own "build,deploy,..."?
> >
> > We d
On 12/09/14 11:08, Paul Eggleton wrote:
> On Tuesday 09 December 2014 10:39:05 Trevor Woerner wrote:
>>
>> Okay. Maybe it'd be best to just revert to bitbake? IOW, does the
>> devtool tool need its own "build,deploy,..."?
> We did talk about this in a previous email, but just to clarify:
>
> "devt
On Tuesday 09 December 2014 10:39:05 Trevor Woerner wrote:
> On 12/09/14 10:10, Paul Eggleton wrote:
> > On Tuesday 09 December 2014 10:00:51 Trevor Woerner wrote:
> >> Would it be possible to make the output of devtool be nice and colourful
> >> like the output of bitbake?
> >>
> >>> Good idea, t
On 12/02/14 09:01, Paul Eggleton wrote:
> On Monday 01 December 2014 23:54:03 Trevor Woerner wrote:
>> On 11/25/14 12:28, Paul Eggleton wrote:
>>> I've then added a new recipe auto-creation script, recipetool, which can
>>> take a source tree or URL and create a skeleton recipe to build it.
>> ...
On 12/09/14 10:10, Paul Eggleton wrote:
> On Tuesday 09 December 2014 10:00:51 Trevor Woerner wrote:
>> Would it be possible to make the output of devtool be nice and colourful
>> like the output of bitbake?
>>> Good idea, this is now done on the branch as well. "devtool build" doesn't
>>> support
On Tuesday 09 December 2014 10:00:51 Trevor Woerner wrote:
> (oops! sorry for going off-list)
>
> On 12/09/14 05:50, Paul Eggleton wrote:
> > On Monday 08 December 2014 22:30:31 Trevor Woerner wrote:
> >> This is really awesome stuff. I'm still playing around with it.
> >>
> >> My current HEAD is
(oops! sorry for going off-list)
On 12/09/14 05:50, Paul Eggleton wrote:
> On Monday 08 December 2014 22:30:31 Trevor Woerner wrote:
>> This is really awesome stuff. I'm still playing around with it.
>>
>> My current HEAD is:
>>
>> commit 6ea5f5368a88317ace198f44a47cf043bc9fb6e6
>> Author
Hi Trevor,
On Thursday 04 December 2014 09:03:37 Trevor Woerner wrote:
> Are you making these changes on the existing contrib/paule/devtool or
> somewhere else?
Actually I hadn't pushed them anywhere; I have just done that on the
paule/devtool branch in both contrib repos. I'm collecting commits
Hi Paul,
Are you making these changes on the existing contrib/paule/devtool or
somewhere else?
A small nit I stumbled on recently... many layers contain a
"recipes-devtools" directory, and I'm thinking that using the same word
for this feature might get confusing (?). Maybe it would be best to
re
On Monday 01 December 2014 23:54:03 Trevor Woerner wrote:
> On 11/25/14 12:28, Paul Eggleton wrote:
> > I've then added a new recipe auto-creation script, recipetool, which can
> > take a source tree or URL and create a skeleton recipe to build it.
>
> ...
>
> > * "recipetool create" ideally nee
On Monday 01 December 2014 23:36:23 Trevor Woerner wrote:
> On 12/01/14 05:11, Paul Eggleton wrote:
> > On Friday 28 November 2014 12:28:00 Trevor Woerner wrote:
> >> Perhaps any recipe you're working on could be automatically included via
> >> an IMAGE_INSTALL_append in conf/local.conf (or maybe t
On 11/25/14 12:28, Paul Eggleton wrote:
> I've then added a new recipe auto-creation script, recipetool, which can
> take a source tree or URL and create a skeleton recipe to build it.
...
> * "recipetool create" ideally needs to become smarter and fill in
>more details of the recipe. At som
On 12/01/14 05:11, Paul Eggleton wrote:
> On Friday 28 November 2014 12:28:00 Trevor Woerner wrote:
>> Perhaps any recipe you're working on could be automatically included via
>> an IMAGE_INSTALL_append in conf/local.conf (or maybe that's too intrusive?)?
> This is something I'd wanted to do - it'
On Friday 28 November 2014 12:28:00 Trevor Woerner wrote:
> These tools are really nice! Some thoughts/comments:
>
> Maybe the "devtool.conf" that gets created could be placed in the
> "conf/" subdirectory (along with the other configuration files such as
> local.conf and bblayers.conf)?
Yes, tha
Hi Paul,
These tools are really nice! Some thoughts/comments:
Maybe the "devtool.conf" that gets created could be placed in the
"conf/" subdirectory (along with the other configuration files such as
local.conf and bblayers.conf)?
Perhaps any recipe you're working on could be automatically includ
Hi Trevor,
On Tuesday 25 November 2014 14:56:14 Trevor Woerner wrote:
> Just thinking out loud here... is there a way to way to have the
> devshell come up without having applied any patches but with the patches
> already queued in, say, a quilt series?
>
> It seems to happen often enough to me th
Wow, this is exciting!
Just thinking out loud here... is there a way to way to have the
devshell come up without having applied any patches but with the patches
already queued in, say, a quilt series?
It seems to happen often enough to me that: a recipe has 10 local
patches which applied fine yes
On Tuesday 25 November 2014 17:51:05 Paul Barker wrote:
> On 25 November 2014 at 17:28, Paul Eggleton
> wrote:
> > I've been looking at how to make it easier for application and system
> > component developers to get their work done using the tools we provide,
> > and I believe this patchset is a
On 25 November 2014 at 17:28, Paul Eggleton
wrote:
> [Note: this is an RFC series for the moment, and shouldn't yet be merged.]
>
> I've been looking at how to make it easier for application and system
> component developers to get their work done using the tools we provide,
> and I believe this p
[Note: this is an RFC series for the moment, and shouldn't yet be merged.]
I've been looking at how to make it easier for application and system
component developers to get their work done using the tools we provide,
and I believe this patchset is a piece of the solution. There's still a
number of
31 matches
Mail list logo
