From 104ac75cb0df0112a54bff1d385bf908410fe527 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kjell=20Hedstr=C3=B6m?= Date: Tue, 27 Aug 2024 21:44:37 -0600 Subject: [PATCH 1/4] Update README.md --- README.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/README.md b/README.md index c0cc0673..467733a4 100644 --- a/README.md +++ b/README.md @@ -109,13 +109,7 @@ You can find it here: https://kjellkod.wordpress.com/2015/06/30/the-worlds-faste ## Continuous Integration The g3log repository is evaluating both github actions and CircleCI for executing test coverage, installation and document generation. For windows the repo is still relying on appveyor. In case you want to look into change any of these setups the following files are the ones of interest. -``` -1. appveyor --> g3log/appveyor.yml -2. circleCI --> g3log/.circleci/config.yml -3. github actions --> g3log/.github/workflows/*.yml - - -``` +See `Actions` for matrix (ubuntu, macos, windows) testing as well as other actions for doc publishing. ## Feedback From df883fdff0de606949b78dad30849f5b9fd0b1a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kjell=20Hedstr=C3=B6m?= Date: Tue, 27 Aug 2024 21:46:23 -0600 Subject: [PATCH 2/4] Delete appveyor.yml --- appveyor.yml | 37 ------------------------------------- 1 file changed, 37 deletions(-) delete mode 100644 appveyor.yml diff --git a/appveyor.yml b/appveyor.yml deleted file mode 100644 index 4b0d9663..00000000 --- a/appveyor.yml +++ /dev/null @@ -1,37 +0,0 @@ -environment: - P: "c:/projects/libs" - -# Operating system (build VM template) -os: Visual Studio 2022 - -# scripts that are called at very beginning, before repo cloning -#init: - - -# clone directory -clone_folder: c:\projects\g3log - -platform: x64 -configuration: Release - -install: - # by default, all script lines are interpreted as batch - -# scripts to run before build -before_build: - - cd c:\projects\g3log\ - - mkdir build - - cd build - -build_script: - - cmake -G "Visual Studio 17" -A x64 -DADD_G3LOG_UNIT_TEST=ON -DWINDOWS_FUNCSIG=ON -DUSE_DYNAMIC_LOGGING_LEVELS=ON -DCHANGE_G3LOG_DEBUG_TO_DBUG=ON -DCMAKE_INSTALL_PREFIX=c:\g3log .. - - cmake --build . --config Release --target install - -# scripts to run after build -after_build: - - cmd /c Release\g3log-FATAL-contract.exe || exit /B 0 - - tree /A /F c:\g3log - - cpack -G "NSIS;ZIP" - - cpack -C Release - - ctest -C Release --verbose - From 8a9d471274ebf572a79ece2b3e856bceed8c3755 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kjell=20Hedstr=C3=B6m?= Date: Tue, 27 Aug 2024 21:48:26 -0600 Subject: [PATCH 3/4] Delete .circleci/config.yml --- .circleci/config.yml | 22 ---------------------- 1 file changed, 22 deletions(-) delete mode 100644 .circleci/config.yml diff --git a/.circleci/config.yml b/.circleci/config.yml deleted file mode 100644 index 9677f418..00000000 --- a/.circleci/config.yml +++ /dev/null @@ -1,22 +0,0 @@ -version: 2.1 -executors: #(1) - exectr: - docker: - - image: cimg/base:edge-20.04 - #docker: - # - image: dockerben/cpptemplate:latest - # example, maybe setup my own image later - # https://thoughts-on-coding.com/2020/04/20/a-cpp-github-template-repository-utilizing-circleci-cmake-docker-and-doxygen/ - # should look into Windows, Ubuntu, OSX executions in parallell with CircleCI ref https://circleci.com/docs/2.0/parallelism-faster-jobs/ -jobs: - build: - executor: exectr #(1) - steps: - - checkout - - run: - name: build_and_run - command: | - ./scripts/buildAndRunTests.sh - - - From 1c40cc6bb390cc4eac63c8bb32ea0212b0dda1f9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kjell=20Hedstr=C3=B6m?= Date: Tue, 27 Aug 2024 21:51:34 -0600 Subject: [PATCH 4/4] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 467733a4..3fc5dea0 100644 --- a/README.md +++ b/README.md @@ -108,7 +108,7 @@ You can find it here: https://kjellkod.wordpress.com/2015/06/30/the-worlds-faste ## Continuous Integration -The g3log repository is evaluating both github actions and CircleCI for executing test coverage, installation and document generation. For windows the repo is still relying on appveyor. In case you want to look into change any of these setups the following files are the ones of interest. +The g3log repository is evaluating github actions for executing test coverage, installation and document generation. In case you want to look into change any of these setups the following files are the ones of interest. See `Actions` for matrix (ubuntu, macos, windows) testing as well as other actions for doc publishing.