- Download and install the following:
- Check that the following files are in the correct directories:
- Start Qt Creator and choose Tools > Options > Build & Run
Configure all of your settings in the Build & Run section.
- Manually set the debugger to MinGW’s gdb.exe.
- Manually set the compiler to MinGW’s g++.exe
- Manually set the Qt version.
- Configure the project kit from the previously set debug, compiler, and Qt version.
- Extract the Shotcut SDK .zip file to a new folder in C:\ called “Projects” (C:\Projects).
- In Qt Creator open shotcut.pro from C:\Projects\Shotcut\src\shotcut.
- In the Shotcut project configuration screen find Run Settings.
- Go to Deployment > Add Deploy Step > Make. In Make arguments, enter “install”
- Go to Run > Add > Custom Executable.
Set Executable to “C:\Projects\Shotcut\shotcut.exe”
- Set your build settings in the Shotcut project configuration so that the build steps include MinGW make steps.
- After clicking Run, you can confirm the newly built executable is the one that is running from the About
dialog: the version will be “adhoc”.
The section above just gets you a working environment for the Shotcut
code, but not any of its dependencies. Some of the dependencies included
in the SDK with source code can be opened and used within Qt Creator -
frei0r and webvfx. Instructions for that are not yet included. In other
cases you can use the Git Bash shell environment. Upon opening a Git
Bash shell, enter (or add to ~/.profile and restart the shell):
export CFLAGS="-Ic:/Projects/Shotcut/include -DHAVE_STRUCT_TIMESPEC"
export LDFLAGS="-Lc:/Projects/Shotcut/lib -Lc:/Projects/Shotcut"
For a project’s configure step, often you can supply the prefix as
make install will work as expected. However,
sometimes you need to copy DLLs from bin/ or lib/ into
/c/Projects/Shotcut where shotcut.exe resides.
When working with git repos from the SDK on Windows, it can helpful to
git config core.fileMode false to prevent unchanged files from
appearing in git status and git diff.
Command Line Debugging
When using gdb at the command line to debug, using Ctrl+C to break
execution will also exit the debugger. There is a program called
breakgdb.exe (source) that can be used to break