mirror of
https://github.com/openembedded/meta-openembedded.git
synced 2026-06-14 05:49:57 +00:00
33b294c8b2
- Change branch name master -> main according to upstream repository.
- Update 2.0.15 -> 2.0.16. Changelog:
1df82b9 Add param traits for CL_DEVICE_SUPPORTED_REGISTER_ALLOCATIONS_ARM (#165)
814e7b2 update the C++ bindings code example (#151)
6d833a5 Update opencl.hpp: Add CL_DEVICE_BOARD_NAME_AMD (#160)
25ad589 Added missing definitions for deprecated prefixes and suffixes for version 2.2 (#159)
21a34b0 Test two additional defines and update descriptions in header (#147)
ff7318c Fix cl::enqueueMapSVM for cl::vector and cl::pointer (#145)
30d4219 Test most of the possible defines (#140)
63d9e41 Fix unreasonable error handling in opencl.hpp (#139)
0198c41 Add support for cl_khr_integer_dot_product v2 (#141)
8df6c8f Transition CI to Github Actions (#142)
Signed-off-by: Daniel Gomez <daniel@qtec.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-oe ======= This layer depends on: URI: git://github.com/openembedded/openembedded-core.git branch: master luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below pacman -S lib32-gcc-libs lib32-glibc Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject' When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"' You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI. layer maintainer: Khem Raj <raj.khem@gmail.com>