On Fri, Mar 15, 2013 at 7:46 AM, Bruce Ashfield
<bruce.ashfi...@windriver.com> wrote:
> On 13-03-15 04:47 AM, Insop Song wrote:
>>
>> ---
>>   recipes-extended/images/core-image-realtime.bb |    1 +
>>   recipes-tools/schedtool-dl/schedtool-dl.bb     |   23
>> +++++++++++++++++++++++
>>   2 files changed, 24 insertions(+)
>>   create mode 100644 recipes-tools/schedtool-dl/schedtool-dl.bb
>>
>> diff --git a/recipes-extended/images/core-image-realtime.bb
>> b/recipes-extended/images/core-image-realtime.bb
>> index 624aacf..386b16b 100644
>> --- a/recipes-extended/images/core-image-realtime.bb
>> +++ b/recipes-extended/images/core-image-realtime.bb
>> @@ -8,5 +8,6 @@ EXTRA_IMAGE_FEATURES = "tools-debug debug-tweaks
>> tools-profile dbg-pkgs"
>>   IMAGE_INSTALL = "\
>>         ${CORE_IMAGE_BASE_INSTALL} \
>>         rt-app \
>> +       schedtool-dl \
>>         libgcc \
>>         "
>
>
> This part of the patch is still a problem, so I'll drop  it on merge.
> We still need to rationalize why we can't extend the oe-core
> rt images:
>
> ./recipes-rt/images/core-image-rt.bb
> ./recipes-rt/images/core-image-rt-sdk.bb
>
> For this addition. Until we work through that, you can carry a local
> patch, or add the tools back via your local.conf adding it to IMAGE_INSTALL.
>
>

I put the "libgcc" because rt-app complained during finish regarding
pthread and libgcc during my previous meta-realtime/meta-dl, which was
using core-image-minimal.

Since, I updated my image bases this time, I might not need it.
I will test without "libgcc" and will update the patch.

I've updated my poky tree to the latest, and I am having trouble due
to "neard" package failure (I post a question on this).
That's why it's taking long to verify and update the patch.


>> diff --git a/recipes-tools/schedtool-dl/schedtool-dl.bb
>> b/recipes-tools/schedtool-dl/schedtool-dl.bb
>> new file mode 100644
>> index 0000000..6b298f1
>> --- /dev/null
>> +++ b/recipes-tools/schedtool-dl/schedtool-dl.bb
>> @@ -0,0 +1,23 @@
>> +DESCRIPTION = "schedtool-dl (scheduler test tool) for deadline scheduler"
>> +SECTION = "devel"
>> +LICENSE = "GPLv2"
>> +LIC_FILES_CHKSUM =
>> "file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984"
>> +PR = "r1"
>> +
>> +SRC_URI = "git://github.com/jlelli/schedtool-dl.git;protocol=git"
>> +SRCREV = "${AUTOREV}"
>
>
> We also want to lock down the SRCREV vs autorev. I'd expect that going
> forward,
> you can maintain/update this once we've merged it, so when a SRCREV
> is known to be good, you can send update patches with the new values
> (just like I do with linux-yocto in oe-core). But in the general case,
> we want to have consistent and reproducible builds and to do that,
> we need a well defined SRCREV.
>

updated and testing is in-progress.


> So one more version of the series and we should be good (you can
> drop the image addition as part of that) .. sorry for all the
> iterations, the first merges always take the longest.
>

I appreciate your through review and will send out the revision soon
as I am done testing.

Insop
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to