Topics

Add application with library to target

Kjeld Flarup
 

I have a functioning Yocto build today, but two of the recipes are optional. An application and a library.
I would like to split my build in two. 

One that contains the basic system with kernel rootfs etc.
A second that just contains the application and the library

If I just had the application, it would be simple just to use the SDK and generate the application. 
But when adding the library, things starts to be more complex. 

I would also like to use my existing recipe with dependencies etc. 

What is the best approach
  • Can this be done with the ADT?
  • Can a layer solve it
  • Do I need to do it all manually with the SDK

--
Regards 
Kjeld Flarup
DEIF A/S

Khem Raj
 

On 7/8/20 2:37 AM, Kjeld Flarup via lists.yoctoproject.org wrote:
I have a functioning Yocto build today, but two of the recipes are
optional. An application and a library.
I would like to split my build in two. 

One that contains the basic system with kernel rootfs etc.
A second that just contains the application and the library

If I just had the application, it would be simple just to use the SDK
and generate the application. 
But when adding the library, things starts to be more complex. 

I would also like to use my existing recipe with dependencies etc. 

What is the best approach

* Can this be done with the ADT?
* Can a layer solve it
* Do I need to do it all manually with the SDK
I think eSDK might be good fit for your usecase.

https://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-extensible

--
Regards 
Kjeld Flarup
DEIF A/S