Skip to content

So what happens if we actually install our own OpenSSL and use that? #62

So what happens if we actually install our own OpenSSL and use that?

So what happens if we actually install our own OpenSSL and use that? #62

Workflow file for this run

on: [push]
name: Test
jobs:
test:
name: Build and test driver on windows-2022
runs-on: windows-2019
env:
CASS_DRIVER_LIBEV_INCLUDES: C:\vcpkg\packages\libev_x64-windows\include\libev
CASS_DRIVER_LIBEV_LIBS: C:\vcpkg\packages\libev_x64-windows\lib
LIBUV_ROOT_DIR: C:\vcpkg\packages\libuv_x64-windows
ZLIB_ROOT_DIR: C:\vcpkg\packages\zlib_x64-windows-static
KERBEROS_ROOT_DIR: C:\vcpkg\packages\krb5_x64-windows
OPENSSL_ROOT_DIR: C:\vcpkg\packages\openssl_x64-windows
steps:
- uses: actions/checkout@v4
- uses: ilammy/msvc-dev-cmd@v1
- name: Install dependencies
run: vcpkg install libuv zlib:x64-windows-static krb5 openssl
- name: Setup env vars
run: |
echo "LIBUV_BIN_DIR=${{ env.LIBUV_ROOT_DIR }}\bin" >> $env:GITHUB_ENV
echo "KERBEROS_BIN_DIR=${{ env.KERBEROS_ROOT_DIR }}\bin" >> $env:GITHUB_ENV
echo "OPENSSL_BIN_DIR=${{ env.OPENSSL_ROOT_DIR }}\bin" >> $env:GITHUB_ENV
- name: Setup env
run: |
ln -s C:\vcpkg\packages\zlib_x64-windows-static\lib\zlib.lib C:\vcpkg\packages\zlib_x64-windows-static\lib\zlibstatic.lib
echo "PATH=${{ env.PATH }};${{ env.LIBUV_BIN_DIR }};${{ env.KERBEROS_BIN_DIR }};${{ env.OPENSSL_BIN_DIR }}" >> $env:GITHUB_ENV
- name: Debug stuff
run: |
echo "PATH is ${{ env.PATH }}"
echo "LIBUV_BIN_DIR contents:"
ls ${{ env.LIBUV_BIN_DIR }}
echo "KERBEROS_BIN_DIR contents:"
ls ${{ env.KERBEROS_BIN_DIR }}
- name: Build and run tests
run: |
mkdir build
cd build
cmake -G "NMake Makefiles" -DCASS_BUILD_UNIT_TESTS=On ..
nmake
ls .
ldd ./cassandra-unit-tests.exe
./cassandra-unit-tests.exe --gtest_output=xml:gtest-results.xml
ls .
- name: Publish test results
uses: mikepenz/action-junit-report@v4
if: success() || failure()
with:
report_paths: build\gtest-results.xml