summaryrefslogtreecommitdiffstats
path: root/meta-nuc
diff options
context:
space:
mode:
authorYogesh Tyagi <yogesh.tyagi@intel.com>2026-05-14 16:12:18 +0800
committerYogesh Tyagi <yogesh.tyagi@intel.com>2026-05-17 23:00:25 +0800
commitff8ad78a0e3531060aa712b708cc01178c564a69 (patch)
treef1c81915ca379491647b63d7103f119dea49ecf2 /meta-nuc
parent2a8d44bf7b9faca3935b851107c70754e1cdcae3 (diff)
downloadmeta-intel-ff8ad78a0e3531060aa712b708cc01178c564a69.tar.gz
intel-oneapi-toolkit: split mkl and ipp into runtime/sycl/staticdev/dev sub-packages
The 2026.0 oneAPI MKL component grew to 1.9 GB on disk, dominated by ~900 MB of static archives, ~330 MB of SYCL/GPU offload libraries and ~80 MB of headers / cmake metadata / sample sources. The IPP component similarly carries ~280 MB of static archives on top of a 537 MB runtime payload. Consumers that only need a CPU BLAS/FFT backend (PyTorch CPU, NumPy, image-processing pipelines) were paying for all of it whenever they installed intel-oneapi-toolkit-mkl or intel-oneapi-toolkit-ipp. Split the two heaviest components along the usual runtime/dev/static seams: intel-oneapi-toolkit-mkl CPU shared libs + dispatch libraries + env/etc/bin glue (~640 MB) intel-oneapi-toolkit-mkl-sycl SYCL / GPU offload shared libs (~330 MB, RDEPENDS -runtime) intel-oneapi-toolkit-mkl-staticdev Static archives, lib/*.a (~900 MB) intel-oneapi-toolkit-mkl-dev Headers, cmake modules, pkgconfig files, share/ examples (~85 MB) intel-oneapi-toolkit-ipp ipp + ippcp runtime shared libs (~540 MB) intel-oneapi-toolkit-ipp-staticdev Static archives (~280 MB) intel-oneapi-toolkit-ipp-dev Headers, cmake, pkgconfig, share PACKAGES ordering places the specific sub-sub-packages before the catch-all component package so first-match-wins puts the heavyweight bits in their dedicated package. FILES patterns use [0-9]* to match the versioned directory only (the sibling 'latest' compatibility symlink is captured by the parent component package). RDEPENDS form a closed chain: -dev depends on the runtime package, -staticdev on -dev, -sycl on -runtime + the CPU runtime, so users that explicitly install a sub-sub-package still get a working environment. The top-level meta-package RDEPENDS:${PN} continues to pull all of the new sub-packages, so an image that asks for the unqualified intel-oneapi-toolkit recipe is unchanged. Signed-off-by: Yogesh Tyagi <yogesh.tyagi@intel.com> Tested-by: Zoltán Böszörményi <zboszor@gmail.com>
Diffstat (limited to 'meta-nuc')
0 files changed, 0 insertions, 0 deletions