3 Commits

Author SHA1 Message Date
Jacob Kahn
c77aad3919
[arrayfire] Remove forge and graphics deps from port (#15027) 2020-12-12 15:35:03 -08:00
Jacob Kahn
2835810bfa
[arrayfire] Update port to fix cuSparse issue with CUDA 10.1 (#14911) 2020-12-04 16:47:00 -08:00
Jacob Kahn
4297ade917
[arrayfire] New Port (#14240)
* [arrayfire] New Port

* Format manifest file

* Remove nvidia cub, forge, and spdlog submodules and use vcpkg ports - add patch

* Remove arrayfire/assets and don't build examples

* Remove arrayfire/glad submodule, use port, update patch

* Add optional freeimage dependency for graphics lib

* Remove rename of arrayfire threads/pass path to build

* Update ports/arrayfire/portfile.cmake

Co-authored-by: Phoebe <20694052+PhoebeHui@users.noreply.github.com>

* Fix up cmake targets files, install bin/dlls to the proper location

* Use debug bin dir if in debug mode

* Fixes for unified, Windows dlls, and more
- Make the unified backend its own feature
- Make the unified and CPU backend default features
- Conditionally create a bin directory if a Windows non-static build for the unified dll
- Remove fftw dependency (relies on MKL)
- Only support x64

* Add warning for Windows static builds

* Ensure CMake assets are in the proper dir for non-Windows builds

* Actually, don't change cmake targets in non-Windows systems

* Remove port-version

* Use MKL for CPU and OpenCL backends

* Patch arrayfire/threads - fix duplicate include

* Use newer af/threads, replace include path to fix Windows builds

* Fix binary dir for output DLLs

* Update select_compute_arch to work with CUDA 11

* Don't include CUB if using CUDA >= 11

* Bump port verison to 3.7.3 to handle CUDA 11+

* Update port to use 3.7.3

* Update to include MSVC 2019 fixes, fixup CMake targets on *nix

* Apply suggestions from code review

* Update ports/arrayfire/portfile.cmake

* Change AF CMake dir since targets.cmake are included by other targets

* Bump to commit with fixed AF version for bits

The v3.7 branch tip was still outputting shared objects with 3.7.2 versions attached to them. It's now fixed

Co-authored-by: Phoebe <20694052+PhoebeHui@users.noreply.github.com>
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
2020-11-19 10:50:38 -08:00