It is useful to build the latest supported version of the driver using the
`make` command.

Signed-off-by: Alin Gabriel Serdean <aserd...@cloudbasesolutions.com>
---
 datapath-windows/automake.mk | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/datapath-windows/automake.mk b/datapath-windows/automake.mk
index b8cf5dd95..60b3d6033 100644
--- a/datapath-windows/automake.mk
+++ b/datapath-windows/automake.mk
@@ -90,3 +90,7 @@ datapath_windows_analyze: all
        MSBuild.exe //nologo //maxcpucount datapath-windows/ovsext.sln 
/target:Build /property:Configuration="Win10Analyze"
        MSBuild.exe //nologo //maxcpucount datapath-windows/ovsext.sln 
/target:Build /property:Configuration="Win8.1Analyze"
        MSBuild.exe //nologo //maxcpucount datapath-windows/ovsext.sln 
/target:Build /property:Configuration="Win8Analyze"
+
+datapath_windows: all
+       MSBuild.exe //nologo //maxcpucount datapath-windows/ovsext.sln 
/target:Build /property:Configuration="Win10Debug"
+       MSBuild.exe //nologo //maxcpucount datapath-windows/ovsext.sln 
/target:Build /property:Configuration="Win10Release"
-- 
2.27.0.windows.1

_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to