<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-intel.git/dynamic-layers/clang-layer/recipes-oneapi/dpcpp-compiler/intel-oneapi-dpcpp-cpp-runtime_2024.0.0-49819.bb, branch master</title>
<subtitle>[no description]</subtitle>
<id>https://git.enea.com/cgit/linux/meta-intel.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-intel.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/'/>
<updated>2026-04-29T15:10:40+00:00</updated>
<entry>
<title>intel-oneapi: drop obsolete standalone component recipes</title>
<updated>2026-04-29T15:10:40+00:00</updated>
<author>
<name>Yogesh Tyagi</name>
<email>yogesh.tyagi@intel.com</email>
</author>
<published>2026-04-29T13:38:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=c5e8f190469d736ba3f4bf7e84b15bb2c274d3d1'/>
<id>urn:sha1:c5e8f190469d736ba3f4bf7e84b15bb2c274d3d1</id>
<content type='text'>
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 &lt;yogesh.tyagi@intel.com&gt;
</content>
</entry>
<entry>
<title>Support whinlatter only</title>
<updated>2026-01-09T15:22:22+00:00</updated>
<author>
<name>Yogesh Tyagi</name>
<email>yogesh.tyagi@intel.com</email>
</author>
<published>2026-01-09T15:22:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=e85060a3d563c1319cc6745996b842a791706d9e'/>
<id>urn:sha1:e85060a3d563c1319cc6745996b842a791706d9e</id>
<content type='text'>
Yocto 5.3 merged most of meta-clang.
Fix recipes structure in dynamic-layers/clang-layer
clang recipes now depend on meta-clang-revival layer

Signed-off-by: Yogesh Tyagi &lt;yogesh.tyagi@intel.com&gt;
</content>
</entry>
</feed>
