not able to select GCC (x86 32bit) tool chain in Qt - macos

Iam not able to select gcc 32bit as the tool chain to compile my qt application.
the following are the details.
QtCreator - 2.4.1 (64bit)
QtSDK - 4.8.0 (64bit)
Platform - OS X Mountain Lion 10.8.2
Xcode - 4.6.2
i wanted to compile my application with 32bit tool chain only. I can able to compile in
windows but in mac it is not. So please help me on this.
List of available tool chains as shown in Qt creator->Preferences->Build&Run are
GCC (x86 32bit)
GCC (x86 64bit)
GCC (ppc 32bit)
GCC (ppc 64bit)
But when i am trying to set tool chain under build settings of the project, it is listing only
as follows
GCC (x86 64bit)
GCC (ppc 64bit)
what i have to do to get 32 bit as well. Thanks in advance.

Create a Kit for this in Creator's settings. It's in Tools->Options->Build & Run. Then add that Kit in the settings of your project.
Unless of course the Qt libraries you've installed are 64-bit only. In that case, you obviously can't build 32-bit applications with them. If that's the case, you need to build Qt on your own for 32-bit.

Related

GCC/G++-11 on windows

Hey I'm trying to compile a program that requires GCC and g++ 11. I've tried msys2 but it only goes up to GCC 10.04
And some of my libraries are supposed to be built on a mingw like environment. So is there any other way of running that program on a windows machine?
Get the latest MinGW-w64 GCC build from https://winlibs.com/

Windows Fortran 64bit

I am using the latest gfortran from MinGW and it seems I'm not getting my code compiled and run in 64bit. Is there a flag or compiler I should be using to take advantage of my 64bit version of Windows 10?

How to get old toolchain for Linux

We have a project that was working fine in Red Hat Enterprise Linux Server release 6.2. Since GCC version is getting updated periodically, we wanted to have our project to be independent of GCC upgrade in local system. Hence we wanted to keep GCC toolchain (binaries and libraries) in our project rather than standard location in the machine. ldd of our binaries generated out of our project should depend on the libraries in my our project not from the gcc libraries available in local system (because it might change at any time).
How do I do that? Where I shall get specific GCC toolchain for intel 64 bit (C & C++ compilers) ?
Current GCC Version: gcc-4.4.6-3.el6.x86_64

Qt Creator 2.7.0 compiler error

Screen-shot from Tools > Options > Build & Run > Compilers
Screen-shot from Tools > Options > Build & Run > Qt versions
Screen-shot from Tools > Options > Build & Run > Kits
Installed Qt creator 2.7.0 on my Windows 7.
Build a test Qt GUI Project - made it run, but encountered the following error:
:-1: error: Qt Creator needs a compiler set up to build. Configure a compiler in the kit options.
Installed MinGW and tried level best to configure at QT's Tools > Options > Build & Run > Compilers, but failed.
Performed various combinations on PATH variable in Environment, but failed.
Nothings working! Not finding any solution.
Does anyone have any resolution for this?
P.S.: No default compiler configured on QT creator.
I notice in screenshot that you have Qt libraries compiled for MSVC2010, but you are trying to use them with MinGW compiler.
On Qt project "downloads" page you will see that there are different binary packages for different compilers. For windows there are 4 packages:
MinGW 4.7.2 32-bit
MSVC 2010 32-bit
MSVC 2010 32-bit with OpenGL
MSVC 2012 64-bit
You must choose package that is binary compatible with your compiler (runtime C library).

Will app built with gcc 4.x on CentOS/RHEL 4.8 run on completely un-updated CentOS/RHEL 4?

We have a commercial application that we build on 32-bit CentOS 4.8 (equivalent to Red Hat Enterprise Linux (RHEL) 4 update 8.
The default gcc compiler is at 3.4.6
We are able to run our binary on both 32- and 64-bit CentOS/RHEL 4 and 5 including completely un-updated RHEL 4.
THE QUESTION: If we update to a newer gcc 4 version, will the binary still run on a completely un-updated RHEL 4
The newest gcc appears to be 4.5.1 and 4.4.5
(And yes there are customers who install the intial version, run on an isolated network with no Internet access, and NEVER update from the as-shipped version.)
This issue has arisen because we are now porting to 64-bit FreeBSD 8.1 for amd64 and the default gcc there is gcc 4.2.1
As long as you're compiling against the same runtime libraries (like glibc) you'll be fine.

Resources