Inital support CMake build and Devcontainer configuration

.devcontainer/Dockerfile

@@ -0,0 +1,16 @@
+FROM mcr.microsoft.com/devcontainers/base:jammy
+
+RUN apt-get update && apt-get install -y \
+    build-essential \
+    clang-tidy \
+    cmake \
+    cppcheck \
+    gdb \
+    libswt-gtk-4-java \
+    mono-complete \
+    openjdk-11-jdk \
+    python3-pip \
+    swig \
+    tcl-dev
+
+RUN pip install scons

.devcontainer/devcontainer.json

@@ -0,0 +1,33 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/ubuntu
+{
+	"name": "Soar Dev Container",
+	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
+	"build": {
+		"dockerfile": "Dockerfile"
+	},
+
+	// Features to add to the dev container. More info: https://containers.dev/features.
+	// "features": {},
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	"postCreateCommand": "./build.sh",
+
+	// Configure tool-specific properties.
+	"customizations": {
+		"vscode": {
+			"extensions": [
+				"ms-vscode.cmake-tools",
+				"josetr.cmake-language-support-vscode",
+				"ms-vscode.cpptools",
+				"ms-python.python"
+			]
+		}
+	},
+
+	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
+	// "remoteUser": "root"
+}

.github/workflows/build.yml

@@ -75,7 +75,7 @@ jobs:
       - name: Pack artifacts
         run: tar -czvf build.tar.gz out/
       - name: upload artifacts
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: Soar-${{ matrix.os }}
           path: ./build.tar.gz
@@ -121,7 +121,7 @@ jobs:
         run: sudo ./do_performance_test.sh
 
       - name: upload performance test results
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: ${{ matrix.os }}-PerformanceTestResults.txt
           path: ./out/SoarPerformanceTests/PerformanceTestResults.txt
@@ -199,7 +199,7 @@ jobs:
         shell: bash
         run: tar -czvf build.tar.gz out/
       - name: upload artifacts
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: Soar-Windows
           path: ./build.tar.gz
@@ -263,7 +263,7 @@ jobs:
           }
 
       - name: upload performance test results
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: Windows-PerformanceTestResults.txt
           path: ./out/SoarPerformanceTests/PerformanceTestResults.txt

.github/workflows/cmake-multi-platform.yml

@@ -0,0 +1,131 @@
+# This starter workflow is for a CMake project running on multiple platforms. There is a different starter workflow if you just want a single platform.
+# See: https://github.com/actions/starter-workflows/blob/main/ci/cmake-single-platform.yml
+name: CMake on multiple platforms
+
+on:
+  push:
+    branches: ["development"]
+  pull_request:
+    branches: ["development"]
+  workflow_dispatch:
+
+jobs:
+  build-nix:
+    runs-on: ${{ matrix.os }}
+
+    strategy:
+      # Set fail-fast to false to ensure that feedback is delivered for all matrix combinations. Consider changing this to true when your workflow is stable.
+      fail-fast: false
+
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        build_type: [Release, Debug]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set reusable strings
+        # Turn repeated input strings (such as the build output directory) into step outputs. These step outputs can be used throughout the workflow file.
+        id: strings
+        shell: bash
+        run: |
+          echo "build-output-dir=${{ github.workspace }}/build" >> "$GITHUB_OUTPUT"
+
+      # Set up Python (required for Conan)
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: 3.13
+
+      # Install Conan
+      - name: Install Conan
+        run: pip install conan
+
+      # Create Conan profile
+      - name: Configure Conan
+        run: |
+          conan profile detect
+
+      # Install dependencies with Conan
+      - name: Install dependencies
+        run: |
+          conan install . --build=missing --settings=build_type=${{ matrix.build_type }}
+
+      - name: Configure CMake
+        # Configure CMake in a 'build' subdirectory. `CMAKE_BUILD_TYPE` is only required if you are using a single-configuration generator such as make.
+        # See https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html?highlight=cmake_build_type
+        run: >
+          cmake -B ${{ steps.strings.outputs.build-output-dir }}
+          -DCMAKE_BUILD_TYPE=${{ matrix.build_type }}
+          -DCMAKE_TOOLCHAIN_FILE=${{ steps.strings.outputs.build-output-dir }}/${{ matrix.build_type}}/generators/conan_toolchain.cmake
+          -S ${{ github.workspace }}
+
+      - name: Build
+        # Build your program with the given configuration. Note that --config is needed because the default Windows generator is a multi-config generator (Visual Studio generator).
+        run: cmake --build ${{ steps.strings.outputs.build-output-dir }} --config ${{ matrix.build_type }}
+
+      - name: Test
+        working-directory:
+        # Execute tests defined by the CMake configuration. Note that --build-config is needed because the default Windows generator is a multi-config generator (Visual Studio generator).
+        # See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail
+        run: ctest --test-dir ${{ steps.strings.outputs.build-output-dir }}/UnitTests/ --output-on-failure  --build-config ${{ matrix.build_type }}
+
+  build-windows:
+    runs-on: ${{ matrix.os }}
+
+    strategy:
+      # Set fail-fast to false to ensure that feedback is delivered for all matrix combinations. Consider changing this to true when your workflow is stable.
+      fail-fast: false
+
+      matrix:
+        os: [windows-latest]
+        build_type: [Release, Debug]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set reusable strings
+        # Turn repeated input strings (such as the build output directory) into step outputs. These step outputs can be used throughout the workflow file.
+        id: strings
+        shell: bash
+        run: |
+          echo "build-output-dir=${{ github.workspace }}\build" >> "$GITHUB_OUTPUT"
+
+      # Set up Python (required for Conan)
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: 3.13
+
+      # Install Conan
+      - name: Install Conan
+        run: pip install conan
+
+      # Create Conan profile
+      - name: Configure Conan
+        run: |
+          conan profile detect
+
+      # Install dependencies with Conan
+      - name: Install dependencies
+        run: |
+          conan install . --build=missing --settings=build_type=${{ matrix.build_type }}
+
+      - name: Configure CMake Windows
+        # Configure CMake in a 'build' subdirectory. `CMAKE_BUILD_TYPE` is only required if you are using a single-configuration generator such as make.
+        # See https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html?highlight=cmake_build_type
+        run: >
+          cmake -B ${{ steps.strings.outputs.build-output-dir }}
+          -DCMAKE_BUILD_TYPE=${{ matrix.build_type }}
+          -DCMAKE_TOOLCHAIN_FILE=${{ steps.strings.outputs.build-output-dir }}\generators\conan_toolchain.cmake
+          -S ${{ github.workspace }}
+
+      - name: Build
+        # Build your program with the given configuration. Note that --config is needed because the default Windows generator is a multi-config generator (Visual Studio generator).
+        run: cmake --build ${{ steps.strings.outputs.build-output-dir }} --config ${{ matrix.build_type }}
+
+      - name: Test
+        working-directory:
+        # Execute tests defined by the CMake configuration. Note that --build-config is needed because the default Windows generator is a multi-config generator (Visual Studio generator).
+        # See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail
+        run: ctest --test-dir ${{ steps.strings.outputs.build-output-dir }}\UnitTests\ --output-on-failure  --build-config ${{ matrix.build_type }}

.gitignore

@@ -81,6 +81,7 @@ venv
 .Python
 env/
 build/
+install/
 develop-eggs/
 dist/
 downloads/
@@ -521,8 +522,12 @@ build/
 /.pydevproject
 user-env*.*
 build_*.*
+!build_time_date.h
 testCommandToFile-output.soar
 soarversion
 build_time_date
 backup.sqlite
 temp_chunks.soar
+
+CMakeUserPresets.json
+Testing/*

.vscode/extensions.json

@@ -5,5 +5,6 @@
         "editorconfig.editorconfig",
         "bdegrend.soar",
         "sysoev.vscode-open-in-github",
+        "ms-vscode.cmake-tools"
     ]
-}
+}