* [build.ps1] do not export vcpkg_root anymore
* [README.md] add a build step related to Set-ExecutionPolicy on Windows
* use scope currentuser to avoid admin powershell
* simplify even more set-executionpolicy command order
* remove unnecessary decoration to shell commands to improve user experience with copy button
* write instructions to build using only cmake
* Update README.md
* add target install
* improve setup scripts for future tests
* improve setup.sh script for more tool installations and add command line flags handling
* add CI tests for setup scripts
* use nuget artifact cache to improve CI build times
* disable interactivity for build script when called from setup script, add kitware gpg key in CI
* enable cudnn in setup.sh
* add a workaround for missing nvidia drivers in CI
* setup CUDA env variables
* remove some very slow builds from travis and move them to github actions
* chmod sh scripts
* use deploy-cuda scripts also in PR pipelines
* install asm tools
* restore links missing for CI when using deploy-cuda.sh
* enable cudnn on ubuntu ci pipelines
* pass CUDA env variables
* add missing cuda install for opencv2 and opencv3 ci pipelines
* remove unnecessary steps
Co-authored-by: Alexey <AlexeyAB@users.noreply.github.com>
* [build.ps1] use x64 also on developer powershell for VS
* improve handling of errors on windows platform
* [build.ps1] bump version
* improve logic handling in uselib_track
* self download ninja if not found on system and not requested to opt-out
* add a flag to clean up vcpkg local binary cache to force restart from scratch
* really delete if requested
* add support for powershell v5
* revert opencv enabled on osx
* improve error handling in initial stages
* intercept failures also when updating darknet sources themselves
* press a key before exiting script, to preserve console host window if not running in a shell
* check path length
* fix: frame delay
when use low performance device such as raspberry pi or jetson nano execute darknet demo, the streaming will be delayed more and more
* fix: operate only in live stream
Co-authored-by: Double.c <double.c@inwinstack.com>
Cublas success is indicated by CUBLAS_STATUS_SUCCESS. This must be used
to determine if a cublas function call was successful.
Although Cuda does not complain if we use cudaError_t, when bulding with
ROCm support it is absolutely necessary to use the correct enum
(cublasStatus_t), else ROCm will always interpret the returned
status as an error and crash.