Customers have requested the ability to have a script that is executed after the RPM processing was complete, but before the dist.tar.bz2 file was created.
This is the documentation snippet for the File System Finalization
feature, known as fs_final.sh. This feature is available in the 1.4
WR Linux runtime product and up. If you want to use it in 1.4, you
must apply the patch WIND00089708.zip
If you create a script or compiled executable called fs_final.sh and place it the same directory as where you initially ran the "configure" command or the _prj directory if you are using the WB, this script or executable will be invoked after the RPM and pre-link phase has run, but before the final export/-dist.tar.bz2 file is created.
The fs_final.sh is invoked in the fakeroot context in from the directory export/dist, relative to where you ran configure. This will allow you to remove or add files, as well as create device nodes or symlinks.
Additionally you can run fs_final.sh script over and over if you like with the make rule "make fs_final_run".
At the point in time that you are satisfied with the fs_final.sh script you can elect to make it part of the BSP template. You can choose to have one master fs_final.sh for the BSP, or you can create an fs_final.sh for each type of file system that is supported. If you are using only one fs_final.sh for the bsp simply place the fs_final.sh in the top level of the bsp directory in your layer or the product install. IE:
wrlinux/templates/board/arm_versatile_926ejs/fs_final.sh
If you wanted to to make independent fs_final.sh scripts for each type of file system, then you would place a fs_final.sh file in each file system director in the bsp template IE:
wrlinux/templates/board/arm_versatile_926ejs/rootfs/glibc_small/fs_final.sh
wrlinux/templates/board/arm_versatile_926ejs/rootfs/glibc_std/fs_final.sh
wrlinux-2.0/wrlinux/templates/board/arm_versatile_926ejs/rootfs/uclibc_small/fs_final.sh IDENTIFIER = WIND00089704-PNELE
