Re: [yocto] How I can add/remove libxxxx-dev.ipk to the installed yocto SDK? SDK partial update #devtool #kirkstone #sdk #yocto

["Altous, Salahaldeen" <Salahaldeen.Altous@leica-camera.com>]

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

Hi Alex,

On Thu, Apr 25, 2024 at 12:26 AM, Alexander Kanavin wrote:

> 
> I would suggest that you teach the 3rd party to set up a Yocto build
> and provide pre-built sstate cache to them. We've added SDK features
> directly into it, and incremental updates are both possible and easy
> in that setup (just pull from the layer repos and rerun bitbake as
> instructed).
> 
> Alex

The 3rd party is using only The Yocto SDK (not the eSDK), they want to test pre-release for one or two libs which are not included in the machine conf yet.

If I provide a pre-build sstate-cache, which command in the SDK can be used to get the updates?

Salah

> 
> 
> On Wed, 24 Apr 2024 at 16:39, Altous, Salahaldeen via
> lists.yoctoproject.org
> <Salahaldeen.Altous=leica-camera.com@lists.yoctoproject.org> wrote:
> 
>> Hi,
>> 
>> I am compiling new version of shared-libs are yocto recipes and plan to
>> ship these libraries to 3rd party without provide a complete SDK, can I
>> only ship the ibxxxx-dev.ipk and install to the already shipped SDK are
>> incremental update.
>> 
>> From time to time I can provide a full update for the SDK, but I would
>> like to avoid frequent update.
>> 
>> what is the best practice to provide partial update without using devtool?
>> is this possible?
>> 
>> Also, can I uninstall/replace these libs which not official released from
>> the installed SDK path?
>> 
>> show I use rpm instead of ipk?
>> 
>> Regards,
>> 
>> Salahaldeen
>> 
>> 
>> 
> 
> 

On Thu, Apr 25, 2024 at 12:26 AM, Alexander Kanavin wrote:

> 
> instructed

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