@SGaist NO, both are 32bit. Seems clearing the build dir and make again solved the problem!

@ed-wright Not sure, but probably you have to do a "nmake distclean" in between or it finds your license information. However, this is the opensource forum. You would need to approach the commercial, they have to able to give the proper answer.

Super good work. Thanks for updating on the way. will be helpful for others.

@mrjj well, thanks. I've tried to add #include <sqltypes.h> just in case, and voilà, now there are errors(C2065, C3861) inside Qt(drivers\odbc\qsql_odbc.cpp). Don't know if it's better, but still something.

Indeed it did the work, it is working fine now, thank you :)

Hi, A bit off topic but why not use the libtiff bundled with Qt ? That could avoid you the trouble having to build an external version of it. Unless you absolutely need that specific version.

Hi, Looks like you've opened a x86 development command line rather than the amd64.

Ok, so I was able to resolve my issue after a lot of messing about. The short of it was that my Makefile.release file wasn't including the cstdint header file. I'm not sure where in the configuration it went wrong (configure.exe) but I had to add to the Makefile.release file the following information: INCPATH= -I"c:<msvc path>\VC\include" INCPATH is already there. You need to add the rest BEFORE the rest of the path information being included. It didn't work when placed afterwards. This worked until I came across another problem with the StringsExtras.h file, which was another issue (had to comment out the 'endif' statements on lines 79 and 91). Anyway, if that helps someone - great!

Why Qt 4.8.6 and not the latest Qt 4.8.7 ? I've compiled Qt 4.8.7 with VS2010, VS2013 and VS2015, in 32 and 64 bits, here's my steps: https://github.com/sandym/qt-patches/tree/master/windows/qt-4.8.7

Hi and welcome to devnet, Unless you're using an old version of Qt, the mkspec for VS2015 is already in so you can build Qt with it. As for jom, you can just call it in place of nmake. Use the full path to the exe and you should be good to go. Hope it helps

OK Thanks