- All (478)
- jom (0)
- Qt Linguist (7)
- Qt Eclipse Integration (9)
- Qt Designer (7)
- Qt Creator (4)
- Qt build system: qmake (31)
- Qt build system: configure (3)
- Qt Assistant (5)
- Printing (4)
- Porting from Qt 3 to Qt 4 (1)
- Plugins (7)
- Qt Visual Studio AddIn (2)
- Qt/MFC Migration (2)
- QtScript (3)
- MDI (2)
- XML (1)
- Widgets (22)
- WebKit (5)
- Tools and Containers (2)
- Threads (2)
- Text Handling (10)
- SQL (6)
- QtTest (1)
- QtService (1)
- Platform: Windows (49)
- Platform: Unix (16)
- Platform: Mac OS X (18)
- Image Formats (2)
- I/O (2)
- Graphicsview (8)
- Font handling (9)
- Event System (18)
- Drag and Drop (4)
- Dialogs (6)
- Desktop integration (3)
- ActiveQt (3)
- Itemviews (60)
- Layout (4)
- Qt Quick (10)
- Qt SDK (1)
- Licensing (2)
- Platform: Embedded Linux (38)
- Painting (32)
- OpenGL (4)
- Object Model (6)
- Network (5)
- Multimedia (3)
- Miscellanous (23)
- Main Window (19)
- Look and Feel (23)
- Development (0)
- Getting Involved (0)
- Routines (0)
How can I detect in the .pro file if I am compiling on a 32 bit or a 64 bit platform?
You can use QMAKE_HOST.arch for this. The QMAKE_HOST variable expresses host information about the machine running qmake and QMAKE_HOST.arch allows you to determine the target architecture. You can use it as follows:
- win32-g++:contains(QMAKE_HOST.arch, x86_64):{
- do something
- }

3 comments
May 3, 2011
Ant Farmer
If I understand things correctly, QMAKE_HOST.arch will tell you if you are compiling on a 32 or 64 bit platform, which is not necessarily the same as the platform you are compiling for, right?
May 4, 2011
Lab Rat
That’s correct. You can use QMAKE_TARGET.arch to decide the platform you are building for. We have added the following FAQ [developer.qt.nokia.com] for this now:
March 18, 2013
Lab Rat
Using Qt 4.8.4, this works for me on Windows but not on Macintosh. On Macintosh
message($$QMAKE_TARGET.arch)
prints nothing in the Qt creator Compile Output pane while on Windows it prints x86_64.
I am not in a position to test in Qt 5.
I have reported this as a bug: https://bugreports.qt-project.org/browse/QTBUG-30263