如何在Visual Studio 2019中配置OpenCV？求无需重复配置的方法

Hey there! I totally get the frustration of reconfiguring OpenCV every time you spin up a new project in Visual Studio 2019. Let’s go through three reliable solutions to eliminate that repetitive work for good:

This is the most flexible and widely recommended method—you’ll build a single configuration file that you can import into any new project in 2 clicks.

• Open your already-configured OpenCV project in VS2019, then go to View > Property Manager (if you don’t see it, search for "Property Manager" in the top search bar).
• In the Property Manager window, expand your project’s node, right-click on the platform you use (e.g., Debug|x64), and select Add New Project Property Sheet.
• Name it something descriptive like OpenCV_Debug_x64.props, save it in a permanent folder (maybe a dedicated "VS Property Sheets" directory so you don’t lose it).
• Right-click the new .props file and select Properties. Replicate all your OpenCV settings here:
  • Under VC++ Directories, paste the same Include Directories and Library Directories you used before.
  • Under Linker > Input, add the appropriate library names (e.g., opencv_world455d.lib for Debug builds).
  • Repeat this process for Release mode if needed, creating a separate OpenCV_Release_x64.props file with the release libraries (like opencv_world455.lib).
• For any new project:
  • Open the Property Manager, right-click your target platform, select Add Existing Property Sheet, and pick your pre-made OpenCV property sheet. All configurations are imported instantly.

If you want every new project of a specific type (like Console Apps) to automatically have OpenCV configured, tweak the default VS template:

• First, find the template directory. For VS2019 Community, it’s usually:
  C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\ProjectTemplates\VC\Windows\Windows Console Application\1033
  (Adjust the path for Professional/Enterprise editions or other project types like Windows Desktop Application.)
• Make a backup of this folder first—you don’t want to break the default template if something goes wrong.
• Open the .vcxproj file inside the folder with a text editor (Notepad++ works great).
• Add your OpenCV configurations directly into the project file:
  1. Add a user macro group to define your OpenCV path (replace with your actual path):

     <PropertyGroup Label="UserMacros">
       <OpenCVRoot>C:\opencv\build</OpenCVRoot>
     </PropertyGroup>
     

  2. Find the <ItemDefinitionGroup> sections for Debug and Release, and add these lines inside each:
     For <ClCompile>:

     <AdditionalIncludeDirectories>$(OpenCVRoot)\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
     

     For <Link>:

     <AdditionalLibraryDirectories>$(OpenCVRoot)\x64\vc16\lib;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
     <AdditionalDependencies>opencv_world455d.lib;%(AdditionalDependencies)</AdditionalDependencies>
     

     (Swap opencv_world455d.lib with the release library for the Release section.)
• Save the file, restart VS2019, and any new project from this template will have OpenCV pre-set up.

If you prefer a zero-manual-config approach, let NuGet handle all the heavy lifting:

• Create a new project, right-click it in Solution Explorer, and select Manage NuGet Packages.
• Go to the Browse tab, search for opencv, and install the official package from the "OpenCV Team".
• The package will automatically configure include directories, linker inputs, and even copy the necessary DLLs to your output directory (you might still need the OpenCV bin path in your system environment variables for runtime, but some versions handle this too).
• That’s it—you can start writing OpenCV code immediately without any manual setup.

Quick Notes #

• If you use multiple OpenCV versions, ensure your property sheet/template points to the correct installation path.
• For property sheets, using separate files for Debug/Release avoids accidental mix-ups of debug and release libraries.
• When modifying templates, double-check the XML syntax—small typos can break the template.

内容的提问来源于stack exchange，提问作者sina ghadiri alamdari