CoreTrace Qt is DISCONTINUED coretrace-gui is its successor !
A modern Qt-based IDE for the CoreTrace project, providing a user-friendly interface for managing and analyzing traces.
Complete documentation for this project is available online: https://coretrace.github.io/coretrace-qt/
The documentation includes:
- API Reference: Technical documentation of the codebase
- User Guide: Instructions for using the application
- Modern Qt-based GUI
- File tree view with context menu support
- Project management
- Trace analysis tools
- Cross-platform support
- Qt 6.x
- CMake 3.16 or higher
- C++17 compatible compiler
- Git
- Qt6 Core
- Qt6 Widgets
- Qt6 Gui
- libcurl
- libssh2
The project includes several shell scripts at the root level that you can use to automate various tasks:
./build.shThis script automates the build process. It will:
- Check for required dependencies
- Create a build directory
- Configure the project with CMake
- Build the project
- Install the executable (if specified)
./clean.shThis script will clean the build directory and remove all build artifacts.
./dist.shThis script creates distribution packages for the project.
./test.shThis script runs all unit tests for the project.
- Clone the repository:
git clone https://github.com/yourusername/coretrace-qt.git
cd coretrace-qt- Make the build script executable:
chmod +x build.sh- Run the build script:
./build.shRun the following command to build the project:
./build.shThis will automate the build process. It will:
- Check for required dependencies
- Create a build directory
- Configure the project with CMake
- Build the project
- Install the executable (if specified)
If you wish to create an AppImage, use:
./app-image-builder.shThis script helps in building an AppImage of the project for wider distribution. However, Wayland users should be aware that currently, AppImages do not work on Wayland. It's recommended to only use build.sh if you are using Wayland.
To clean the repository and remove any build artifacts, run:
./clean.shThis will clean the build directory and remove all temporary files and build outputs.
For Windows builds, we recommend using MXE (MinGW-w64 Cross Compiler) to create a standalone executable.
-
Install MXE following their installation guide
-
Use the provided Makefile:
make -f Makefile.windowsThis will create a standalone .exe file with all required dependencies.
coretrace-qt/
├── src/ # Source files
├── includes/ # Header files
├── resources/ # Resources (icons, etc.)
├── build/ # Build directory (created by build.sh)
├── CMakeLists.txt # CMake configuration
├── Makefile # Windows build configuration USE WITH MXE !
├── build.sh # Build script
└── README.md # This file
- Create new source files in the
src/directory - Add corresponding headers in the
includes/directory - Update CMakeLists.txt with new files
- Rebuild the project
- Follow Qt coding conventions
- Use C++17 features
- Document all public interfaces
- Write unit tests for new features
The project uses GitHub Actions to automatically verify AppImage builds:
- Workflow:
.github/workflows/appimage-build-test.yml - Triggers: Push/PR to
mainordevelopbranches - Verification: Ensures AppImage is successfully generated
- Artifacts: AppImage saved for 7 days after successful build
To quickly check if an AppImage was generated locally:
./check-appimage.sh- Fork the repository
- Create a feature branch
- Commit your changes
- Push to the branch
- Create a Pull Request
Mail: cedric.roulof@epitech.eu
Discord: shookapic (faster response)