I messed it up, this relates to: https://lists.yoctoproject.org/g/yocto/message/51705

#dunfell #vmdk #hddimg #iso

Some more information: Build Configuration: BB_VERSION= "1.46.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING= "universal" TARGET_SYS= "x86_64-poky-linux" MACHINE= "virtualbox" DISTRO= "my-gnu-linux" DIS

#dunfell #vmdk #hddimg #iso

Hi Quentin, Thank you for the earlier help. After that, I got a QA Issue and I was trying to solve it, but I'm unable to do it. Any suggestions would be helpful. Package contains non-symlink .so: tokb

#dunfell #yocto

Thank you! it worked. Thanks, Vijay Rakesh.

#dunfell #yocto

Do you have B set up somewhere in your recipe? Otherwise try ${S}/lib/libopentok.so for the source path. Quentin

#dunfell #yocto

This is the path to libopentok.so tmp/work/aarch64-poky-linux/tokbox/1.0-r0/libopentok_linux_llvm_arm64/lib/ Thanks, Vijay Rakesh.

#dunfell #yocto

If you go into ${WORKDIR} of your recipe (tmp/work/<arch>/<recipe name>), what is the path to libopentok.*.so? Quentin

#dunfell #yocto

By changing to S = "${WORKDIR}/libopentok_linux_llvm_arm64" error got eliminated, thank you. Now, how can I install the file under opentok_linux_llvm_arm64/lib/libopentok.so into the rootfs? I tried t

#dunfell #yocto

I figured out URL is hyperlinked with another URL. When I use a hyperlinked URL it is getting copied and extracted into the working directory. Thanks. Thanks, Vijay Rakesh.

#dunfell #yocto

<vijayrakeshmunganda@...> wrote: What I mean is, do you see the file "libopentok_linux_llvm_arm64-2.18.1.tgz" itself under ${WORKDIR}? i.e. has it been copied instead of extracted? Also, please

#dunfell #yocto

Hi, S = "${WORKDIR}/libopentok_linux_llvm_arm64" This is the root directory of your archive and should be used for `S` Cheers, Quentin

#dunfell #yocto

Hi Paul Barker, No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can only see it in the downloads directory. I'm Yocto Project Dunfell version. Thanks, Vijay Rakesh.

#dunfell #yocto

<vijayrakeshmunganda@...> wrote: Does the .tgz file get placed in ${WORKDIR} without being extracted? Also, which Yocto Project version/branch are you using? Thanks,

#dunfell #yocto

Hi Zoran, Thanks for the reply. The reason behind CMakeLists.txt does not appear is because tgz file is getting extracted into the source folder, it is empty when I checked. My recipe is unable to ext

#dunfell #yocto

Just maybe... This web pointer can help you! https://stackoverflow.com/questions/46448682/cmake-error-the-source-does-not-appear-to-contain-cmakelists-txt/52068568 Zoran _______ <vijayrakeshmunganda@g

#dunfell #yocto

Anyone, please suggest. Thanks, Vijay Rakesh

#dunfell #yocto

Hi All, I'm trying to install the Tokbox library into the build, but the tar file is not getting extracted into the folder. Here is my recipe code, kindly please help me where I went wrong. Recipe: DE

#dunfell #yocto

Hi VR, Please make sure that the interface name in hostapd.conf matches with the wireless interface name of your target. By default it is set to wlan0, but it could be different in your target (for ex

#linux #kernel #dunfell

Hello Team, I need to use High availability cluster in my project. I'm generating OS for Rpi using Ycot. I'm using dunfell poky version 3.1.3. I'm adding ntp tzdata pacemaker haveged and crmsh command

#dunfell #raspberrypi #yocto

I am seeing problems in git fetcher using a github repo using lfs + ssh in dunfell. I find if I set "lfs=0" it still attempts to download the lfs objects and fails. Same behavior if "lfs=1". SRC_URI =

#dunfell