Kom was designed to make this type of operation simple and without too many thoughts on how to adapt the project to the new system.
Actually a project created with Kom is not touched in any way.
The initialization of the project (to be clear about: ". koprofile") automates the configuration of the project. The only thing you need to know where the project is to find the overlays used.
Take a practical example: own project own_proj extend OpenEmbedded overlay and we have created a new images myimages.bb.
For some reason, we should move your project in another system new_system in another PC which have the OpenEmbedded overlay path installed in /opt/overlays/openembedded.
Moreover, you should rename project as barfoo. and placed in your new home directory.
To move your project, first move own_proj directory in new system. In this example the move operation is make with scp:
# Move project scp -r /tmp/own_proj new_system:~/barfoo # Configure kom to find OpenEmbedded kom -o oe /opt/overlays/openembedded # Configure kom to find Bitbake kom -s -v [bitbake_path] # Update project's configuration . komprofile # Finish! Now can start to use bitbake..
With these simple steps, you are now ready to use bitbake!
