github
/
openvpn-gui
mirror of https://github.com/OpenVPN/openvpn-gui
1
0
Fork 0
Code Issues Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
672 Commits
3 Branches
112 Tags
18 MiB
Tree: 819629e2a5
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '819629e2a5'
${ noResults }
openvpn-gui/CMakePresets.json

294 lines
8.7 KiB
Raw Normal View History Unescape

Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
{
"version": 2,
"configurePresets": [
{
"name": "base",
"hidden": true,
"binaryDir": "${sourceDir}/out/build/${presetName}",
cmake: replace Ninja generator with MSVC Ninja makes build slightly faster but requires running "x64" developer command prompt, not the "default" one. Without that, cmake silenly produces x86 binaries and it might take a while to find out the reason. To avoid confusion, switch back to MSVC generator. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"generator": "Visual Studio 16 2019",
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"cacheVariables": {
"CMAKE_TOOLCHAIN_FILE": {
"value": "$env{VCPKG_ROOT}/scripts/buildsystems/vcpkg.cmake",
"type": "FILEPATH"
}
},
"vendor": { "microsoft.com/VisualStudioSettings/CMake/1.0": { "hostOS": [ "Windows" ] } }
},
{
"name": "ossl3",
"hidden": true,
"cacheVariables": {
"VCPKG_MANIFEST_DIR": "${sourceDir}/vcpkg_manifests/openssl_3"
}
},
{
"name": "ossl1.1.1",
"hidden": true,
"cacheVariables": {
"VCPKG_MANIFEST_DIR": "${sourceDir}/vcpkg_manifests/openssl_1.1.1"
}
},
{
"name": "x64",
"hidden": true,
"architecture": {
cmake: replace Ninja generator with MSVC Ninja makes build slightly faster but requires running "x64" developer command prompt, not the "default" one. Without that, cmake silenly produces x86 binaries and it might take a while to find out the reason. To avoid confusion, switch back to MSVC generator. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"value": "x64"
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
}
},
{
"name": "arm64",
"hidden": true,
"architecture": {
CMakePresets.json: use MSVC generator for ARM64 builds Sadly, CMake/Ninja combo doesn't work well for ARM64 (similar to https://stackoverflow.com/questions/47581784/building-a-x86-application-with-cmake-ninja-and-clang-on-x64-windows) - it silently produces x64 binaries instead of arm64. Switch to slower MSVC generator. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"value": "arm64"
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
}
},
{
"name": "x86",
"hidden": true,
"architecture": {
"value": "Win32"
}
},
{
"name": "debug",
"hidden": true,
"cacheVariables": {
"CMAKE_BUILD_TYPE": "Debug"
}
},
{
"name": "release",
"hidden": true,
"cacheVariables": {
"CMAKE_BUILD_TYPE": "Release"
}
},
Support for OpenVPN 3 This adds optional support for using OpenVPN3 client as an alternative to openvpn2. Just replacing one client with another will not work: - OpenVPN3 doesn't use interactive service, it uses "agent" service with completely different protocol. OpenVPN GUI needs to talk to agent using HTTP and JSON. - OpenVPN3 management interface realtime notifications must be explicitly turned on in order for GUI to work. To enable using openvpn3: - use any of *-ovpn3 presets (cmake build system) - ./configure --enable-ovpn3 (mingw) To switch betweet openvpn2 and openvpn3, see "OpenVPN Engine" radiobutton group in Settings -> Advanced dialog. OnReady() implementation was slighly changed - "log all on" replaced with "log on all" - according to management interface documentation this is the right way to do it, and also OpenVPN3 only supports "on all" order. Management interface - enabled OpenVPN3 client (omiclient.exe) and agent (ovpnagent.exe) are now part of openvpn3 repo. Co-authored-by: Christopher Ng <facboy@gmail.com> Signed-off-by: Christopher Ng <facboy@gmail.com> Signed-off-by: Lev Stipakov <lev@openvpn.net>
5 years ago
{
"name": "ovpn3",
"hidden": true,
"cacheVariables": {
"CLI_OVPN3": "ON"
}
},
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
{
"name": "x64-debug-ossl3",
"inherits": [ "base", "ossl3", "x64", "debug" ]
},
{
"name": "x64-debug-ossl1.1.1",
"inherits": [ "base", "ossl1.1.1", "x64", "debug" ]
},
{
"name": "arm64-debug-ossl3",
"inherits": [ "base", "ossl3", "arm64", "debug" ]
},
{
"name": "arm64-debug-ossl1.1.1",
"inherits": [ "base", "ossl1.1.1", "arm64", "debug" ]
},
{
"name": "x86-debug-ossl3",
"inherits": [ "base", "ossl3", "x86", "debug" ]
},
{
"name": "x86-debug-ossl1.1.1",
"inherits": [ "base", "ossl1.1.1", "x86", "debug" ]
},
{
"name": "x64-release-ossl3",
"inherits": [ "base", "ossl3", "x64", "release" ]
},
{
"name": "x64-release-ossl1.1.1",
"inherits": [ "base", "ossl1.1.1", "x64", "release" ]
},
{
"name": "arm64-release-ossl3",
"inherits": [ "base", "ossl3", "arm64", "release" ]
},
{
"name": "arm64-release-ossl1.1.1",
"inherits": [ "base", "ossl1.1.1", "arm64", "release" ]
},
{
"name": "x86-release-ossl3",
"inherits": [ "base", "ossl3", "x86", "release" ]
},
{
"name": "x86-release-ossl1.1.1",
"inherits": [ "base", "ossl1.1.1", "x86", "release" ]
Support for OpenVPN 3 This adds optional support for using OpenVPN3 client as an alternative to openvpn2. Just replacing one client with another will not work: - OpenVPN3 doesn't use interactive service, it uses "agent" service with completely different protocol. OpenVPN GUI needs to talk to agent using HTTP and JSON. - OpenVPN3 management interface realtime notifications must be explicitly turned on in order for GUI to work. To enable using openvpn3: - use any of *-ovpn3 presets (cmake build system) - ./configure --enable-ovpn3 (mingw) To switch betweet openvpn2 and openvpn3, see "OpenVPN Engine" radiobutton group in Settings -> Advanced dialog. OnReady() implementation was slighly changed - "log all on" replaced with "log on all" - according to management interface documentation this is the right way to do it, and also OpenVPN3 only supports "on all" order. Management interface - enabled OpenVPN3 client (omiclient.exe) and agent (ovpnagent.exe) are now part of openvpn3 repo. Co-authored-by: Christopher Ng <facboy@gmail.com> Signed-off-by: Christopher Ng <facboy@gmail.com> Signed-off-by: Lev Stipakov <lev@openvpn.net>
5 years ago
},
{
"name": "x64-debug-ossl3-ovpn3",
"inherits": [ "x64-debug-ossl3", "ovpn3" ]
},
{
"name": "x64-debug-ossl1.1.1-ovpn3",
"inherits": [ "x64-debug-ossl1.1.1", "ovpn3" ]
},
{
"name": "arm64-debug-ossl3-ovpn3",
"inherits": [ "arm64-debug-ossl3", "ovpn3" ]
},
{
"name": "arm64-debug-ossl1.1.1-ovpn3",
"inherits": [ "arm64-debug-ossl1.1.1", "ovpn3" ]
},
{
"name": "x86-debug-ossl3-ovpn3",
"inherits": [ "x86-debug-ossl3", "ovpn3" ]
},
{
"name": "x86-debug-ossl1.1.1-ovpn3",
"inherits": [ "x86-debug-ossl1.1.1", "ovpn3" ]
},
{
"name": "x64-release-ossl3-ovpn3",
"inherits": [ "x64-release-ossl3", "ovpn3" ]
},
{
"name": "x64-release-ossl1.1.1-ovpn3",
"inherits": [ "x64-release-ossl1.1.1", "ovpn3" ]
},
{
"name": "arm64-release-ossl3-ovpn3",
"inherits": [ "arm64-release-ossl3", "ovpn3" ]
},
{
"name": "arm64-release-ossl1.1.1-ovpn3",
"inherits": [ "arm64-release-ossl1.1.1", "ovpn3" ]
},
{
"name": "x86-release-ossl3-ovpn3",
"inherits": [ "x86-release-ossl3", "ovpn3" ]
},
{
"name": "x86-release-ossl1.1.1-ovpn3",
"inherits": [ "x86-release-ossl1.1.1", "ovpn3" ]
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
}
],
"buildPresets": [
{
"name": "x64-release-ossl3",
cmake: replace Ninja generator with MSVC Ninja makes build slightly faster but requires running "x64" developer command prompt, not the "default" one. Without that, cmake silenly produces x86 binaries and it might take a while to find out the reason. To avoid confusion, switch back to MSVC generator. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"configurePreset": "x64-release-ossl3",
"configuration": "Release"
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
},
{
"name": "x64-release-ossl1.1.1",
cmake: replace Ninja generator with MSVC Ninja makes build slightly faster but requires running "x64" developer command prompt, not the "default" one. Without that, cmake silenly produces x86 binaries and it might take a while to find out the reason. To avoid confusion, switch back to MSVC generator. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"configurePreset": "x64-release-ossl1.1.1",
"configuration": "Release"
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
},
{
"name": "x86-release-ossl3",
"configurePreset": "x86-release-ossl3",
"configuration": "Release"
},
{
"name": "x86-release-ossl1.1.1",
"configurePreset": "x86-release-ossl1.1.1",
"configuration": "Release"
},
{
"name": "arm64-release-ossl3",
CMakePresets: fix arm64 debug/release config Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"configurePreset": "arm64-release-ossl3",
"configuration": "Release"
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
},
{
"name": "arm64-release-ossl1.1.1",
CMakePresets: fix arm64 debug/release config Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"configurePreset": "arm64-release-ossl1.1.1",
"configuration": "Release"
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
},
{
"name": "x64-debug-ossl3",
cmake: replace Ninja generator with MSVC Ninja makes build slightly faster but requires running "x64" developer command prompt, not the "default" one. Without that, cmake silenly produces x86 binaries and it might take a while to find out the reason. To avoid confusion, switch back to MSVC generator. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"configurePreset": "x64-debug-ossl3",
"configuration": "Debug"
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
},
{
"name": "x64-debug-ossl1.1.1",
cmake: replace Ninja generator with MSVC Ninja makes build slightly faster but requires running "x64" developer command prompt, not the "default" one. Without that, cmake silenly produces x86 binaries and it might take a while to find out the reason. To avoid confusion, switch back to MSVC generator. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"configurePreset": "x64-debug-ossl1.1.1",
"configuration": "Debug"
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
},
{
"name": "x86-debug-ossl3",
"configurePreset": "x86-debug-ossl3",
"configuration": "Debug"
},
{
"name": "x86-debug-ossl1.1.1",
"configurePreset": "x86-debug-ossl1.1.1",
"configuration": "Debug"
},
{
"name": "arm64-debug-ossl3",
CMakePresets: fix arm64 debug/release config Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"configurePreset": "arm64-debug-ossl3",
"configuration": "Debug"
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
},
{
"name": "arm64-debug-ossl1.1.1",
CMakePresets: fix arm64 debug/release config Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
"configurePreset": "arm64-debug-ossl1.1.1",
"configuration": "Debug"
Support for OpenVPN 3 This adds optional support for using OpenVPN3 client as an alternative to openvpn2. Just replacing one client with another will not work: - OpenVPN3 doesn't use interactive service, it uses "agent" service with completely different protocol. OpenVPN GUI needs to talk to agent using HTTP and JSON. - OpenVPN3 management interface realtime notifications must be explicitly turned on in order for GUI to work. To enable using openvpn3: - use any of *-ovpn3 presets (cmake build system) - ./configure --enable-ovpn3 (mingw) To switch betweet openvpn2 and openvpn3, see "OpenVPN Engine" radiobutton group in Settings -> Advanced dialog. OnReady() implementation was slighly changed - "log all on" replaced with "log on all" - according to management interface documentation this is the right way to do it, and also OpenVPN3 only supports "on all" order. Management interface - enabled OpenVPN3 client (omiclient.exe) and agent (ovpnagent.exe) are now part of openvpn3 repo. Co-authored-by: Christopher Ng <facboy@gmail.com> Signed-off-by: Christopher Ng <facboy@gmail.com> Signed-off-by: Lev Stipakov <lev@openvpn.net>
5 years ago
},
{
"name": "x64-release-ossl3-ovpn3",
"configurePreset": "x64-release-ossl3-ovpn3",
"configuration": "Release"
},
{
"name": "x64-release-ossl1.1.1-ovpn3",
"configurePreset": "x64-release-ossl1.1.1-ovpn3",
"configuration": "Release"
},
{
"name": "x86-release-ossl3-ovpn3",
"configurePreset": "x86-release-ossl3-ovpn3",
"configuration": "Release"
},
{
"name": "x86-release-ossl1.1.1-ovpn3",
"configurePreset": "x86-release-ossl1.1.1-ovpn3",
"configuration": "Release"
},
{
"name": "arm64-release-ossl3-ovpn3",
"configurePreset": "arm64-release-ossl3-ovpn3",
"configuration": "Release"
},
{
"name": "arm64-release-ossl1.1.1-ovpn3",
"configurePreset": "arm64-release-ossl1.1.1-ovpn3",
"configuration": "Release"
},
{
"name": "x64-debug-ossl3-ovpn3",
"configurePreset": "x64-debug-ossl3-ovpn3",
"configuration": "Debug"
},
{
"name": "x64-debug-ossl1.1.1-ovpn3",
"configurePreset": "x64-debug-ossl1.1.1-ovpn3",
"configuration": "Debug"
},
{
"name": "x86-debug-ossl3-ovpn3",
"configurePreset": "x86-debug-ossl3-ovpn3",
"configuration": "Debug"
},
{
"name": "x86-debug-ossl1.1.1-ovpn3",
"configurePreset": "x86-debug-ossl1.1.1-ovpn3",
"configuration": "Debug"
},
{
"name": "arm64-debug-ossl3-ovpn3",
"configurePreset": "arm64-debug-ossl3-ovpn3",
"configuration": "Debug"
},
{
"name": "arm64-debug-ossl1.1.1-ovpn3",
"configurePreset": "arm64-debug-ossl1.1.1-ovpn3",
"configuration": "Debug"
Use vcpkg manifest and cmake presets Manifest is a convenient way to automatically install dependencies. Since we have to support both OpenSSL 1.1.1 (for OpenVPN 2.5) and OpenSSL 3 (for coming OpenVPN 2.6) and manifest file name is hardcoded, we create two manifests and put them into different directories. To simplify build process, define configuration presets for arch (x86/x64/arm64), debug/release and oss1.1.1/ossl3. This way building is greatly simplified: cmake -S . --preset x64-debug-ossl3 cmake --build --preset x64-debug-ossl3 Update GitHub Actions script accordingly. Signed-off-by: Lev Stipakov <lev@openvpn.net>
3 years ago
}
]
}