Installation and Deployment

• 

  Unsolved Cannot build Qt Creator 4.4.0 from source
  • blazar0112

  2
  2
  Posts
  14
  Views

  

  @blazar0112 I'm quite sure it does not require C++17.
  How did you call configure?

• 

  Unsolved How to use Qt creator with source built qt
  designer creator qt5.9.1 • • vasu_gupta

  2
  2
  Posts
  19
  Views

  

  Qt Designer is included in Qt sources and works only for UI files. Qt Creator (the IDE) is a separate application and a separate project. You need to install or compile it first, for example from qt.io/downloads.

  Once you have Qt Creator installer, you need to open the settings, add your Qt Version, then add a so called Kit (which is Qt Version + compiler bundle), and then you are ready to go.

  If you want to avoid all that hassle, use the Qt installer from the link above - it will install Qt, Qt Creator, and set everything up for you, completely automatically.

• 

  Unsolved Cross-compiled Qt5.9.2 for RPi B+ leads to non executable binaries
  • Mark81

  9
  9
  Posts
  101
  Views

  

  So basically a big cleanup and rebuild ?

• 

  Solved undefined symbol: _ZN7QWidget8qwsEventEP8QWSEvent
  • Sarath AK

  20
  20
  Posts
  179
  Views

  

  @Sarath-AK

  Finally my meta-toolchain-qt working for my target ,

  Thank you for your cooperation.

• 

  Solved What are the source and build directories for a plugin testing Qt Creator instance?
  plugin build directory qt creator source configure • • hlindberg

  3
  3
  Posts
  55
  Views

  

  Thank you for the welcome and clarification, SGaist!

  It wasn't immediately apparent to me that I actually needed the Qt Creator sources to create a plugin for the IDE. Fortunately I got some good advice from a project team member of mine on the steps of solving the problem. I downloaded the sources, compiled them and finally made a copy of the build directory. This way I got the two instances of Qt Creator needed for development and testing. All is as it should now.

• 

  Unsolved Not able to compile anything after installation Qt 5.9.1
  • Venusian Lion

  2
  2
  Posts
  38
  Views

  

  Hi and welcome to devnet,

  What exactly did you install ? You seem to have some sort of mess between MinGW and Visual Studio.

  If you want to use only VS2017, then just install the Qt for VS2017 package.

• 

  Unsolved Qt 5.9.1 Static build failing
  • Kayote

  5
  5
  Posts
  61
  Views

  

  Yes it's a MingGW build. I am using the exact same OpenSSL build as I used on my other PC which build successfully with Qt 5.5 and 5.6, so I really don't know why it wont work now.

• 

  Solved Visual Studio 2015 create standalone release application
  • fenomeno83

  8
  8
  Posts
  69
  Views

  

  Glad you got it working and thanks for sharing.

  Since you have it running now, please mark the thread as solved using the "Topic Tools" button so that other form users may know a solution has been found :)

• 

  Unsolved Unattended/silent/quiet installation of Qt 5.8 on Windows
  • davek711

  2
  2
  Posts
  23
  Views

  

  I would like to install Qt 5.8 using the qt-enterprise-windows-x86-msvc2015_64-5.8.0.exe installer. I have tried using a controller script as advised in other posts but this still brings up the interactive installer:

  qt-enterprise-windows-x86-msvc2015_64-5.8.0.exe --script qt-installer-noninteractive.qt

  The script qt-installer-noninteractive.qt script looks as follows:

  function Controller() {
  installer.setDefaultPageVisible(QInstaller.Introduction, false);
  installer.setDefaultPageVisible(QInstaller.TargetDirectory, false);
  installer.setDefaultPageVisible(QInstaller.ComponentSelection, false);
  installer.setDefaultPageVisible(QInstaller.LicenseCheck, false);
  installer.setDefaultPageVisible(QInstaller.StartMenuSelection, false);
  installer.setDefaultPageVisible(QInstaller.ReadyForInstallation, false);
  installer.setDefaultPageVisible(QInstaller.PerformInstallation, false);

  installer.autoRejectMessageBoxes(); installer.installationFinished.connect(function() { gui.clickButton(buttons.FinishButton); })

  }

  Controller.prototype.WelcomePageCallback = function() {
  gui.clickButton(buttons.NextButton);
  }

  Controller.prototype.CredentialsPageCallback = function() {
  gui.clickButton(buttons.NextButton);
  }

  Controller.prototype.IntroductionPageCallback = function() {
  gui.clickButton(buttons.NextButton);
  }

  Controller.prototype.TargetDirectoryPageCallback = function()
  {
  gui.clickButton(buttons.NextButton);
  }

  Controller.prototype.ComponentSelectionPageCallback = function() {

  gui.clickButton(buttons.NextButton);

  }

• 

  Unsolved What happens if I load the GPL library using Qt's QPluginLoader?
  • donbit

  3
  3
  Posts
  33
  Views

  

  Hi,

  IIRC, that's more complicated than that. You should ask a lawyer or at least contact the fsfe to get their opinion on that.

• 

  Unsolved How to build a static version of Qt 5.9 with OpenSSL and MariaDB support (os X) ?
  static mariadb openssl • • Selzig

  2
  2
  Posts
  28
  Views

  

  Hi and welcome to devnet,

  Understand the licensing constraints of using a static build of Qt and be ready to abide by them Install an up to date version of OpenSSL (the system version is just too old) Install MariaDB Download Qt's source Read documentation about static building Pass the -openssl-linked as parameter to configure Pass -sql-mysql as parameter to configure Pass the -I and -L parameters as needed in order for Qt to find the MariaDB and OpenSSL libraries. Call make -jX where X is the number of cores of your machine multiplied by 2 plus 1. Go grab <insert favorite beverage> and look at your processors heating up Call make install Enjoy development
• 

  Unsolved windeployqt.exe does not gather the correct DLLs
  • stvokr

  2
  2
  Posts
  39
  Views

  

  Hi,

  Because when you call windeployqt on the command line, you will be calling the first the system can find which will be the one in the order of the PATH environment variable.

  Basically: don't modify your PATH environment variable system wide like you do especially when dealing with development software.

  Qt Creator does the work for you when you develop so you don't have to do funky stuff to get your application running. If you want to use something like windeployqt from the command line, IIRC, Qt already provides links with environment setup done to get a command line ready to use. So you should rather use that or like on other OS, use the full path to the executable you want to use.

  Again: do not modify the PATH environment variable system wide.

• 

  Unsolved CmakeFiles Error
  • AlexE

  2
  2
  Posts
  21
  Views

  

  Hi,

  The first thing I'd do is update cmake, the current version is 3.9.2.

• 

  This topic is deleted!
  • AlexE

  1
  1
  Posts
  1
  Views

  No one has replied

• 

  Solved toolchain.prf(50): system(execute) requires one or two arguments.
  • titan83

  2
  2
  Posts
  30
  Views

  

  @titan83 And I answer myself to question above.
  In file mkspecs/features/default_pre.prf I commented last line "load(toolchain)"

• 

  Unsolved How can I include Qt framework qm files in Visual Studio Qt project?
  • mihai

  1
  1
  Posts
  17
  Views

  No one has replied

• 

  Unsolved Installing Qt "Network error while downloading "
  • Rikardo 0

  4
  4
  Posts
  38
  Views

  

  On the same page you downloaded Qt from.

  Or here in the officia releases folder.

• 

  Unsolved qoic plugin installation
  qt creator drivers plugin qoci • • Lasith

  5
  5
  Posts
  56
  Views

  

  Thanx bro! I just guessed and download it :D

• 

  Unsolved SSL handshake failed error while installing Qt on KDE Ubuntu
  • lak021

  7
  7
  Posts
  146
  Views

  

  What did you not understand ?

  Try Installing libssl1.0

• 

  Unsolved Error Running Cmake Through qt Creator
  • psy.song

  2
  2
  Posts
  19
  Views

  

  Hi and welcome to devnet,

  Can you show your CMakeLIsts.txt file ?

• 

  Unsolved Installing qoci plugin
  qtcreator c++ oci installation • • Lasith

  4
  4
  Posts
  46
  Views

  

  http://download.qt.io/official_releases/qt/

  You also have the MaintenanceTool that offers that possibility.

• 

  Solved Error: execvp: ../sample/mainwindow.ui: Permission denied**
  • Sarath AK

  7
  7
  Posts
  85
  Views

  

  i have compiled qt 4.8.7 manually , now its working .

  Thank you

• 

  Unsolved Builing on Pi3 @ Raspbian Stretch fails
  raspberry pi 3 raspbian raspberry • • Vitalic66

  4
  4
  Posts
  57
  Views

  

  Ok, I've missed that article.

  From the looks of it, you seem to be currently essentially interested in building qtbase, so you could call configure directly in it to shorten the list of options.

  Intuitively, I'd avoid the reduce-exports and sysroot parameters.

• 

  Solved Error building QT 5.9.1 from souces
  • Dmitriano

  5
  5
  Posts
  71
  Views

  

  @raven-worx yes I deleted all the sources and did 'git clone' again.

  (2) helps! But (1) does not.

• 

  Solved Support needed in acheiving Qt Code Obfuscation using Commercial License
  • Divya Shekar

  3
  3
  Posts
  80
  Views

  

  Hi Sierdzio,

  Thanks for your prompt reply. It cleared all our doubts on obfuscating C++ code.

  Thanks & Regards,
  Divya

• 

  Unsolved Application crash with "QtQuick.Window" is not installed after adding a library (Android Deploy)
  • Trungus

  1
  1
  Posts
  21
  Views

  No one has replied

• 

  Unsolved Installing problem windows 10
  • TeeKlub

  2
  2
  Posts
  51
  Views

  

  Hi and welcome to devnet,

  Did you try to change the mirror used to download ?

• 

  Unsolved How to compile QT source code with optimizations while producing debug symbols
  • xoraxrax

  4
  4
  Posts
  59
  Views

  

  PS C:\Qt\Qt4.8.4\qt-everywhere-opensource-src-4.8.4> .\configure -h Unable to detect the platform from environment. Use -platform command lineargument or set the QMAKESPEC environment variable and run configure again See the README file for a list of supported operating systems and compilers. Usage: configure [-buildkey <key>] [-release] [-debug] [-debug-and-release] [-shared] [-static] [-no-fast] [-fast] [-no-exceptions] [-exceptions] [-no-accessibility] [-accessibility] [-no-rtti] [-rtti] [-no-stl] [-stl] [-no-sql-<driver>] [-qt-sql-<driver>] [-plugin-sql-<driver>] [-system-sqlite] [-arch <arch>] [-D <define>] [-I <includepath>] [-L <librarypath>] [-help] [-no-dsp] [-dsp] [-no-vcproj] [-vcproj] [-no-qmake] [-qmake] [-dont-process] [-process] [-no-style-<style>] [-qt-style-<style>] [-redo] [-saveconfig <config>] [-loadconfig <config>] [-qt-zlib] [-system-zlib] [-no-gif] [-no-libpng] [-qt-libpng] [-system-libpng] [-no-libtiff] [-qt-libtiff] [-system-libtiff] [-no-libjpeg] [-qt-libjpeg] [-system-libjpeg] [-no-libmng] [-qt-libmng] [-system-libmng] [-no-qt3support] [-mmx] [-no-mmx] [-3dnow] [-no-3dnow] [-sse] [-no-sse] [-sse2] [-no-sse2] [-no-iwmmxt] [-iwmmxt] [-openssl] [-openssl-linked] [-no-openssl] [-no-dbus] [-dbus] [-dbus-linked] [-platform <spec>] [-qtnamespace <namespace>] [-qtlibinfix <infix>] [-no-phonon] [-phonon] [-no-phonon-backend] [-phonon-backend] [-no-multimedia] [-multimedia] [-no-audio-backend] [-audio-backend] [-no-script] [-script] [-no-scripttools] [-scripttools] [-no-webkit] [-webkit] [-webkit-debug] [-graphicssystem raster|opengl|openvg] [-no-directwrite] [-directwrite] [-no-nis] [-nis] [-qpa] [-no-cups] [-cups] [-no-iconv] [-iconv] [-sun-iconv] [-gnu-iconv] [-neon] [-no-neon] [-largefile] [-little-endian] [-big-endian] [-font-config] [-no-fontconfig] [-posix-ipc] Installation options: You may use these options to turn on strict plugin loading: -buildkey <key> .... Build the Qt library and plugins using the specified <key>. When the library loads plugins, it will only load those that have a matching <key>. Configure options: The defaults (*) are usually acceptable. A plus (+) denotes a default value that needs to be evaluated. If the evaluation succeeds, the feature is included. Here is a short explanation of each option: -release ........... Compile and link Qt with debugging turned off. * -debug ............. Compile and link Qt with debugging turned on. + -debug-and-release . Compile and link two Qt libraries, with and without debugging turned on. -opensource ........ Compile and link the Open-Source Edition of Qt. -commercial ........ Compile and link the Commercial Edition of Qt. -developer-build ... Compile and link Qt with Qt developer options (including auto-tests exporting) * -shared ............ Create and use shared Qt libraries. -static ............ Create and use static Qt libraries. -ltcg .............. Use Link Time Code Generation. (Release builds only) * -no-ltcg ........... Do not use Link Time Code Generation. * -no-fast ........... Configure Qt normally by generating Makefiles for all project files. -fast .............. Configure Qt quickly by generating Makefiles only for library and subdirectory targets. All other Makefiles are created as wrappers which will in turn run qmake -no-exceptions ..... Disable exceptions on platforms that support it. * -exceptions ........ Enable exceptions on platforms that support it. -no-accessibility .. Do not compile Windows Active Accessibility support. * -accessibility ..... Compile Windows Active Accessibility support. -no-stl ............ Do not compile STL support. * -stl ............... Compile STL support. -no-sql-<driver> ... Disable SQL <driver> entirely, by default none are turned on. -qt-sql-<driver> ... Enable a SQL <driver> in the Qt Library. -plugin-sql-<driver> Enable SQL <driver> as a plugin to be linked to at run time. Available values for <driver>: mysql psql oci odbc tds db2 + sqlite sqlite2 ibase (drivers marked with a '+' have been detected as available on this system) -system-sqlite ..... Use sqlite from the operating system. -no-qt3support ..... Disables the Qt 3 support functionality. -no-opengl ......... Disables OpenGL functionality -opengl <api> ...... Enable OpenGL support with specified API version. Available values for <api>: * desktop - Enable support for Desktop OpenGL es1 - Enable support for OpenGL ES Common Profile es2 - Enable support for OpenGL ES 2.0 * -no-openvg ......... Disables OpenVG functionality -openvg ............ Enables OpenVG functionality Requires EGL support, typically supplied by an OpenGL or other graphics implementation -platform <spec> ... The operating system and compiler you are building on. (default %QMAKESPEC%) -xplatform <spec> .. The operating system and compiler you are cross compiling to. See the README file for a list of supported operating systems and compilers. * -no-nis ............ Do not build NIS support. -nis ............... Build NIS support. -qpa ............... Enable the QPA build. QPA is a window system agnostic implementation of Qt. -neon .............. Enable the use of NEON instructions. * -no-neon ........... Do not enable the use of NEON instructions. -no-iconv .......... Do not enable support for iconv(3). -iconv ............. Enable support for iconv(3). -sun-iconv ......... Enable support for iconv(3) using sun-iconv. -gnu-iconv ......... Enable support for iconv(3) using gnu-libiconv -largefile ......... Enables Qt to access files larger than 4 GB. * -little-endian ..... Target platform is little endian (LSB first). -big-endian ........ Target platform is big endian (MSB first). -fontconfig ........ Build with FontConfig support. * -no-fontconfig ..... Do not build with FontConfig support. -posix-ipc ......... Enable POSIX IPC. -system-proxies .... Use system network proxies by default. * -no-system-proxies . Do not use system network proxies by default. -qtnamespace <namespace> Wraps all Qt library code in 'namespace name {...} -qtlibinfix <infix> Renames all Qt* libs to Qt*<infix> -D <define> ........ Add an explicit define to the preprocessor. -I <includepath> ... Add an explicit include path. -L <librarypath> ... Add an explicit library path. -l <libraryname> ... Add an explicit library name, residing in a librarypath. -graphicssystem <sys> Specify which graphicssystem should be used. Available values for <sys>: * raster - Software rasterizer opengl - Using OpenGL acceleration, experimental! openvg - Using OpenVG acceleration, experimental! -help, -h, -? ...... Display this information. Third Party Libraries: -qt-zlib ........... Use the zlib bundled with Qt. + -system-zlib ....... Use zlib from the operating system. See http://www.gzip.org/zlib -no-gif ............ Do not compile GIF reading support. -no-libpng ......... Do not compile PNG support. -qt-libpng ......... Use the libpng bundled with Qt. + -system-libpng ..... Use libpng from the operating system. See http://www.libpng.org/pub/png -no-libmng ......... Do not compile MNG support. -qt-libmng ......... Use the libmng bundled with Qt. + -system-libmng ..... Use libmng from the operating system. See See http://www.libmng.com -no-libtiff ........ Do not compile TIFF support. -qt-libtiff ........ Use the libtiff bundled with Qt. + -system-libtiff .... Use libtiff from the operating system. See http://www.libtiff.org -no-libjpeg ........ Do not compile JPEG support. -qt-libjpeg ........ Use the libjpeg bundled with Qt. + -system-libjpeg .... Use libjpeg from the operating system. See http://www.ijg.org Qt for Windows only: -no-dsp ............ Do not generate VC++ .dsp files. * -dsp ............... Generate VC++ .dsp files, only if spec "win32-msvc". -no-vcproj ......... Do not generate VC++ .vcproj files. * -vcproj ............ Generate VC++ .vcproj files, only if platform "win32-msvc.net". -no-incredibuild-xge Do not add IncrediBuild XGE distribution commands to custom build steps. + -incredibuild-xge .. Add IncrediBuild XGE distribution commands to custom build steps. This will distribute MOC and UIC steps, and other custom buildsteps which are added to the INCREDIBUILD_XGE variable. (The IncrediBuild distribution commands are only added to Visual Studio projects) -no-plugin-manifests Do not embed manifests in plugins. * -plugin-manifests .. Embed manifests in plugins. -no-qmake .......... Do not compile qmake. * -qmake ............. Compile qmake. -dont-process ...... Do not generate Makefiles/Project files. This will override -no-fast if specified. * -process ........... Generate Makefiles/Project files. -no-rtti ........... Do not compile runtime type information. * -rtti .............. Compile runtime type information. -no-mmx ............ Do not compile with use of MMX instructions + -mmx ............... Compile with use of MMX instructions -no-3dnow .......... Do not compile with use of 3DNOW instructions + -3dnow ............. Compile with use of 3DNOW instructions -no-sse ............ Do not compile with use of SSE instructions + -sse ............... Compile with use of SSE instructions -no-sse2 ........... Do not compile with use of SSE2 instructions + -sse2 .............. Compile with use of SSE2 instructions -no-openssl ........ Do not compile in OpenSSL support + -openssl ........... Compile in run-time OpenSSL support -openssl-linked .... Compile in linked OpenSSL support -no-dbus ........... Do not compile in D-Bus support + -dbus .............. Compile in D-Bus support and load libdbus-1 dynamicall y -dbus-linked ....... Compile in D-Bus support and link to libdbus-1 -no-phonon ......... Do not compile in the Phonon module + -phonon ............ Compile the Phonon module (Phonon is built if a decent C++ compiler is used.) -no-phonon-backend . Do not compile the platform-specific Phonon backend-pl ugin * -phonon-backend .... Compile in the platform-specific Phonon backend-plugin -no-multimedia ..... Do not compile the multimedia module * -multimedia ........ Compile in multimedia module -no-audio-backend .. Do not compile in the platform audio backend into QtMu ltimedia + -audio-backend ..... Compile in the platform audio backend into QtMultimedi a -no-webkit ......... Do not compile in the WebKit module + -webkit ............ Compile in the WebKit module (WebKit is built if a decent C++ compiler is used.) -webkit-debug ...... Compile in the WebKit module with debug symbols. -no-script ......... Do not build the QtScript module. + -script ............ Build the QtScript module. -no-scripttools .... Do not build the QtScriptTools module. + -scripttools ....... Build the QtScriptTools module. -no-declarative .... Do not build the declarative module + -declarative ....... Build the declarative module -no-declarative-debug Do not build the declarative debugging support * -declarative-debug . Build the declarative debugging support * -no-directwrite .... Do not build support for DirectWrite font rendering -directwrite ....... Build support for DirectWrite font rendering (experimental, requires DirectWrite availability on target systems, e.g. Windows Vista with Platform Update, Windows 7, etc.) -arch <arch> ....... Specify an architecture. Available values for <arch>: * windows windowsce symbian boundschecker generic -no-style-<style> .. Disable <style> entirely. -qt-style-<style> .. Enable <style> in the Qt Library. Available styles: * windows + windowsxp + windowsvista * plastique * cleanlooks * motif * cde windowsce windowsmobile s60 -no-native-gestures Do not use native gestures on Windows 7. * -native-gestures ... Use native gestures on Windows 7. * -no-mp ............. Do not use multiple processors for compiling with MSVC -mp ................ Use multiple processors for compiling with MSVC (-MP) -loadconfig <config> Run configure with the parameters from file configure_ <config>.cache. -saveconfig <config> Run configure and save the parameters in file configure_<config>.cache. -redo .............. Run configure with the same parameters as last time. Qt for Windows CE only: -no-iwmmxt ......... Do not compile with use of IWMMXT instructions + -iwmmxt ............ Do compile with use of IWMMXT instructions (Qt for Windows CE on Arm only) * -no-crt ............ Do not add the C runtime to default deployment rules -qt-crt ............ Qt identifies C runtime during project generation -crt <path> ........ Specify path to C runtime used for project generation. -no-cetest ......... Do not compile Windows CE remote test application + -cetest ............ Compile Windows CE remote test application -signature <file> .. Use file for signing the target project * -phonon-wince-ds9 .. Enable Phonon Direct Show 9 backend for Windows CE Qt for Symbian OS only: * -no-freetype ....... Do not compile in Freetype2 support. -qt-freetype ....... Use the libfreetype bundled with Qt. -system-freetype ... Use the libfreetype provided by the system. -fpu <flags> ....... VFP type on ARM, supported options: softvfp(default) | vfpv2 | softvfp+vfpv2 -no-s60 ............ Do not compile in S60 support. * -s60 ............... Compile with support for the S60 UI Framework -no-usedeffiles .... Disable the usage of DEF files. -usedeffiles ....... Enable the usage of DEF files. PS C:\Qt\Qt4.8.4\qt-everywhere-opensource-src-4.8.4>
• 

  Unsolved Debug libs are linked to release version of the app
  • Dmitriano

  3
  3
  Posts
  48
  Views

  

  Hi @SGaist !
  They are ANGLE QT libraries. DLLs in C:\Qt\Qt5.9.1\5.9.1\msvc2015\bin\ and LIBS in C:\Qt\Qt5.9.1\5.9.1\msvc2015\lib, I use them directly, because I am not sure there is ANGLE module for QMake.

  Still cannot figure out how it works, if I specify the libraries with CMake like this:

  target_link_libraries(${PROJECT_NAME} debug ${ANGLE_LIB_DIR}libEGLd.lib debug ${ANGLE_LIB_DIR}libGLESv2d.lib optimized ${ANGLE_LIB_DIR}libEGL.lib optimized ${ANGLE_LIB_DIR}libGLESv2.lib)

  and then run

  msbuild MyApp.sln /p:Configuration=Release

  the libs are linked correctly.

• 

  Unsolved Getting Error while building application with static build of Qt 5.8
  • guru007

  1
  1
  Posts
  27
  Views

  No one has replied

• 

  Unsolved QMake command is executed 3 times
  • Dmitriano

  1
  1
  Posts
  32
  Views

  No one has replied

• 

  Solved QMake errors with platform-specific sections like android: and win32:
  • Dmitriano

  2
  2
  Posts
  42
  Views

  

  figured this out, it is because the brace should be on the same line like "android {"

• 

  Unsolved Mac OS Deployment - libqcoca.dylib
  • ModelTech

  5
  5
  Posts
  63
  Views

  

  Have tried macdeployqt already several times, but:

  ~/Qt/5.9.1/clang_64/bin/macdeployqt dfm.app/ ERROR: no file at "/usr/lib/libdfmcore.1.dylib"

  And this shows that it does not find my core library. Nethertheless, my .pro file has the following lines:

  win32:CONFIG(release, debug|release): LIBS += -L$$PWD/../build/core/release -ldfmcore else:win32:CONFIG(debug, debug|release): LIBS += -L$$PWD/../build/core/debug -ldfmcore else:unix:CONFIG(release, debug|release): LIBS += -L$$PWD/../build/release/core -ldfmcore else:unix:CONFIG(debug, debug|release): LIBS += -L$$PWD/../build/debug/core -ldfmcore

  The application runs perfectly fine from Qt Creator.

• 

  Solved Not all lib files got statically built
  • Shpacuh

  7
  7
  Posts
  110
  Views

  

  @SGaist Yes I am.

  I'm considering to mark the topic as solved because I figured out why it only SEEMED that not all libraries are being statically compiled, it's because :

  The first time I built them I set the prefix to the same folder an already installed Qt was, making them scattered across the various subdirectories When I set the -prefix flag the next time to another location I forgot to run the make install step

  So after fixing those two mistakes I had my statically built Qt up and running. As for the Designer plugin not being statically built that's not a problem anymore because I actually didn't need it. My current problems are far out of the reach the original topic, so if need be Ill open another thread at a later time.

  Thanks for the help anyways.

• 

  Unsolved Qt Static Build 'Runtime Mismatch' MSVC
  • Contempt

  12
  12
  Posts
  134
  Views

  

  What are these externals ?

• 

  Unsolved Unable to locate ICU library icuin51.dll
  • Denis Dolzhenko

  3
  3
  Posts
  53
  Views

  

  @hskoglund Ok that helped

  As for the deployment on a different pc, Do I need to install the MinGW package supplied by QT, or is there a way to use the MinGW installer to get the needed dependancies?
  I tried installing MinGW on a pc without having QT on it, but its complaining about libwinthread-1.dll missing.

  I never had that issue when I used 5.8 VC and everything worked after I installed vcredist.exe.

• 

  Solved Ubuntu QMYSQL driver loaded error.
  • Kosta

  7
  7
  Posts
  63
  Views

  

  @SGaist So i went to the options Build & Run and added a new kit with the following values

  Name: Qt 5.9.1 File System name: *empty* Device Type: Desktop Device: Local Pc (default for desktop) Sysroot: *empty* C: GCC C x86 64bit /usr/bin C++: GCC C++ x86 64bit /usr/bin Environment: *has a non changable value* No changes to apply Debugger: System GDB at /usr/bin/gdb Qt Version: Qt 5.9.1 (build_qt5) Qt mkspec: *empty* CMake Tool: System CMake at /usr/bin/cmake

  Now the DB connection seems to work but when i do

  QSqlDatabase db = QSqlDatabase::addDatabase("QMYSQL"); db.setHostName("localhost"); db.setDatabaseName("files"); db.setUserName("root"); db.setPassword("kosta"); bool ok = db.open(); QSqlQueryModel *model = new QSqlQueryModel; model->setQuery("SELECT id, comment, pdf FROM pdf"); model->setHeaderData(0, Qt::Horizontal, tr("id")); model->setHeaderData(1, Qt::Horizontal, tr("comment")); model->setHeaderData(2, Qt::Horizontal, tr("pdf")); QTableView *view = new QTableView; view->setModel(model); ui->cent->addWidget(view); view->show();

  (cent is a layout i added in the form just for debug purpose) Nothing appears and i get an error saying that Qt didnt ship anymore with font database or something so i went ahead and created a fonts directory in build_qt5/lib i took the font Oxygen from Google fonts. So everything works perfectly thanks a lot for that! I am now looking to add the oxygen font for my overall application but i should be able to figure that out alone.

  Again thanks alot!

• 

  Unsolved How to get QtCreator to use static libs for Release?
  • lonnie

  16
  16
  Posts
  220
  Views

  

  @SGaist said in How to get QtCreator to use static libs for Release?:

  On a side note, .lib files on Windows are used for static libraries as well as import libraries when using .dlls. Usually you can spot the difference with the size of the file.

  I did NOT know that and always assumed that a .lib was for static linking. I never generate dll files so really only have ever encountered .lib files.

  Thanks for cluing me in.

• 

  Unsolved Cross-compiled application running on target gets killed and shows "Illegal Instruction".
  • name_qt

  12
  12
  Posts
  103
  Views

  

  @name_qt Can you try with a debug build?
  Also, after it crashed you can get backtrace with bt in GDB.

• 

  Unsolved Qt Installer non-interactive
  • adowdy

  3
  3
  Posts
  125
  Views

  

  @SGaist -- Thank you for linking to QTIFW-166. This does appear to be talking about these issues. Sadly, the end solution they cite is precisely what doesn't work. '-platform' is an unrecognized argument with the version of the installer 'qt-opensource-linux-x64-5.6.2.run'. This is a seperate issue from the script not being able to uncheck 'Run Qt Creator' in the installer GUI, of course.

  My first guess is that the feature doesn't exist in the installer version I've got. I am wondering -- how do I check the version of the installer framework is being used with any given package? Maybe the installer framework version is too old on my 5.6.2.run file. Not that that would help much, since I am locked to this Qt version for my needs and I need a method of installing it over commandline without X server and without user interactivity.

  AD