@sierdzio Thank you for all the info, I think I'll be able to take things on from here.

Have a lovely day :)

Indeed it is! :( It is something that we are looking into doing for certain this FY.

I'm running MacOS Mojave 10.14.5 and have Xcode 10.2 installed.
The reason for the above error is due to the configure option -c++std c++11. Removing that constraint allowed the build to progress. I got two further build errors:

In qtcanvas3d, which I was able to circumvent by skipping the module. In qtvirtualkeyboard, the hunspell include path incorrectly includes the hunspell subfolder since the header file refers to `hunspell/hunspell.h'. I hacked this by creating a subfolder and a symlink back to the header file in its original location.
(See error details below.)

With these workarounds, I was able to get a successful make using the following configuration: ../configure -qtlibinfix 5.14.1G -qtlibinfix-plugins -opensource -debug-and-release -developer-build -framework -pkg-config -nomake tests -skip qtandroidextras -skip qtwayland -skip qtwebchannel -skip qtwebengine -skip qtwebglplugin -skip qtwebview -skip qtwinextras -skip qtx11extras -skip qtcanvas3d

Expecting make install to install into the default -prefix location, I was disappointed to find that /usr/local did not contain any new Qt folders; neither Qt-5.14.1 nor Qt-5.14.1G were there, nor were there any other new folders there that might have come from the build. I'll need to debug this issue, but since I haven't used qmake before, I'll need to get familair with its way of doing things first, including understanding .pro files.

I am pleased to see that the significant outputs from my build are all marked with the suffix I asked for in the -qtlibinfix 5.14.1G -qtlibinfix-plugins configuration options. Hopefully this will make it easier to debug the qt_gui_cpp package in ROS Kinetic. What is nice is that the header I am having difficulties with in the ROS build compiled correctly in my Qt build. Thus I can be sure that until ROS builds, the error is in ROS not Qt.

Error (1) qtcanvas3d:

/Users/user/Programming/Qt/qt5/build/qtbase/bin/moc -DQT_NO_LINKED_LIST -DQT_NO_FOREACH -DQTCANVAS3D_LIBRARY -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_PLUGIN -DQT_OPENGLEXTENSIONS_LIB -DQT_QUICK_LIB -DQT_GUI_LIB -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB --include /Users/user/Programming/Qt/qt5/build/qtcanvas3d/src/imports/qtcanvas3d/.moc/debug/moc_predefs.h -I/Users/user/Programming/Qt/qt5/qtbase/mkspecs/macx-clang -I/Users/user/Programming/Qt/qt5/qtcanvas3d/src/imports/qtcanvas3d -I/Users/user/Programming/Qt/qt5/build/qtbase/include -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtOpenGLExtensions -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQuick -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtGui -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQmlModels -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQml/5.14.1 -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQml/5.14.1/QtQml -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQml -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtNetwork -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtCore/5.14.1 -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtCore/5.14.1/QtCore -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtCore -I. -I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1 -I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/10.0.1/include -I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include -F/Users/user/Programming/Qt/qt5/build/qtbase/lib -Muri=QtCanvas3D /Users/user/Programming/Qt/qt5/qtcanvas3d/src/imports/qtcanvas3d/glstatestore_p.h -o .moc/debug/moc_glstatestore_p.cpp /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -c -pipe -stdlib=libc++ -g -std=c++1y -fapplication-extension -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk -mmacosx-version-min=10.13 -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions -Wall -Wextra -Winconsistent-missing-override -Wobjc-interface-ivars -Wobjc-method-access -Wobjc-multiple-method-names -Werror=unguarded-availability -Werror=unguarded-availability-new -Werror=unsupported-availability-guard -fPIC -DQT_NO_LINKED_LIST -DQT_NO_FOREACH -DQTCANVAS3D_LIBRARY -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_PLUGIN -DQT_OPENGLEXTENSIONS_LIB -DQT_QUICK_LIB -DQT_GUI_LIB -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I/Users/user/Programming/Qt/qt5/qtcanvas3d/src/imports/qtcanvas3d -I. -I/Users/user/Programming/Qt/qt5/build/qtbase/include -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtOpenGLExtensions -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQuick -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtGui -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQmlModels -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQml/5.14.1 -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQml/5.14.1/QtQml -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQml -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtNetwork -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtCore/5.14.1 -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtCore/5.14.1/QtCore -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtCore -I.moc/debug -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/OpenGL.framework/Headers -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/AGL.framework/Headers -I/Users/user/Programming/Qt/qt5/qtbase/mkspecs/macx-clang -F/Users/user/Programming/Qt/qt5/build/qtbase/lib -o .obj/debug/moc_glstatestore_p.o .moc/debug/moc_glstatestore_p.cpp rm -f libqtcanvas3d_debug.dylib /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -stdlib=libc++ -headerpad_max_install_names -fapplication-extension -arch x86_64 -Wl,-syslibroot,/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk -mmacosx-version-min=10.13 -Wl,-rpath,@executable_path/../Frameworks -Wl,-rpath,/Users/user/Programming/Qt/qt5/build/qtbase/lib -single_module -dynamiclib -o libqtcanvas3d_debug.dylib .obj/debug/arrayutils.o .obj/debug/qcanvas3d_plugin.o .obj/debug/enumtostringmap.o .obj/debug/abstractobject3d.o .obj/debug/canvas3d.o .obj/debug/buffer3d.o .obj/debug/canvasrendernode.o .obj/debug/context3d.o .obj/debug/contextattributes.o .obj/debug/framebuffer3d.o .obj/debug/program3d.o .obj/debug/renderbuffer3d.o .obj/debug/shader3d.o .obj/debug/shaderprecisionformat.o .obj/debug/teximage3d.o .obj/debug/texture3d.o .obj/debug/uniformlocation.o .obj/debug/activeinfo3d.o .obj/debug/canvasglstatedump.o .obj/debug/compressedtextures3tc.o .obj/debug/compressedtexturepvrtc.o .obj/debug/glcommandqueue.o .obj/debug/renderjob.o .obj/debug/canvasrenderer.o .obj/debug/canvastextureprovider.o .obj/debug/glstatestore.o .obj/debug/openglversionchecker.o .obj/debug/moc_qcanvas3d_plugin.o .obj/debug/moc_abstractobject3d_p.o .obj/debug/moc_canvas3d_p.o .obj/debug/moc_buffer3d_p.o .obj/debug/moc_canvasrendernode_p.o .obj/debug/moc_context3d_p.o .obj/debug/moc_contextattributes_p.o .obj/debug/moc_framebuffer3d_p.o .obj/debug/moc_program3d_p.o .obj/debug/moc_renderbuffer3d_p.o .obj/debug/moc_shader3d_p.o .obj/debug/moc_shaderprecisionformat_p.o .obj/debug/moc_teximage3d_p.o .obj/debug/moc_texture3d_p.o .obj/debug/moc_uniformlocation_p.o .obj/debug/moc_activeinfo3d_p.o .obj/debug/moc_canvasglstatedump_p.o .obj/debug/moc_compressedtextures3tc_p.o .obj/debug/moc_compressedtexturepvrtc_p.o .obj/debug/moc_glcommandqueue_p.o .obj/debug/moc_canvasrenderer_p.o .obj/debug/moc_canvastextureprovider_p.o .obj/debug/moc_glstatestore_p.o -F/Users/user/Programming/Qt/qt5/build/qtbase/lib /Users/user/Programming/Qt/qt5/build/qtbase/lib/libQt5OpenGLExtensions5.14.1G_debug.a -framework QtQuick5.14.1G -framework QtGui5.14.1G -framework AppKit -framework Metal -framework QtQmlModels5.14.1G -framework QtQml5.14.1G -framework QtNetwork5.14.1G -framework QtCore5.14.1G -framework DiskArbitration -framework IOKit -framework OpenGL -framework AGL Undefined symbols for architecture x86_64: "QtCanvas3D::CanvasUniformLocation::staticMetaObject", referenced from: int qmlRegisterUncreatableType<QtCanvas3D::CanvasUniformLocation>(char const*, int, int, char const*, QString const&) in qcanvas3d_plugin.o QtPrivate::MetaObjectForType<QtCanvas3D::CanvasUniformLocation*, void>::value() in qcanvas3d_plugin.o "vtable for QtCanvas3D::CanvasUniformLocation", referenced from: QtCanvas3D::CanvasUniformLocation::CanvasUniformLocation(QtCanvas3D::CanvasGlCommandQueue*, QObject*) in uniformlocation.o QtCanvas3D::CanvasUniformLocation::~CanvasUniformLocation() in uniformlocation.o NOTE: a missing vtable usually means the first non-inline virtual member function has no definition. ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[5]: *** [/Users/user/Programming/Qt/qt5/build/qtbase/qml/QtCanvas3D/libqtcanvas3d_debug.dylib] Error 1 make[4]: *** [debug-all] Error 2 make[3]: *** [sub-qtcanvas3d-make_first] Error 2 make[2]: *** [sub-imports-make_first-ordered] Error 2 make[1]: *** [sub-src-make_first] Error 2 make: *** [module-qtcanvas3d-make_first] Error 2

Error (2) qtvirtualkeyboard:

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -c -include.pch/debug/QtHunspellInputMethod5.14.1G_debug_x86_64.pch/c++_x86_64 -pipe -stdlib=libc++ -g -std=c++1y -fapplication-extension -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk -mmacosx-version-min=10.13 -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions -Wall -Wextra -Winconsistent-missing-override -Wobjc-interface-ivars -Wobjc-method-access -Wobjc-multiple-method-names -Werror=unguarded-availability -Werror=unguarded-availability-new -Werror=unsupported-availability-guard -fPIC -DQT_NO_LINKED_LIST -DQT_NO_FOREACH -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_LINKED_LIST -DQHUNSPELLINPUTMETHOD_LIBRARY -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_BUILD_HUNSPELLINPUTMETHOD_LIB -DQT_BUILDING_QT -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x050000 -DQT_DEPRECATED_WARNINGS_SINCE=0x060000 -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_VIRTUALKEYBOARD_LIB -DQT_QUICK_LIB -DQT_GUI_LIB -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I/Users/user/Programming/Qt/qt5/qtvirtualkeyboard/src/plugins/hunspell/hunspellinputmethod -I. -I/Users/user/Programming/Qt/qt5/build/qtbase/include -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtHunspellInputMethod -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtHunspellInputMethod/5.14.1 -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtHunspellInputMethod/5.14.1/QtHunspellInputMethod -I/usr/local/Cellar/hunspell/1.6.2/include/hunspell -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtVirtualKeyboard/5.14.1 -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtVirtualKeyboard/5.14.1/QtVirtualKeyboard -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtGui/5.14.1 -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtGui/5.14.1/QtGui -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtVirtualKeyboard -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQuick -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtGui -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtCore/5.14.1 -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtCore/5.14.1/QtCore -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQmlModels -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtQml -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtNetwork -I/Users/user/Programming/Qt/qt5/build/qtbase/include/QtCore -I.moc/debug -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/OpenGL.framework/Headers -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/AGL.framework/Headers -I/Users/user/Programming/Qt/qt5/qtbase/mkspecs/macx-clang -F/Users/user/Programming/Qt/qt5/build/qtbase/lib -o .obj/debug/hunspellinputmethod.o /Users/user/Programming/Qt/qt5/qtvirtualkeyboard/src/plugins/hunspell/hunspellinputmethod/hunspellinputmethod.cpp In file included from /Users/user/Programming/Qt/qt5/qtvirtualkeyboard/src/plugins/hunspell/hunspellinputmethod/hunspellinputmethod.cpp:30: In file included from /Users/user/Programming/Qt/qt5/build/qtbase/include/QtHunspellInputMethod/5.14.1/QtHunspellInputMethod/private/hunspellinputmethod_p_p.h:1: In file included from /Users/user/Programming/Qt/qt5/build/qtbase/include/QtHunspellInputMethod/5.14.1/QtHunspellInputMethod/private/../../../../../../../qtvirtualkeyboard/src/plugins/hunspell/hunspellinputmethod/hunspellinputmethod_p_p.h:45: In file included from /Users/user/Programming/Qt/qt5/build/qtbase/include/QtHunspellInputMethod/5.14.1/QtHunspellInputMethod/private/hunspellworker_p.h:1: /Users/user/Programming/Qt/qt5/build/qtbase/include/QtHunspellInputMethod/5.14.1/QtHunspellInputMethod/private/../../../../../../../qtvirtualkeyboard/src/plugins/hunspell/hunspellinputmethod/hunspellworker_p.h:51:10: fatal error: 'hunspell/hunspell.h' file not found #include <hunspell/hunspell.h> ^~~~~~~~~~~~~~~~~~~~~ 1 error generated. make[6]: *** [.obj/debug/hunspellinputmethod.o] Error 1 make[5]: *** [debug-all] Error 2 make[4]: *** [sub-hunspellinputmethod-make_first] Error 2 make[3]: *** [sub-hunspell-make_first] Error 2 make[2]: *** [sub-plugins-make_first] Error 2 make[1]: *** [sub-src-make_first] Error 2 make: *** [module-qtvirtualkeyboard-make_first] Error 2

We had a similar problem. There does not appear to be any purpose for a lot of the stuff that Qt Creator piles into the ".app" file, and it interferes with Apple Notarization.

We solved the problem by simply creating a command file that deletes the conflicting files:

# Clean out detritus that prevents notarization cd foo.app find . -name "*.h" -delete find . -name "*.prl" -delete find . -name "*.cstemp" -delete find . -name "Headers" -delete find ./ -name "*_debug" -delete

Hi,

Check the QWidget::winId.

Screenshot 2020-04-11 at 5.13.33 PM.png

i am getting this error
i am using,

Qt Creator 4.11.2
Based on Qt 5.14.2 (Clang 10.0 (Apple), 64 bit)

Built on Mar 27 2020 02:24:45

From revision 699407b4ba

Copyright 2008-2020 The Qt Company Ltd. All rights reserved.

The program is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

Android Studio 3.6.2
please help
i am not able to create build for android in qt
thanks!!!!!

That's not valid css. border does not take 4 separate width parameters, only one shared across all sides. If you want to set borders different for each side you need to use border-width:

border: solid #000000; border-width: 0px 0px 2px 0px;

The Jenkins instance is hosted on a different server and is currently connected to several linux slaves that build properly. It's just the macos slave that has the issue.

It seems to be slow in both qmake and make steps.

We just found a solution that requires us to switch the user to itself before running the command.

sudo -u <loggedinuser> -i bash /script/containging/build/commands.sh

I'm not sure why this has to be done since we are already logged in as the user that we are switching to. My guess is that Apple enables certain restrictions for remote users.

Great question, @GerryH!

My impression is that the automotive industry is one of biggest customers for the Qt Company (TQtC) at the moment. 3D graphics and Qt Quick are vital to the automotive IVIs, so TQtC and their partners (like KDAB, a major contributor to Qt 3D) will continue to pour lots of resources into them. In general, I believe that any effort you invest into Qt Quick and Qt 3D is quite safe for the next 5-10 years.

The path forward isn't easy -- Vulkan, Metal, and DirectX 12 support are all far far behind the level of OpenGL support, so it will be years before they catch up. Nonetheless, my gut feeling tells me that dropping support for Apple is unthinkable, so TQtC will adapt to Apple's demands. And given Apple's history of viciously dropping backwards compatibility, the sense of urgency is definitely there.

Some possible ways forward are:

Use MoltenGL to keep the OpenGL backend usable on Apple platforms (TQtC either forms a direct partnership with Molten, or Qt customers buy MoltenGL themselves), OR Add abstraction layers to decouple Qt from OpenGL and add a Metal backend directly, OR Like #2 but provide a Vulkan backend for Qt 3D and Qt Quick, and then use MoltenVK to support Apple platforms (like how OpenGL + ANGLE is currently used to support Windows)

Personally, I think #3 makes most sense because Vulkan support directly benefits Qt on all platforms, not just Apple platforms. However, I can't tell if this is a feasible business strategy for TQtC or not, or what kind of tradeoffs exist compared to a direct Metal backend.

But anyway, for a more reliable source, this recent email from a TQtC employee suggests that they are currently planning the direct-Metal route: https://lists.qt-project.org/pipermail/interest/2018-December/063503.html There should be a more formal announcement sometime this year.

(Disclaimer: I, too, am a mere community member who lacks a crystal ball)

May I suggest to change for Python 3 ?
Python 2.7 will reached end of life next year so it's not a good idea to start a new project with it.

hmmm Common mistake. Qt Creator is not Qt. Now you can move the case to SOLVED.

Thank You @SGaist and @AndyS. I am able to get QToolButton of QTabBar by applying Fusion style.

I applied Fusion Style By:

#include "mainwindow.h" #include <QTimer> #include <QtGlobal> #include <QFile> #include <QLocale> #include <QSplashScreen> #include <QGuiApplication> #include <qstylefactory.h> int main(int argc, char *argv[]) { QLocale::setDefault(QLocale::system()); QApplication a(argc, argv); a.setStyle(QStyleFactory::create("Fusion")); MainWindow w; w.showMaximized(); return a.exec(); }

Thank you both very much for your help. I had a suspect that the problem was related to power saving because when on AC the problem was still present but intervals with no communication were shorter. Unfortunately I won't be able to test the solution in the linked page before a week or so. I will read something about App Nap in the meanwhile, now that I know what to look for :-)

@aha_1980 Thank you for exact answer. I am able to call the script with help of Qt creator Project settings.

@SGaist Thank you sir for your advise. I solve this issue. By mistake, I put the " \ (backward slash)" before LIBS variable in ChargeDischarge2 .pro file. Now project ChargeDischarge2 is build.

1st of all, thanks for your effort, I use LyX myself.

The doc says:

this indicates that the widget will paint over its entire area with opaque colors. The widget's area will initially be uninitialized

set the widget's Qt::WA_OpaquePaintEvent, avoiding any unnecessary overhead associated with repainting the widget's background

Meaning it is saying it won't bother painting a background but it's not committing to leaving the old painted background in place so I still think you are relying on undefined behaviour.

On the other hand, I think this also impacts the performance of widgets with Qt::WA_OpaquePaintEvent on macOS so it is probably worth highlighting it with a bug report and/or an email on the mailing list

Hi,

Do you mean you have two different executable started ?