[Buildroot] which templates are used?
Bjørn Forsman
bjorn.forsman at gmail.com
Tue Apr 12 17:54:50 UTC 2011
On 12 April 2011 08:42, Patryk Benderz <Patryk.Benderz at esp.pl> wrote:
> [cut]
>> Buildroot has a quirk: the rootfs skeleton is copied to the target dir
>> only once(!). If you change any files in ./fs/skeleton (or your custom
>> path) you have to do "make clean" and start over (or hack the
>> Makefile, around line 420...).
> It's not a quirk. I always thought its designed like that.
Yes, it's most likely intended.
But why not always copy skeleton to target dir? I think it would be
more user friendly. If you remove stuff from skeleton you will get out
of sync with target dir, but without a package manager that
out-of-sync problem is inevitable (unless doing full "make clean &&
make".. painfully slow for small skeleton changes). And there *is*
currently an out-of-sync problem in that changes to ./fs/skeleton is
not copied to target dir. And that is confusing.
I think it is more common to *change* skeleton files than to remove,
so I would definitely like to see always-copy-skeleton functionality
in Buildroot.
> You should
> work and modify files in directory buildroot/output/target, shouldn't
> you?
If you meant "you should not modify files in buildroot/output/target"
then yes. That directory is the output of builds and "make clean" will
destroy it.
Best regards,
Bjørn Forsman
More information about the buildroot
mailing list