pip install error on windows

[StenniHub]

I keep getting an error that is preventing me from installing vedadet on a windows system. I have created a conda environment and installed the build dependencies + pytorch 1.10 and cuda 10.2 (also tried cuda 11). Also installed ninja through pip and setup visual studio build tools. When the setup reaches build_ext I just get the following error:

Installing collected packages: vedadet
Running setup.py develop for vedadet
Running command 'C:\Users\Fredr\miniconda3\envs\vedadet\python.exe' -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'D:\dev\vedadet\setup.py'"'"'; file='"'"'D:\dev\vedadet\setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' develop --no-deps
running develop
running egg_info
writing vedadet.egg-info\PKG-INFO
writing dependency_links to vedadet.egg-info\dependency_links.txt
writing requirements to vedadet.egg-info\requires.txt
writing top-level names to vedadet.egg-info\top_level.txt
reading manifest file 'vedadet.egg-info\SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'vedadet.egg-info\SOURCES.txt'
running build_ext
error: [WinError 2] The system cannot find the file specified
ERROR: Command errored out with exit status 1: 'C:\Users\Fredr\miniconda3\envs\vedadet\python.exe' -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'D:\dev\vedadet\setup.py'"'"'; file='"'"'D:\dev\vedadet\setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' develop --no-deps Check the logs for full command output.

--verbose unfortunately did not add any useful information. If it thinks it's the setup.py file that it cannot find, then I don't know why that would be because the absolute path looks correct. Have attempted to install both on python 3.9 and python 3.8.