Re: [yocto] Including Python3 modules in generated SDK do not work (python3-node-semver, kirkstone)

Hi Ross, On Thu, Feb 15, 2024 at 04:04 AM, Ross Burton wrote: > > On 15 Feb 2024, at 07:27, Altous, Salahaldeen via lists.yoctoproject.org > wrote: > >> Hello, >> >> I am using one application which is using a python3 module >> (python3-node-semver), I w

Re: [yocto] Including Python3 modules in generated SDK do not work (python3-node-semver, kirkstone)

at 10:39 PM, Altous, Salahaldeen wrote: > > > > Hi Ross, > > > > On Thu, Feb 15, 2024 at 04:04 AM, Ross Burton wrote: > > >> On 15 Feb 2024, at 07:27, Altous, Salahaldeen via lists.yoctoproject.org >> wrote: >> >>> Hello, >>

Re: [yocto] Http access token fetching with gitsm fetcher

Hi Adrian, Hi Yoann, I have two project when is using dunfell and another one with using Kirkstone. with the Dunfell project I was using one recipe with fetching from git repo like this SRC_URI = "git://${ COMPANY_GIT_REPO }/path/to/project.git;protocol=https; *user=token_name:${TOKEN}"* The

Re: [yocto] Http access token fetching with gitsm fetcher

Hi Janne, On Fri, Apr 19, 2024 at 06:44 AM, Janne Kiiskila wrote: > > > > * SRC_URI = "git://${ COMPANY_GIT_REPO }/path/to/project.git;protocol=https; > *user=token_name:${TOKEN}"* > * The https+Token was working fine with Dunfell, now I have ported this > recipe to kirkstone but it is not wor

[yocto] Yocto common place holder for includes which used multiple recipe

Hi All, I need a common place holder to share one include files which can be used by multiple recipe (this include files includes some variables like SRC_URL, tag, gitbranch, ..., etc). I can copy it to each recipe but I am looking for the best practice to share a common inc file for all recip

Re: [yocto] Yocto common place holder for includes which used multiple recipe

= "0.2.1-dev" is this something possible with bbclass? Salahaldeen > > > Alex > > On Tue, 23 Apr 2024 at 13:57, Altous, Salahaldeen via > lists.yoctoproject.org > wrote: > >> Hi All, >> >> I need a common place holder to share one include

Re: [yocto] Yocto common place holder for includes which used multiple recipe

se.bbclass > Thanks I will give a try > > > Alex > > On Tue, 23 Apr 2024 at 14:19, Altous, Salahaldeen via > Lists.Yoctoproject.Org > wrote: > >> Hi Alex >> >> thanks for your quick reply. >> >> On Tue, Apr 23, 2024 at 05:02 AM,

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

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 ib-dev.ipk and install to the already shipped SDK are incremental update. >From time to time I can provide a full update for the

[yocto] Installing Multiple Versions of the Same Library with a single recipe

Hi, can I install Multiple Versions of the Same shared Library with single recipe? by provide different tag or should i make a new recipe for every lib version? Regards, Salahaldeen -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62995): https:/

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

e-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 > wrote: > >> Hi, >> >> I am compiling new version of shared-libs are yocto recipes and plan to &g

Re: [yocto] Installing Multiple Versions of the Same Library with a single recipe

no resources!!) this company want to reuse the old module as it is. Salah > > > Alex > > On Wed, 24 Apr 2024 at 16:59, Altous, Salahaldeen via > lists.yoctoproject.org > wrote: > >> Hi, >> >> can I install Multiple Versions of the Same shared L

[yocto] requires libsqlite3.so()(64bit), but no providers found in RDEPENDS:xxx? [file-rdeps] #kirkstone #yocto

Hi All, I have one yocto recipe which is using libsqlite3, the compile task is OK but I got this error with do_package_qa /usr/lib/libexample.so.0.2.3 contained in package example requires libsqlite3.so()(64bit), but no providers found in RDEPENDS:example.? [file-rdeps] I have added this to t

Re: [yocto] requires libsqlite3.so()(64bit), but no providers found in RDEPENDS:xxx? [file-rdeps] #kirkstone #yocto

RCREV}+git${SRCPV}" #SRCREV = "${AUTOREV}" SRCREV = "${EXT_EXAMPLE_GIT_TAG}" S = "${WORKDIR}/git" DEPENDS += " sqlite3" RDEPENDS_${PN} += " libsqlite3.so()(64bit)" SKIPTESTS = "true" export SKIPTESTS EXTRA_OECMAKE += "-D

Re: [yocto] requires libsqlite3.so()(64bit), but no providers found in RDEPENDS:xxx? [file-rdeps] #kirkstone #yocto

*To:* salahaldeen.alt...@leica-camera.com; yocto@lists.yoctoproject.org > *Subject:* Re: [yocto] requires libsqlite3.so()(64bit), but no providers > found in RDEPENDS:xxx? [file-rdeps] #kirkstone #yocto > > > > > > > > > Can you show the complete recipe? >

Re: [yocto] requires libsqlite3.so()(64bit), but no providers found in RDEPENDS:xxx? [file-rdeps] #kirkstone #yocto

On Tue, May 14, 2024 at 02:37 AM, Ross Burton wrote: > > On 14 May 2024, at 08:55, Altous, Salahaldeen via lists.yoctoproject.org > wrote: > >> Hi All, >> I have one yocto recipe which is using libsqlite3, the compile task is OK >> but I got this error

[yocto] depoly-ipks are missing the lib**.so file for shared library yocto recipe #kirkstone #yocto

Hi All, I have one yocto recipe which inherit meson as build system and generate the right libs in the image folder ├── liblc_core.so -> liblc_core.so.0 ├── liblc_core.so.0 -> liblc_core.so.0.4.7 └── liblc_core.so.0.4.7 but in the deploy-ipks the .so symbolic link is missing drwxr-xr-x root/roo

Re: [yocto] depoly-ipks are missing the lib**.so file for shared library yocto recipe #kirkstone #yocto

Hi Ross, On Mon, Jun 10, 2024 at 03:38 AM, Ross Burton wrote: > > On 10 Jun 2024, at 11:26, Altous, Salahaldeen via lists.yoctoproject.org > wrote: > >> Hi All, >> >> I have one yocto recipe which inherit meson as build system and generate >>