How to use Source control with yocto builds

[w2vy]

We are starting to do some development for imx using yocto.

One thing we need is the ability to work on a common codebase.

We will have add-on layers for our custom subsystems, granted that the bulk of the code will be pulled from *other* control systems, but I want to be able to save our custom layers and other configuration settings saved in our local CVS system.

Anyone else doing this?

(And if not, WHY NOT? :smileyhappy:)

Tom

[w2vy]

I was more asking is anyone using CVS or SVN or (fill in the blank) to save their changes.

Changes like custom layers, etc

I have no desire to put everything we download into source control;

That's what the yocto tools are for, downloading official sources and applying our custom changes and compiling it all.

But there are files I create to tell bitbake what to do differently for me...

it is THOSE files I want to check into a source control system so when (not IF) my system blows up I don't lose everything

tom

[jimmychan]

This may useful for you

For your reference :

Creating a custom distribution image with Yocto for the RIoTboard