Mac OS X is not needed when compiling your Qt applications. You will need a working Mac OS X (at least on a virtual machine) with XCode installed to take necessary files from there.
CMAKE QT MAC OS X FULL
It took away a full day of time and a bunch of nerves. I collected according to this instruction.
CMAKE QT MAC OS X FOR MAC OS X
nf for Windows 32 › Cross compilation for Mac OS XĬross-compilation for Mac OS X is also very similar, except that you will need to compile a compiler. configure -xplatform win32-x-g++ -prefix /usr/local/qt4win32 CROSS_COMPILE=i686-w64-mingw32-no-webkit -no-phonon -no-phonon-backend -no-script -no-scripttools -no-multimedia -no-qt3support -fast -nomake demos -nomake examples -nomake tools -device-option -little-endian -qt-zlib -qt-libpng -qt-libjpeg -openssl-linked -no-fontconfig -no-3dnow -no-ssse3 -continue Except that there is an official assembly, and the library itself does not have to be compiled! It is enough to compile qmake, uic, moc, rcc. They will be used in QtCreator!ĭo not delete the unpacked directory after installation as it will be used. And a few ELF 64-bit LSB executables: qmake, uic, moc, rcc.
I have PE32+ DLLs in my /usr/local/qt4win64/bin after installation. It collects the necessary utilities for Linux, which will be used to build windows-binaries. The native system compiler is used at the first stage of compilation. It contains x86_64-w64-mingw32- g++ (in the Ubuntu package it should be installed separately).
The package g++-mingw-w64-x86-64 must be installed for such an assembly. For a complete list of options, see the command. I compile a minimal version of Qt without webkit, phonon, multimedia, etc. configure -xplatform win64-x-g++ CROSS_COMPILE=x86_64-w64-mingw32-prefix /usr/local/qt4win64 -no-webkit -no-phonon -no-phonon-backend -no-script -no-scripttools -no-multimedia -no-qt3support -fast -nomake demos -nomake examples -nomake tools -device-option -little-endian -qt-zlib -qt-libpng -qt-libjpeg -openssl-linked -no-fontconfig -no-3dnow -no-ssse3 -continue
I executed configure with the following parameters: In fact, only the paths were replaced in the specification file. Copy the win32-g ++ folder to win64-x-g ++ in the mkspecs directory of the unpacked archive. Download the source codes qt-everywhere from the official site. But the second one can be solved via compilation only…ĭo not forget to put directly the cross-compiler itself (it is searched in the package manager by the name “mingw”) before cross-compiling. This approach has several disadvantages: 1) QtCreator does not know anything about the installed library 2) There is no official Qt build for Windows 圆4. Qt compilation is not necessary in this case, you can download the binaries from the official site. You need to create a mkspecs configuration, put the Qt files into the appropriate directory and that’s it. An example of a solution to this problem can be found here or in Russian. Usually one of the most popular problems is the assembly of the Windows version of the application originally developed under Linux.
0 kommentar(er)
