[LEDE-DEV] Makefile question

[Philip Prindeville]

> On Feb 12, 2017, at 11:20 PM, Philip Prindeville <philipp_subx at redfish-solutions.com> wrote:
> 
> 
>> On Feb 12, 2017, at 11:15 PM, David Lang <david at lang.hm> wrote:
>> 
>> On Sun, 12 Feb 2017, Philip Prindeville wrote:
>> 
>>>>>>>> If you look for where the /files/* are copied into the filesystem, that is probably the place you would want to add your scripting hooks.
>>>>>>> 
>>>>>>> Good idea.  I’ll look there.
>>>>>> 
>>>>>> Once you find this, may I suggest that you create /scripts/* and contribute the infrastructure to support it back upstream?
>>>>>> 
>>>>>> I have seen a lot of people wanting to do similar things.
>>>>> 
>>>>> 
>>>>> Surprisingly, I’m still trying to find in the Makefiles where $(topdir)/files/ gets copied over…
>>>>> 
>>>>> -Philip
>>>> 
>>>> It's prepare_rootfs doing this job at the moment.
>>>> 
>>>>              yousong
>>> 
>>> Sorry to be thick headed, but what’s the path to that?
>> 
>> grep -r "/files/" finds
>> 
>> scripts/env:            cp -a "$ENVDIR/files/"* "$BASEDIR/files" 2>/dev/null >/dev/null
> 
> 
> That juggles the “live” set of contents for files/ versus alternate sets you might have stashed away in env/files/ …
> 
> That not what yousong was talking about, I don’t think.
> 

Okay, my bad.  I was looking in an OpenWRT tree and not an LEDE tree because I thought that part of the two was the same.

It’s not.

Openwrt has prepare_generic_squashfs and LEDE has prepare_rootfs, and they’re very different.