From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Insop Song <insop.song@gmail.com>
Cc: yocto@yoctoproject.org, dvhart@linux.intel.com,
linux-yocto@yoctoproject.org
Subject: Re: [PATCH 1/1] add scheedtool-dl for testing sched_deadline use jiri's github as a main repo
Date: Fri, 15 Mar 2013 07:46:54 -0700 [thread overview]
Message-ID: <5143345E.9070703@windriver.com> (raw)
In-Reply-To: <a766d16a1cf4da3c2dd13b8c7e53f89775733187.1363347615.git.insop.song@gmail.com>
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.
> 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.
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.
Cheers,
Bruce
> +
> +S = "${WORKDIR}/git"
> +
> +do_compile() {
> + oe_runmake
> +}
> +
> +do_install() {
> + install -d ${D}${bindir}
> + install -m 0755 schedtool ${D}${bindir}
> +}
> +
> +FILES_{PN} = "${bindir}/schedtool"
> +
> +PARALLEL_MAKE = ""
>
next prev parent reply other threads:[~2013-03-15 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 11:47 [PATCH 0/1] add scheedtool-dl for testing sched_deadline Insop Song
2013-03-15 11:47 ` [PATCH 1/1] add scheedtool-dl for testing sched_deadline use jiri's github as a main repo Insop Song
2013-03-15 14:46 ` Bruce Ashfield [this message]
2013-03-16 8:30 ` Insop Song
2013-03-17 5:01 ` Khem Raj
2013-03-17 6:51 ` Insop Song
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5143345E.9070703@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=insop.song@gmail.com \
--cc=linux-yocto@yoctoproject.org \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.