How to organize OE environment for intermediate builds

How to organize OE environment for intermediate builds

[Alexander Shashkevych]

Hello,

I would like to ask you how do you organize your development environments for OE?

Let me explain. From my point of view OE build system is well suited for builds of released code, but not for code that is still under development with many intermediate builds. My case: I started a project for Freescale platform and due to bsp headers/libs/cross-compiling it can be built only within OE environment. I have already committed initial code to my project's repo and have already written layers&recipes to build project from git. That was not a problem and it works. Then I added new changes to my project and stuck. Before I'll commit them into git I need to build&test to be sure that everything is OK, but to build changes with bitbake they should be committed first. Mutual exclusive situation: can't commit without build and can't build without commit.

How do you escape this? How to best organize OE environment for intermediate builds without commits?

PS: I hope you understand that endless commit'n'push of each little change for just-to-test is extremely superfluous.

Regards,
Alexander

Re: How to organize OE environment for intermediate builds

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

On Fri, Nov 14, 2014 at 12:27:03AM +0200, Alexander Shashkevych wrote:
> Hello,

Hi,

> 
> I would like to ask you how do you organize your development environments for OE?
> 
> Let me explain. From my point of view OE build system is well suited for builds of released code, but not for code that is still under development with many intermediate builds. My case: I started a project for Freescale platform and due to bsp headers/libs/cross-compiling it can be built only within OE environment. I have already committed initial code to my project's repo and have already written layers&recipes to build project from git. That was not a problem and it works. Then I added new changes to my project and stuck. Before I'll commit them into git I need to build&test to be sure that everything is OK, but to build changes with bitbake they should be committed first. Mutual exclusive situation: can't commit without build and can't build without commit.
> 
> How do you escape this? How to best organize OE environment for intermediate builds without commits?
> 
> PS: I hope you understand that endless commit'n'push of each little change for just-to-test is extremely superfluous.

Check externalsrc.bbclass

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

Re: How to organize OE environment for intermediate builds

[Alexander Shashkevych]

On Fri, Nov 14, 2014 at 1:56 PM, Martin Jansa <martin.jansa@gmail.com> wrote:

>> How do you escape this? How to best organize OE environment for intermediate builds without commits?
>>
>> PS: I hope you understand that endless commit'n'push of each little change for just-to-test is extremely superfluous.
>
> Check externalsrc.bbclass

That's what I'm looking for. Thank you!

Regards,
Alexander