meta-ohos-acts: remove obsolete layer

Currently ACTS are planned to be built together with OpenHarmony dependencies
in a single recipe using gn.bbclass. This renders all xts-acts related recipes
and the layer itself obsolete.

Closes: https://git.ostc-eu.org/OSTC/planning/maintenance/-/issues/18



Signed-off-by: robert.drab <robert.drab@huawei.com>

flavours/linux/bblayers.conf.sample

@@ -16,7 +16,6 @@ BBLAYERS ?= " \
   ##OEROOT##/meta-yocto-bsp \
   ##OEROOT##/../meta-zephyr \
   ##OEROOT##/../meta-ohos/meta-ohos-core \
-  ##OEROOT##/../meta-ohos/meta-ohos-acts \
   ##OEROOT##/../meta-ohos/meta-ohos-blueprints \
   ##OEROOT##/../meta-ohos/meta-ohos-staging \
   ##OEROOT##/../meta-freertos \

meta-ohos-acts/README.md

-<!--
-SPDX-FileCopyrightText: Huawei Inc.
-
-SPDX-License-Identifier: Apache-2.0
--->
-
-# Introduction
-
-This README file contains information on the contents of the meta-ohos-acts layer.
-
-Please see the corresponding sections below for details.
-
-# Dependencies
-
-This layer has no dependencies outside of poky.
-
-# Patches
-
-Please submit any patches for meta-ohos-acts layer as pull requests against the
-meta-ohos repository at https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/
-
-# Table of Contents
-
-- Adding the meta-ohos-acts layer to your build
-- Misc
-
-## Adding the meta-ohos-acts layer to your build
-
-Run 'bitbake-layers add-layer <path to meta-ohos>/meta-ohos-acts'
-
-## Misc
-
-This layer builds a subset of the ACTS (Application Compatibility Test Suite)
-for All Scenarios OS. Some tests are not ported yet. Some tests are excluded
-because they are duplicated in the greater bitbake ecosystem (e.g. LTP). Some
-tests are hardware or kernel specific and are not considered in this phase yet.

meta-ohos-acts/conf/layer.conf

-# SPDX-FileCopyrightText: Huawei Inc.
-#
-# SPDX-License-Identifier: Apache-2.0
-
-# We have a conf and classes directory, add to BBPATH
-BBPATH .= ":${LAYERDIR}"
-
-# We have recipes-* directories, add to BBFILES
-BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
-            ${LAYERDIR}/recipes-*/*/*.bbappend"
-
-BBFILE_COLLECTIONS += "meta-ohos-acts"
-BBFILE_PATTERN_meta-ohos-acts = "^${LAYERDIR}/"
-BBFILE_PRIORITY_meta-ohos-acts = "6"
-
-LAYERDEPENDS_meta-ohos-acts = "core"
-LAYERSERIES_COMPAT_meta-ohos-acts = "dunfell"
-
-LICENSE_PATH += "${LAYERDIR}/custom-licenses"

meta-ohos-acts/custom-licenses/MulanPSL-2.0

-木兰宽松许可证， 第2版
-
-2020年1月 http://license.coscl.org.cn/MulanPSL2
-
-您对“软件”的复制、使用、修改及分发受木兰宽松许可证，第2版（“本许可证”）的如下条款的约束：
-
-0.   定义
-
-“软件” 是指由“贡献”构成的许可在“本许可证”下的程序和相关文档的集合。
-
-“贡献” 是指由任一“贡献者”许可在“本许可证”下的受版权法保护的作品。
-
-“贡献者” 是指将受版权法保护的作品许可在“本许可证”下的自然人或“法人实体”。
-
-“法人实体” 是指提交贡献的机构及其“关联实体”。
-
-“关联实体” 是指，对“本许可证”下的行为方而言，控制、受控制或与其共同受控制的机构，此处的控制是指有受控方或共同受控方至少50%直接或间接的投票权、资金或其他有价证券。
-
-1.   授予版权许可
-
-每个“贡献者”根据“本许可证”授予您永久性的、全球性的、免费的、非独占的、不可撤销的版权许可，您可以复制、使用、修改、分发其“贡献”，不论修改与否。
-
-2.   授予专利许可
-
-每个“贡献者”根据“本许可证”授予您永久性的、全球性的、免费的、非独占的、不可撤销的（根据本条规定撤销除外）专利许可，供您制造、委托制造、使用、许诺销售、销售、进口其“贡献”或以其他方式转移其“贡献”。前述专利许可仅限于“贡献者”现在或将来拥有或控制的其“贡献”本身或其“贡献”与许可“贡献”时的“软件”结合而将必然会侵犯的专利权利要求，不包括对“贡献”的修改或包含“贡献”的其他结合。如果您或您的“关联实体”直接或间接地，就“软件”或其中的“贡献”对任何人发起专利侵权诉讼（包括反诉或交叉诉讼）或其他专利维权行动，指控其侵犯专利权，则“本许可证”授予您对“软件”的专利许可自您提起诉讼或发起维权行动之日终止。
-
-3.   无商标许可
-
-“本许可证”不提供对“贡献者”的商品名称、商标、服务标志或产品名称的商标许可，但您为满足第4条规定的声明义务而必须使用除外。
-
-4.   分发限制
-
-您可以在任何媒介中将“软件”以源程序形式或可执行形式重新分发，不论修改与否，但您必须向接收者提供“本许可证”的副本，并保留“软件”中的版权、商标、专利及免责声明。
-
-5.   免责声明与责任限制
-
-“软件”及其中的“贡献”在提供时不带任何明示或默示的担保。在任何情况下，“贡献者”或版权所有者不对任何人因使用“软件”或其中的“贡献”而引发的任何直接或间接损失承担责任，不论因何种原因导致或者基于何种法律理论，即使其曾被建议有此种损失的可能性。
-
-6.   语言
-
-“本许可证”以中英文双语表述，中英文版本具有同等法律效力。如果中英文版本存在任何冲突不一致，以中文版为准。
-
-条款结束
-
-如何将木兰宽松许可证，第2版，应用到您的软件
-
-如果您希望将木兰宽松许可证，第2版，应用到您的新软件，为了方便接收者查阅，建议您完成如下三步：
-
-1， 请您补充如下声明中的空白，包括软件名、软件的首次发表年份以及您作为版权人的名字；
-
-2， 请您在软件包的一级目录下创建以“LICENSE”为名的文件，将整个许可证文本放入该文件中；
-
-3， 请将如下声明文本放入每个源文件的头部注释中。
-
-Copyright (c) [Year] [name of copyright holder]
-[Software Name] is licensed under Mulan PSL v2.
-You can use this software according to the terms and conditions of the Mulan PSL v2.
-You may obtain a copy of Mulan PSL v2 at:
-         http://license.coscl.org.cn/MulanPSL2
-THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OF ANY KIND,
-EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO NON-INFRINGEMENT,
-MERCHANTABILITY OR FIT FOR A PARTICULAR PURPOSE.
-See the Mulan PSL v2 for more details.
-Mulan Permissive Software License，Version 2
-Mulan Permissive Software License，Version 2 (Mulan PSL v2)
-
-January 2020 http://license.coscl.org.cn/MulanPSL2
-
-Your reproduction, use, modification and distribution of the Software shall be subject to Mulan PSL v2 (this License) with the following terms and conditions:
-
-0. Definition
-
-Software means the program and related documents which are licensed under this License and comprise all Contribution(s).
-
-Contribution means the copyrightable work licensed by a particular Contributor under this License.
-
-Contributor means the Individual or Legal Entity who licenses its copyrightable work under this License.
-
-Legal Entity means the entity making a Contribution and all its Affiliates.
-
-Affiliates means entities that control, are controlled by, or are under common control with the acting entity under this License, ‘control’ means direct or indirect ownership of at least fifty percent (50%) of the voting power, capital or other securities of controlled or commonly controlled entity.
-
-1. Grant of Copyright License
-
-Subject to the terms and conditions of this License, each Contributor hereby grants to you a perpetual, worldwide, royalty-free, non-exclusive, irrevocable copyright license to reproduce, use, modify, or distribute its Contribution, with modification or not.
-
-2. Grant of Patent License
-
-Subject to the terms and conditions of this License, each Contributor hereby grants to you a perpetual, worldwide, royalty-free, non-exclusive, irrevocable (except for revocation under this Section) patent license to make, have made, use, offer for sale, sell, import or otherwise transfer its Contribution, where such patent license is only limited to the patent claims owned or controlled by such Contributor now or in future which will be necessarily infringed by its Contribution alone, or by combination of the Contribution with the Software to which the Contribution was contributed. The patent license shall not apply to any modification of the Contribution, and any other combination which includes the Contribution. If you or your Affiliates directly or indirectly institute patent litigation (including a cross claim or counterclaim in a litigation) or other patent enforcement activities against any individual or entity by alleging that the Software or any Contribution in it infringes patents, then any patent license granted to you under this License for the Software shall terminate as of the date such litigation or activity is filed or taken.
-
-3. No Trademark License
-
-No trademark license is granted to use the trade names, trademarks, service marks, or product names of Contributor, except as required to fulfill notice requirements in section 4.
-
-4. Distribution Restriction
-
-You may distribute the Software in any medium with or without modification, whether in source or executable forms, provided that you provide recipients with a copy of this License and retain copyright, patent, trademark and disclaimer statements in the Software.
-
-5. Disclaimer of Warranty and Limitation of Liability
-
-THE SOFTWARE AND CONTRIBUTION IN IT ARE PROVIDED WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL ANY CONTRIBUTOR OR COPYRIGHT HOLDER BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING, BUT NOT LIMITED TO ANY DIRECT, OR INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING FROM YOUR USE OR INABILITY TO USE THE SOFTWARE OR THE CONTRIBUTION IN IT, NO MATTER HOW IT’S CAUSED OR BASED ON WHICH LEGAL THEORY, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-6. Language
-
-THIS LICENSE IS WRITTEN IN BOTH CHINESE AND ENGLISH, AND THE CHINESE VERSION AND ENGLISH VERSION SHALL HAVE THE SAME LEGAL EFFECT. IN THE CASE OF DIVERGENCE BETWEEN THE CHINESE AND ENGLISH VERSIONS, THE CHINESE VERSION SHALL PREVAIL.
-
-END OF THE TERMS AND CONDITIONS
-
-How to Apply the Mulan Permissive Software License，Version 2 (Mulan PSL v2) to Your Software
-
-To apply the Mulan PSL v2 to your work, for easy identification by recipients, you are suggested to complete following three steps:
-
-Fill in the blanks in following statement, including insert your software name, the year of the first publication of your software, and your name identified as the copyright owner;
-Create a file named "LICENSE" which contains the whole context of this License in the first directory of your software package;
-Attach the statement to the appropriate annotated syntax at the beginning of each source file.
-Copyright (c) [Year] [name of copyright holder]
-[Software Name] is licensed under Mulan PSL v2.
-You can use this software according to the terms and conditions of the Mulan PSL v2.
-You may obtain a copy of Mulan PSL v2 at:
-         http://license.coscl.org.cn/MulanPSL2
-THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OF ANY KIND,
-EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO NON-INFRINGEMENT,
-MERCHANTABILITY OR FIT FOR A PARTICULAR PURPOSE.
-See the Mulan PSL v2 for more details.

meta-ohos-acts/recipes-kernel/linux/linux-yocto/0001-fragment-jffs2-tests.cfg

-# SPDX-FileCopyrightText: Huawei Inc.
-#
-# SPDX-License-Identifier: Apache-2.0
-
-CONFIG_MTD=y
-CONFIG_MTD_BLOCK=y
-CONFIG_MTD_BLOCK2MTD=m
-CONFIG_JFFS2_FS=y

meta-ohos-acts/recipes-kernel/linux/linux-yocto_5.%.bbappend

-# SPDX-FileCopyrightText: Huawei Inc.
-#
-# SPDX-License-Identifier: Apache-2.0
-
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-SRC_URI += "file://0001-fragment-jffs2-tests.cfg"

meta-ohos-acts/recipes-ohos-global-i18n-lite/ohos-global-i18n-lite/ohos-global-i18n-lite/GNUmakefile

-# SPDX-FileCopyrightText: Huawei Inc.
-#
-# SPDX-License-Identifier: Apache-2.0
-
-include z.mk
-
-Project.Name=ohos-global-i18n-lite
-Project.Version=1
-
-$(eval $(call ZMK.Import,Configure))
-
-libglobal_i18n.so: CPPFLAGS += -iquote $(ZMK.OutOfTreeSourcePath)interfaces/kits/i18n/include
-libglobal_i18n.so: CPPFLAGS += -iquote $(ZMK.OutOfTreeSourcePath)frameworks/i18n/include
-libglobal_i18n.so: LDLIBS += -lsec
-libglobal_i18n.so.Sources = $(wildcard $(ZMK.OutOfTreeSourcePath)frameworks/i18n/src/*.cpp)
-$(eval $(call ZMK.Expand,Library.So,libglobal_i18n.so))
-
-# Public header files
-global-i18n-lite-headers-public.InstallDir = $(includedir)
-global-i18n-lite-headers-public.Headers = $(wildcard $(ZMK.OutOfTreeSourcePath)interfaces/kits/i18n/include/*.h)
-$(eval $(call ZMK.Expand,HeaderGroup,global-i18n-lite-headers-public))
-
-# XXX: OHOS locale/i18n resource data base file that is expected to be present
-# in the /storage/data directory on the target. There are others expectations
-# regarding this particular location, e.g. that it is mounted on a jffs2 fs.
-# To avoid unnecessary rootfs structure constraints placing it in
-# /usr/share/ohos-global-i18n-lite location for the time being to be put in an
-# appropriate place by the ACTS global_lite test suite spread task.
-frameworks/i18n/i18n.dat.InstallDir = $(datadir)/$(Project.Name)
-# FIXME: This installs a binary blob that's required by the shard library.
-# Issue on gitee: https://gitee.com/openharmony/global_i18n_lite/issues/I3HZXS
-$(eval $(call ZMK.Expand,InstallUninstall,frameworks/i18n/i18n.dat))
\ No newline at end of file

meta-ohos-acts/recipes-ohos-global-i18n-lite/ohos-global-i18n-lite/ohos-global-i18n-lite_git.bb

-# SPDX-FileCopyrightText: Huawei Inc.
-#
-# SPDX-License-Identifier: Apache-2.0
-
-SUMMARY = "OpenHarmony i18n library"
-DESCRIPTION = "OpenHarmony library providing i18n capabilities like date, \
-time and numbers formatting or months and weekdays handling."
-
-LICENSE = "Apache-2.0"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=a832eda17114b48ae16cda6a500941c2"
-
-SRC_URI = "git://gitee.com/openharmony/global_i18n_lite.git;protocol=https \
-           file://GNUmakefile \
-"
-SRCREV = "1de9116474acc560b79dc5b5ecf5354c4d7089c0"
-PV = "0.0+git${SRCPV}"
-S = "${WORKDIR}/git"
-
-inherit zmk
-
-DEPENDS += "ohos-libsec"
-
-# The OHOS uses unversioned versioned libraries.
-# Move the naked .so files to the primary package.
-SOLIBS = ".so"
-FILES_SOLIBSDEV = ""
-
-do_configure_prepend() {
-    # global_i18n_lite component is being built using zmk compatible makefile
-    cp ${WORKDIR}/GNUmakefile ${S}
-}

meta-ohos-acts/recipes-ohos-googletest/ohos-googletest/ohos-googletest/googletest-gcc-11.patch

-diff -up git/googletest/include/gtest/hwext/gtest-tag.h.omv~ git/googletest/include/gtest/hwext/gtest-tag.h
---- git/googletest/include/gtest/hwext/gtest-tag.h.omv~	2021-07-06 19:01:12.828013607 +0200
-+++ git/googletest/include/gtest/hwext/gtest-tag.h	2021-07-06 19:01:24.291492486 +0200
-@@ -3,7 +3,8 @@
- #ifndef GTEST_INCLUDE_GTEST_GTEST_TAG_H_
- #define GTEST_INCLUDE_GTEST_GTEST_TAG_H_
- 
--#include <string.h>
-+#include <string>
-+#include <cstring>
- #include <map>
- #include <vector>
- 

meta-ohos-acts/recipes-ohos-googletest/ohos-googletest/ohos-googletest_git.bb

-# SPDX-FileCopyrightText: Huawei Inc.
-#
-# SPDX-License-Identifier: Apache-2.0
-
-LICENSE = "BSD-3-Clause"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=cbbd27594afd089daa160d3a16dd515a \
-                    file://googlemock/LICENSE;md5=cbbd27594afd089daa160d3a16dd515a \
-                    file://googlemock/scripts/generator/LICENSE;md5=2c0b90db7465231447cf2dd2e8163333 \
-                    file://googletest/LICENSE;md5=cbbd27594afd089daa160d3a16dd515a"
-
-SRC_URI = "git://git.ostc-eu.org/OSTC/OHOS/components/staging/third_party_googletest.git;protocol=https;branch=ostc-next \
-file://googletest-gcc-11.patch"
-SRCREV = "54337710388898ae818bbc2c0e0457c9b86e335e"
-S = "${WORKDIR}/git"
-PV = "0.0+git${SRCPV}"
-
-# The OHOS fork of googletest is not versioned properly.
-# Move the naked .so files to the primary package.
-SOLIBS = ".so"
-FILES_SOLIBSDEV = ""
-
-inherit zmk
-
-do_configure_prepend() {
-    # Remove upstream autotools. Those are unmaintained in the OHOS fork.
-    # They cause bitbake to be confused and run the wrong build system.
-    rm -f ${S}/Makefile.am ${S}/configure.ac ${S}/configure
-}

meta-ohos-acts/recipes-ohos-libsec/ohos-libsec/ohos-libsec_git.bb

-# SPDX-FileCopyrightText: Huawei Inc.
-#
-# SPDX-License-Identifier: Apache-2.0
-
-LICENSE = "MulanPSL-2.0"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=2ba4788337b3607f139c2267ed50d32b"
-
-SRC_URI = "git://git.ostc-eu.org/OSTC/OHOS/components/staging/third_party_bounds_checking_function.git;protocol=https;branch=ostc"
-SRCREV = "256b1fc30d387f47cac1a376b2f1f28148b94804"
-S = "${WORKDIR}/git"
-PV = "0.0+git${SRCPV}"
-
-# The OHOS fork of libsec is not versioned properly.
-# Move the naked .so files to the primary package.
-SOLIBS = ".so"
-FILES_SOLIBSDEV = ""
-
-inherit zmk

meta-ohos-acts/recipes-ohos-xts-acts/ohos-xts-acts/ohos-xts-acts_git.bb

-# SPDX-FileCopyrightText: Huawei Inc.
-#
-# SPDX-License-Identifier: Apache-2.0
-
-LICENSE = "Apache-2.0"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=98c2e72b17fae6c40fb14fd5e43b29ec"
-
-SRC_URI = "git://git.ostc-eu.org/OSTC/OHOS/components/staging/xts_acts.git;protocol=https;branch=ostc-next"
-SRCREV = "defe7649c4baa33b405785201b9d686722ef66da"
-S = "${WORKDIR}/git"
-PV = "0.0+git${SRCPV}"
-
-# The OHOS uses unversioned versioned libraries.
-# Move the naked .so files to the primary package.
-SOLIBS = ".so"
-FILES_SOLIBSDEV = ""
-
-inherit zmk
-
-# jffs2 image size defaults to 1MB
-ACTS_JFFS2_IMG_SIZE ?= "0x100000"
-
-# FIXME this should be fixed properly instead of adding this workaround.
-# When using modern compilers with -Warray-bounds, they find at least one
-# legitimate issue with the code in xts:
-# | ../git/kernel_lite/mem_posix/src/ActsMemApiTest.cpp:229:25: error: 'void* mempcpy(void*, const void*, size_t)' forming offset [13, 15] is out of the bounds [0, 13] of object 'srcStr' with type 'char [13]' [-Werror=array-bounds]
-# |   229 |     pt = (char *)mempcpy(destStr, srcStr, 16);
-# |       |                  ~~~~~~~^~~~~~~~~~~~~~~~~~~~~
-# | ../git/kernel_lite/mem_posix/src/ActsMemApiTest.cpp:224:10: note: 'srcStr' declared here
-# |   224 |     char srcStr[] = "this is str1";
-# |       |          ^~~~~~
-#
-# (Copying 16 characters from a string of 12)
-#
-# However, making the error non-fatal is no worse than not using
-# -Werror=array-bounds globally (previous situation), so it is an
-# ok workaround until this is fixed properly.
-TARGET_CFLAGS_remove = "-Werror=array-bounds"
-
-do_install_append() {
-    # Prepare jffs2 image to be mounted on the target
-    # mkfs.jffs2 requires a directory to make an image out of
-    mkdir -p ${B}/.jffs-empty-dir
-    mkfs.jffs2 --root=${B}/.jffs-empty-dir --pad=${ACTS_JFFS2_IMG_SIZE} -o ${B}/jffs2.img
-    rm -rf ${B}/.jffs-empty-dir
-    install -d ${D}${datadir}/acts-data
-    install -m 644 ${B}/jffs2.img ${D}${datadir}/acts-data
-}
-
-FILES_${PN} += "${datadir}/acts-data/*"
-
-DEPENDS += "\
-    libcap \
-    mtd-utils-native \
-    ohos-global-i18n-lite \
-    ohos-googletest \
-    ohos-libsec \
-"
-DEPENDS_append_toolchain-clang += "compiler-rt"
-RRECOMMENDS_${PN} += "\
-    kernel-module-block2mtd \
-    ltp \
-"

meta-ohos-core/recipes-core/packagegroups/packagegroup-oniro-tests.bb

@@ -11,6 +11,5 @@ PACKAGES = "\
 	"
 
 RDEPENDS_packagegroup-oniro-tests = "\
-	ohos-xts-acts \
 	ptest-runner \
         "