Delete patch that's included in this release. Changelog: - Add support for MbedTLS - Add Reverse Proxy implementation - Add support for wireless pairing (AppleTV) - Embed 3rd party libraries for ed25519 and SRP6a - Fixes in idevicedebug - idevicecrashreport: Allow filtering crash reports by filename - Add idevicedevmodectl tool - Fixes for idevicebackup2 - Add property_list_client_get_service_client() and service_get_connection() functions - Add idevicebtlogger - Add new idevice_events_subscribe/unsubscribe API - Move LIBIMOBILEDEVICE_API to public headers - Add afc_strerror function - Add libimobiledevice_version() function - Use libimobiledevice-glue's SHA1 implementation - Add support for iOS 17+ Personalized Developer Disk image mounting - Fix compilation on MSVC - Add idevice_strerror() to interface - Add new idevice_get_device_version() to interface - Add os_trace_relay service implementation - Fixes for idevicesyslog - afc: Add afc_get_file_info_plist and afc_get_device_info_plist functions ... and several other internal changes Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.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.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' 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