From c95f74a88b32f9822fc33e1964f71716d7caac8c Mon Sep 17 00:00:00 2001
From: AlexYue <yj976240184@qq.com>
Date: Fri, 17 May 2024 01:52:55 +0800
Subject: [PATCH] it should be one cmake command instead of vcpkg command
 (#5622)

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 30334406f..8fbe1a573 100644
--- a/README.md
+++ b/README.md
@@ -268,7 +268,7 @@ vcpkg install --overlay-ports=<path to the vcpkg-custom-ports above>
 If you are building using CMAKE, you can instruct CMAKE to apply the overlay ports using the following command line switches:
 
 ```sh
-vcpkg -DVCPKG_MANIFEST_MODE=ON -DVCPKG_OVERLAY_PORTS=<path to the vcpkg-custom-ports above> -DVCPKG_MANIFEST_DIR=<path to the directory containing the vcpkg.json file>
+cmake -DVCPKG_MANIFEST_MODE=ON -DVCPKG_OVERLAY_PORTS=<path to the vcpkg-custom-ports above> -DVCPKG_MANIFEST_DIR=<path to the directory containing the vcpkg.json file>
 ```
 
 In addition, if you need to consume OpenSSL from a dynamic linked library/shared object, you can set the VCPKG triplet to reflect that you want to build the library with dynamic entries. Set the VCPKG_you can set the environment variable to `x64-windows-static` or `x64-windows-dynamic` depending on whether you want to use the static or dynamic version of OpenSSL.