opae-sdk: fix FTBFS after migration to pyproject.toml

This resolves a failure to build the latest OPAE SDK which migrated to
pyproject.toml to specify Python module build dependencies (PEP 518).

OFS/opae-sdk#2917
https://peps.python.org/pep-0518/

Closes: #1

recipes-ofs/opae-sdk/opae-sdk_git.bb

@@ -13,9 +13,9 @@ DEPENDS = "\
     libedit \
     python3 \
     python3-jsonschema-native \
+    python3-pip-native \
     python3-pybind11 \
     python3-pyyaml-native \
-    python3-setuptools-native \
     spdlog \
     tbb \
     udev \
@@ -27,6 +27,18 @@ PKGV = "${GITPKGVTAG}"
 
 inherit cmake pkgconfig python3native
 
+# Tell pip install to use build dependencies provided by bitbake
+# in the recipe's sysroot, instead of trying to download and
+# install the build dependencies. The latter fails since bitbake
+# builds recipes in an isolated sandbox without network access.
+#
+# https://github.com/OFS/meta-ofs/issues/1
+# https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-no-build-isolation
+#
+# PIP_NO_CACHE_DIR and PIP_NO_BUILD_ISOLATION behave opposite to how they read
+# https://github.com/pypa/pip/issues/5735
+export PIP_NO_BUILD_ISOLATION = "off"
+
 # Work around linking error for Python extension modules
 #
 # ld: cannot find crti.o: No such file or directory