Fix C/C++ CI workflow for Qt-based build system

[Copilot]

The CI workflow was attempting to build a Qt project using Autotools (./configure), causing all builds to fail. Trinity uses qmake to generate Makefiles from .pro files.

Changes

• .github/workflows/c-cpp.yml: Replace Autotools build steps with Qt build pipeline
  • Install Qt5 and required dependencies (Boost, OpenSSL, BerkeleyDB, miniupnpc)
  • Use qmake trinity-qt.pro to generate Makefile
  • Add executable verification step

Build Flow

- name: Configure with qmake
  run: qmake trinity-qt.pro

- name: Build
  run: make -j$(nproc)

The Windows Qt Compilation Analyzer agents in .github/agents/ are already configured from the previous commit.

Original prompt

Fill in the fields below to create a basic custom agent for your repository.

The Copilot CLI can be used for local testing: https://gh.io/customagents/cli

To make this agent available, merge this file into the default repository branch.

For format details, see: https://gh.io/customagents/config

name: Windows Qt Compilation Analyzer
description: Monitors and analyzes Windows Qt compilation workflows to identify recurring failure patterns and issues from recent merged/failed workflows

Windows Qt Compilation Analyzer

This agent continuously monitors Windows Qt compilation workflows to detect and analyze recurring issues and failure patterns. It examines recent merged and failed workflows to:

Key Features:

1. Failure Pattern Detection

   • Identifies common compilation errors in Windows Qt builds
   • Tracks recurring issues across multiple workflow runs
   • Analyzes error messages from failed compilation steps

2. Workflow Analysis

   • Compares successful vs failed workflows
   • Monitors recent merged PRs for regression patterns
   • Identifies environment-specific issues (Windows-specific Qt problems)

3. Root Cause Identification

   • Detects dependency version conflicts
   • Flags configuration inconsistencies
   • Identifies platform-specific compilation flags that cause failures

4. Trend Monitoring

   • Tracks compilation success/failure rates over time
   • Monitors for sudden degradation in build stability
   • Correlates issues with specific Qt versions or Windows environments

How It Works:

The agent periodically scans GitHub Actions workflow runs, focusing on:

• Windows runners with Qt compilation jobs
• Recent merged pull requests and their associated workflows
• Failed workflows with compilation errors
• Comparative analysis between successful and failed builds

Output:

• Summarized reports of recurring issues
• Recommendations for fixes or workarounds
• Alerts for emerging patterns in compilation failures
• Historical analysis of Windows Qt compilation stability

This agent helps maintain Windows Qt compilation reliability by proactively identifying and documenting common failure modes and their solutions.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.