linux/meta-intel.git/dynamic-layers, branch master

intel-oneapi: drop obsolete standalone component recipes

2026-04-29T15:10:40+00:00

Remove the per-component apt-package recipes superseded by the unified intel-oneapi-toolkit_2026.0.0.198.bb recipe, which packages the same components as sub-packages of a single offline installer (intel-oneapi-toolkit-{compiler,runtime,mkl,tbb,dpl,ipp,...}). Consumers should reference the canonical toolkit sub-package names directly. Recipes removed: * intel-oneapi-dpcpp-cpp_2024.0.0-49819.bb * intel-oneapi-dpcpp-cpp-runtime_2024.0.0-49819.bb * intel-oneapi-mkl_2024.0.0-49656.bb * intel-oneapi-ipp_2021.10.0-653.bb * setup-intel-oneapi-env_2023.0.0-25370.bb (and its intel-oneapi-runtime.conf helper) The setup-intel-oneapi-env helper installed a single ld.so.conf.d snippet pointing the dynamic loader at /opt/intel/oneapi/lib (and lib/intel64, lib/ia32, lib/emu). It dates back to the 2023.0 oneAPI layout. The unified toolkit installs libs under per-component directories such as /opt/intel/oneapi/{compiler,mkl, tbb,...}/2026.0/lib, not the flat /opt/intel/oneapi/lib that the conf file targets, so the ld.so.conf entries no longer point at real directories. Loadability of oneAPI binaries on the target is provided by: * setvars.sh / per-component env/vars.sh sourcing (the canonical Intel-supported entry point that every test and example uses) * $ORIGIN-relative RUNPATH baked into the shipped shared objects by the Intel installer * /etc/OpenCL/vendors/intel-cpu.icd written by the unified toolkit recipe's do_install for ICD loader discovery * virtual-opencl-icd / level-zero-loader RDEPENDS on intel-oneapi-toolkit-runtime for the OpenCL / Level Zero loaders The setup-intel-oneapi-env filename version (2023.0.0-25370) was a stale carry-over from when the recipe was first added; nothing in the recipe ever referenced ${PV}. Signed-off-by: Yogesh Tyagi

intel-oneapi-toolkit: add unified 2026.0.0.198 recipe

2026-04-29T13:51:34+00:00

Intel oneAPI 2026.0 ships the former Base and HPC toolkits as a single offline self-extracting installer instead of as the per- component apt packages used in the 2021/2024 layout. Add a recipe that consumes intel-oneapi-toolkit-2026.0.0.198_offline.sh via a pseudo-free do_unpack_vendor task and stages /opt/intel/oneapi into the rootfs. The recipe partitions the installed tree into sub-packages along component boundaries: intel-oneapi-toolkit-{compiler,runtime,mkl, tbb,dpl,debugger,ipp,ccl,vtune,common,licensing}. Consumers should reference these canonical sub-package names directly rather than the per-component apt names that the 2021/2024 standalone recipes exposed. The runtime sub-package additionally: * registers /opt/intel/oneapi/compiler/2026.0/lib/libintelocl.so as /etc/OpenCL/vendors/intel-cpu.icd so systems without an Intel GPU expose an Intel OpenCL platform via the standard ICD mechanism; * installs a libxml2.so.2 -> libxml2.so.16 SONAME compat symlink, because the prebuilt libcommon_clang.so / libintelocl.so are linked against the libxml2 2.x SONAME while current oe-core ships libxml2 3.x as libxml2.so.16. libxml2 3.x is API-compatible with the option-parsing surface the binaries use. The bundle is x86_64-only so COMPATIBLE_HOST is restricted. Signed-off-by: Yogesh Tyagi

ispc: isolate LLVM superbuild from recipe-sysroot-native

2026-04-08T17:31:41+00:00

The ISPC superbuild internally builds LLVM (stage1/stage2). The generated toolchain files inherit Yocto flags and sysroot paths, causing CMake to locate libraries from recipe-sysroot-native. This leads to linking failures when host compiler toolchains are used together with libraries built against a newer glibc, resulting in errors such as: undefined reference to `__isoc23_wcstol@GLIBC_2.38' Fix this by isolating the LLVM superbuild from Yocto sysroot: * Patch generated stage1/stage2 toolchain files: - Replace symbolic compiler names (cc/c++) with ${BUILD_CC}/${BUILD_CXX} - Clear injected CMake compiler and linker flags * Prevent CMake from searching recipe-sysroot-native: - Set CMAKE_FIND_ROOT_PATH_MODE_* to NEVER * Disable optional LLVM features requiring external libraries (libedit, terminfo, zstd, zlib) * Scope environment cleanup to the cmake build invocation to avoid leaking Yocto flags into the superbuild This ensures the internal LLVM build uses a consistent host environment, avoiding GLIBC ABI mismatches. Remove ncurses dependency as terminfo/libedit are disabled. Signed-off-by: Yogesh Tyagi

oidn : drop old recipe

2026-03-03T13:38:21+00:00

Signed-off-by: Yogesh Tyagi

thermald: remove and migrate to meta-oe

2026-02-25T07:49:15+00:00

thermald now supports ARM platforms [1], so move it out of meta-intel to allow broader reuse. [1] thermal_daemon 1931a12e7e ("Add ARM backend and enable ARM platform detection") Signed-off-by: Anuj Mittal Signed-off-by: Yogesh Tyagi

embree, openvkl, ospray: Skip buildpaths QA check

2026-02-16T17:26:50+00:00

Add INSANE_SKIP for buildpaths QA check in RenderKit recipes that use ISPC for code generation. ISPC (Intel SPMD Program Compiler) embeds absolute build paths in generated binaries and debug information by design. This is necessary for: 1. Debug information accuracy - ISPC generates C++ wrapper code with #line directives pointing to original .ispc source files 2. Error reporting during kernel execution - backtraces reference original source locations 3. Profiling support - performance tools need source file locations Affected packages: - embree: ISPC kernels for ray tracing primitives - openvkl: ISPC kernels for volume rendering - ospray: ISPC kernels for rendering algorithms This resolves QA errors that prevent SDK image builds when RenderKit stack is included. Signed-off-by: Yogesh Tyagi

oidn: Add recipe for version 2.4.1

2026-02-16T17:26:50+00:00

Add Intel Open Image Denoise (OIDN) 2.4.1, an open-source library for high-performance, high-quality denoising of images rendered with ray tracing. Key features: - Machine learning-based denoising filters optimized for Intel CPUs - ISPC-accelerated kernels for vectorization - Supports HDR and LDR images - Multiple filter types: RT, RTLightmap Dependencies: - ISPC 1.25.0+ for kernel compilation - TBB for task parallelism - CMake 3.1+ Build configuration: - GPU support disabled (OIDN_DEVICE_GPU=OFF) - Apps disabled for minimal footprint - Static TBB linkage Part of Intel RenderKit stack upgrade coordinated with: - ISPC 1.29.1 - embree 4.4.0 - openvkl 2.0.1 - ospray 3.2.0 - rkcommon 1.15.2 Signed-off-by: Yogesh Tyagi

ispc: Upgrade to version 1.29.1 with build fixes and ptest support

2026-02-16T17:23:58+00:00

Upgrade from 1.24.0 to 1.29.1 with bundled LLVM 20.1 using superbuild. Recipe changes: - Upgrade to ISPC 1.29.1 with bundled LLVM 20.1 using superbuild - Add patches for multiarch header detection and CMake policy updates - Split do_install() into base (native+target) and target-only sections * Base: Install compiler binaries (ispc, check_isa) to ${bindir} * Target-only: Install test suite to ${libdir}/ispc/gio/ - Make do_install_ptest() target-only to avoid native build issues - Create separate test packages with class-specific definitions: * ispc-ptest: Yocto ptest integration at /usr/lib/ispc/ptest/ - Add run-ptest script for ptest-runner integration - Add pkg_postinst to create /lib64 symlink for binary compatibility Dependencies and packaging: - Add ncurses to DEPENDS for libedit linking (terminfo functions) - Skip file-rdeps and buildpaths QA checks for bundled LLVM - Set RDEPENDS for ptest: bash, python3-multiprocessing - Make PACKAGES, FILES, and RDEPENDS class-specific for proper separation Build configuration: - Use superbuild with bundled LLVM 20.1, vc-intrinsics, SPIRV-Translator - Forward ISPCRT_BUILD_TASK_MODEL for TBB support - Set custom build/install directories for superbuild stage2 output - Export empty CFLAGS/CXXFLAGS/LDFLAGS_FOR_BUILD for clean builds Fixes: - ispc-native build failures when test packages were defined - Link errors with libedit.so requiring ncurses terminfo symbols - QA errors from duplicate PACKAGES definitions - Proper class separation between native and target builds - GLIBC_2.42 symbol resolution issues Signed-off-by: Yogesh Tyagi

recipes: inherit pkgconfig

2026-02-10T17:03:42+00:00

Instead of depending directly on pkgconfig-native, inherit the pkgconfig class. At the moment this just adds a layer of indirection to the right provider of pkgconfig, but there are patches in flight to move exports into the class to isolate the variables. Signed-off-by: Ross Burton Signed-off-by: Yogesh Tyagi

linux-npu-driver: Set COMPATIBLE_HOST to restrict compatibility to x86_64 hosts

2026-02-05T06:49:31+00:00

- Added "COMPATIBLE_HOST" to restrict the "linux-npu-driver" recipe to x86_64 Linux-based build systems. - Ensured that the recipe is not compatible with systems using musl libc. This change ensures the recipe builds only on x86_64 hosts with glibc and avoids issues with musl-based systems. Signed-off-by: Yongxin Liu Signed-off-by: Yogesh Tyagi