halide 19.0.0__cp313-cp313-win_amd64.whl → 21.0.0__cp313-cp313-win_amd64.whl

halide/share/doc/Halide/doc/BuildingHalideWithCMake.md

@@ -31,6 +31,7 @@ are looking for Halide's CMake coding guidelines, see [CodeStyleCMake.md].
   * [Build options](#build-options)
   * [Installing](#installing)
 * [Building Halide with pip](#building-halide-with-pip)
+  * [Using ccache with pip builds](#using-ccache-with-pip-builds)
 <!-- TOC -->
 
 # Installing CMake
@@ -147,8 +148,8 @@ building the core pieces of Halide.
 | [flatbuffers] | `~=23.5.26`        | `WITH_SERIALIZATION=ON`    |                                                     |
 | [wabt]        | `==1.0.36`         | `Halide_WASM_BACKEND=wabt` | Does not have a stable API; exact version required. |
 | [V8]          | trunk              | `Halide_WASM_BACKEND=V8`   | Difficult to build. See [WebAssembly.md]            |
-| [Python]      | `>=3.8`            | `WITH_PYTHON_BINDINGS=ON`  |                                                     |
-| [pybind11]    | `~=2.10.4`         | `WITH_PYTHON_BINDINGS=ON`  |                                                     |
+| [Python]      | `>=3.9`            | `WITH_PYTHON_BINDINGS=ON`  |                                                     |
+| [pybind11]    | `~=2.11.1`         | `WITH_PYTHON_BINDINGS=ON`  |                                                     |
 
 Halide maintains the following compatibility policy with LLVM: Halide version
 `N` supports LLVM versions `N`, `N-1`, and `N-2`. Our binary distributions
@@ -243,16 +244,18 @@ from the root of the repository.
 On macOS, it is possible to install all dependencies via [Homebrew][homebrew]:
 
 ```shell
-$ brew install llvm flatbuffers wabt python pybind11 doxygen eigen libpng libjpeg openblas
+$ brew install llvm flatbuffers wabt python pybind11 doxygen eigen libpng libjpeg-turbo openblas
 ```
 
 The `llvm` package includes `clang`, `clang-format`, and `lld`, too. To ensure
-CMake can find the keg-only dependencies, set the following:
+CMake can find LLVM, set the following cache variable:
 
 ```shell
-$ export CMAKE_PREFIX_PATH="/opt/homebrew:/opt/homebrew/opt/llvm:/opt/homebrew/opt/jpeg"
+$ cmake ... -DHalide_ROOT=/opt/homebrew/opt/llvm
 ```
 
+Or use the `macOS` CMake preset, which does this for you.
+
 ### Ubuntu / Debian
 
 On Ubuntu you should install the following packages (this includes the Python
@@ -260,7 +263,7 @@ module dependencies):
 
 ```
 $ sudo apt install clang-tools lld llvm-dev libclang-dev liblld-dev \
-    libpng-dev libjpeg-dev libgl-dev python3-dev python3-numpy python3-scipy \
+    libpng-dev libjpeg-dev libgl-dev python3-dev python3-numpy \
     python3-imageio python3-pybind11 libopenblas-dev libeigen3-dev \ 
     libatlas-base-dev doxygen
 ```
@@ -514,6 +517,71 @@ However, this comes with a few caveats:
 Even so, this is a very good method of installing Halide. It supports both
 Python and C++ `find_package` workflows.
 
+## Using ccache with pip builds
+
+Because Python's build infrastructure creates temporary CMake build directories,
+simply setting `CMAKE_CXX_COMPILER_LAUNCHER` to `ccache` is insufficient to
+produce a well-cached build. The following settings should serve as a starting
+point to configure your environment (assuming `$PWD` is the repository root)
+for using `ccache` with `pip install .`.
+
+```shell
+# Point CMake to ccache
+export CMAKE_C_COMPILER_LAUNCHER=ccache
+export CMAKE_CXX_COMPILER_LAUNCHER=ccache
+
+# Settings to make ccache try to ignore the build directory
+export CCACHE_BASEDIR=$PWD
+export CCACHE_NOHASHDIR=true
+
+# Enable caching of pre-compiled headers and rewrite debug paths
+# -Xclang -fno-pch-timestamp is only necessary when using Clang (not GCC)
+export CCACHE_SLOPPINESS=include_file_ctime,include_file_mtime,pch_defines,time_macros
+export CFLAGS="-Xclang -fno-pch-timestamp -fdebug-prefix-map=$PWD=."
+export CXXFLAGS="$CFLAGS"
+
+# Locate the temporary build beneath $PWD so that CCACHE_BASEDIR works
+export TMPDIR=$PWD/build/tmp
+
+# If using uv, don't create a temporary venv
+export UV_NO_BUILD_ISOLATION=1
+```
+
+See the CCache documentation on [compiling in different directories] and on
+using [precompiled headers] for more information about these settings. To check
+that ccache is working, run,
+
+```shell
+$ uv pip install .  # first run, populate cache
+Resolved 4 packages in 397ms
+      Built halide @ file:///Users/areinking/dev/Halide
+Prepared 1 package in 29.17s
+Installed 1 package in 8ms
+ + halide==20.0.0.dev87+gf6c939fd3.d20250724 (from file:///Users/areinking/dev/Halide)
+$ ccache -z
+Statistics zeroed
+$ uv pip install .  # second run, reload from cache
+Resolved 4 packages in 338ms
+      Built halide @ file:///Users/areinking/dev/Halide
+Prepared 1 package in 10.82s
+Uninstalled 1 package in 7ms
+Installed 1 package in 6ms
+ ~ halide==20.0.0.dev87+gf6c939fd3.d20250724 (from file:///Users/areinking/dev/Halide)
+$ ccache -s
+Cacheable calls:   1079 / 1080 (99.91%)
+  Hits:            1079 / 1079 (100.0%)
+    Direct:        1079 / 1079 (100.0%)
+    Preprocessed:     0 / 1079 ( 0.00%)
+  Misses:             0 / 1079 ( 0.00%)
+Uncacheable calls:    1 / 1080 ( 0.09%)
+Local storage:
+  Cache size (GB):  2.2 / 30.0 ( 7.24%)
+  Hits:            1079 / 1079 (100.0%)
+  Misses:             0 / 1079 ( 0.00%)
+```
+
+On this test system (an M3 MacBook Pro), the build is three times faster,
+with a 100% cache hit rate!
 
 [ATLAS]: http://math-atlas.sourceforge.net/
 
@@ -577,6 +645,8 @@ Python and C++ `find_package` workflows.
 
 [cmake_presets]: https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html
 
+[compiling in different directories]: https://ccache.dev/manual/4.11.3.html#_compiling_in_different_directories
+
 [doxygen-download]: https://www.doxygen.nl/download.html
 
 [doxygen]: https://www.doxygen.nl/index.html
@@ -603,6 +673,8 @@ Python and C++ `find_package` workflows.
 
 [pipx]: https://pipx.pypa.io/stable/
 
+[precompiled headers]: https://ccache.dev/manual/4.11.3.html#_precompiled_headers
+
 [pybind11]: https://github.com/pybind/pybind11
 
 [pypi-cmake]: https://pypi.org/project/cmake/

halide/share/doc/Halide/doc/HalideCMakePackage.md

@@ -392,6 +392,7 @@ add_halide_library(<target> FROM <generator-target>
                    [NAMESPACE cpp-namespace]
                    [USE_RUNTIME hl-target]
                    [PARAMS param1 [param2 ...]]
+                   [DEPENDS [dep1 dep2 ...]]
                    [TARGETS target1 [target2 ...]]
                    [FEATURES feature1 [feature2 ...]]
                    [FEATURES[<triple>] feature1 [feature2 ...]]
@@ -463,6 +464,12 @@ When `CMAKE_OSX_ARCHITECTURES` is set and the `TARGETS` argument resolves to
 `cmake`, the generator will be run once for each architecture and the results
 will be fused together using `lipo`. This behavior extends to runtime targets.
 
+Sometimes, the generation will need to read files that were generated during the
+build. To declare dependencies on these files, use the `DEPENDS` argument. Paths
+listed here will be passed verbatim to `add_custom_command`, and so will be
+relative to the source directory. Use absolute paths when referring to files
+outside the source directory.
+
 To use an autoscheduler, set the `AUTOSCHEDULER` argument to a target named like
 `Namespace::Scheduler`, for example `Halide::Adams2019`. This will set the
 `autoscheduler` GeneratorParam on the generator command line to `Scheduler`
@@ -532,8 +539,8 @@ will be added to the extension as a callable method of the module. Note that
 every library specified must be built with the `PYTHON_EXTENSION` keyword
 specified, and all libraries must use the same Halide runtime.
 
-The result will be a shared library of the form `<target>.<soabi>.so`, where 
-`<soabi>` describes the specific Python version and platform (e.g., 
+The result will be a shared library of the form `<target>.<soabi>.so`, where
+`<soabi>` describes the specific Python version and platform (e.g.,
 `cpython-310-darwin` for Python 3.10 on macOS.)
 
 ### `add_halide_runtime`

halide/share/doc/Halide/doc/Python.md

@@ -31,7 +31,7 @@
   * [License](#license)
 <!-- TOC -->
 
-Halide provides Python bindings for most of its public API. Python 3.8 (or
+Halide provides Python bindings for most of its public API. Python 3.9 (or
 higher) is required. The Python bindings are supported on 64-bit Linux, OSX, and
 Windows systems.
 
@@ -85,12 +85,17 @@ $ python3 -m pip install -U pip "setuptools[core]" wheel
 $ python3 -m pip install -r requirements.txt
 ```
 
+Or, if using `uv` the following command is equivalent:
+
+```shell
+uv venv --python 3.12  # for example
+uv pip install -r requirements.txt
+```
+
 Then build and install Halide:
 
 ```shell
-$ cmake -G Ninja -S . -B build \
-        -DCMAKE_BUILD_TYPE=Release \ 
-        -DWITH_PYTHON_BINDINGS=ON
+$ cmake -G Ninja -S . -B build -DCMAKE_BUILD_TYPE=Release
 $ cmake --build build
 $ cmake --install build --prefix .local
 ```
@@ -126,6 +131,16 @@ Then it should be as simple as:
 $ pip install .
 ```
 
+When using `uv`, this entire workflow can be run via
+
+```shell
+$ uv sync
+```
+
+If you need a different Python version, you can add `--python 3.xy` to this 
+command. If you wish to install compatible build tools into the venv (e.g. 
+CMake, ninja), rather than use your system tools, pass `--group tools` here.
+
 ## Documentation and Examples
 
 As mentioned elsewhere, the Python API attempts to mimic the

halide/share/doc/Halide/doc/RunGen.md

@@ -125,7 +125,7 @@ Generator, and inits every element to zero:
 
 ```
 # Input is a 3-dimensional image with extent 123, 456, and 3
-# (bluring an image of all zeroes isn't very interesting, of course)
+# (bluring an image of all zeros isn't very interesting, of course)
 $ ./bin/local_laplacian.rungen --output_extents=[100,200,3] input=zero:[123,456,3] levels=8 alpha=1 beta=1 output=/tmp/out.png
 ```
 

{halide-19.0.0.data → halide-21.0.0.data}/data/share/cmake/Halide/HalideConfig.cmake

@@ -1,6 +1,9 @@
 cmake_minimum_required(VERSION 3.28)
 
 include(CMakeFindDependencyMacro)
-find_dependency(Python 3)
+find_dependency(
+    Python 3
+    COMPONENTS Interpreter Development.Module
+)
 
 include("${Python_SITEARCH}/halide/lib/cmake/Halide/HalideConfig.cmake")

{halide-19.0.0.data → halide-21.0.0.data}/data/share/cmake/Halide/HalideConfigVersion.cmake

@@ -9,19 +9,19 @@
 # The variable CVF_VERSION must be set before calling configure_file().
 
 
-set(PACKAGE_VERSION "19.0.0")
+set(PACKAGE_VERSION "21.0.0")
 
 if(PACKAGE_VERSION VERSION_LESS PACKAGE_FIND_VERSION)
   set(PACKAGE_VERSION_COMPATIBLE FALSE)
 else()
 
-  if("19.0.0" MATCHES "^([0-9]+)\\.")
+  if("21.0.0" MATCHES "^([0-9]+)\\.")
     set(CVF_VERSION_MAJOR "${CMAKE_MATCH_1}")
     if(NOT CVF_VERSION_MAJOR VERSION_EQUAL 0)
       string(REGEX REPLACE "^0+" "" CVF_VERSION_MAJOR "${CVF_VERSION_MAJOR}")
     endif()
   else()
-    set(CVF_VERSION_MAJOR "19.0.0")
+    set(CVF_VERSION_MAJOR "21.0.0")
   endif()
 
   if(PACKAGE_FIND_VERSION_RANGE)

{halide-19.0.0.data → halide-21.0.0.data}/data/share/cmake/HalideHelpers/HalideHelpersConfig.cmake

@@ -1,6 +1,9 @@
 cmake_minimum_required(VERSION 3.28)
 
 include(CMakeFindDependencyMacro)
-find_dependency(Python 3)
+find_dependency(
+    Python 3
+    COMPONENTS Interpreter Development.Module
+)
 
 include("${Python_SITEARCH}/halide/lib/cmake/HalideHelpers/HalideHelpersConfig.cmake")

{halide-19.0.0.data → halide-21.0.0.data}/data/share/cmake/HalideHelpers/HalideHelpersConfigVersion.cmake

@@ -9,19 +9,19 @@
 # The variable CVF_VERSION must be set before calling configure_file().
 
 
-set(PACKAGE_VERSION "19.0.0")
+set(PACKAGE_VERSION "21.0.0")
 
 if(PACKAGE_VERSION VERSION_LESS PACKAGE_FIND_VERSION)
   set(PACKAGE_VERSION_COMPATIBLE FALSE)
 else()
 
-  if("19.0.0" MATCHES "^([0-9]+)\\.")
+  if("21.0.0" MATCHES "^([0-9]+)\\.")
     set(CVF_VERSION_MAJOR "${CMAKE_MATCH_1}")
     if(NOT CVF_VERSION_MAJOR VERSION_EQUAL 0)
       string(REGEX REPLACE "^0+" "" CVF_VERSION_MAJOR "${CVF_VERSION_MAJOR}")
     endif()
   else()
-    set(CVF_VERSION_MAJOR "19.0.0")
+    set(CVF_VERSION_MAJOR "21.0.0")
   endif()
 
   if(PACKAGE_FIND_VERSION_RANGE)

halide-21.0.0.dist-info/METADATA

@@ -0,0 +1,302 @@
+Metadata-Version: 2.2
+Name: halide
+Version: 21.0.0
+Summary: Halide is a programming language designed to make it easier to write high-performance image and array processing code.
+Keywords: array,compiler,domain-specific language,dsl,gpu,hexagon,image processing,machine learning,performance,programming language
+Author-Email: The Halide team <halide-dev@lists.csail.mit.edu>
+Maintainer-Email: Alex Reinking <areinking@adobe.com>
+License: Copyright (c) 2012-2020 MIT CSAIL, Google, Facebook, Adobe, NVIDIA CORPORATION, and other contributors.
+         
+         Developed by:
+         
+           The Halide team
+           http://halide-lang.org
+         
+         Permission is hereby granted, free of charge, to any person obtaining a copy of
+         this software and associated documentation files (the "Software"), to deal in
+         the Software without restriction, including without limitation the rights to
+         use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+         of the Software, and to permit persons to whom the Software is furnished to do
+         so, subject to the following conditions:
+         
+         The above copyright notice and this permission notice shall be included in all
+         copies or substantial portions of the Software.
+         
+         THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+         IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+         FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+         AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+         LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+         OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+         SOFTWARE.
+         
+         -----
+         
+         apps/bgu is Copyright 2016 Google Inc. and is Licensed under the Apache License,
+         Version 2.0 (the "License"); you may not use this file except in compliance
+         with the License.
+         
+         Apache License
+         
+         Version 2.0, January 2004
+         
+         http://www.apache.org/licenses/
+         
+         TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+         
+         1. Definitions.
+         
+         "License" shall mean the terms and conditions for use, reproduction, and
+         distribution as defined by Sections 1 through 9 of this document.
+         
+         "Licensor" shall mean the copyright owner or entity authorized by the
+         copyright owner that is granting the License.
+         
+         "Legal Entity" shall mean the union of the acting entity and all other
+         entities that control, are controlled by, or are under common control with
+         that entity. For the purposes of this definition, "control" means (i) the
+         power, direct or indirect, to cause the direction or management of such
+         entity, whether by contract or otherwise, or (ii) ownership of fifty percent
+         (50%) or more of the outstanding shares, or (iii) beneficial ownership of such
+         entity.
+         
+         "You" (or "Your") shall mean an individual or Legal Entity exercising
+         permissions granted by this License.
+         
+         "Source" form shall mean the preferred form for making modifications,
+         including but not limited to software source code, documentation source, and
+         configuration files.
+         
+         "Object" form shall mean any form resulting from mechanical transformation or
+         translation of a Source form, including but not limited to compiled object
+         code, generated documentation, and conversions to other media types.
+         
+         "Work" shall mean the work of authorship, whether in Source or Object form,
+         made available under the License, as indicated by a copyright notice that is
+         included in or attached to the work (an example is provided in the Appendix
+         below).
+         
+         "Derivative Works" shall mean any work, whether in Source or Object form, that
+         is based on (or derived from) the Work and for which the editorial revisions,
+         annotations, elaborations, or other modifications represent, as a whole, an
+         original work of authorship. For the purposes of this License, Derivative
+         Works shall not include works that remain separable from, or merely link (or
+         bind by name) to the interfaces of, the Work and Derivative Works thereof.
+         
+         "Contribution" shall mean any work of authorship, including the original
+         version of the Work and any modifications or additions to that Work or
+         Derivative Works thereof, that is intentionally submitted to Licensor for
+         inclusion in the Work by the copyright owner or by an individual or Legal
+         Entity authorized to submit on behalf of the copyright owner. For the purposes
+         of this definition, "submitted" means any form of electronic, verbal, or
+         written communication sent to the Licensor or its representatives, including
+         but not limited to communication on electronic mailing lists, source code
+         control systems, and issue tracking systems that are managed by, or on behalf
+         of, the Licensor for the purpose of discussing and improving the Work, but
+         excluding communication that is conspicuously marked or otherwise designated
+         in writing by the copyright owner as "Not a Contribution."
+         
+         "Contributor" shall mean Licensor and any individual or Legal Entity on behalf
+         of whom a Contribution has been received by Licensor and subsequently
+         incorporated within the Work.
+         
+         2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+         
+         3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+         
+         4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+         
+         (a) You must give any other recipients of the Work or Derivative Works a copy
+         of this License; and
+         
+         (b) You must cause any modified files to carry prominent notices stating that
+         You changed the files; and
+         
+         (c) You must retain, in the Source form of any Derivative Works that You
+         distribute, all copyright, patent, trademark, and attribution notices from the
+         Source form of the Work, excluding those notices that do not pertain to any
+         part of the Derivative Works; and
+         
+         (d) If the Work includes a "NOTICE" text file as part of its distribution,
+         then any Derivative Works that You distribute must include a readable copy of
+         the attribution notices contained within such NOTICE file, excluding those
+         notices that do not pertain to any part of the Derivative Works, in at least
+         one of the following places: within a NOTICE text file distributed as part of
+         the Derivative Works; within the Source form or documentation, if provided
+         along with the Derivative Works; or, within a display generated by the
+         Derivative Works, if and wherever such third-party notices normally appear.
+         The contents of the NOTICE file are for informational purposes only and do not
+         modify the License. You may add Your own attribution notices within Derivative
+         Works that You distribute, alongside or as an addendum to the NOTICE text from
+         the Work, provided that such additional attribution notices cannot be
+         construed as modifying the License.
+         
+         You may add Your own copyright statement to Your modifications and may provide
+         additional or different license terms and conditions for use, reproduction, or
+         distribution of Your modifications, or for any such Derivative Works as a
+         whole, provided Your use, reproduction, and distribution of the Work otherwise
+         complies with the conditions stated in this License.
+         
+         5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+         
+         6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+         
+         7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+         
+         8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+         
+         9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
+         
+         END OF TERMS AND CONDITIONS
+         
+         -----
+         
+         apps/support/cmdline.h is Copyright (c) 2009, Hideyuki Tanaka and is licensed
+         under the BSD 3-Clause license.
+         
+         Redistribution and use in source and binary forms, with or without
+         modification, are permitted provided that the following conditions are met:
+         * Redistributions of source code must retain the above copyright
+         notice, this list of conditions and the following disclaimer.
+         * Redistributions in binary form must reproduce the above copyright
+         notice, this list of conditions and the following disclaimer in the
+         documentation and/or other materials provided with the distribution.
+         * Neither the name of the <organization> nor the
+         names of its contributors may be used to endorse or promote products
+         derived from this software without specific prior written permission.
+         
+         THIS SOFTWARE IS PROVIDED BY <copyright holder> ''AS IS'' AND ANY
+         EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+         WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+         DISCLAIMED. IN NO EVENT SHALL <copyright holder> BE LIABLE FOR ANY
+         DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+         (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+         LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+         ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+         (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+         SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+         
+         ----
+         
+         dependencies/spirv is Copyright (c) 2014-2018 The Khronos Group Inc.
+         
+         Permission is hereby granted, free of charge, to any person obtaining a copy
+         of this software and/or associated documentation files (the "Materials"),
+         to deal in the Materials without restriction, including without limitation
+         the rights to use, copy, modify, merge, publish, distribute, sublicense,
+         and/or sell copies of the Materials, and to permit persons to whom the
+         Materials are furnished to do so, subject to the following conditions:
+         
+         The above copyright notice and this permission notice shall be included in
+         all copies or substantial portions of the Materials.
+         
+         MODIFICATIONS TO THIS FILE MAY MEAN IT NO LONGER ACCURATELY REFLECTS KHRONOS
+         STANDARDS. THE UNMODIFIED, NORMATIVE VERSIONS OF KHRONOS SPECIFICATIONS AND
+         HEADER INFORMATION ARE LOCATED AT https://www.khronos.org/registry/
+         
+         THE MATERIALS ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+         OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+         FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
+         THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+         LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+         FROM,OUT OF OR IN CONNECTION WITH THE MATERIALS OR THE USE OR OTHER DEALINGS
+         IN THE MATERIALS.
+         
+         
+         ----
+         
+         dependencies/vulkan is Copyright (c) 2014-2017 The Khronos Group Inc.
+         
+         Licensed under the Apache License, Version 2.0 (the "License");
+         you may not use this file except in compliance with the License.
+         You may obtain a copy of the License at
+         
+            http://www.apache.org/licenses/LICENSE-2.0
+         
+         Unless required by applicable law or agreed to in writing, software
+         distributed under the License is distributed on an "AS IS" BASIS,
+         WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+         See the License for the specific language governing permissions and
+         limitations under the License.
+         
+         ----
+         
+         apps/linear_algebra/include/cblas.h is licensed under the BLAS license.
+         
+         The reference BLAS is a freely-available software package. It is available from
+         netlib via anonymous ftp and the World Wide Web. Thus, it can be included in
+         commercial software packages (and has been). We only ask that proper credit be
+         given to the authors.
+         
+         Like all software, it is copyrighted. It is not trademarked, but we do ask the
+         following:
+         
+         If you modify the source for these routines we ask that you change the name of
+         the routine and comment the changes made to the original.
+         
+         We will gladly answer any questions regarding the software. If a modification is
+         done, however, it is the responsibility of the person who modified the routine
+         to provide support.
+         
+         
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: GPU
+Classifier: Environment :: GPU :: NVIDIA CUDA
+Classifier: Environment :: WebAssembly
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Natural Language :: English
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: C++
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Topic :: Multimedia :: Graphics
+Classifier: Topic :: Scientific/Engineering
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Scientific/Engineering :: Image Processing
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Topic :: Software Development :: Compilers
+Classifier: Topic :: Software Development :: Libraries
+Project-URL: Homepage, https://halide-lang.org
+Project-URL: Documentation, https://github.com/halide/Halide/blob/main/doc/Python.md
+Project-URL: Documentation (C++), https://halide-lang.org/docs
+Project-URL: Issues, https://github.com/halide/Halide/issues
+Project-URL: Repository, https://github.com/halide/Halide.git
+Requires-Python: >=3.9
+Requires-Dist: imageio>=2
+Requires-Dist: numpy>=1.26
+Description-Content-Type: text/markdown
+
+Halide is a programming language designed to make it easier to write
+high-performance image and array processing code on modern machines. Halide
+currently targets:
+
+- CPU architectures: X86, ARM, Hexagon, PowerPC, RISC-V
+- Operating systems: Linux, Windows, macOS, Android, iOS, Qualcomm QuRT
+- GPU Compute APIs: CUDA, OpenCL, Apple Metal, Microsoft Direct X 12, Vulkan
+
+Rather than being a standalone programming language, Halide is embedded in
+Python. This means you write Python code that builds an in-memory representation
+of a Halide pipeline using Halide's Python API. You can then compile this
+representation to an object file, or JIT-compile it and run it in the same
+process.
+
+## Using Halide from C++
+Halide is also available as a C++ library. This package provides the development
+files necessary to use Halide from C++, including a CMake package. On Linux and
+macOS, CMake's `find_package` command should find Halide as long as you're in
+the same virtual environment you installed it in. On Windows, you will need to
+add the virtual environment root directory to `CMAKE_PREFIX_PATH`. This can be
+done by running `set CMAKE_PREFIX_PATH=%VIRTUAL_ENV%` in `cmd`.
+
+Other build systems can find the Halide root path by running `python -c 
+"import halide; print(halide.install_dir())"`.