Depreacate Numpy build tooling.

Author: freakboy3742

Makefile

@@ -558,33 +558,3 @@ vars-$1: $$(foreach target,$$(TARGETS-$1),vars-$$(target))
 endef
 
 $(foreach os,$(OS),$(eval $(call build,$(os))))
-
-###########################################################################
-# Compiling Python Libraries with binary components
-###########################################################################
-
-HOST_PYTHON=$(CURDIR)/build/macOS/python/bin/python3
-HOST_PIP=$(CURDIR)/build/macOS/python/bin/pip3
-
-# Ensure pip and setuptools are available
-pip: Python-macOS
-	$(HOST_PYTHON) -m ensurepip
-
-# Create the directory that will contain installed packages
-dist/app_packages:
-	mkdir -p dist/app_packages
-
-# Makefiles for individual binary packages that are supported.
-include patch/numpy/Makefile.numpy
-
-define build-app-packages
-packages-$1: numpy-$1
-endef
-
-$(foreach os,$(OS),$(eval $(call build-app-packages,$(os))))
-
-app_packages: numpy
-
-# Dump vars (for test)
-vars: $(foreach os,$(OS),vars-$(os))
-	@echo "APP_PACKAGES: $(APP_PACKAGES)"

README.rst

@@ -52,26 +52,6 @@ This should:
 The build products will be in the `build` directory; the compiled frameworks
 will be in the `dist` directory.
 
-Binary packages
----------------
-
-These tools are also able to compile the following packages that have binary
-components:
-
-* `numpy <patch/numpy/README.rst>`__
-
-These binary components are not compiled by default. However, the build
-infrastructure of this project can compile them on request. You can run::
-
-    make <name of package>
-
-to build a specific package; or, to build all supported packages::
-
-    make app_packages
-
-For details on how to add these binary packages to your project, see the
-package-specific documentation linked above.
-
 .. _for macOS: https://briefcase-support.org/python?platform=macOS&version=3.10
 .. _for iOS: https://briefcase-support.org/python?platform=iOS&version=3.10
 .. _for tvOS: https://briefcase-support.org/python?platform=tvOS&version=3.10