Ansible
PS DSC
Downloads:
1,514
Downloads of v 4.9.0.20240121:
122
Last Update:
11 Feb 2024
Package Maintainer(s):
Software Author(s):
- OpenCV team
Tags:
opencv image processing programming library c++ cpp- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Development files for OpenCV
This is not the latest version of Development files for OpenCV available.
- 1
- 2
- 3
4.9.0.20240121 | Updated: 11 Feb 2024
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
1,514
Downloads of v 4.9.0.20240121:
122
Maintainer(s):
Software Author(s):
- OpenCV team
Development files for OpenCV 4.9.0.20240121
This is not the latest version of Development files for OpenCV available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by OpenCV team. The inclusion of OpenCV team trademark(s), if any, upon this webpage is solely to identify OpenCV team goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Are Exempted or Have Failed
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Development files for OpenCV, run the following command from the command line or from PowerShell:
>
To upgrade Development files for OpenCV, run the following command from the command line or from PowerShell:
>
To uninstall Development files for OpenCV, run the following command from the command line or from PowerShell:
>
Deployment Method:
NOTE
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download libopencv-dev --internalize --version=4.9.0.20240121 --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade libopencv-dev -y --source="'INTERNAL REPO URL'" --version="'4.9.0.20240121'" [other options]See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade libopencv-dev -y --source="'INTERNAL REPO URL'" --version="'4.9.0.20240121'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install libopencv-dev
win_chocolatey:
name: libopencv-dev
version: '4.9.0.20240121'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'libopencv-dev' do
action :install
source 'INTERNAL REPO URL'
version '4.9.0.20240121'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller libopencv-dev
{
Name = "libopencv-dev"
Version = "4.9.0.20240121"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'libopencv-dev':
ensure => '4.9.0.20240121',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
Package Approved
This package was approved by moderator flcdrg on 21 Jul 2024.
Description
OpenCV development defaults package.
Package info
- The purpose of this package is to be more or less the equivalent of https://packages.ubuntu.com/noble/libopencv-dev. The MinGW/GCC version is chosen as the current one available on GitHub Actions hosted runners. Note that the existing https://community.chocolatey.org/packages/OpenCV official package does not provide binaries for MinGW/GCC.
Quick start
- After installing Chocolatey, run
choco install -y libopencv-dev cmake.install --installargs 'ADD_CMAKE_TO_PATH=System'in PowerShell, reboot and then get the folder from https://www.ensta-bretagne.fr/lebars/Share/ImageOpenCV454_Ubuntu22.04.zip and inside, trycmake -G "MinGW Makefiles" ., thencmake --build ., then.\ImageOpenCV.exein a new PowerShell window and check that an image appears in a window.
Troubleshooting
- Check that all the packages and their dependencies were installed, if one failed (e.g. due to network-related errors) try to reinstall it using
--forceor try a previous version...
Package parameters
The following package parameters can be set:
/url:URL- Will install the specified self-extracting OpenCV package, see e.g. versions from https://github.com/lebarsfa/Packages/releases (the WindowsPATHmight need to be updated manually with e.g.C:\OpenCV4.9.0\x86\vc15\bin, you might need to set manually CMake variablesOpenCV_ARCHe.g. tox86,OpenCV_RUNTIMEe.g. tovc15,OpenCV_STATICe.g. toON, rename folders e.g. fromC:\OpenCV4.9.0\x86\mingwtoC:\OpenCV4.9.0\x86\mingw7, etc.). By default, only the MinGW libraries compatible with the corresponding MinGW Chocolatey package dependency are installed. Use the standard parameterchoco install --ignore-dependencies ...to avoid installing MinGW Chocolatey package dependency if needed./checksum:SHA256- SHA256 checksum of the self-extracting OpenCV package specified by the/urlparameter. If needed, use the standard parameterchoco install --ignore-checksums ...for trusted sources./urlX:URL- Same as above, with X in [1,99], except this will not disable the installation of the MinGW libraries compatible with the corresponding MinGW Chocolatey package dependency./checksumX:SHA256- SHA256 checksum of the self-extracting OpenCV package specified by the/urlXparameter. If needed, use the standard parameterchoco install --ignore-checksums ...for trusted sources./InstallDir:INSTALLDIR- Installation directory./NoPath- Will not try to update WindowsPATH./NoRegistry- Will not try to update Windows registry./32and64- Will install both 32 and 64 bit versions of the default MinGW libraries.
To pass package parameters, use--params "''"(e.g.choco install libopencv-dev --params "'/NoPath /32and64'"), and to install multiple self-extracting OpenCV packages together (if they are not mutually exclusive due to other reasons), try e.g.
choco install -y chocolatey-core.extension
choco install -y --ignore-dependencies libopencv-dev --params "'/url:https://github.com/lebarsfa/Packages/releases/download/libopencv-dev.4.9.0.20240121/libopencv-dev.4.9.0_x64_vc17_staticlib_Debug.exe /url1:https://github.com/lebarsfa/Packages/releases/download/libopencv-dev.4.9.0.20240121/libopencv-dev.4.9.0_x64_vc17_lib_Debug.exe /url2:https://github.com/lebarsfa/Packages/releases/download/libopencv-dev.4.9.0.20240121/libopencv-dev.4.9.0_x64_vc17_staticlib_Release.exe /url3:https://github.com/lebarsfa/Packages/releases/download/libopencv-dev.4.9.0.20240121/libopencv-dev.4.9.0_x64_vc17_lib_Release.exe'"
Files
tools\chocolateybeforemodify.ps1
$ErrorActionPreference = 'Stop'; # Stop on all errors.
# Source variables which are shared between install and uninstall.
. $PSScriptRoot\sharedVars.ps1
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$pp = Get-PackageParameters
$packageDir = Join-Path "$toolsDir" ".." -Resolve
$installDir = $env:SystemDrive
if ($pp.InstallDir -or $pp.InstallationPath) {
$installDir = $pp.InstallDir + $pp.InstallationPath
}
Write-Host "$CMakePackageName$CMakePackageVer is going to be uninstalled from '$installDir'"
$root = Join-Path $installDir "$CMakePackageName$CMakePackageVer"
$newpath = [environment]::GetEnvironmentVariable("Path","Machine")
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\mingw\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\mingw\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc8\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc8\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc9\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc9\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc10\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc10\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc11\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc11\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc12\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc12\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc14\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc14\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc15\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc15\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc16\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc16\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc17\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc17\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc18\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc18\bin" }) -join ';'
[environment]::SetEnvironmentVariable("Path",$newpath,"Machine")
try {
Get-ItemProperty -Path $CMakeSystemRepositoryPath\$CMakePackageName | Select-Object -ExpandProperty $CMakePackageName$CMakePackageVer -ErrorAction Stop | Out-Null
Remove-ItemProperty -Path $CMakeSystemRepositoryPath\$CMakePackageName -Name $CMakePackageName$CMakePackageVer
}
catch {
}
if (Test-Path $root) {
if ((Resolve-Path $root).Path -notcontains (Resolve-Path $packageDir).Path) {
Remove-Item -Recurse -Force $root
}
}
tools\chocolateyinstall.ps1
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop'; # Stop on all errors.
# Source variables which are shared between install and uninstall.
. $PSScriptRoot\sharedVars.ps1
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$pp = Get-PackageParameters
$packageDir = Join-Path "$toolsDir" ".." -Resolve
$installDir = $env:SystemDrive
if ($pp.InstallDir -or $pp.InstallationPath) {
$installDir = $pp.InstallDir + $pp.InstallationPath
}
Write-Host "$CMakePackageName$CMakePackageVer is going to be uninstalled from '$installDir'"
$root = Join-Path $installDir "$CMakePackageName$CMakePackageVer"
$newpath = [environment]::GetEnvironmentVariable("Path","Machine")
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\mingw\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\mingw\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc8\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc8\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc9\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc9\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc10\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc10\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc11\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc11\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc12\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc12\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc14\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc14\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc15\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc15\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc16\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc16\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc17\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc17\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x86\vc18\bin" }) -join ';'
$newpath = ($newpath.Split(';') | Where-Object { $_ -ne "$root\x64\vc18\bin" }) -join ';'
[environment]::SetEnvironmentVariable("Path",$newpath,"Machine")
try {
Get-ItemProperty -Path $CMakeSystemRepositoryPath\$CMakePackageName | Select-Object -ExpandProperty $CMakePackageName$CMakePackageVer -ErrorAction Stop | Out-Null
Remove-ItemProperty -Path $CMakeSystemRepositoryPath\$CMakePackageName -Name $CMakePackageName$CMakePackageVer
}
catch {
}
if (Test-Path $root) {
if ((Resolve-Path $root).Path -notcontains (Resolve-Path $packageDir).Path) {
Remove-Item -Recurse -Force $root
}
}
tools\sharedVars.ps1
# Some of these variables might not be used in links to simplify parsing of files...
if ((Get-ProcessorBits 32) -or $env:ChocolateyForceX86 -eq $true) { $arch = "x86" } else { $arch = "x64" }
$MinGWMVer = "11"
$CMakeRegistryPath = "HKCU:\SOFTWARE\Kitware\CMake"
$CMakeSystemRepositoryPath = "HKLM:\SOFTWARE\Kitware\CMake\Packages"
$CMakePackageName = "OpenCV"
$CMakePackageVer = "4.9.0"
Virus Scan Results
Log in or click on link to see number of positives.
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Version History
| Add to Builder | Version | Downloads | Last Updated | Status |
|---|---|---|---|---|
| Development files for OpenCV 4.10.0.20240808 | 55 | Thursday, August 8, 2024 | Approved | |
| Development files for OpenCV 4.10.0 | 23 | Friday, August 9, 2024 | Exempted | |
| Development files for OpenCV 4.9.0.20240808 | 24 | Wednesday, August 7, 2024 | Exempted | |
| Development files for OpenCV 4.9.0.20240121 | 122 | Sunday, February 11, 2024 | Approved | |
| Development files for OpenCV 4.9.0 | 173 | Sunday, January 21, 2024 | Approved | |
| Development files for OpenCV 4.6.0.20240808 | 19 | Thursday, August 8, 2024 | Exempted | |
| Development files for OpenCV 4.6.0.20230510 | 32 | Sunday, February 11, 2024 | Approved | |
| Development files for OpenCV 4.6.0 | 214 | Sunday, May 28, 2023 | Approved | |
| Development files for OpenCV 4.5.4.20240807 | 40 | Monday, August 19, 2024 | Exempted | |
| Development files for OpenCV 4.5.4.20240203 | 26 | Sunday, February 11, 2024 | Exempted | |
| Development files for OpenCV 4.5.4.20230429 | 295 | Saturday, April 29, 2023 | Approved | |
| Development files for OpenCV 4.5.4.20230225 | 132 | Saturday, February 25, 2023 | Exempted | |
| Development files for OpenCV 4.5.4 | 160 | Wednesday, November 23, 2022 | Exempted | |
| Development files for OpenCV 4.2.0.20230429 | 38 | Sunday, May 28, 2023 | Approved | |
| Development files for OpenCV 4.2.0 | 161 | Monday, November 21, 2022 | Exempted |
Dependencies
-
- chocolatey-core.extension (≥ 1.1.0)
- mingw (= 11.2.0.07112021)
Discussion for the Development files for OpenCV Package
Ground Rules:
- This discussion is only about Development files for OpenCV and the Development files for OpenCV package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Development files for OpenCV, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.