From: Denys Dmytriyenko <denis@denix.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] opencl-headers: Initial recipe for OpenCL headers
Date: Mon, 15 Oct 2018 15:34:37 -0400 [thread overview]
Message-ID: <20181015193437.GI7186@denix.org> (raw)
In-Reply-To: <CAJTo0LYk2Z866pnf7gAt=JaqrfF+f857SDet0G-iLssvp44fVA@mail.gmail.com>
On Mon, Oct 15, 2018 at 08:07:06PM +0100, Burton, Ross wrote:
> On Mon, 15 Oct 2018 at 20:01, Denys Dmytriyenko <denis@denix.org> wrote:
> > > > > > > > > > +do_install () {
> > > > > > > > > > + install -d ${D}${includedir}/CL/
> > > > > > > > > > + for f in ${S}/CL/*.h; do
> > > > > > > > > > + install -m 0644 $f ${D}${includedir}/CL/
> > > > > >
> > > > > > Single file install? Not very optimized...
> > > >
> > > > > Its not a single file, Installing all the header files.
> > > >
> > > > It's a single file install in a for loop, hence my comment about being
> > > > unoptimal. Why not use "cp *.h"?
> > >
> > > I agree its suboptimal use here. May be
> > >
> > > install [OPTION]... -t DIRECTORY SOURCE
> > >
> > > could be tamed to make it better.
> > > however cp messes the file permissions up if not used with right opts.
> > > So I would not prefer it unless used with right
> > > options to respect the file perms. Install does it correctly,
> >
> > Agree, cp would require passing correct options, but there are plenty of
> > examples alreay.
>
> If we're bikeshedding a micro-optimisation then surely this is optimal:
>
> install -m 0644 -D -t ${D}${includedir}/CL ${S}/CL/*.h
>
> That combines the mkdir and cp in one command.
+1
And who said bikeshedding is a waste of time? :)
--
Denys
next prev parent reply other threads:[~2018-10-15 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 15:40 [PATCH] opencl-headers: Initial recipe for OpenCL headers Ankit Navik
2018-10-03 23:10 ` akuster808
2018-10-06 8:49 ` Ankit Navik
2018-10-14 18:29 ` Khem Raj
2018-10-15 3:12 ` Denys Dmytriyenko
2018-10-15 10:43 ` Ankit Navik
2018-10-15 18:14 ` Denys Dmytriyenko
2018-10-15 18:19 ` Khem Raj
2018-10-15 19:00 ` Denys Dmytriyenko
2018-10-15 19:07 ` Burton, Ross
2018-10-15 19:34 ` Denys Dmytriyenko [this message]
2018-10-16 4:40 ` Ankit Navik
2018-10-15 10:41 ` Ankit Navik
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=20181015193437.GI7186@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.