Add unittest jobs for standalone Asio builds

Add a separate job definition for building and testing the code with
standalone Asio. The jobs differ enough that it seems to make most
sense to keep them completely separated.

.github/workflows/unittest.yml

@@ -3,7 +3,7 @@ name: unittest
 on: [push, pull_request]
 
 jobs:
- unittest:
+ unittest-boost-asio:
  name: "${{matrix.generator}} ${{matrix.toolset}} Boost ${{matrix.boost_version}} ${{matrix.build_type}} C++${{matrix.standard}} ${{matrix.name_args}}"
  runs-on: ${{matrix.os}}
  defaults:
@@ -139,3 +139,49 @@ jobs:
  - name: Setup tmate session
  if: ${{ failure() }}
  uses: mxschmitt/action-tmate@v3
+
+ unittest-standalone-asio:
+ name: "Asio ${{matrix.build_type}} C++${{matrix.standard}}"
+ runs-on: ${{matrix.os}}
+ defaults:
+ run:
+ shell: bash
+ strategy:
+ fail-fast: false
+ matrix:
+ os: [windows-2022]
+ build_type: [Debug, Release]
+ standard: [14, 17, 20]
+
+ steps:
+ - name: Checkout
+ uses: actions/checkout@v3
+ with:
+ fetch-depth: 0
+
+ - name: Create build directory
+ run: mkdir build
+
+ - name: Configure
+ working-directory: build
+ run: |
+ cmake -DCMAKE_CXX_STANDARD=${{matrix.standard}} \
+ -DENABLE_WINTLS_STANDALONE_ASIO=ON \
+ "${GITHUB_WORKSPACE}"
+
+ - name: Build
+ working-directory: build
+ run: |
+ cmake --build . \
+ -j \
+ --config ${{matrix.build_type}}
+
+ - name: Run tests
+ working-directory: build
+ run: ctest -C ${{matrix.build_type}}
+ env:
+ CTEST_OUTPUT_ON_FAILURE: True
+
+ - name: Setup tmate session
+ if: ${{ failure() }}
+ uses: mxschmitt/action-tmate@v3