[Buildroot] Where does post-build script belong?

Thomas De Schampheleire patrickdepinguin+buildroot at gmail.com
Wed Feb 29 07:41:07 UTC 2012


On Tue, Feb 28, 2012 at 11:19 PM, Arnout Vandecappelle <arnout at mind.be> wrote:
> On Tuesday 28 February 2012 22:06:28 Steve Calfee wrote:
>> > I seem to be completely lost.  Is board/mycompany/myproduct/skeleton
>> > above a post-build script or a custom skelecton (something you set
>> > BR2_ROOTFS_SKELETON_CUSTOM_PATH to point to)?
>> Hi Grant,
>>
>> I was not aware of that config option. In fact there are no uses of it
>> in the current /board... stuff. What I and what I think others have done
>> is create my own mini-skeleton in the board.... directory. I can then
>> stick in scripts, etc files and maybe even externally built binaries
>> into /usr/bin/ in my local area. Then when the post build script is
>> executed I just copy all the files from my skeleton to the target
>> skeleton. This will overlay the default stuff (that are duplicates in my
>> area) and add any new stuff. After the post-build script the target
>> skeleton will get all packaged up as a rootfs for your target system.
>>
>> Someone else will have to describe what that option is for.
>
>  If you ask me, BR2_ROOTFS_SKELETON_CUSTOM_PATH is indeed useless and
> should be deprecated.

Although I'm not using it myself, I don't think this needs to be
deprecated. I can imagine that there are users who have a
significantly different skeleton that it would be a nuisance to have
to tweak it from a script.

Although we may recommend in the docs to use the post-build script +
rootfs-additions, I would keep the custom option as well.

Best regards,
Thomas



More information about the buildroot mailing list