From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] piglit: enable ptest support
Date: Tue, 02 Sep 2014 08:35:44 +0100 [thread overview]
Message-ID: <1409643344.29296.262.camel@ted> (raw)
In-Reply-To: <540572C3.4080607@windriver.com>
On Tue, 2014-09-02 at 15:33 +0800, Robert Yang wrote:
>
> On 09/02/2014 10:14 AM, Robert Yang wrote:
> >
> >
> > On 08/28/2014 10:09 PM, Burton, Ross wrote:
> >> On 18 August 2014 06:39, Chong Lu <Chong.Lu@windriver.com> wrote:
> >>> +env PIGLIT_BUILD_DIR=`pwd`/.. piglit-run.py `pwd`/tests/sanity.tests
> >>> `pwd`/results/sanity.results 2>&1
> >>
> >> You shouldn't need to set PIGLIT_BUILD_DIR.
> >>
> >> The sanity tests are very basic so this won't count as "running
> >> piglit" in any meaningful QA sense.
> >>
> >>> @@ -36,7 +37,6 @@ do_install() {
> >>> cp -Pr lib/ ${D}${libdir}/piglit/
> >>> cp -Pr framework/ ${D}${libdir}/piglit/
> >>> cp -Pr generated_tests/ ${D}${libdir}/piglit/
> >>> - cp -Pr tests/ ${D}${libdir}/piglit/
> >>> cp -Pr templates/ ${D}${libdir}/piglit/
> >>>
> >>> sed -i -e
> >>> 's|sys.path.append(.*)|sys.path.append("${libdir}/piglit")|'
> >>> ${D}${bindir}/piglit-*.py
> >>> @@ -46,3 +46,7 @@ do_install() {
> >>> FILES_${PN}-dbg += "${libdir}/piglit/*/.debug/"
> >>>
> >>> RDEPENDS_${PN} = "python waffle python-json python-subprocess
> >>> python-multiprocessing python-textutils python-netserver python-shell
> >>> mesa-demos"
> >>> +
> >>> +do_install_ptest() {
> >>> + cp -Pr tests/ ${D}${PTEST_PATH}/
> >>> +}
> >>
> >> Why move the tests directory to the -ptests package? That makes
> >> piglit unusable without installing piglit-ptest.
> >
> > Hello, if we keep the tests dir in piglit, shall we add perl to
>
> Sorry, bash, in fact.
A bash dependency on the piglit recipe isn't an issue. Its only an issue
where it forces bash or perl into "small" builds. If you're including
piglit, its not a small build :)
Cheers,
Richard
next prev parent reply other threads:[~2014-09-02 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 5:39 [PATCH V2 0/1] piglit: enable ptest support Chong Lu
2014-08-18 5:39 ` [PATCH 1/1] " Chong Lu
2014-08-28 14:09 ` Burton, Ross
2014-09-02 2:14 ` Robert Yang
2014-09-02 7:33 ` Robert Yang
2014-09-02 7:35 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-18 3:11 [PATCH 0/1] " Chong Lu
2014-08-18 3:11 ` [PATCH 1/1] " Chong Lu
2014-08-18 5:39 ` Chong Lu
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=1409643344.29296.262.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox