I've been evaluating QT Jambi for an application I'm developing, and on the way I've read that QT Jambi faces some troubles at development time on Win64. However, I won't develop on Win64 so it doesn't matter for now, but what I really need to know is whether an application that is built using QT Jambi would run seamlessly on Win64 or not.
Thanks,
There is basic support for win64 already present, there just haven’t been releases for that platform. So I assure you, win64 will work as win32 does, there shouldn’t be any differences.
Related
I know there are tons of informations out there on the web about my question.
I have searched and tried for at least 2 days to get my setup up and running. But there are many unclear points and i would be very happy if someone could help me with answering my questions.
My situation:
I have an i.MX6 Eval Board on my desk which is running uboot with Linux Kernel 4.9.2. There is no distro on top. Just the kernel with busybox.
Attached to the board is a LCD TFT which is accesed through the Framebuffer. There is no GPU in the Processor.
To compile uboot and the kernel, i use the linaro toolchain gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf This toolchain is located at /opt/toolchain. The compilation of the kernel and uboot works without any problems.
Now i would like to start the application development with QT Creator. I have therefore read a lot of topics on various forums and sites on the web. Unfortunately i did not get it working.
First of all i have a confusion about the meaning of the title: http://doc.qt.io/qt-4.8/qt-embedded-install.html
There is a guide how to install "Installing Qt for Embedded Linux" Does this mean that this version is for an embedded linux, so it means that it has to be installed on the embedded device. Or does it mean that it guides you how to install QT to develop for a target system and install QT on an other system?
Before i wrote this question, i have already installed QT5.7 from their website. After some googling, i figured out that there are some changes in the windowsystem between 4.8 and 5.x. Since i dont have any GPU and therefore i dont have any OpenGL support, im not sure whether i should better go with 4.8 or whether i could use the 5.x version. Usually i tend to use the latest versions if possible.
Next i saw, that i have to define the sysroot directory. In the sysroot directory there have to be the compiled libs for qt for the arm architecture. Is there a precompiled version of these libs or do i have to compile them by my self? If yes, where to start?
EDIT:
In some tutorials they use the angstrom toolchain with a "qte" suffix My linaro toolchain does not have such an suffix. Is it also possible to use my linaro toolchain to build the qt applications?
Maybe you will notice that im new to QT and to the Embedded Linux world.
Anyhow i hope there are people out there who will be happy to share their knowledge about this topic with me.
Thanks.
We have a desktop application built with Qt 4.8.4 which makes use of ICU. I am now porting that application to Qt 5.2.1. I notice a new configure option: -icu. What does this do? I'm trying to determine if I should use it or not.
I've read that it "enables ICU support." What does that mean? And does that matter for porting an application that is already using ICU under 4.8.4?
In case it matters: we plan to build on Windows, Mac OSX, and several Linux distros.
Note: our application does not use webkit.
I am trying to cross compile a Qt4 application on Linux for Windows. I need to create an .exe (32 bit) from a Qt project, and I'm compiling under Linux (32 bit). Note that I'm not using Qt Creator, I am compiling with qmake.
I tried following many other tutorials/answers but I can't seem to make it work. Some suggest that I need MinGW but I can't find it for my platform (PCLinuxOS). Does anyone know where I can get it? Is there any other solution (apart from using Wine/Windows)?
I already have a copy of the headers and DLLs from Qt4 for Windows.
MXE does exactly what you want. It cross compiles to Windows. It comes with Qt, as well as many other libraries.
It's much easier to use than setting up a MinGW compiler on your own. You can start building in a matter of minutes, rather than spend the whole day setting up a cross compiler manually.
I need to port one of my old program to Windows. The current version uses Qt 3 on Linux.
I'd like to see it within few days only to do some tests.
Instead of porting my code on Qt 4 (no time now), is it possible to recompile on Windows with Qt 3? Do I also need minGW? Which problems may I have doing this porting?
I can't find Qt 3 for windows, can someone give me a link? or I can use the same qt source I use on Linux?
Yes, you can !
Download the qt-win-3.3.x-8 project on Sourceforge.
QT4 still has back-compatible QT3 classes, prefixed with Q3* (see http://qt-project.org/doc/qt-4.8/qt3support.html)
You should be able to compile & run you QT3 app on QT4 via those classes with minimal adaptations.
Qt-3.2 for Windows was also distributed in a CD bundled with the book "C++ GUI programming with Qt3" at no additional cost with a license for non-commercial use.
ISBN: 978-0131240728
The supported compilers were MSVC and Borland. MingW is not mentioned.
I've been searching for this info with no luck. I'm using SDK1 with 4.7.0. Works fine but has some issues with Postres so I need to update. The thing is...
I go to download RC SDK1.1 and I see windows version is 1.5GB!!
The Linux version is about 700MB.
Why is Win version more than double?
SDK1 was about 320MB for windows and 400MB+ for Linux.
So Windows version was relatively smaller than Linux version considerably and sdk1 was drastically smaller than sdk1.1. I hear that 1.5GB unpacks to 5GB.
Of course, if you download the framework and creator separately than it is normal size (roughly equivalent to SDK1). This just adds to confusion. Isn't the SDK == Framework + creator ?
Something is wrong here... Any ideas what is going on? Should I wait till full release version?
I think thats because only Windows supports development for Symbian platform using Symbian SDK that can be installed (other platforms use remote compiler). Nokia with Qt SDK 1.1 announcement mentioned that they refactored Symbian toolchains so now you can use Symbian ^ 1 and Symbian ^ 3 native APIs. I think that what made the installer so huge. On the web site I noticed they have web installer, so I'd recommend to download the web installer which is just 15Mb and I suppose it should be a wizzard page that allows you to select which parts to install. Just don't install Symbian native SDK or anything else you don't need.
Hope that helps