Let's study the code in figure 6.1starting from main():

run qmake by right-clicking root-element of a project-tree and selecting Run qmake.

keep in mind that sometimes you want to.

close the Options window, and you should be able to build & run, as well as to debug.check under Kits that you have an auto-detected kit comprising of a Qt Version, a Debugger, and a Compiler.It usually doesn't matter to our framework if you are selecting a 32-bit version or not, as we are not going anywhere near the 32-bit limits, anyway. Note that the list will usually show several versions ending on something like “(amd64_x86)” meaning that this would be running on a 64-bit machine and generating code for a 32-bit machine. check under Compilers that the Visual C++ compiler was correctly auto-detected.check under Debuggers that two versions of cdb.exe (32/64-bit) were found in the Windows Kits folder.check under Qt Versions that your installed Qt Version got auto-detected.make should show you its version number.Open a command prompt and type “make -v” to check that it is working.Alternatively, older Windows binaries can be obtained from:.Thus you should have already installed it. Make is bundled and installed with Install-VBCC.exe, as described elsewhere (v4.2.90 at the time of writing).In case you get a stack overflow warning type “stack 20000” and try again.Open a newshell and type “make -v” to check that make is working.

The author just bumped the version number for his efforts.

Please note that the v3.75 from Aminet is in fact a v3.74 ported natively for Amiga.

Get a native Amiga binary from: and put it to your path.

The forthfollowing test should run on both platforms. It is your choice to install it on Amiga and/or PC.

We are using GNU make for building the Amiga target, as it is a free standard tool that is available on both Amiga and current plattforms.

Instaling WinUAE 5.1.0