If there are .bat,.cmd and .sh versions of scripts, that means to use the one that corresponds to the platform you are on. For windows this is .bat, for macOS it is .cmd, and for UNIX it is .sh.
First run the _env script. Adjust as appropriate. You could add conditional expressions based on hostname to customize it if different for your machine. The _env script is expected to set QTDIR to where it is installed on your machine and set PATH to contain qmake. Also MAKE is expected to be set to the command to be used to run make (for example it could be set to nmake).
To build, from the provided prompt, then run "sh build-all.sh". This should work even from windows.
To clean, run "sh clean.sh"
New instructions:
The UNIX shell scripts are able to be run from a DOS cmd prompt by running them with the sh.bat script. For example:
sh build-all.sh
This will use the sh.bat script to interpret and translate the unix commands in to equivalent windows DOS commands. The shell scripts are therefore obviously restricted to the subset of supported commands that can be translated to. Environment variables must be surrounded with braces, eg "${VAR}". Common commands like cp, echo, mkdir, cd are supported and will translate unix slashes to DOS slashes for all the arguments. Also the make command is translated to %MAKE%, so it can be set up to build with VisualStudio by setting MAKE to nmake etc.
Recent versions of Windows 10 now have curl and tar commands so these can be used too. With tar you can even use it to zip and unzip files using the appropriate options instead of specifically using the zip, gzip etc commands which aren't currently explicitly available yet in Windows 10.
Old instructions:
First install Qt + MingW compiler Add both Qt and MingW bin directories to your PATH Verify they work by opening a command prompt and typing "make -v" and "qmake -v" and make sure those commands are found.
A) Using QDevelop
1) First run the "build-libexif.bat" script 2) Now open Photoframe.pro with QDevelop, click build 3) Use the "refresh-translations.bat" for deployment 4) Use "clean.bat" before making a dist package
B) Using command line only
1) "build-all.bat" will do everything 2) "run.bat" to run it 3) "clean.bat" to remove everything built