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 >> 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/root 0 2024-05-08 14:29 ./usr/ >> drwxr-xr-x root/root 0 2024-05-08 14:29 ./usr/lib/ >> lrwxrwxrwx root/root 0 2024-05-08 14:29 ./usr/lib/liblc_core.so.0 -> >> liblc_core.so.0.4.7 >> -rwxr-xr-x root/root 26536 2024-05-08 14:29 ./usr/lib/liblc_core.so.0.4.7 >> and in the dev-ipk package the missing *.so exist >> drwxr-xr-x root/root 0 2024-05-08 14:29 ./usr/lib/ >> lrwxrwxrwx root/root 0 2024-05-08 14:29 ./usr/lib/liblc_core.so -> >> liblc_core.so.0 >> I need to have all in on files/symbolic-link in the release ipk, and the >> rootfs wihtout the need to install the dev-ipk later on, any idea what I >> need to add in the yocto recipe or the meson file > > This is intended behaviour. Conventionally, libraries are versioned (eg > liblc_core.so < http://liblc_core.so/>.0.4.7 ) so that specific binaries > link against specific ABIs at runtime, and there are convenience symlinks > (liblc_core.so < http://liblc_core.so/ >) that are used at link time so you > can just link to liblc_core.so < http://liblc_core.so/ > and that is > resolved to a specific ABI version. > > This means that at _runtime_ you need the real library, and not the > symlink. The symlinks are packaged into the -dev package alongside the > headers because they’re only needed if you’re compiling code. > > This is convention, and there are exceptions. There are two possibilities > here: > > 1) The versioned shared library shouldn’t be versioned, because other > binaries use dlopen(“liblc_core.so < http://liblc_core.so/ >”) at runtime > instead of linking to it at build time. If this is the case then if it’s > sensible remove the versioning entirely (as it’s pointless) and read > https://docs.yoctoproject.org/next/dev-manual/prebuilt-libraries.html#non-versioned-libraries > . > > 2) You don’t actually need the .so at runtime. thanks for the explanation, I will remove the versioning and add these variables to my recipes SOLIBS = ".so" FILES_SOLIBSDEV = "" "The symlinks are packaged into the -dev package alongside the headers because they’re only needed if you’re compiling code" Can I use the -dev package to cross compile? similar to the sysroot in the yocto-SDK Regards, Salah > > > Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63320): https://lists.yoctoproject.org/g/yocto/message/63320 Mute This Topic: https://lists.yoctoproject.org/mt/106589714/21656 Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[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/root 0 2024-05-08 14:29 ./usr/ drwxr-xr-x root/root 0 2024-05-08 14:29 ./usr/lib/ lrwxrwxrwx root/root 0 2024-05-08 14:29 ./usr/lib/liblc_core.so.0 -> liblc_core.so.0.4.7 -rwxr-xr-x root/root 26536 2024-05-08 14:29 ./usr/lib/liblc_core.so.0.4.7 and in the dev-ipk package the missing *.so exist drwxr-xr-x root/root 0 2024-05-08 14:29 ./usr/lib/ lrwxrwxrwx root/root 0 2024-05-08 14:29 ./usr/lib/liblc_core.so -> liblc_core.so.0 I need to have all in on files/symbolic-link in the release ipk, and the rootfs wihtout the need to install the dev-ipk later on, any idea what I need to add in the yocto recipe or the meson file? Regards, Salahaldeen -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63301): https://lists.yoctoproject.org/g/yocto/message/63301 Mute This Topic: https://lists.yoctoproject.org/mt/106589714/21656 Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
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 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 the example recipe RDEPENDS but still the problem is
>> not solved, any idea?
>> DEPENDS += " sqlite3"
>> RDEPENDS_${PN} += " libsqlite3.so()(64bit)”
>
> Does this recipe contain precompiled binaries?
No, I build this example library as shared lib from source
>
> Ross
Regards,
Salah
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63091): https://lists.yoctoproject.org/g/yocto/message/63091
Mute This Topic: https://lists.yoctoproject.org/mt/106090753/21656
Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] requires libsqlite3.so()(64bit), but no providers found in RDEPENDS:xxx? [file-rdeps] #kirkstone #yocto
Hi Qi,
On Tue, May 14, 2024 at 01:42 AM, Chen Qi wrote:
>
>
>
> How about using the following setting?
>
>
>
> RDEPENDS:${PN} += “sqlite3”
>
>
>
>
>
>
>
I have added this (RDEPENDS_${PN} += "sqlite3") to the recipe but I see the
same error!!
>
>
>
>
>
>
>
>
>
>
>
> Regards,
>
>
>
> Qi
>
>
>
>
>
>
>
> *From:* yocto@lists.yoctoproject.org *On
> Behalf Of* Alexander Kanavin
> *Sent:* Tuesday, May 14, 2024 4:34 PM
> *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?
>
>
>
>
>
>
>
>
>
> Alex
>
>
>
>
>
>
>
>
> On Tue 14. May 2024 at 9.56, Altous, Salahaldeen via lists.yoctoproject.org
> (
> https://urldefense.com/v3/__http:/lists.yoctoproject.org__;!!AjveYdw8EvQ!eO_pOhB66A-tCePBTH62mvBSO1pjmPHgKJU88d0uBTcaaIQxnpreuCx-LEC_L30IGEsV7gr_DrB3xVNkWeYVA1XOR2w$
> ) wrote:
>
>
>
>>
>>
>> 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 the example recipe RDEPENDS but still the problem is
>> not solved, any idea?
>>
>>
>>
>> DEPENDS += " sqlite3"
>> RDEPENDS_${PN} += " libsqlite3.so()(64bit)"
>>
>>
>>
>>
>>
>>
>>
>> Regards,
>>
>>
>>
>> Salahaldeen
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63087): https://lists.yoctoproject.org/g/yocto/message/63087
Mute This Topic: https://lists.yoctoproject.org/mt/106090753/21656
Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] requires libsqlite3.so()(64bit), but no providers found in RDEPENDS:xxx? [file-rdeps] #kirkstone #yocto
Hi Alex,
On Tue, May 14, 2024 at 01:33 AM, Alexander Kanavin wrote:
>
> Can you show the complete recipe?
>
>
inherit component-versions
inherit cmake
SRC_URI =
"${GIT_URI_YOCTO}${EXT_EXAMPLE_GIT_URI};protocol=ssh;branch=${EXT_EXAMPLE_GIT_BRANCH}"
PV = "${SRCREV}+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 += "-DBUILD_SHARED_LIBS=ON "
Regards,
Salah
>
>
>
> Alex
>
> On Tue 14. May 2024 at 9.56, Altous, Salahaldeen via lists.yoctoproject.org
> ( http://lists.yoctoproject.org ) leica-camera@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 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 the example recipe RDEPENDS but still the problem is
>> not solved, any idea?
>>
>>
>>
>> DEPENDS += " sqlite3"
>> RDEPENDS_${PN} += " libsqlite3.so()(64bit)"
>>
>>
>>
>>
>>
>>
>>
>> Regards,
>>
>>
>>
>> Salahaldeen
>>
>>
>>
>>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63086): https://lists.yoctoproject.org/g/yocto/message/63086
Mute This Topic: https://lists.yoctoproject.org/mt/106090753/21656
Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[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 the example recipe RDEPENDS but still the problem is not
solved, any idea?
DEPENDS += " sqlite3"
RDEPENDS_${PN} += " libsqlite3.so()(64bit)"
Regards,
Salahaldeen
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63083): https://lists.yoctoproject.org/g/yocto/message/63083
Mute This Topic: https://lists.yoctoproject.org/mt/106090753/21656
Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Installing Multiple Versions of the Same Library with a single recipe
Hi Alex On Thu, Apr 25, 2024 at 12:29 AM, Alexander Kanavin wrote: > > You should find out why people want same that library in different > versions in the first place. This indicates some kind of dysfunction > in the product development process. the reason behind that, that this company have one external module which development in the past with an early version of this library and currently there is a new module which developed with the new version. I know the right way is to rewrite the old module with the new lib version but for some reasons (no access to source code/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 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 (#63000): https://lists.yoctoproject.org/g/yocto/message/63000 Mute This Topic: https://lists.yoctoproject.org/mt/105711657/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] How I can add/remove libxxxx-dev.ipk to the installed yocto SDK? SDK partial update #devtool #kirkstone #sdk #yocto
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 > 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 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 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 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62998): https://lists.yoctoproject.org/g/yocto/message/62998 Mute This Topic: https://lists.yoctoproject.org/mt/105711257/21656 Mute #devtool:https://lists.yoctoproject.org/g/yocto/mutehashtag/devtool Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone Mute #sdk:https://lists.yoctoproject.org/g/yocto/mutehashtag/sdk Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[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://lists.yoctoproject.org/g/yocto/message/62995 Mute This Topic: https://lists.yoctoproject.org/mt/105711657/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[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 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 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62994): https://lists.yoctoproject.org/g/yocto/message/62994 Mute This Topic: https://lists.yoctoproject.org/mt/105711257/21656 Mute #devtool:https://lists.yoctoproject.org/g/yocto/mutehashtag/devtool Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone Mute #sdk:https://lists.yoctoproject.org/g/yocto/mutehashtag/sdk Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Yocto common place holder for includes which used multiple recipe
On Tue, Apr 23, 2024 at 05:27 AM, Alexander Kanavin wrote:
>
> Yes this should be fine. But don't forget to inherit it in all the
> recipes that would use these variables.
>
> Here's an example:
> https://git.yoctoproject.org/poky/tree/meta/classes-recipe/gnomebase.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, Alexander Kanavin wrote:
>>
>> I think you can simply make it a class and put under
>> classes/some.bbclass? Plenty of recipes in oe-core do this, see e.g.
>> gnomebase.bbclass.
>>
>> I need something like these these variables
>>
>> EXTERNAL_PROJECT_XXX_TYPE ?= "lib"
>> EXTERNAL_PROJECT_XXX_NAME ?= "lc_xxx"
>> EXTERNAL_PROJECT_XXX_GIT_URI ?=
>> "${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
>> EXTERNAL_PROJECT_XXX_GIT_BRANCH ?= "development"
>> EXTERNAL_PROJECT_XXX_GIT_TAG ?= "0.4.3-dev"
>>
>> EXTERNAL_PROJECT_YYY_TYPE ?= "lib"
>> EXTERNAL_PROJECT_YYY_NAME ?= "lc-yyy"
>> EXTERNAL_PROJECT_XXX_GIT_URI ?=
>> "${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
>> EXTERNAL_PROJECT_YYY_GIT_BRANCH ?= "development"
>> EXTERNAL_PROJECT_YYY_GIT_TAG ?= "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 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 recipes in meta-xxx which can be found by
>> default and this need to be under meta-xxx folder.
>>
>> thanks in advance.
>>
>>
>>
>> Regards,
>>
>> Salahaldeen Altous
>
>
Thanks I will give a try
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62989): https://lists.yoctoproject.org/g/yocto/message/62989
Mute This Topic: https://lists.yoctoproject.org/mt/105687839/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Yocto common place holder for includes which used multiple recipe
Hi Alex
thanks for your quick reply.
On Tue, Apr 23, 2024 at 05:02 AM, Alexander Kanavin wrote:
>
> I think you can simply make it a class and put under
> classes/some.bbclass? Plenty of recipes in oe-core do this, see e.g.
> gnomebase.bbclass.
I need something like these these variables
EXTERNAL_PROJECT_XXX_TYPE ?= "lib"
EXTERNAL_PROJECT_XXX_NAME ?= "lc_xxx"
EXTERNAL_PROJECT_XXX_GIT_URI ?=
"${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
EXTERNAL_PROJECT_XXX_GIT_BRANCH ?= "development"
EXTERNAL_PROJECT_XXX_GIT_TAG ?= "0.4.3-dev"
EXTERNAL_PROJECT_YYY_TYPE ?= "lib"
EXTERNAL_PROJECT_YYY_NAME ?= "lc-yyy"
EXTERNAL_PROJECT_XXX_GIT_URI ?=
"${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
EXTERNAL_PROJECT_YYY_GIT_BRANCH ?= "development"
EXTERNAL_PROJECT_YYY_GIT_TAG ?= "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 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 recipes in meta-xxx which can be found by
>> default and this need to be under meta-xxx folder.
>>
>> thanks in advance.
>>
>>
>>
>> Regards,
>>
>> Salahaldeen Altous
>>
>>
>>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62987): https://lists.yoctoproject.org/g/yocto/message/62987
Mute This Topic: https://lists.yoctoproject.org/mt/105687839/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[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 recipes in meta-xxx which can be found by default and this need to be under meta-xxx folder. thanks in advance. Regards, Salahaldeen Altous -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62985): https://lists.yoctoproject.org/g/yocto/message/62985 Mute This Topic: https://lists.yoctoproject.org/mt/105687839/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
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 working and I get this error
> * fatal: could not read Password for 'https://git@COMPANY_GIT_REPO': No
> such device or address
>
>
>
>
> Finally, something I might be able to contribute with.
>
> * Do not put ever any credentials to any recipes. That’s not the right
> place for them and they will leak.
> * Credentials are a build machine configuration issue. You can use git
> redirects for this purpose.
>
>
> This type of thing is only required for private repositories typically,
> here is an example for a GitHub action
>
>
>
> https://github.com/PelionIoT/actions
>
>
>
> that does it. But, essentially it boils down to configuring git:
>
>
>
>
>
>
>
> git config --global user.name "Your BOT"
>
>
>
> git config --global user.email y...@email.com
>
>
>
> git config --global url. https://${{ inputs.github_token }}@github.com/ (
> https://$%7b%7b%20inputs.github_token%20%7d...@github.com/ ).insteadOf
> g...@github.com:
>
>
>
>
> git config --global url. https://${{ inputs.github_token }}@github (
> https://$%7b%7b%20inputs.github_token%20%7d%7d@github ).insteadOf
> https://github
>
>
>
>
> I hope this helps.
>
>
>
>
>
>
>
thanks for your help, I will give it a try.
>
>
>
>
>
>
>
>
>
>
>
> Best Regards,
>
>
>
>
>
>
>
> Janne Kiiskilä
>
>
>
Regards,
Salahaldeen Altous
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62973): https://lists.yoctoproject.org/g/yocto/message/62973
Mute This Topic: https://lists.yoctoproject.org/mt/102079282/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
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 https+Token was working fine with Dunfell, now I have ported this recipe to
kirkstone but it is not working and I get this error
fatal: could not read Password for 'https://git@COMPANY_GIT_REPO': No such
device or address
Is this known WONTFIX bug was also in dunfell? or introduced only in the new
yocto version?
is this only applied for gitsm or also for git?
Thanks in advance.
Regards,
Salahaldeen Altous
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62968): https://lists.yoctoproject.org/g/yocto/message/62968
Mute This Topic: https://lists.yoctoproject.org/mt/102079282/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Including Python3 modules in generated SDK do not work (python3-node-semver, kirkstone)
I have one more question, why when I have added the "python-node-semver" to my image IMAGE_INSTALL:append = " python3-node-semver" it was not by default part of the host SDK!! is this something special for the python packages? Regards, Salahaldeen On Thu, Feb 15, 2024 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, >>> >>> I am using one application which is using a python3 module >>> (python3-node-semver), I was trying to provide the application developer >>> with the yocto SDK but I cannot locate this module in the new generate >>> SDK, I have tried to add this manually by adding these lines to machine >>> config like this >>> >>> IMAGE_INSTALL:append = " python3-node-semver" >>> TOOLCHAIN_HOST_TASK += " python3-node-semver " >>> >>> https://layers.openembedded.org/layerindex/recipe/333689/ >>> >>> but still not working, python3-node-semver is available on the target but >>> not in the host SDK!! Any idea what this happening? >> >> If you want a recipe to be available in the _host_ part of the SDK then >> you need to add nativesdk-python3-node-semver to TOOLCHAIN_HOST_TASK. > > > > thanks for your quick help, I will use nativesdk-python3-node-semver > > >> You _should_ have got an error from trying to install a target package >> into the host SDK. > > > > Yes, I have seen some error but was not self explained > > > > do_populate_sdk: Unable to install packages. > > > > > > > > ** opkg_prepare_url_for_install: Couldn't find anything to satisfy > 'python3-node-semver'.* > > > > Regards, > > > > Salahaldeen > > >> >> Ross > > > Hi Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62509): https://lists.yoctoproject.org/g/yocto/message/62509 Mute This Topic: https://lists.yoctoproject.org/mt/104369867/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
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 was trying to provide the application developer >> with the yocto SDK but I cannot locate this module in the new generate >> SDK, I have tried to add this manually by adding these lines to machine >> config like this >> >> IMAGE_INSTALL:append = " python3-node-semver" >> TOOLCHAIN_HOST_TASK += " python3-node-semver " >> >> https://layers.openembedded.org/layerindex/recipe/333689/ >> >> but still not working, python3-node-semver is available on the target but >> not in the host SDK!! Any idea what this happening? > > If you want a recipe to be available in the _host_ part of the SDK then > you need to add nativesdk-python3-node-semver to TOOLCHAIN_HOST_TASK. thanks for your quick help, I will use nativesdk-python3-node-semver > > You _should_ have got an error from trying to install a target package > into the host SDK. Yes, I have seen some error but was not self explained do_populate_sdk: Unable to install packages. ** opkg_prepare_url_for_install: Couldn't find anything to satisfy 'python3-node-semver'.* Regards, Salahaldeen > > > Ross Hi Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62508): https://lists.yoctoproject.org/g/yocto/message/62508 Mute This Topic: https://lists.yoctoproject.org/mt/104369867/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
