Add application with library to target

Add application with library to target

[Kjeld Flarup]

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

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

[-- Attachment #2: Type: text/html, Size: 812 bytes --]

Re: [yocto] Add application with library to target

[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
> 
> 
> 

Building extensible SDK

[Kjeld Flarup]

The eSDK looks interesting, but the documentation does not say anything about how to build it.
Am I missing something about how to obtain the eSDK?


Regards
Kjeld Flarup
DEIF R&D - Platform Software



________________________________________
From: Khem Raj <raj.khem@gmail.com>
Sent: Friday, July 10, 2020 02:38
To: Kjeld Flarup; yocto@lists.yoctoproject.org
Subject: Re: [yocto] Add application with library to target

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
>
> 
>

Re: [yocto] Building extensible SDK

[Khem Raj]

On 7/28/20 2:58 AM, Kjeld Flarup via lists.yoctoproject.org wrote:
> The eSDK looks interesting, but the documentation does not say anything about how to build it.
> Am I missing something about how to obtain the eSDK?

its all in the manual e.g.

https://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-building-an-sdk-installer

> 
> 
> Regards
> Kjeld Flarup
> DEIF R&D - Platform Software
> 
> 
> 
> ________________________________________
> From: Khem Raj <raj.khem@gmail.com>
> Sent: Friday, July 10, 2020 02:38
> To: Kjeld Flarup; yocto@lists.yoctoproject.org
> Subject: Re: [yocto] Add application with library to target
> 
> 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
>>
>>
>>
>>
>> 

Re: [yocto] Building extensible SDK

[Kjeld Flarup]

Thanks Khem

I guess the eSDK is quite new then.

I have to ask my BSP supplier, about what version of Yocto they are using.

"The extensible SDK can currently only be built for the same architecture as the machine being built on - SDK_ARCH is
set to i686 (likely via setting SDKMACHINE) which is different from the architecture of the build machine (x86_64)."


Regards
Kjeld Flarup
DEIF R&D - Platform Software



________________________________________
From: Khem Raj <raj.khem@gmail.com>
Sent: Thursday, July 30, 2020 7:40:04 AM
To: Kjeld Flarup; yocto@lists.yoctoproject.org
Subject: Re: [yocto] Building extensible SDK

On 7/28/20 2:58 AM, Kjeld Flarup via lists.yoctoproject.org wrote:
> The eSDK looks interesting, but the documentation does not say anything about how to build it.
> Am I missing something about how to obtain the eSDK?

its all in the manual e.g.

https://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-building-an-sdk-installer

>
>
> Regards
> Kjeld Flarup
> DEIF R&D - Platform Software
>
>
>
> ________________________________________
> From: Khem Raj <raj.khem@gmail.com>
> Sent: Friday, July 10, 2020 02:38
> To: Kjeld Flarup; yocto@lists.yoctoproject.org
> Subject: Re: [yocto] Add application with library to target
>
> 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
>>
>>
>>
>>
>>