Indeed, it's usually better to have git in between these two.

Qt creator seems to work. Therefore I am not worrying about the statistic plugin message.

@zeethree50 said in Libicu, needed by Qt5Core, compilation issues. Please help!! Worked fine in 18.04, but not 16.04.:

And it worked for me

Great, so please don't forget to mark your post as solved!

The following shows how much content the folder (or AppImage) will ultimately contain (for comparison with the above first step of staging).

In fact, I even had to abbreviate the listing below because the Qt forum disallows more than ~32K characters per post :)

AppImage_staging/ ├── app.desktop ├── app.png ├── AppRun -> usr/bin/app └── usr ├── bin │ ├── app │ ├── event_filter.o │ ├── gui_tests.o │ ├── libapp.so │ ├── libapp.so.1 │ ├── libapp.so.1.0 │ ├── libapp.so.1.0.0 │ ├── liblibstylesplugin.so │ ├── libminutil.so │ ├── libminutil.so.1 │ ├── libminutil.so.1.0 │ ├── libminutil.so.1.0.0 │ ├── libtestmain.so │ ├── libtestmain.so.1 │ ├── libtestmain.so.1.0 │ ├── libtestmain.so.1.0.0 │ ├── lib_tests │ ├── libutil.so │ ├── libutil.so.1 │ ├── libutil.so.1.0 │ ├── libutil.so.1.0.0 │ ├── main.o │ ├── Makefile │ ├── moc_event_filter.cpp │ ├── moc_event_filter.o │ ├── moc_gui_tests.cpp │ ├── moc_gui_tests.o │ ├── moc_predefs.h │ ├── provision.sh │ ├── qt.conf │ └── view_model_collection.o ├── lib │ ├── libicudata.so.56 │ ├── libicui18n.so.56 │ ├── libicuuc.so.56 │ ├── libQt5Core.so.5 │ ├── libQt5DBus.so.5 │ ├── libQt5Gui.so.5 │ ├── libQt5Network.so.5 │ ├── libQt5QmlModels.so.5 │ ├── libQt5Qml.so.5 │ ├── libQt5QmlWorkerScript.so.5 │ ├── libQt5QuickControls2.so.5 │ ├── libQt5Quick.so.5 │ ├── libQt5QuickTemplates2.so.5 │ ├── libQt5Svg.so.5 │ ├── libQt5Widgets.so.5 │ └── libQt5XcbQpa.so.5 ├── plugins │ ├── bearer │ │ ├── libqconnmanbearer.so │ │ ├── libqgenericbearer.so │ │ └── libqnmbearer.so │ ├── imageformats │ │ ├── libqgif.so │ │ ├── libqicns.so │ │ ├── libqico.so │ │ ├── libqjpeg.so │ │ ├── libqsvg.so │ │ ├── libqtga.so │ │ ├── libqtiff.so │ │ ├── libqwbmp.so │ │ └── libqwebp.so │ ├── platforminputcontexts │ │ ├── libcomposeplatforminputcontextplugin.so │ │ └── libibusplatforminputcontextplugin.so │ ├── platforms │ │ └── libqxcb.so │ ├── platformthemes │ │ └── libqgtk3.so │ └── xcbglintegrations │ ├── libqxcb-egl-integration.so │ └── libqxcb-glx-integration.so ├── qml │ ├── Qt │ │ └── labs │ │ ├── folderlistmodel │ │ │ ├── libqmlfolderlistmodelplugin.so │ │ │ ├── plugins.qmltypes │ │ │ └── qmldir │ │ └── settings │ │ ├── libqmlsettingsplugin.so │ │ ├── plugins.qmltypes │ │ └── qmldir │ ├── QtGraphicalEffects │ │ ├── Blend.qml │ │ ├── BrightnessContrast.qml │ │ ├── Colorize.qml │ │ ├── ColorOverlay.qml │ │ ├── ConicalGradient.qml │ │ ├── Desaturate.qml │ │ ├── DirectionalBlur.qml │ │ ├── Displace.qml │ │ ├── DropShadow.qml │ │ ├── FastBlur.qml │ │ ├── GammaAdjust.qml │ │ ├── GaussianBlur.qml │ │ ├── Glow.qml │ │ ├── HueSaturation.qml │ │ ├── InnerShadow.qml ... truncated ... │ │ │ │ ├── PictureSpecifics.qml │ │ │ │ ├── PictureSpecifics.qmlc │ │ │ │ ├── PieMenuSpecifics.qml │ │ │ │ ├── PieMenuSpecifics.qmlc │ │ │ │ ├── qtquickextras.metainfo │ │ │ │ ├── StatusIndicatorSpecifics.qml │ │ │ │ ├── StatusIndicatorSpecifics.qmlc │ │ │ │ ├── ToggleButtonSpecifics.qml │ │ │ │ └── ToggleButtonSpecifics.qmlc │ │ │ ├── Dial.qml │ │ │ ├── Dial.qmlc │ │ │ ├── Gauge.qml │ │ │ ├── Gauge.qmlc │ │ │ ├── libqtquickextrasplugin.so │ │ │ ├── PieMenu.qml │ │ │ ├── PieMenu.qmlc │ │ │ ├── plugins.qmltypes │ │ │ ├── Private │ │ │ │ ├── CircularButton.qml │ │ │ │ ├── CircularButton.qmlc │ │ │ │ ├── CircularButtonStyleHelper.qml │ │ │ │ ├── CircularButtonStyleHelper.qmlc │ │ │ │ ├── CircularTickmarkLabel.qml │ │ │ │ ├── CircularTickmarkLabel.qmlc │ │ │ │ ├── Handle.qml │ │ │ │ ├── Handle.qmlc │ │ │ │ ├── PieMenuIcon.qml │ │ │ │ ├── PieMenuIcon.qmlc │ │ │ │ ├── qmldir │ │ │ │ ├── TextSingleton.qml │ │ │ │ └── TextSingleton.qmlc │ │ │ ├── qmldir │ │ │ ├── StatusIndicator.qml │ │ │ ├── StatusIndicator.qmlc │ │ │ ├── ToggleButton.qml │ │ │ ├── ToggleButton.qmlc │ │ │ ├── TumblerColumn.qml │ │ │ ├── TumblerColumn.qmlc │ │ │ ├── Tumbler.qml │ │ │ └── Tumbler.qmlc │ │ ├── Layouts │ │ │ ├── libqquicklayoutsplugin.so │ │ │ ├── plugins.qmltypes │ │ │ └── qmldir │ │ ├── PrivateWidgets │ │ │ ├── libwidgetsplugin.so │ │ │ ├── plugins.qmltypes │ │ │ └── qmldir │ │ ├── Templates.2 │ │ │ ├── libqtquicktemplates2plugin.so │ │ │ ├── plugins.qmltypes │ │ │ └── qmldir │ │ └── Window.2 │ │ ├── libwindowplugin.so │ │ ├── plugins.qmltypes │ │ └── qmldir │ └── QtQuick.2 │ ├── libqtquick2plugin.so │ ├── plugins.qmltypes │ └── qmldir └── share ├── applications │ └── app.desktop └── icons └── hicolor └── 256x256 └── apps └── app.png

@Yalimyulad said in Post installing Qmake for new devices:

Is it possible to somehow copy the Qmake I have built from raspberry pi to my desktop?

Nothing is physically stopping you, but it won't work.

qmake is created and specific to the Qt FrameWork/Compiler used for that framework.
The compiler on your pi is not the same as the one you would use for cross compiling

If you want to really cross compile for the Pi , you will have to jump through some loops.
There are some guides out there for example this wiki entries

https://wiki.qt.io/Raspberry_Pi_Beginners_Guide
https://wiki.qt.io/RaspberryPi2EGLFS

@mrjj thank you :)

@vishbynature It's config.log file located in the same directory from which you called configure. It is a text file, nothing special. Look for compile errors in that file related to to what you need.

@CodeinSipper said in installing Qbluetooth module:

how to install it on windows?

Using Qt Maintenance Tool from your Qt set-up.

@Pablo-J-Rogina
I will look into it.

@vishbynature
I don't claim to understand what the best way to do whatever you want here is. Maybe @Pablo-J-Rogina's suggestion of a database. The one thing I can tell you is that achieving whatever you are attempting by seeking to byte #80 in a text file and overwriting what is there is not the right approach.

If you want some solution which involves sticking with text files, it should look something like: open the existing file for read, open a new file for write, read stuff from old and write to new, making whatever modifications you wish as you go along, close both, delete old file, rename new to old. A few more steps than you wanted! Or, if file not too large, read whole file into some memory structure, make your changes there, write whole memory structure back to the file, completely replacing it.

You should always use the full path to the qmake binary of the Qt version you want to use to build your project/library/module.

It's not a problem of Qt Creator. The mkspec used for the RPI3 is still valid unless your sysroot comes from a Debian Stretch were they have changed the library name.

You need to modify the mkspec under devices that matches the Rpi3

@Sivamani-V said in How to connect to mysql server in ubuntu 16.04?.:

QMYSQL Driver not loaded. Available drivers: QMYSQL QSQLITE QMYSQL3

This gets asked so many times, here & elsewhere. Googling for your message will bring up many hits. Under Linux/Ubuntu it's usually libmysqlclient or libqt5sql5-mysql or similar which is missing/has dependencies missing/wrong version.

Does the app work if you start it with --single-process added to the command line?

Hi @Tegan,

Not sure what the best approach is, but I'd:

check the installer's md5sum against https://download.qt.io/archive/qt/5.6/5.6.3/md5sums.txt compare the output of ldd qt-opensource-linux-x64-5.6.3.run on both hosts, then run the installer with gdb

Cheers.

I built qt and font show up now. Thanks a lot jsulm for the support.

I am experiencing this problem on 5.11.2 running Linux Mint. So it is still there.

Using the following formulation:
QColorDialog dlg(colored->getColor());
dlg.setOption(QColorDialog::DontUseNativeDialog);
dlg.setOption(QColorDialog::ShowAlphaChannel);
dlg.open(this,SLOT(slot_colorChanged(QColor)));
dlg.exec();

First problem: the dialog initializes with color black, not the given color. When pressing OK, the slot is triggered
but the color is always color white, whatever is selected in the dialg. So essentially it does not work at all.

using the formulation
QColor newColor = QColorDialog::getColor(m_color, this, QString(), QColorDialog::DontUseNativeDialog);
does work as was mentioned before

@raven-worx I don't have any experience with TTS either, also I can't find much info about the current infrastructure on Linux, resp. on KDE. I have installed speech-dispatcher. And I can make it speak in the terminal, using its own spd-say command. I'm not sure how speech-dispatcher and flite are related. I think speech-dispacher is an abstraction layer / daemon, and flite is one of several "engines" it can use.

spd-say --list-output-modules says:

OUTPUT MODULES
flite
cicero
generic
dummy
espeak

The following packages that seem to be relevant have been installed:

speech-dispatcher libspeechd2 flite libflite1 speech-dispatcher-flite libqt5texttospeech5 libqt5texttospeech5-dev qtspeech5-flite-plugin

Note that no qtspeech5-speechdispatcher-plugin (or similar) exists in the repo. But looking at the Qt Speech sources, it seems there should be such a plugin.

Anyways, when I build an application for testing ....

QTextToSpeech::availableEngines() returns "flite" availableLocales() gives "en_US" and availableVoices() says "kal16".