@Christian-Ehrlicher Thank you for responding.
Yes I am. I have only one kit configured for this projecct at the moment which is using MinGW 8.1 with QtCreator 14.0.1 (if it matters).

0275c63c-eaf2-4ff3-8efd-ab236ff07428-image.png
f8f06dbc-8ddb-45ad-b650-e51cde60e840-image.png

@Ahsan-Niaz said in Releasing exe for 32 bit windows from a 64 bit windows qt creator:

Is it possible to add kits or whatever in my current qt creator.

Yes

As I already mentioned, I already have a project running perfectly on 64 bit windows. I want to create an exe that should run perfectly on 32 bit windows.
Please guide me with what steps I should follow. Thanks

Close Qt Creator Run MaintenanceTool.exe Select and install a 32-bit version of Qt from the MaintenanceTool Install a compatible 32-bit compiler If you're using MinGW, install it from the Qt installer If you're using MSVC, install it from Microsoft's website Open your project in Qt Creator and enable your 32-bit kit: https://doc.qt.io/qtcreator/creator-configuring-projects.html Build and deploy your application using your 32-bit kit

I don't want to reinstall qt and select the packages or kits because its a headache.

You don't need to reinstall Qt.

You must install a new version of Qt on top of your existing installation.

Recently, I had to run an exe released from 64bit windows qt creator for my client on his 32 bit windows.

The bitness of Qt Creator does not matter. What's important is the bitness of your kit. (Qt Creator can manage many versions of Qt, both 32-bit and 64-bit, at the same time)

@SGaist said in Win32 static linking?:

Qt Creator architecture has nothing to do with the architecture of your application.

To build a 32bit version of your application, use the 32bit package for MSVC2017. The same goes for the 64bit version.

Yeah, that worked. When I tried it in 5.12.0 and failed, there must have been something misconfigured.

I currently don't know for the static version, however when building the dynamic version you can say to configure that it should build dynamic backend selection.

Following some info from another post, I tried the following configure.bat options:

-prefix "C:\Qt\Qt5.12.2\5.12.2\msvc2017sr" -release -platform win32-msvc -confirm-license -opensource -nomake examples -nomake tests -static -static-runtime -opengl dynamic -angle -combined-angle-lib -no-feature-d3d12

Now it works on the 32-bit Windows machine I used to build Qt and the application (and still works fine on the 64-bit machine I can also build it on), but when I run it on another Win7 64-bit machine that has never had Qt installed on it, I just get the window frame again. Is it looking for a DLL? I only have a nebulous idea of what some of those configure options actually mean, so I don't know what to try next.

yes, specify 32 and 64 for msvc2015
i was able to ignore the warnings
the kits i picked worked

@raven-worx Got keys from plugin meta data ("audiocapture")
QFactoryLoader::QFactoryLoader() checking directory path "/home/MYPATH/build-desktop-system-dev-Desktop_Qt_5_5_1_GCC_32bit-Release/MY_PROJECT/mediaservice" ...
defaultServiceProvider::requestService(): no service found for - "org.qt-project.qt.mediaplayer"

thank you @yuvaram and @jsulm
i will try your solution.

@nitish_linked As @SGaist said use absolute path to your qmake. If you just call qmake the system looks in some predefined locations (like /usr/bin) and in directories PATH is showing to and finds qmake from your distribution.

Last week i sent a "false positive" report to avast av and now looks like the MSVC2015-32bit package is not blocked anymore