At last, a user-interface friendly Wine (A compatibility layer capable of running Windows applications under Linux) Manager.
You can find the latest version on the Releases page of GitLab.
Download the WineGUI package you require for your Linux distribution (we provide .deb
, .rpm
and .tar.gz
files). Typically you should use .deb
file for Ubuntu and Linux Mint distros.
Install the package and you are ready to go! WineGUI should be listed in your menu.
- Graphical user-interface on top of Wine
- Creating a new machine using an easy step-by-step wizard
- Application list per machine (with search feature and refresh button)
- Editing and removing Windows machines in a breeze
- Configure window installing additional software with just a single click (like installing DirectX)
- One-button click to run a program, open the
C:
drive, simulate a reboot or kill all processes
WineGUI is created by using GTK3 toolkit (Gtkmm C++-interface) and C++ code.
Development has been done in VSCcodium, using the following extensions:
- C/C++
- CMake
- CMake Tools
- GitLab Workflow
See latest WineGUI Developer Docs.
Dependencies should be met before build:
- gcc/g++ (advised: v8 or later)
- cmake (advised: v3.10 or later)
- ninja-build
- libgtkmm-3.0-dev (implicit dependency with libgtk-3-dev)
- libjson-glib-dev
- pkg-config
Optionally:
- doxygen
- graphviz
- rpm
- clang-format
- cppcheck (v2.10 or higher)
Hint: You could execute ./scripts/deps.sh
script for Debian based systems (incl. Ubuntu and Linux Mint) in order to get all the dependencies installed automatically.
Run: ./scripts/build.sh
Or execute: mkdir -p build && cd build && cmake -GNinja .. && ninja
Execute within the build directory: ninja run
Or:
./build/bin/winegui
Cmake is only needed once, after that you can often use:
ninja
Clean the build via: ninja clean
Hint: Run ninja help
for all available targets.
You can use the helper script: ./scripts/build_debug.sh
Start debugging in GDB (GNU Debugger):
cd build_debug
gdb -ex=run bin/winegui
First build the (Linux) target including debug symbols. Binary should be present in the build/bin
folder.
Next, check for memory leaks using valgrind
by executing:
./scripts/valgrind.sh
Or to generate a memory usage plot in massif format, execute:
./scripts/valgrind_plot.sh
For production build and DEB file package, you can run: ./scripts/build_prod.sh
Or use:
cmake -DCMAKE_BUILD_TYPE=Release
ninja
Or build with generated doxygen files locally:
cmake -GNinja -Ddoc=ON
ninja
Before you can make a new release, align the version number in WineGUI with the version you want to release. Then create a new tagged version in Gitlab with the same version name.
Note: Only a release tag
on the main
branch will trigger the publish task.
We use our own Clang LLVM C++ Programming Style Format, using clang-format command.
To automatically comply to our style format execute following script (inplace edits are performed for you):
./scripts/fix_format.sh
Check only for errors, run: ./scripts/check_format.sh
First we try to use the Google C++ Style Guide as basis.
Next, we also tend to follow the popular C++ Core Guidelines as much as possible.
For continuous integration & delivery we use our Dockerfile to create a Docker image.
This image (danger89/gtk3-docker-cmake-ninja
) is hosted on Dockerhub.
A helper script can be used: ./scripts/build_and_upload_image.sh