IBY and OBY Files

-----------------------------------IBY and OBY Files --------------------------

-------IBY and OBY are text files. There is no fantastic architecture behind it; it’s all for understanding purpose. Suppose consider a situation writing a C++ application, we are placing all declaration in the header file and finally including the header file in the “.cpp” file, instead of doing that we can directly place all the declaration in the “.cpp” file itself but it is not recommended because time to understand the code is based on coding guidelines so we are doing like that.

Consider that, we have five modules, that to be added in ROM build. How we will tell this information to ROM build tool?
Module1
--------IBY = (information) (Needed files for rom build)
Module2
--------IBY = (information) (Needed files for rom build)
Module3
--------IBY = (information) (Needed files for rom build)
Module4
--------IBY = (information) (Needed files for rom build)
Module5
--------IBY = (information) (Needed files for rom build)

-------- Each module contains an IBY file, Its only for storing information about that particular module, so that build tool can use the information for creating CORE or ROFS image, Whenever kernel executing a program it needs some resource file in some particular directory, those files and where it should be copied, all these information is provided by this (IBY) file. When kernel executing a program it will get all the resources from there.

-------- IBY is mainly focused to a particular module. OBY file is nothing; it just contains all IBY files. Don’t argue why we should maintain that because as I said before, it’s all for understanding. Suppose consider a situation that u need to update a module, finally its necessary to change something in IBY file that time we no need to disturb the OBY file just modifying IBY file will reflect in OBY. It’s totally Object oriented concept that means “Reducing programmers work burden” nothing else.