From: Darren Hart <dvhart@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Koen Kooi <koen@beagleboard.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] [RFC] kernel: rework kernel and module classes to allow for building out-of-tree modules
Date: Tue, 15 Mar 2011 13:01:04 -0700 [thread overview]
Message-ID: <4D7FC580.7060307@linux.intel.com> (raw)
In-Reply-To: <1300217648.30423.1837.camel@rex>
On 03/15/2011 12:34 PM, Richard Purdie wrote:
> On Tue, 2011-03-15 at 12:27 -0700, Darren Hart wrote:
>>
>> On 03/15/2011 11:23 AM, Richard Purdie wrote:
>>> On Tue, 2011-03-15 at 10:24 -0700, Khem Raj wrote:
>>>> On Tue, Mar 15, 2011 at 10:07 AM, Darren Hart<dvhart@linux.intel.com> wrote:
>>>>>
>>>>> What are the ownership and perms on those?
>>>>>
>>>>> I suppose we could avoid the .pc directory - but it's going to require
>>>>> something more than cp or some additional scripting. Something like tar's
>>>>> exclude functionality might be needed - but I hate to add the intermediate
>>>>> step as the kernel recipes are already so slow.
>>>>
>>>>
>>>> hmmm I wonder why those are marked non readable in .pc directory that
>>>> seems wrong to me
>>>
>>> Its quilt that does this. Kind of annoying but its been doing that for a
>>> few versions now...
>>
>> I recall purging .pc for this reason (just in other development, outside
>> of poky).
>>
>> I take it deleting .pc from the build dir would be bad as it would make
>> build/hack/build fail to work on the workdir tree. That leaves changing
>> the permissions and copying it, or just avoiding the copy. I'm leaning
>> towards avoiding the copy - but I hate to add a ton of scripting logic
>> in the copy, but that may be the best solution.
>
> Can't you just do a "cp -r xxx/*" and if you need any . files "cp
> xxx/.*" ?
Well yes, I suppose I can. Duh. Sorry, forest for the trees and all that.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-03-15 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 7:25 [PATCH] [RFC] kernel: rework kernel and module classes to allow for building out-of-tree modules Darren Hart
2011-03-15 8:31 ` Koen Kooi
2011-03-15 17:07 ` Darren Hart
2011-03-15 17:24 ` Khem Raj
2011-03-15 18:23 ` Richard Purdie
2011-03-15 19:27 ` Darren Hart
2011-03-15 19:34 ` Richard Purdie
2011-03-15 20:01 ` Darren Hart [this message]
2011-03-16 2:02 ` Khem Raj
2011-03-15 17:25 ` Koen Kooi
2011-03-16 6:50 ` Darren Hart
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=4D7FC580.7060307@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=koen@beagleboard.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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