Feed for discussion Qt General in project Qt.

post122697: Slogger to Slogger2

Manoj Chandran R — Wed, 26 Nov 2025 17:21:14 GMT

We are currently porting our application to QNX 7.1. Our application uses QNX slogger for logging, and as part of the migration, we need to port our logging mechanism as well. We understand that in the latest QNX versions, slogger is no longer available and has been replaced by slogger2.

Has anyone had experience migrating from slogger to slogger2-based logging?

post122372: Re: "How to" move a Qt Creator Project to QNX

Mustafa Calis — Mon, 11 Sep 2023 16:53:40 GMT

Hello Dennis,

Could you share your "qmake_qnx.pdf"? The link does not work anymore.

I am trying to migrate a Qt Creator Desktop project to QNX Momentics IDE.

Best regards,

MC

post121953: Qmake Path Issue

Manoj Chandran R — Tue, 11 Oct 2022 06:18:08 GMT

We installed the QT through QNX Software Center (fig QT_QNX)

We are using SDP 7.0 and QNX Momentics IDE (Version: 7.0.4.v201905030143) in our design.  During compilation, we are getting error in qmake.(fig 1)

We understand that it was because of some issue in setting the Environment variable of QT PATH (\qt\Qt5.6.2\win64\x86_64\target\x86\bin) in Momentics IDE.  We are using a ‘.bat’ file to set the required PATH for the project.  And from the .bat file, we open the Momentics IDE through the command “start %QNX_INSTALL%..\..\..\QNX\"QNX_Momentics_IDE"\qde.exe -data %XXX_ROOT%\.. -vmargs eclipse.p2.data.area=%QNX_INSTALL%..\..\..\QNX\"QNX_Momentics_IDE"\p2””.

In the “Environment tab” under project settings, we found that the toolchain path is prepended before the path we created with .bat file. We manually modified the PATH variable in IDE, by declaring the of QT PATH (\qt\Qt5.6.2\win64\x86_64\target\x86\bin) before the toolchain path. And the compilation was successful. (fig 2)

Could you please let us know, how we can solve the issue?  Also, is there any method to prepend the QT path variable before toolchain PATH from the .bat file?

post121952: Qmake Path Issue

Manoj Chandran R — Tue, 11 Oct 2022 06:14:02 GMT

We installed the QT through QNX software center (Fig QT_QNX).

We are using SDP 7.0 and QNX Momentics IDE (Version: 7.0.4.v201905030143) in our design.  During compilation, we are getting error in qmake.(fig 1)

We understand that it was because of some issue in setting the Environment variable of QT PATH (\qt\Qt5.6.2\win64\x86_64\target\x86\bin) in Momentics IDE.  We are using a ‘.bat’ file to set the required PATH for the project.  And from the .bat file, we open the Momentics IDE through the command “start %QNX_INSTALL%..\..\..\QNX\"QNX_Momentics_IDE"\qde.exe -data %XXX_ROOT%\.. -vmargs eclipse.p2.data.area=%QNX_INSTALL%..\..\..\QNX\"QNX_Momentics_IDE"\p2””.

In the “Environment tab” under project settings, we found that the toolchain path is prepended before the path we created with .bat file. We manually modified the PATH variable in IDE, by declaring the of QT PATH (\qt\Qt5.6.2\win64\x86_64\target\x86\bin) before the toolchain path. And the compilation was successful. (fig 2)

Could you please let us know, how we can solve the issue?  Also, is there any method to prepend the QT path variable before toolchain path from the .bat file?

Regards,

Manoj

post121812: How to run a Qt app on QNX 7

julien zhong — Fri, 03 Jun 2022 06:02:52 GMT

when I try to run the Qt app with following command

export LD_LIBRARY_PATH=/qt/lib

export QT_PLUGIN_PATH=/qt/plugins

export QML2_IMPORT_PATH=/qt/qml

export QT_QPA_FONTDIR=/qt/lib/fonts

export QT_DEBUG_PLUGINS=1

export QQNX_PHYSISCREEN_SIZE=150,100

export LD_DEBUG=1

random -p

waitfor /dev/random

waitfor /dev/slog2e

echo "starting the app"

/home/app/test

echo "the app started"

I got following errors

debug: Looking up symbol eglCreateSync

debug: Symbol eglCreateSync could not be resolved in this scope

NULL

debug: Looking up symbol eglDestroySync

debug: Symbol eglDestroySync could not be resolved in this scope

NULL

debug: Looking up symbol eglClientWaitSync

debug: Symbol eglClientWaitSync could not be resolved in this scope

NULL

debug: Looking up symbol eglGetSyncAttrib

debug: Symbol eglGetSyncAttrib could not be resolved in this scope

NULL

debug: Looking up symbol eglCreateImage

debug: Symbol eglCreateImage could not be resolved in this scope

NULL

debug: Looking up symbol eglDestroyImage

debug: Symbol eglDestroyImage could not be resolved in this scope

NULL

debug: Looking up symbol eglGetPlatformDisplay

debug: Symbol eglGetPlatformDisplay could not be resolved in this scope

NULL

debug: Looking up symbol eglCreatePlatformWindowSurface

debug: Symbol eglCreatePlatformWindowSurface could not be resolved in this scope

NULL

debug: Looking up symbol eglCreatePlatformPixmapSurface

debug: Symbol eglCreatePlatformPixmapSurface could not be resolved in this scope

NULL

debug: Looking up symbol eglWaitSync

debug: Symbol eglWaitSync could not be resolved in this scope

NULL

Process 1450012 (test) terminated SIGSEGV code=1 fltno=11 ip=00000001000788c0(/usr/lib/ldqnx-64.so.2@strlen+0x0000000000000000) mapaddr=00000000000788c0. ref=0000000000000000

Memory fault (core dumped)

post121480: Re: Building/Running Qt 5 on QNX SDP 7.1

cheng changnan(deleted) — Fri, 02 Jul 2021 03:15:28 GMT

Hi Daniel,

Did you make it?

post121020: Re: Building/Running Qt 5 on QNX SDP 7.1

Daniel Hines — Tue, 06 Oct 2020 18:18:26 GMT

I've been attempting to build Qt 5.15.1 for QNX 7.1, and I'm running into an issue that I don't know how to get around.

Preconditions:

The Qt 5.15 source code is downloaded into a source directory, and I've created separated build and install directories for Qt

Python 3.8 and ActivePerl have been installed as prerequisites for building Qt, and their paths have been added to the PATH variable

I'm using MinGW as the compiler

I've executed qnxsdp-env.bat

Procedure:

1) Execute configure.bat from the build directory "C:\Qt\qt-build-5.15.1-qnx-armle-v7-qcc>..\qt-everywhere-src-5.15.1\configure.bat -prefix ..\qt-install-5.15.1-qnx-armle-v7-qcc -platform win32-g++ -xplatform qnx-armle-v7-qcc -confirm-license -opensource"

2) After configure returns successfully, execute mingw32-make from the build directory "C:\Qt\qt-build-5.15.1-qnx-armle-v7-qcc>mingw32-make"

I've attached a build log, and the error output from the last command is shown below:

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: .obj/YarrInterpreter.obj: in function `JSC::Yarr::byteCompile(JSC::Yarr::YarrPattern&, WTF::BumpPointerAllocator*, JSC::NoLock*)':

YarrInterpreter.cpp:(.text+0x34a): undefined reference to `JSC::Yarr::wordUnicodeIgnoreCaseCharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrInterpreter.cpp:(.text+0x3a0): undefined reference to `JSC::Yarr::newlineCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrInterpreter.cpp:(.text+0x3f8): undefined reference to `JSC::Yarr::wordcharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: .obj/YarrJIT.obj: in function `JSC::Yarr::YarrPattern::newlineCharacterClass()':

YarrJIT.cpp:(.text._ZN3JSC4Yarr11YarrPattern21newlineCharacterClassEv[_ZN3JSC4Yarr11YarrPattern21newlineCharacterClassEv]+0x28): undefined reference to `JSC::Yarr::newlineCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: .obj/YarrJIT.obj: in function `JSC::Yarr::YarrPattern::wordUnicodeIgnoreCaseCharCharacterClass()':

YarrJIT.cpp:(.text._ZN3JSC4Yarr11YarrPattern39wordUnicodeIgnoreCaseCharCharacterClassEv[_ZN3JSC4Yarr11YarrPattern39wordUnicodeIgnoreCaseCharCharacterClassEv]+0x28): undefined reference to `JSC::Yarr::wordUnicodeIgnoreCaseCharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: .obj/YarrJIT.obj: in function `JSC::Yarr::YarrPattern::wordcharCharacterClass()':

YarrJIT.cpp:(.text._ZN3JSC4Yarr11YarrPattern22wordcharCharacterClassEv[_ZN3JSC4Yarr11YarrPattern22wordcharCharacterClassEv]+0x28): undefined reference to `JSC::Yarr::wordcharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: .obj/YarrPattern.obj: in function `JSC::Yarr::dumpCharacterClass(WTF::PrintStream&, JSC::Yarr::YarrPattern*, JSC::Yarr::CharacterClass*)':

YarrPattern.cpp:(.text+0x472): undefined reference to `JSC::Yarr::newlineCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text+0x4e0): undefined reference to `JSC::Yarr::digitsCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text+0x540): undefined reference to `JSC::Yarr::spacesCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text+0x5b8): undefined reference to `JSC::Yarr::wordcharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text+0x632): undefined reference to `JSC::Yarr::nonwordcharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text+0x6ac): undefined reference to `JSC::Yarr::wordUnicodeIgnoreCaseCharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text+0x726): undefined reference to `JSC::Yarr::nondigitsCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text+0x76e): undefined reference to `JSC::Yarr::nonspacesCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text+0x9f4): undefined reference to `JSC::Yarr::nonwordUnicodeIgnoreCaseCharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: .obj/YarrPattern.obj: in function `JSC::Yarr::YarrPattern::compile(WTF::String const&, void*)':

YarrPattern.cpp:(.text+0x17d8): undefined reference to `JSC::Yarr::newlineCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: .obj/YarrPattern.obj: in function `JSC::Yarr::YarrPatternConstructor::atomCharacterClassBuiltIn(JSC::Yarr::BuiltInCharacterClassID, bool)':

YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb]+0xf6): undefined reference to `JSC::Yarr::nondigitsCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb]+0x158): undefined reference to `JSC::Yarr::nonspacesCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb]+0x1e6): undefined reference to `JSC::Yarr::spacesCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb]+0x244): undefined reference to `JSC::Yarr::digitsCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb]+0x2b0): undefined reference to `JSC::Yarr::nonwordUnicodeIgnoreCaseCharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb]+0x432): undefined reference to `JSC::Yarr::wordcharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb]+0x4a0): undefined reference to `JSC::Yarr::wordUnicodeIgnoreCaseCharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomCharacterClassBuiltInENS0_23BuiltInCharacterClassIDEb]+0x52e): undefined reference to `JSC::Yarr::nonwordcharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: .obj/YarrPattern.obj: in function `JSC::Yarr::YarrPatternConstructor::atomBuiltInCharacterClass(JSC::Yarr::BuiltInCharacterClassID, bool)':

YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomBuiltInCharacterClassENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomBuiltInCharacterClassENS0_23BuiltInCharacterClassIDEb]+0xee): undefined reference to `JSC::Yarr::spacesCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomBuiltInCharacterClassENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomBuiltInCharacterClassENS0_23BuiltInCharacterClassIDEb]+0x150): undefined reference to `JSC::Yarr::digitsCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomBuiltInCharacterClassENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomBuiltInCharacterClassENS0_23BuiltInCharacterClassIDEb]+0x1ea): undefined reference to `JSC::Yarr::wordUnicodeIgnoreCaseCharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomBuiltInCharacterClassENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomBuiltInCharacterClassENS0_23BuiltInCharacterClassIDEb]+0x242): undefined reference to `JSC::Yarr::wordcharCreate()'

c:\Users\danhin\qnx710\\host\win64\x86_64\usr\bin\arm-unknown-nto-qnx7.1.0eabi-ld: YarrPattern.cpp:(.text._ZN3JSC4Yarr22YarrPatternConstructor25atomBuiltInCharacterClassENS0_23BuiltInCharacterClassIDEb[_ZN3JSC4Yarr22YarrPatternConstructor25atomBuiltInCharacterClassENS0_23BuiltInCharacterClassIDEb]+0x29a): undefined reference to `JSC::Yarr::newlineCreate()'

cc: c:/Users/danhin/qnx710//host/win64/x86_64/usr/bin/arm-unknown-nto-qnx7.1.0eabi-ld caught signal 1

mingw32-make[3]: *** [Makefile:1059: ../../lib/libQt5Qml.so.5.15.1] Error 1

mingw32-make[2]: *** [Makefile:102: sub-qml-make_first-ordered] Error 2

mingw32-make[1]: *** [Makefile:50: sub-src-make_first] Error 2

mingw32-make: *** [Makefile:340: module-qtdeclarative-make_first] Error 2

Any ideas as to what is going on?

Thanks

post120937: Re: Building/Running Qt 5 on QNX SDP 7.1

James McDonnell — Fri, 11 Sep 2020 21:21:28 GMT

Hi Daniel,

You'll need to re-build the Qt libraries with QNX 7.1. The ones in the Qt5 evaluation package will be built for QNX 7.0.

James

post120936: Building/Running Qt 5 on QNX SDP 7.1

Daniel Hines — Fri, 11 Sep 2020 20:33:52 GMT

Greetings QNX Developer Community:

Before getting to the meat of this post, I would like to clarify that I am a beginner with both Qt and QNX. I downloaded the evaluation of QNX 7.1, as well as an evaluation of Qt 5. Qt's official documentation for Qt for QNX says that it is supported for QNX 7.0. Is it possible to build/run Qt 5 on QNX 7.1? I haven't found any documentation/tutorials specifically for this. Just as a test, I attempted to build a simple HelloWorld Qt project against my QNX 7.1 install, and there were a bunch of errors on missing libraries. Upon further inspection, I found that the libraries were there, but they were different versions (i.e. libc.so.5 instead of libc.so.4, for example). At this point in time, I don't have any target hardware, as I was tasked with evaluating QNX and Qt for use in future projects.

Thanks,

Daniel

post119700: Re: Remote QT display / VNC

Sebastian Kranz — Wed, 08 May 2019 05:36:00 GMT

Hello,

we compiled Qt5.12.x and here the embedded vnc server works.

Another option is to use something like libvncserver and build up your own vnc server, which we are investigating at the moment. It works pretty well and there is also a webbrowser client, so any device can connect to a session.

Regards,

Sebastian

> Hi, We have a requirement to remote the display ... Target is QNX7, imx6 CPU.

>

> Using QNX6.6, we have found a small utility, rfbserv , on a demo to do the

> works....

> But now this utility is no more available on QNX7.0

>

> We have try to use the VNC embedded in qt, both compiling the 5.8 and 5.9

> with no results (see errors)

> Question is: is it possible to remote, in any way, the display using screen?

>

> Please help, thanks in advance

> Mario

>

post119597: Re: how to bring shell builtin into QNX 6.6 QT 5.3.1

mike scott(deleted) — Thu, 21 Mar 2019 06:27:56 GMT

> You can run "ls" and so on - can you run "ksh"?

Hi Malte Mundt,

As suggested, I tried "ksh", then no commands can be executed ever since. i.e., "ls" or "pwd" will bring the content of the current directory; then input "ksh", no response as expected; after that, "ls" or "pwd" also stops working.

I checked that the "ksh" is available @

# find -iname "ksh"

./proc/boot/ksh

./base/bin/ksh

Please advise, thanks in advance

Mike

post119580: Re: how to bring shell builtin into QNX 6.6 QT 5.3.1

Malte Mundt — Thu, 14 Mar 2019 11:04:45 GMT

You can run "ls" and so on - can you run "ksh"?

post119571: how to bring shell builtin into QNX 6.6 QT 5.3.1

mike scott(deleted) — Fri, 08 Mar 2019 06:49:10 GMT

Hi QNX,

       qnx sdp 6.6,

       BSP_ti-am335x-beaglebone_br-660_be-660_SVN797070_JBN574.zip

       beaglebone black Rev. C

       QT 5.3.1

I implemented a QT program similar to https://evileg.com/en/post/261/

input filesystem command such as "ls", which will list the files under current directory. and "pwd" will show the

current directory path. "ls" / "pwd" and lots of other commands are available @ /opt/qnx660/target/qnx6/armle-v7/bin, however there is no "cd" since 'cd' is a shell builtin.

Please advise how I can bring the shell environment into this QT program, in which then I am able to use "cd" to

change directories.

Thanks in advance

Mike

post119530: Re: Remote QT display / VNC

Dennis Kellly(deleted) — Tue, 19 Feb 2019 14:25:59 GMT

>>> open a support plan only for such utility can be a bit expensive

Agreed... but easiest.

>>> The other option should be a bit complicated to handle or maintain in the time.

Also agreed - its more work. Depends on if "apps" are in the future of your product.

If you go with the network data model, you have the option of using the QML as javascript on a webpage - or in a true mobile app.

post119529: Re: Remote QT display / VNC

mario sangalli — Tue, 19 Feb 2019 14:14:10 GMT

Thanks for the answer: open a support plan only for such utility can be a bit expensive ,

The other option should be a bit complicated to handle or mantains in the time.

mario

post119528: Re: Remote QT display / VNC

Dennis Kellly(deleted) — Tue, 19 Feb 2019 13:42:34 GMT

A new, optimized VNC server for screen (not Qt-based) is available via a QNX "custom support plan".

As an alternative you could consider driving your local UI via network 'localhost' - then build the same Qt app for Windows using a remote network connection. The two UI's would both be able to control the embedded system and stay "in sync".

post119527: Remote QT display / VNC

mario sangalli — Tue, 19 Feb 2019 09:23:24 GMT

Hi, We have a requirement to remote the display ... Target is QNX7, imx6 CPU.

Using QNX6.6, we have found a small utility, rfbserv , on a demo to do the works....

But now this utility is no more available on QNX7.0

We have try to use the VNC embedded in qt, both compiling the 5.8 and 5.9

with no results (see errors)

Question is: is it possible to remote, in any way, the display using screen?

Please help, thanks in advance

Mario

Running a QT 5.8.1:

---------------------------------

Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile))

Abort (core dumped)

Running QT 5.9.8:

---------------------------------

[12]/usr/local/Qt-5.9.8/examples/datavisualization/customproxy> ./customproxy -platform vnc

This plugin does not support createPlatformOpenGLContext!

This plugin does not support createPlatformOpenGLContext!

"Couldn't initialize the OpenGL context."

post119459: Re: why QT apps loss of integrated parts?

mike scott(deleted) — Wed, 30 Jan 2019 04:28:54 GMT

never mind,

after reboot the device, everything is working fine now.

Mike

post119453: why QT apps loss of integrated parts?

mike scott(deleted) — Tue, 29 Jan 2019 09:25:02 GMT

Hi QNX,

       qnx sdp 6.6, qnx sdk for apps and media 1.1,

       BSP_ti-am335x-beaglebone_br-660_be-660_SVN797070_JBN574.zip

       touchscreen 800x480

Following 《QNX SDK for Apps and Media 1.1 Getting Started》pp.39~40, I have built a target image for beaglebone black, which boot-up the device and started the QT gui program named Homescreen, as shown by the 1st attached image file "hmi.png".

However, the individual apps are not functioning right. For example, the helloworld app should looks like as 2nd attached image file "helloworld.png". On my screen, the blue squared parts are all missing, i.e., loss of "close application", "volume control" and qnx title.

Building process has been recorded in attached text file.

Please advise, thanks in advance

Mike

post118907: How to use QNX valgrind to check for qt sample app memory leaks?

Sangyool Lee(deleted) — Thu, 28 Jun 2018 08:32:59 GMT

I tried, but an error occurred.

# valgrind ./pcsi

==23269537== Memcheck, a memory error detector

==23269537== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.

==23269537== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info

==23269537== Command: ./pcsi

==23269537==

QML debugging is enabled. Only use this in a safe environment.

==23269537== Invalid read of size 8

==23269537==    at 0x3932C: ??? (in /lib64/libc.so.4)

==23269537==  Address 0x1965cd0 is 16 bytes before a block of size 40 alloc'd

==23269537==    at 0xC478C: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-arm64-nto.so)

==23269537==

==23269537== Invalid read of size 8

==23269537==    at 0x36A60: ??? (in /lib64/libc.so.4)

==23269537==  Address 0x1965cd0 is 16 bytes before a block of size 40 alloc'd

==23269537==    at 0xC478C: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-arm64-nto.so)

==23269537==

free malloc object that is not allocated:/builds/workspace/sdp700/build_aarch64/lib/c/alloc/dlist.c:1129

Killed

post118789: Sample build file

Asheesh Jain(deleted) — Wed, 25 Apr 2018 12:10:19 GMT

Dear All, I am new to QNX QT interaction, I want to create a QNX6.6 OS image with QT environment which runs on x86 CPU, If anyone can share it, please do the same. It would be very helpful to me... Thanks in advanced...

post118747: Re: Which Qt Creator version to match QNX Qt 5.3.1 development framework?

Dennis Kellly(deleted) — Thu, 05 Apr 2018 17:02:29 GMT

>>>3. I think the examples referred to in the guide are from Apps and Media 1.1.

Yes, If you install "apps and media 1.1", you will get a "qnx660\source" directory containing "appsmedia_qt_source_v1_1.zip". These are the source examples for AnM (not for CAR).

There is some additional info about using Qt Creator for QNX in this pdf - however Qt Creator keeps evolving - the doc has not :)

https://blackberry.watchdox.com/ngdox/viewer/b0b77c0e-f198-44a2-8248-39ae32e11a3a

.

post118746: Re: Which Qt Creator version to match QNX Qt 5.3.1 development framework?

James McDonnell — Thu, 05 Apr 2018 16:48:48 GMT

Qt Creator 3.2.1 matches QNX Qt 5.3.1.

1. Creator should be fine once you've set it up with QNX Qt 5.3.1.

2. No, the guide hasn't been updated for later versions of Qt Creator. :-(

3. I think the examples referred to in the guide are from Apps and Media 1.1. The guide is actually geared more toward this product. If you're using vanilla QNX 6.6.0, you can get generic Qt examples by installing the open source Qt 5.3.1 for Windows.

post118738: Which Qt Creator version to match QNX Qt 5.3.1 development framework?

Mike Yue — Thu, 05 Apr 2018 00:24:44 GMT

Hi All,

I planned to create a Qt demo app for QNX Car 2 platform(J6 based, QNX 6.6.0), so recently start working on Qt development.

I've downloaded and installed QNX Qt 5.3.1 development framework(from http://www.qnx.com/download/feature.html?programid=26835, assumed this is the most recent version for our QNX Qt development), and installed the opensource version Qt Creator(4.6.0, Based on Qt 5.10.1, was downloaded from https://www.qt.io/download#section-2)

So far there some questions:

1. While configuring the toolchain in Qt Creator for qmake, there was a error - "Invalid Qt Version".

    The error disappeared after I picked SDP folder "c:\QNX660"

    Wonder if the mismatch will affect Qt development following.

    Should I pick the appropriate Qt version while installing Qt Creator to override the Qt 5.3.1(which was from QNX)?

2. The Qt Developer's Guide(http://pegasus.ott.qnx.com/download/download/26837/Qt_Developers_Guide.pdf) is old, could match the Qt 5.3.1 development framework, but not Qt Creator .

    Is there an new version guide available?

3. The Qt 5.3.1(which was from QNX) doesn't come with the examples, which are referenced in the Qt Developer's Guide.

    Anywhere to find the Qt examples for QNX target?

Thank you for your time for these newbie's questions.

Mike

post118672: Re: RE: QT on IM.X6q with SDP 6.6

Dennis Kellly(deleted) — Wed, 14 Mar 2018 16:26:23 GMT

>>>Warning: "slog2info" is not found on the device

Just because slogger2 is running does not mean that slog2info is present.. Put it in /bin just to be sure.

Dennis

post118671: Re: RE: QT on IM.X6q with SDP 6.6

mario sangalli — Wed, 14 Mar 2018 14:58:09 GMT

I made /var/run as a writable regualr dir but with luck:

drwxrwxrwx 2 root root 4096 Dec 31 19:05 run

the same error occurs...

post118670: RE: QT on IM.X6q with SDP 6.6

Malte Mundt — Wed, 14 Mar 2018 14:17:22 GMT

AFAIR, when /tmp was pointing to /dev/shmem, it's not good for Qt. In /dev/shmem, it's not possible to create subdirectories, and that can be a problem for Qt. Make /tmp a writeable /tmp folder on a block device or devb ram disk at least.

> -----Original Message-----

> From: mario sangalli [mailto:community-noreply@qnx.com]

> Sent: Wednesday, March 14, 2018 3:14 PM

> To: general-qt <general-qt@community.qnx.com>

> Subject: Re: QT on IM.X6q with SDP 6.6

>

> Hi James,

>

> the  /var/run is writeable:

>

> lrwxrwxrwx   1 root      root              4 Mar 13  2018 run -> /tmp

>

> and also /tmp is writable:

>

> lrwxrwxrwx   1 root      root             10 Mar 13  2018 /tmp -> /dev/shmem

>

>

>

> _______________________________________________

>

> Qt General

> http://community.qnx.com/sf/go/post118669

> To cancel your subscription to this discussion, please e-mail general-qt-

> unsubscribe@community.qnx.com

post118669: Re: QT on IM.X6q with SDP 6.6

mario sangalli — Wed, 14 Mar 2018 14:13:51 GMT

Hi James,

the  /var/run is writeable:

lrwxrwxrwx   1 root      root              4 Mar 13  2018 run -> /tmp

and also /tmp is writable:

lrwxrwxrwx   1 root      root             10 Mar 13  2018 /tmp -> /dev/shmem

post118668: Re: QT on IM.X6q with SDP 6.6

James McDonnell — Wed, 14 Mar 2018 14:00:49 GMT

The slog2info message is probably not important.

Unfortunately, the Qt Creator QNX tests aren't complete. They don't verify that /var/run is writeable. Offhand, I don't recall if anything else is required. Try this first.

post118667: QT on IM.X6q with SDP 6.6

mario sangalli — Wed, 14 Mar 2018 11:44:29 GMT

We'are porting a QT application on our custom board based on IM..X 6q processor and QNX SDP6.6, following this guide:

http://doc.qt.io/qt-5/platform-notes-qnx.html

From QT Creator's Device test the target seem configured in the right way:

Connecting to host...

Checking kernel version...

QNX 6.6.0 i.MX6Q_Cpu_Coms

Checking if specified ports are available...

All specified ports are available.

Checking for awk...

awk found.

Checking for grep...

grep found.

Checking for kill...

kill found.

Checking for netstat...

netstat found.

Checking for print...

print found.

Checking for printf...

printf found.

Checking for ps...

ps found.

Checking for read...

read found.

Checking for sed...

sed found.

Checking for sleep...

sleep found.

Checking for uname...

uname found.

Checking for slog2info...

slog2info found.

Device test finished successfully.

But when I start debugging the QT application I get the following error showing in ApplicationOutput window:

Debugging starts

Preparing remote side...

Warning: "slog2info" is not found on the device, debug output not available!Debugging has finished

and an error window popup saying: ' Cannot continue debugged process: the program is not being run.'

The Slogger2 process and qconn are runnig on the target.

Any suggestions to solve the issue?

Regards.

post118565: Re: Building Qt 5.7.1 for QNX 6.6.0 armle-v7

Benedikt Franz(deleted) — Tue, 13 Feb 2018 08:19:26 GMT

Thanks, I just created a post.

Thanks again for your help!

post118561: Re: Building Qt 5.7.1 for QNX 6.6.0 armle-v7

Dennis Kellly(deleted) — Mon, 12 Feb 2018 12:16:19 GMT

If everything works (gles2gears, qt) then I suspect the messages are bogus - likely a bug perhaps already fixed. You might try posting to the discussion at http://community.qnx.com/sf/discussion/do/listTopics/projects.graphics/discussion.advanced_graphics... but not sure how well that discussion is monitored. If you post, stick to the simple case of the errors with gles2grears.

post118559: Re: Building Qt 5.7.1 for QNX 6.6.0 armle-v7

Benedikt Franz(deleted) — Mon, 12 Feb 2018 09:43:35 GMT

Thanks for the pdf, I got the font system to work with Qt now. Thanks a lot!!!

I still get that weird error about the glesv2-sc-dlls failing to load... The gles2gears example runs fine, but it does give me the same error message. I got the Qt hellowindow example to run ok, too, but also with the same error.

post118534: Re: Building Qt 5.7.1 for QNX 6.6.0 armle-v7

Dennis Kellly(deleted) — Fri, 09 Feb 2018 14:27:31 GMT

It sounds like the error occurs when gles2 is requjired. Widget programs, like the clock only require gles1. QML programs require gles2.

Try gles2-gears - it must work before you try QML programs!.

It "sounds like" your screen driver contains "mixed" version components.

D

post118533: Re: Building Qt 5.7.1 for QNX 6.6.0 armle-v7

Benedikt Franz(deleted) — Fri, 09 Feb 2018 14:21:17 GMT

Thanks. I didn't get an email yet.

Sorry, I didn't express myself very well. The error does occur for some programs, but not for others. It does always occur for the qt/examples/opengl/cube/cube binary. The analogclock binary never produces such an error.

post118532: Re: Building Qt 5.7.1 for QNX 6.6.0 armle-v7

Dennis Kellly(deleted) — Fri, 09 Feb 2018 14:12:29 GMT

I sent you a pdf vIa email containing more info about the QNX font system. Let me know if you don't get it.

Regarding the screen dll errors, I haven't encountered that. Since it only happens "sometimes", it sounds like timing.

Dennis

post118531: Re: Building Qt 5.7.1 for QNX 6.6.0 armle-v7

Benedikt Franz(deleted) — Fri, 09 Feb 2018 13:40:15 GMT

Okay guys, thanks for your help so far. The problem was indeed that the /usr/lib/libfontconfig.so and .so.1 were missing. I added them to my build and now I Qt does start up and show something (though not always) - analogclock does show something (I'll attach a screenshot, I have a sneaky feeling it's missing some letters?)

In general, fonts don't show. I noticed that the folder QT_QPA_FONTDIR=/home/qt5/lib/fonts doesn't exist. Did I miss something during my first build? I do have two files libfreetype.so and .so.1:

# ls -la /usr/lib/libfreetype.so*

-rwxr-xr-x 1 1002 1002 390379 Feb 23 2014 /usr/lib/libfreetype.so

-rwxr-xr-x 1 1002 1002 390379 Feb 23 2014 /usr/lib/libfreetype.so.1

I also sometimes get error messages about a missing library glesv2-sc-dlls:

libs: load_object: attempt load of /usr/lib/graphics/iMX6X/glesv2-sc-dlls

libs: dlopen: Library cannot be found

libs: dlopen("glesv2-sc-dlls",1536)

Mode: LOCAL GROUP

libs: load_object: attempt load of glesv2-sc-dlls

libs: dlopen: Library cannot be found

libs: dlopen("/usr/lib/graphics/iMX6X/glesv2-sc-dlls.so",1536)

Mode: LOCAL GROUP

libs: load_object: attempt load of /usr/lib/graphics/iMX6X/glesv2-sc-dlls.so

libs: dlopen: Library cannot be found

libs: dlopen("glesv2-sc-dlls.so",1536)

Mode: LOCAL GROUP

libs: load_object: attempt load of glesv2-sc-dlls.so

libs: dlopen: Library cannot be found

libs: dlopen("/usr/lib/graphics/iMX6X/libGLSLC.so",1536)

Mode: LOCAL GROUP

Thanks a lot!

post118530: Re: Building Qt 5.7.1 for QNX 6.6.0 armle-v7

Dennis Kellly(deleted) — Thu, 08 Feb 2018 16:29:29 GMT

You can get "could not find or load the Qt platform plugin "qnx"" if the freetype font system in non-functional.

post118529: Re: Building Qt 5.7.1 for QNX 6.6.0 armle-v7

James McDonnell — Thu, 08 Feb 2018 16:22:47 GMT

The target needs additional shared objects. Run the application with LD_DEBUG=libs (e.g., LD_DEBUG=libs analogClock). It'll tell you what's missing.

post118528: Building Qt 5.7.1 for QNX 6.6.0 armle-v7

Benedikt Franz(deleted) — Thu, 08 Feb 2018 16:17:31 GMT

I am trying to build Qt 5.7.1 for QNX 6.6.0 running atop an i.MX6q processor (armle-v7). Actually, the build itself succeeded, but Qt refuses to start up. Here's what I did:

I essentially followed the instructions found here:

http://wiki.qt.io/Building_Qt_for_QNX_Neutrino_OS

and here:

http://wiki.qt.io/QNX-App-development-and-deployment

I used git to check out version 5.7.1 to my Debian host system and built Qt as per the instructions in the Qt Wiki. I then uploaded the Qt build (the folders bin, doc, examples, include, lib, mkspecs and plugins) to the target board to local eMMC storage (/home/qt5, although I have tried /opt/qt/ before with the same result). I set up the envvars needed for Qt as follows:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/qt5/lib

export QT_PLUGIN_PATH=/home/qt5/plugins

export QML2_IMPORT_PATH=/home/qt5/qml

export QML_IMPORT_PATH=/home/qt5/imports

export QQNX_PHYSICAL_SCREEN_SIZE="217,136"

export QT_DEBUG_PLUGINS=1

export QT_QPA_PLATFORM_PLUGIN_PATH=/home/qt5/plugins

export QT_QPA_FONTDIR=/home/qt5/lib/fonts

When I try to run a Qt binary, I get the following error (see attached file for full dump):

Got keys from plugin meta data ("qnx")

QFactoryLoader::QFactoryLoader() checking directory path "/home/qt5/examples/gui/analogclock/platforms" ...

Cannot load library /home/qt5/plugins/platforms/libqqnx.so: (Library cannot be found)

QLibraryPrivate::loadPlugin failed on "/home/qt5/plugins/platforms/libqqnx.so" : "Cannot load library /home/qt5/plugins/platforms/libqqnx.so: (Library cannot be found)"

This application failed to start because it could not find or load the Qt platform plugin "qnx"

in "/home/qt5/plugins".

Those files are, however, exactly where they are supposed to be. Running ldd on the Qt binary didn't reveal any dead links, either. Screen does run and the gles-gears sample binaries work with no issues.

Please help. I'm stuck and I don't know what to do.

Thanks a lot!

post118354: RE: Is it possible to use newer compiler in QNX7 and Qt?

Vincent Hui(deleted) — Wed, 10 Jan 2018 02:08:50 GMT

Thank Malte Mundt.

I wish the compiler of QNX7 can be upgraded to gcc 5.5 very soon.

post118342: RE: Is it possible to use newer compiler in QNX7 and Qt?

Malte Mundt — Mon, 08 Jan 2018 08:16:43 GMT

I wouldn't say it is not possible. QNX offers Custom Support Plan contracts to supply whatever their users need, if it's outside that standard product. I am aware of several cases where updated compiler versions were made available for 6.x customers under a CSP plan, and I'm sure it can be done for 7 aswell. It's a matter of time and budget.

Cheers,

- Malte

From: James McDonnell [mailto:community-noreply@qnx.com]

Sent: Thursday, January 4, 2018 2:29 AM

To: general-qt <general-qt@community.qnx.com>

Subject: Re: Is it possible to use newer compiler in QNX7 and Qt?

Unfortunately, that's not possible. QNX only supports specific compiler versions.

From: community-noreply@qnx.com<mailto:community-noreply@qnx.com>

Sent: January 3, 2018 4:00 AM

To: general-qt@community.qnx.com<mailto:general-qt@community.qnx.com>

Reply-to: general-qt@community.qnx.com<mailto:general-qt@community.qnx.com>

Subject: Is it possible to use newer compiler in QNX7 and Qt?

I would like to use C++ 17 new features in QNX7 and Qt. Is it possible update gcc to 7.2 so that I use C++17 features?

Thanks

_______________________________________________

Qt General

http://community.qnx.com/sf/go/post118307

To cancel your subscription to this discussion, please e-mail general-qt-unsubscribe@community.qnx.com<mailto:general-qt-unsubscribe@community.qnx.com>

post118330: Re: Is it possible to use newer compiler in QNX7 and Qt?

James McDonnell — Thu, 04 Jan 2018 02:48:01 GMT

I suspect that's a long way off :-(.

From: community-noreply@qnx.com

Sent: January 3, 2018 8:46 PM

To: general-qt@community.qnx.com

Reply-to: general-qt@community.qnx.com

Subject: Re: Is it possible to use newer compiler in QNX7 and Qt?

Thank James.

Do you know when will compiler be changed to gcc 5.5 or higher version?

https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.5

_______________________________________________

Qt General

http://community.qnx.com/sf/go/post118329

To cancel your subscription to this discussion, please e-mail general-qt-unsubscribe@community.qnx.com

post118329: Re: Is it possible to use newer compiler in QNX7 and Qt?

Vincent Hui(deleted) — Thu, 04 Jan 2018 02:08:02 GMT

Thank James.

Do you know when will compiler be changed to gcc 5.5 or higher version?

https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.5

post118328: Re: Is it possible to use newer compiler in QNX7 and Qt?

James McDonnell — Thu, 04 Jan 2018 01:50:15 GMT

Unfortunately, that's not possible. QNX only supports specific compiler versions.

From: community-noreply@qnx.com

Sent: January 3, 2018 4:00 AM

To: general-qt@community.qnx.com

Reply-to: general-qt@community.qnx.com

Subject: Is it possible to use newer compiler in QNX7 and Qt?

I would like to use C++ 17 new features in QNX7 and Qt. Is it possible update gcc to 7.2 so that I use C++17 features?

Thanks

_______________________________________________

Qt General

http://community.qnx.com/sf/go/post118307

To cancel your subscription to this discussion, please e-mail general-qt-unsubscribe@community.qnx.com

post118307: Is it possible to use newer compiler in QNX7 and Qt?

Vincent Hui(deleted) — Wed, 03 Jan 2018 09:21:44 GMT

I would like to use C++ 17 new features in QNX7 and Qt. Is it possible update gcc to 7.2 so that I use C++17 features?

Thanks

post118277: Re: how to export qt environment

hu jiaqi — Fri, 15 Dec 2017 06:01:34 GMT

Hi Dennis:

I add QWS_MOUSE_PROTO="qnx:/dev/devi/touch0 qnx:/dev/devi/mouse0"

in [virtual=armle-v7,raw] .bootstrap = { } or

[+script] .script = {} ,then I build again the bsp,when the system restart ,

I run echo $QWS_MOUSE_PROTO ,it is empty.

Why it can not export in the build file?

So I using following command.The usb mouse work fine in the qt program

/bin/sh -c "/home/go.sh" &

# cat /home/go.sh

export QWS_MOUSE_PROTO="qnx:/dev/devi/touch0 qnx:/dev/devi/mouse0"

/home/test_program -qws &

post118275: Re: how to export qt environment

Dennis Kellly(deleted) — Thu, 14 Dec 2017 13:20:54 GMT

First, you do not waitfor the device /dev/devi/mouse0 to appear.  USB enumeration may take some time.

Second, In the build file, it is ineffective to use "export" - you are not in a shell.  Variables are set in the build fille environment without "export".  For example,

LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll:/lib/dll/pci

I suggest you put your Qt app call into a shell script, say "/proc/boot/go.sh".  Then you call it from the build file like

/bin/sh -c "/proc/boot/go.sh" &

You can use "sh" or "ksh" depending on your build.

post118272: how to export qt environment

hu jiaqi — Thu, 14 Dec 2017 09:48:45 GMT

Hello:

I am using qnx6.5 on am335x , I want to deploy qt program on it.

If I use the following command on console then the qt program can run with usb mouse support,the mouse can

move on the screen.

devi-hid -Pr mouse kbd

export QWS_MOUSE_PROTO="qnx:/dev/devi/touch0 qnx:/dev/devi/mouse0"

/home/test_program -qws

However, I want my qt program run after power up so I add the following line at the tail of my build file.

the usb mouse can not use,usb mouse can not move.

Can anyone tell me how to make the test_program run with usb mouse support after power up?

devi-hid -Pr mouse kbd

reopen /dev/ser1

[+session] sh &

export QWS_MOUSE_PROTO="qnx:/dev/devi/touch0 qnx:/dev/devi/mouse0"

/home/test_program -qws &

post117912: Re: How to get a screenshot of the window with area of OpenGL in QNX6.6?

Vova Beliy(deleted) — Wed, 26 Jul 2017 05:37:51 GMT

> I found in help how to make a screenshot of the display.

> http://www.qnx.com/developers/docs/6.6.0.update/index.html#com.qnx.doc.screen/topic/manual/cscreen_screenshot_disp_sample.html

post117906: Re: How to compile Qt5.8 for QNX7 ?

Dennis Kellly(deleted) — Tue, 25 Jul 2017 00:35:13 GMT

>>>Building for 64-bit targets (aarch64le or x86_64) is a bit more difficult because the mkspecs are currently broken.

According to https://bugreports.qt.io/browse/QTBUG-59644 64-bit compiles were fixed in Qt 5.9.1.

I built Qt 5.9.2 for x86_64 and had no issues.

post117788: Re: How to compile Qt5.8 for QNX7 ?

Claudia Choi — Tue, 13 Jun 2017 19:12:24 GMT

I followed the steps from Nicolas Pinault 03/31/2017 6:07 AM and was able to build Qt 58 successfully on 6.6 using mingw32.

post117713: How much is The QT5.3 Business? How to charge?

Li Chunmei(deleted) — Mon, 08 May 2017 01:34:18 GMT

How much is The QT5.3 Business License?

post117647: how many times can save ? when using Qt Enterprise compile QML

Li Chunmei(deleted) — Fri, 14 Apr 2017 09:47:18 GMT

I test the most simple QML demo startup costs for more than 1s，I want to know how many times can save when using Qt Enterprise compile QML?

In Analyze > QML Profiler:

All Before Creating time can save?

post117644: Re: How to combine Qml window and native openglES window better?

Dennis Kellly(deleted) — Thu, 13 Apr 2017 11:43:58 GMT

Guess it depends on what you are doing in the openGL window, but I assume it would be an independent thread controllable by the UI.

post117643: Re: How to combine Qml window and native openglES window better?

Li Chunmei(deleted) — Thu, 13 Apr 2017 01:25:35 GMT

Hi Dennis:

First thank you for your reply, should I Create a thread of native opengl window alone? Or like a normal QT Class registered to the QML? Excuse me, what kind of way of thinking is correct?

Thanks.

post117642: Re: QQnxScreen:failed to query screen mode. Using default value of 60Hz

Li Chunmei(deleted) — Thu, 13 Apr 2017 01:01:37 GMT

Hi：

You're right, so now I return to QT5.3, use native opengles2 development 3D, but I don't know how to combinate it and QML window together

post117637: Re: QQnxScreen:failed to query screen mode. Using default value of 60Hz

James McDonnell — Wed, 12 Apr 2017 12:20:46 GMT

The Qt planets example works with Qt Enterprise 5.6.2 on an OMAP5 board (TI-5432) with the Apps and Media 1.1 image. Any other example that I try produces "QOpenGLShader::link: "Link Error: Vertex shader is missing.\nLink Error: Fragment shader is missing.\n"" I'm guessing Qt does something that the QNX OpenGL implementation doesn't like :-(.

post117636: Re: How to combine Qml window and native openglES window better?

Dennis Kellly(deleted) — Wed, 12 Apr 2017 11:05:45 GMT

You can make opengl appear "on top" of qml by setting z-order.   Numeric number for z-order must be higher than your qml window (which is normally a low integer).

The following calls set size, position and z-order for your opengl window:

int wf_pos[2] = { WF_UL_X, WF_UL_Y };

int wf_size[2] = { WF_WIDTH, WF_HEIGHT };  // fixed

int zorder = 100;  // some default

        ...

if (wf_size[0] > 0 && wf_size[1] > 0)

{

rc = screen_set_window_property_iv(screen_win, SCREEN_PROPERTY_SIZE, wf_size);

if (rc)

{

perror("screen_set_window_property_iv(SCREEN_PROPERTY_SIZE)");

goto fail5;

}

}

else

{

rc = screen_get_window_property_iv(screen_win, SCREEN_PROPERTY_SIZE, wf_size);

if (rc)

{

perror("screen_get_window_property_iv(SCREEN_PROPERTY_SIZE)");

goto fail5;

}

}

if (wf_pos[0] != 0 || wf_pos[1] != 0)

{

rc = screen_set_window_property_iv(screen_win, SCREEN_PROPERTY_POSITION, wf_pos);

if (rc)

{

perror("screen_set_window_property_iv(SCREEN_PROPERTY_POSITION)");

goto fail5;

}

}

rc = screen_set_window_property_iv(screen_win, SCREEN_PROPERTY_ZORDER, &zorder);

if (rc)

{

perror("screen_set_window_property_iv(SCREEN_PROPERTY_ZORDER)");

goto fail5;

}

post117635: How to combine Qml window and native openglES window better?

Li Chunmei(deleted) — Wed, 12 Apr 2017 07:44:12 GMT

I use native openGLes API draws a 3D animation, I want to know how to make it and QML window stack up.

Thanks

post117634: Re: QQnxScreen:failed to query screen mode. Using default value of 60Hz

Li Chunmei(deleted) — Wed, 12 Apr 2017 07:30:36 GMT

My QNX6.6 currently run in Win 7 VM, but this is for debugging, my real work device is embedded ARMV7, and run Qt3D failed,

Maybe I should stick with QT5.3, but change the thinking development of 3D.

I am trying to now, do you have any good Suggestions can give me

post117632: Re: QQnxScreen:failed to query screen mode. Using default value of 60Hz

James McDonnell — Tue, 11 Apr 2017 13:29:05 GMT

I've run Qt3D applications (the planets example) on 6.6.0 but it's been a while since I did this.

I've used Qt 5.6.2 on 6.6.0 but I haven't used Qt3D 5.6.2 on 6.6.0.

Are you trying this in the virtual machine or an actual device? What kind of device?

post117620: Re: QQnxScreen:failed to query screen mode. Using default value of 60Hz

Li Chunmei(deleted) — Sat, 08 Apr 2017 15:24:08 GMT

Hi：

I am running a QML demo with Qt5.6.2, and have 3D.Core component in demo, I know the basic problem is that 3D run failed, but i do not know the reason.

can i use QT5.6.2 under QNX6.6 correctly? if not, what are the limits(3D part is the key point)?

post117615: Re: QQnxScreen:failed to query screen mode. Using default value of 60Hz

James McDonnell — Fri, 07 Apr 2017 13:04:16 GMT

The message isn't reporting a problem that would affect Qt3D functionality.

What are you running this on?

post117612: QQnxScreen:failed to query screen mode. Using default value of 60Hz

Li Chunmei(deleted) — Fri, 07 Apr 2017 03:19:08 GMT

Hi, all:

Due to the demand of the 3D,I compiling Qt5.6.2 under QNX6.6;

when i use Qt3D.Core or Qt3D.Render, run application in VM return error log:

QQnxScreen:failed to query screen mode. Using default value of 60Hz

and SceneLoader Component used in my application Status=Error;

What reason is this?

QNX6.6 does not support Such as the Qt3D.Core module development?

Who can give me some help.

Thanks.

post117609: Re: How to compile Qt5.8 for QNX7 ?

Li Chunmei(deleted) — Thu, 06 Apr 2017 08:25:09 GMT

Hello：

I compiled Qt5.6.2 succeeded; and specifies -opengl es2;

I think it is more convenient to use Qt5.6.2 development 3D, but failed, I'm in VM cannot be used SceneLoader components in QML;

Does not support openGL es2.0 ?

post117601: Re: How to compile Qt5.8 for QNX7 ?

James McDonnell — Wed, 05 Apr 2017 11:43:05 GMT

It should build with QNX 6.6. I'm not aware of any problems doing so but I haven't built the entirety of Qt 5.8 with 6.6 recently.

post117600: Re: How to compile Qt5.8 for QNX7 ?

Li Chunmei(deleted) — Wed, 05 Apr 2017 08:09:10 GMT

hello:

I want to know if I can be in compiling Qt5.8 under QNX6.6 ?

If can't, what are the limits?

Thanks.

post117594: Re: how to cross compiling assimp library?

Li Chunmei(deleted) — Sat, 01 Apr 2017 08:57:52 GMT

> The cmake toolchain at https://bugs.freedesktop.org/attachment.cgi?id=116103&

> action=edit is enough to get cmake to do the right thing.

>

> cmake -G "Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=<qnx-toolchain-file-path> <assimp-src-path>

>

> But with 3.3.1 source the make chokes and dies when it gets to BaseImporter.

> cpp. Code changes might be needed to get it to build for QNX 6.6.0 and you

> have to do something about the Boost dependency.

Hi:

As you say，build 3.3.1 get error about BaseImporter.cpp,but I build 3.1.1 or 3.2 get error about ImporterRegistry.cpp, I think this is caused by the same reason, I am looking for a solution.

Thanks

post117592: Re: how to cross compiling assimp library?

Li Chunmei(deleted) — Sat, 01 Apr 2017 03:56:33 GMT

> The cmake toolchain at https://bugs.freedesktop.org/attachment.cgi?id=116103&

> action=edit is enough to get cmake to do the right thing.

>

> cmake -G "Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=<qnx-toolchain-file-path> <assimp-src-path>

>

> But with 3.3.1 source the make chokes and dies when it gets to BaseImporter.

> cpp. Code changes might be needed to get it to build for QNX 6.6.0 and you

> have to do something about the Boost dependency.

I use cmake-gui Specify the toolchain-file, but get an error about "project files may be invalid",Similar to the attachment pictures

post117591: Re: how to cross compiling assimp library?

Li Chunmei(deleted) — Sat, 01 Apr 2017 03:07:45 GMT

> The cmake toolchain at https://bugs.freedesktop.org/attachment.cgi?id=116103&

> action=edit is enough to get cmake to do the right thing.

>

> cmake -G "Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=<qnx-toolchain-file-path> <assimp-src-path>

>

> But with 3.3.1 source the make chokes and dies when it gets to BaseImporter.

> cpp. Code changes might be needed to get it to build for QNX 6.6.0 and you

> have to do something about the Boost dependency.

Hi：

sorry, i want to know how to use Toolchain_QNX_660.cmake file Involved in your link?

thanks.

post117590: Re: How to use Qt delevop 3D under QNX system?

Li Chunmei(deleted) — Sat, 01 Apr 2017 03:01:51 GMT

> It might be easier to build Qt 5.6 yourself and utilize Qt 3D or Qt Quick 3D.

Hi：

are you compiling in QT5.6 under QNX6.6 platform successful?

post117589: Re: How to use Qt delevop 3D under QNX system?

Li Chunmei(deleted) — Sat, 01 Apr 2017 02:59:02 GMT

> It might be easier to build Qt 5.6 yourself and utilize Qt 3D or Qt Quick 3D.

I know 3D in Qt5.5 version above development are very friendly, what do you mean I compile a Qt5.6 version under the environment of QNX6.6? I don't know this way is workable

post117588: Re: how to cross compiling assimp library?

James McDonnell — Fri, 31 Mar 2017 21:35:00 GMT

The cmake toolchain at https://bugs.freedesktop.org/attachment.cgi?id=116103&action=edit is enough to get cmake to do the right thing.

cmake -G "Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=<qnx-toolchain-file-path> <assimp-src-path>

But with 3.3.1 source the make chokes and dies when it gets to BaseImporter.cpp. Code changes might be needed to get it to build for QNX 6.6.0 and you have to do something about the Boost dependency.

post117587: Re: How to use Qt delevop 3D under QNX system?

James McDonnell — Fri, 31 Mar 2017 20:11:04 GMT

It might be easier to build Qt 5.6 yourself and utilize Qt 3D or Qt Quick 3D.

post117581: Re: How to compile Qt5.8 for QNX7 ?

Nicolas Pinault — Fri, 31 Mar 2017 10:07:58 GMT

Good news !!! Qt applications are working correctly on the target !

Here are the steps I used to compile QT5.8 :

1) Install MinGW-W64 :

I use version 5.3.0 (Qt wiki says Qt5.8 needs 5.3.0).

If the installer works, you are lucky, else download the archive from Sourceforge. Here is the url I used : https://netcologne.dl.sourceforge.net/project/mingw-w64/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/sjlj/x86_64-5.3.0-release-win32-sjlj-rt_v4-rev0.7z

Extract the 7zip archive in c:\mingw-w64 (remove the first folder level of the archive when extracting).

2) Install Perl.

Select latest ActivestatePerl (as stated somewhere in Qt wiki)

3) Open a DOS box (command prompt)

4) Create root directory

z:

mkdir QNX7

cd QNX7

5) Get Qt source code

git clone git://code.qt.io/qt/qt5.git qt58

cd qt58

git checkout 5.8

perl init-repository --module-subset=default,-qtwebkit,-qtwebkit-examples,-qtwebengine,-qtwebchannel

6) Build Qt

cd ..

mkdir qt58-build

cd qt58-build

mkdir int result

cd int

set PATH=c:\mingw-w64\bin;%PATH%

c:\qnx700\qnxsdp-env.bat

..\..\qt58\configure.bat -extprefix z:\QNX7\qt58-build\result -xplatform qnx-armle-v7-qcc -opensource -confirm-license -release -nomake examples -nomake tests -force-debug-info -separate-debug-info

mingw32-make -j8

mingw32-make install

7) Configure momentics :

Open the Preferences Dialog Box (Window/Preferences)

Select Qt in the left list

Remove the default entry

Add a new entry : In location, select Bowse and go to Z:\QNX7\qt58-build\result\bin\qmake.exe

You're done.

post117580: how to cross compiling assimp library?

Li Chunmei(deleted) — Fri, 31 Mar 2017 05:51:43 GMT

Dear all:

I want to cross compile assimp library on Windows platforms by QT,and used to import 3D model;

but Cmake failed,can you give me some help about cross-compilation library

Thanks.

post117579: How to use Qt delevop 3D under QNX system?

Li Chunmei(deleted) — Fri, 31 Mar 2017 05:11:28 GMT

I use the Qt version is 5.3.1 through the QML drawing interface,want to drawing 3D model in QML,should I call opengles2.0 native interface, or Qt interface? How can I draw 3D model in QML and displayed on the screen QNX system?

post117576: Re: How to compile Qt5.8 for QNX7 ?

Nicolas Pinault — Thu, 30 Mar 2017 14:21:00 GMT

I'm building on Windows10.

Upgrading MinGW-W64 to 5.3.0 solved the problem.

I've made some great progress.

I believe I have a working flow now.

I'll publish all the details when I have confirmed that the binaries are usable on the target..

post117575: Re: How to compile Qt5.8 for QNX7 ?

James McDonnell — Thu, 30 Mar 2017 14:15:13 GMT

Uh, what version of Windows are you building on? That's a Windows function that needs at least Windows Vista (or Windows Server 2008). I suspect that Qt's minimum Windows version is Windows 7.

post117574: Re: How to compile Qt5.8 for QNX7 ?

Dennis Kellly(deleted) — Thu, 30 Mar 2017 10:46:03 GMT

Thanks James for these instructions. Worked perfectly on linux.

Only change I made was to put the default prefix at my traditional location (-prefix /opt/qt5).

post117573: Re: How to compile Qt5.8 for QNX7 ?

Nicolas Pinault — Thu, 30 Mar 2017 08:24:16 GMT

I still get the same error when running configure.bat. After a while, I get :

g++ -o "../bin/qmake.exe" project.o option.o property.o main.o ioutils.o proitems.o qmakevfs.o qmakeglobals.o qmakeparser.o qmakeevaluator.o qmakebuiltins.o makefile.o unixmake2.o unixmake.o mingw_make.o winmakefile.o projectgenerator.o meta.o makefiledeps.o metamakefile.o xmloutput.o pbuilder_pbx.o msvc_vcproj.o msvc_vcxproj.o msvc_nmake.o msvc_objectmodel.o msbuild_objectmodel.o qtextcodec.o qutfcodec.o qstring.o qstring_compat.o qstringbuilder.o qtextstream.o qiodevice.o qringbuffer.o qdebug.o qmalloc.o qglobal.o qarraydata.o qbytearray.o qbytearraymatcher.o qdatastream.o qbuffer.o qlist.o qfiledevice.o qfile.o qfilesystementry.o qfilesystemengine.o qfsfileengine.o qfsfileengine_iterator.o qregexp.o qvector.o qbitarray.o qdir.o qdiriterator.o quuid.o qhash.o qfileinfo.o qdatetime.o qstringlist.o qabstractfileengine.o qtemporaryfile.o qmap.o qmetatype.o qsettings.o qsystemerror.o qlibraryinfo.o qvariant.o qvsnprintf.o qlocale.o qlocale_tools.o qlinkedlist.o qnumeric.o qcryptographichash.o qxmlstream.o qxmlutils.o qlogging.o qjson.o qjsondocument.o qjsonparser.o qjsonarray.o qjsonobject.o qjsonvalue.o qfilesystemengine_win.o qfilesystemiterator_win.o qfsfileengine_win.o qlocale_win.o qsettings_win.o qsystemlibrary.o registry.o -static -s -lole32 -luuid -ladvapi32 -lkernel32 -Wl,--gc-sections

qsettings.o: In function `windowsConfigPath':

z:/QNX7/Qt/s/qtbase/src/corelib/io/qsettings.cpp:959: undefined reference to `SHGetKnownFolderPath'

collect2.exe: error: ld returned 1 exit status

Makefile:175: recipe for target '../bin/qmake.exe' failed

mingw32-make: *** [../bin/qmake.exe] Error 1

Building qmake failed, return code 2

Obviously, the problem appears at the link phase.

Does the MinGW-W64 version is of importance ?

post117571: Re: How to compile Qt5.8 for QNX7 ?

James McDonnell — Wed, 29 Mar 2017 16:24:26 GMT

I use MinGW-W64 (4.9.2) to build on Windows. On Windows, you have to use short paths or the Qt source paths get truncated because they're too deep. I tried the following just now (assumes 5.8 Qt source is in \QtD\58\s):

Open a MinGW-W64 terminal

%HOMEPATH%/qnx700/qnxsdp-env.bat

mkdir \QtD\58\qrai \QtD\58\qrar

cd \QtD\58\qrai

C:\QtD\58\s\configure.bat -prefix /usr/qt5 -extprefix C:\QtD\58\qrar -xplatform qnx-armle-v7-qcc -opensource -confirm-license -release -nomake examples -nomake tests -force-debug-info -separate-debug-info

make -j4 module-qtbase

make module-qtbase-install_subtargets

post117570: Re: How to compile Qt5.8 for QNX7 ?

Nicolas Pinault — Wed, 29 Mar 2017 15:05:55 GMT

I tried VS2015 but as expected, it does not work. MAKEFLAGS set in qnxsdp-env.bat is problematic.

I also tried with MinGW64 (modern MinGW) but got an error after a while.

Maybe I have to try with MinGW...

post117569: Re: How to compile Qt5.8 for QNX7 ?

James McDonnell — Wed, 29 Mar 2017 13:38:12 GMT

What's your host compiler? As far as I know, the only one that will work is MinGW.

post117567: Re: How to compile Qt5.8 for QNX7 ?

Nicolas Pinault — Wed, 29 Mar 2017 07:12:34 GMT

Hi James,

Thanks for your answer.

I'm currently using 32 bit arm target. So, I'm not concerned about 64 bit broken files.

However, I'm currently using Windows for dev. I am not successful cross compiling with Windows.

The commands you use are similar to the ones I use. I always end with an error somewhere.

Maybe I have to setup up a Linux box or VM.

Keep trying...

Nicolas

post117565: Re: How to compile Qt5.8 for QNX7 ?

James McDonnell — Tue, 28 Mar 2017 14:22:14 GMT

From git on...Linux?

source ~/qnx700/qnxsdp-env.sh

git clone git://code.qt.io/qt/qt5.git qt58

cd qt58

git checkout 5.8

./init-repository --module-subset=default,-qtwebkit,-qtwebkit-examples,-qtwebengine,-qtwebchannel

cd ..

mkdir qt58-build

cd qt58-build

mkdir int result

cd int

../../qt58/configure -prefix /usr/qt5 -extprefix $HOME/qt58-build/result -xplatform qnx-armle-v7-qcc -opensource -confirm-license -release -nomake examples -nomake tests -force-debug-info -separate-debug-info

make -j4

make install

Building for 64-bit targets (aarch64le or x86_64) is a bit more difficult because the mkspecs are currently broken.

Windows should be similar.

QtMultimedia won't work because the QNX Multimedia component hasn't been released yet. It'll build; it just won't be of any use.

You might have to drop other repositories if they won't build for QNX.

post117564: How to compile Qt5.8 for QNX7 ?

Nicolas Pinault — Tue, 28 Mar 2017 10:07:29 GMT

Anyone has a detailed procedure to compile Qt5.8 for QNX7 (armv7le) ?

Nicolas

post117545: Re: VMWare reference image can't be patched with patch 3875

James McDonnell — Thu, 16 Mar 2017 14:44:19 GMT

Hi Adam,

Try "mount -uw /base".

James

post117523: VMWare reference image can't be patched with patch 3875

Adam Treat — Sat, 11 Mar 2017 00:17:08 GMT

The latest reference image for QNX 6.6 vmware

<http://www.qnx.com/download/feature.html?programid=26854> can not be

patched according to instructions for patch 3875

<http://www.qnx.com/developers/articles/rel_5948_26.html#VMWARE> because

the root filesystem is read-only. How do I copy the files from the patch

over to the vmware target on a read only filesystem?

post117086: Re: How to get a screenshot of the window with area of OpenGL in QNX6.6?

Vova Beliy(deleted) — Fri, 04 Nov 2016 14:32:41 GMT

I found in help how to make a screenshot of the display.

http://www.qnx.com/developers/docs/660/index.jsp?topic=%2Fcom.qnx.doc.screen%2Ftopic%2Fmanual%2Fcscreen_screenshot_disp_sample.html

post117084: How to get a screenshot of the window with area of OpenGL in QNX6.6?

Vova Beliy(deleted) — Fri, 04 Nov 2016 07:35:06 GMT

Good day. I am writing an app under QNX6.6 - screenhot of the window, on which have is widget QGLWidget.

I can not make a screenshot of the window with area of OpenGL.

Here is the code in Qt:

-----------------------------------------------------

QPixmap pixmap;

QString file_image;

pixmap = QPixmap::grabWidget(QApplication::activeWindow(), this->pos().x(), this->pos().y(), this->width(), this->height());

file_image = QApplication::applicationDirPath() + "/screen_img.png");

pixmap.save(file_image, "PNG");

-----------------------------------------------------

The image is created, but instead of OpenGL - black area.

How in QNX6.6 get a screenshot of a window or of the entire display with area of OpenGL?

post114561: Unable to execute binary over NFS even with exec mount option

Tom Long(deleted) — Thu, 01 Oct 2015 16:00:34 GMT

Setup:

NFS share resides on Windows Server 2012

Target is QNX 6.5

Mount options used:      fs-nfs3 mynas:/myshare /mnt/mynas

Problem:

I am unable to execute a .out residing on the server.  I can read/write to the NFS just fine.  I can copy the binary down to the client and execute just fine.  But when I try to execute the binary I get the following error:

sh: mybinary.out: value too large to be stored in datatype

Things I've tried:

- Explicitly setting the "exec" option in a mount command.  I was sure this was the culprit, but no.

- Playing with every NFS setting there is.  I have the "Allow unmapped user Unix access" option checked.

- confirmed I have no ulimits set

post114389: Re: Screen command failed on QNX 6.6 VMWare

James McDonnell — Mon, 31 Aug 2015 16:46:21 GMT

"OpenGL Window Example" is a Qt example that comes with Qt Creator.  It uses direct GL calls to display a spinning triangle with a gradient fill.

To setup Qt in the running VM, I usually use an NFS share that maps the Qt base directory from my host to /Qt5 in the VM and then do the following exports:

  export QML_IMPORT_PATH=/Qt5/qml

  export QML2_IMPORT_PATH=/Qt5/qml

  export QT_LIB_PATH=/Qt5/lib

  export QT_LIBRARY_PATH=/Qt5/lib

  export QT_PLUGIN_PATH=/Qt5/plugins

  export QT_QPA_FONTDIR=/Qt5/lib/fonts

  export QT_QPA_PLATFORM=qnx:nofullscreen

  export QQNX_PHYSICAL_SCREEN_SIZE=277,159

This makes all of Qt available.  You could also copy Qt to the VM.

post114388: Re: Screen command failed on QNX 6.6 VMWare

Tran Hung(deleted) — Mon, 31 Aug 2015 16:25:23 GMT

Oh ! Thanks James for your information.I found the libQt5OpenGL in

directory : C:\QNX-qt\Qt-5.3.1-x86\lib.How to use Qt OpenGL on QNX ? Do QNX

support Qt OpenGL on QtQuick ? How to use openglwindow on Qt ? What's

include header files?

2015-08-31 22:46 GMT+07:00 James McDonnell <community-noreply@qnx.com>:

> Derived from QOpenGLWidiget? QNX doesn't support QOpenGLWidget :-(.

>

> Take a look at the slog2 output from the Qt application (slog2info) to see

> whether this is the case.

>

> Try the openglwindow example instead to see whether OpenGL is working. Or

> run the gles2-gears example (not a Qt application).

>

>

>

> _______________________________________________

>

> Qt General

> http://community.qnx.com/sf/go/post114387

> To cancel your subscription to this discussion, please e-mail

> general-qt-unsubscribe@community.qnx.com

>

post114387: Re: Screen command failed on QNX 6.6 VMWare

James McDonnell — Mon, 31 Aug 2015 15:46:22 GMT

Derived from QOpenGLWidiget? QNX doesn't support QOpenGLWidget :-(.

Take a look at the slog2 output from the Qt application (slog2info) to see whether this is the case.

Try the openglwindow example instead to see whether OpenGL is working. Or run the gles2-gears example (not a Qt application).

post114386: Re: Screen command failed on QNX 6.6 VMWare

Tran Hung(deleted) — Mon, 31 Aug 2015 15:03:00 GMT

Hi James !

Thanks for helping me.Today, i have fixed this problem.It seems like i

install patch graphics error.I'm trying to uninstall this patch and

reinstall it.I try again and succeed.

But i have a problem with deploy Qt Applications to QNX VMWare.I'm trying

to run Qt widget application with no add OpenGL module on QNX 6.6 VMWare

target.It run successfully.Then i'm trying to run Qt widget application

with add OpenGL module and format code is OpenGL ES.I'm run it on QNX 6.6

VMWare with commands :

- run gpu_drv

- run screen (QNX 6.6 VMWare Screen is black).

- run program ./sample_glwidget but nothing happened.

Can you guide me how to deploy Qt Application with OpenGL ES to QNX VMWare ?

2015-08-31 21:26 GMT+07:00 James McDonnell <community-noreply@qnx.com>:

> Hi Tran,

>

> I get the error you're seeing when I don't enable 3D graphics. Does VMWare

> Workstation allow you to check the box despite the "3D accelerations is not

> supported in this guest operating system" message? In VMWare Fusion, I'm

> able to do this and then screen is able to start. What's your host OS?

>

> I don't have TeamViewer.

>

> James

>

>

>

> _______________________________________________

>

> Qt General

> http://community.qnx.com/sf/go/post114385

> To cancel your subscription to this discussion, please e-mail

> general-qt-unsubscribe@community.qnx.com

>

post114385: Re: Screen command failed on QNX 6.6 VMWare

James McDonnell — Mon, 31 Aug 2015 14:26:19 GMT

Hi Tran,

I get the error you're seeing when I don't enable 3D graphics. Does VMWare Workstation allow you to check the box despite the "3D accelerations is not supported in this guest operating system" message? In VMWare Fusion, I'm able to do this and then screen is able to start. What's your host OS?

I don't have TeamViewer.

James

post114382: Re: Screen command failed on QNX 6.6 VMWare

Tran Hung(deleted) — Sat, 29 Aug 2015 15:50:58 GMT

i tried :

export GRAPHICS_ROOT=/usr/lib/graphics/vmware

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$GRAPHICS_ROOT

and

echo $GRAPHICS_ROOT

result : /usr/lib/graphics/vmware

echo $LD_LIBRARY_PATH

result : usr/lib:/lib:/lib/dll:/usr/lib/graphics/vmware

but i still get the error : no gpu support

2015-08-29 22:46 GMT+07:00 Hung Tran <hungelc18@gmail.com>:

> Hi Dannis !

> Thank you very much.

> - I used QNX SDP 6.6 runtime ISO for VMWare.Links download here :

> http://www.qnx.com/download/feature.html?programid=26217

> - I installed with many options :

> Guest operating systems : Other.Version : Other.

> Memory : 2GB

> Processors : 4

> Hard Disk (IDE) : 20GB

> - I install qnx-sdp-6.6 and qnx-sdk-for-apps-and-media for windows

> host.And i install patch-660-3875-660-Graphics-GA with applypatch command.

> - I copy files to VMWare

> Host (under *$QNX_TARGET/*)Virtual machine (under root directory(/) )

> etc/system/config/scaling.confetc/system/config/scaling.conf

> usr/share/gles/textures/brick_wall.tga

> usr/share/gles/textures/brick_wall.tgausr/share/gles/textures/bubble.png

> usr/share/gles/textures/bubble.pngusr/share/images/wallpaper.jpg

> usr/share/images/wallpaper.jpgx86/bin/screeninfobin/screeninfo

> x86/lib/dll/libwfdcfg-sample.solib/dll/libwfdcfg-sample.so

> x86/lib/dll/screen-gles1.solib/dll/screen-gles1.so

> x86/lib/dll/screen-gles2blt.solib/dll/screen-gles2blt.so

> x86/lib/dll/screen-gles2.solib/dll/screen-gles2.sox86/lib/dll/screen-sw.so

> lib/dll/screen-sw.sox86/lib/libgestures.so.1lib/libgestures.so.1

> x86/lib/libinputevents.so.1lib/libinputevents.so.1x86/lib/libkalman.so.1

> lib/libkalman.so.1x86/lib/libmtouch-calib.so.1lib/libmtouch-calib.so.1

> x86/lib/libmtouch-devi.so.1lib/libmtouch-devi.so.1

> x86/lib/libmtouch-fake.so.1lib/libmtouch-fake.so.1

> x86/lib/libmtouch-inject.so.1lib/libmtouch-inject.so.1x86/sbin/gpu_drv

> sbin/gpu_drvx86/sbin/screensbin/screenx86/usr/bin/calib-touch

> usr/bin/calib-touchx86/usr/bin/display_imageusr/bin/display_image

> x86/usr/bin/egl-configsusr/bin/egl-configsx86/usr/bin/eventsusr/bin/events

> x86/usr/bin/font-freetypeusr/bin/font-freetypex86/usr/bin/gles1-gears

> usr/bin/gles1-gearsx86/usr/bin/gles2-gearsusr/bin/gles2-gears

> x86/usr/bin/gles2-mazeusr/bin/gles2-mazex86/usr/bin/gpudbgusr/bin/gpudbg

> x86/usr/bin/print-gesturesusr/bin/print-gesturesx86/usr/bin/screenshot

> usr/bin/screenshotx86/usr/bin/sw-vsyncusr/bin/sw-vsyncx86/usr/bin/vkey

> usr/bin/vkeyx86/usr/bin/yuv-testusr/bin/yuv-test

> x86/usr/lib/graphics/vmware/graphics.conf

> usr/lib/graphics/vmware/graphics.conf

> x86/usr/lib/graphics/vmware/libAtcDecompressor.so

> usr/lib/graphics/vmware/libAtcDecompressor.so

> x86/usr/lib/graphics/vmware/libAtcDecompressor.so.1

> usr/lib/graphics/vmware/libAtcDecompressor.so.1

> x86/usr/lib/graphics/vmware/libegl_gallium.so

> usr/lib/graphics/vmware/libegl_gallium.so

> x86/usr/lib/graphics/vmware/libHwEGL.sousr/lib/graphics/vmware/libHwEGL.so

> x86/usr/lib/graphics/vmware/libHwglapi.so

> usr/lib/graphics/vmware/libHwglapi.so

> x86/usr/lib/graphics/vmware/libHwGLESv1_CM_g.so

> usr/lib/graphics/vmware/libHwGLESv1_CM_g.so

> x86/usr/lib/graphics/vmware/libHwGLESv1_CM.so

> usr/lib/graphics/vmware/libHwGLESv1_CM.so

> x86/usr/lib/graphics/vmware/libHwGLESv2.so

> usr/lib/graphics/vmware/libHwGLESv2.so

> x86/usr/lib/graphics/vmware/libHwGPU.sousr/lib/graphics/vmware/libHwGPU.so

> x86/usr/lib/graphics/vmware/libHwWFDvmware.so

> usr/lib/graphics/vmware/libHwWFDvmware.so

> x86/usr/lib/graphics/vmware/libllvmpipe_drv.so

> usr/lib/graphics/vmware/libllvmpipe_drv.so

> x86/usr/lib/graphics/vmware/libmesa_texcompress_atc.so

> usr/lib/graphics/vmware/libmesa_texcompress_atc.so

> x86/usr/lib/graphics/vmware/libmesa_texcompress_pvrt.so

> usr/lib/graphics/vmware/libmesa_texcompress_pvrt.so

> x86/usr/lib/graphics/vmware/libmesa_texcompress.so

> usr/lib/graphics/vmware/libmesa_texcompress.so

> x86/usr/lib/graphics/vmware/libpipe_vmwgfx_drv.so

> usr/lib/graphics/vmware/libpipe_vmwgfx_drv.so

> x86/usr/lib/graphics/vmware/libst_HwGL_g.so

> usr/lib/graphics/vmware/libst_HwGL_g.so

> x86/usr/lib/graphics/vmware/libst_HwGL.so

> usr/lib/graphics/vmware/libst_HwGL.so

> x86/usr/lib/graphics/vmware/libvmwsvga.so

> usr/lib/graphics/vmware/libvmwsvga.sox86/usr/lib/libEGL.so.1

> usr/lib/libEGL.so.1x86/usr/lib/libGLESv1_CL.so.1usr/lib/libGLESv1_CL.so.1

> x86/usr/lib/libGLESv1_CM.so.1usr/lib/libGLESv1_CM.so.1

> x86/usr/lib/libGLESv2.so.1usr/lib/libGLESv2.so.1x86/usr/lib/libscreen.so.1

> usr/lib/libscreen.so.1x86/usr/lib/libswblit.so.1usr/lib/libswblit.so.1

> x86/usr/lib/libWFD.so.1usr/lib/libWFD.so.1x86/lib/libgestures.so

> lib/libgestures.sox86/lib/libinputevents.solib/libinputevents.so

> x86/lib/libkalman.solib/libkalman.sox86/lib/libmtouch-calib.so

> lib/libmtouch-calib.sox86/lib/libmtouch-devi.solib/libmtouch-devi.so

> x86/lib/libmtouch-fake.solib/libmtouch-fake.sox86/lib/libmtouch-inject.so

> lib/libmtouch-inject.sox86/usr/lib/libEGL.sousr/lib/libEGL.so

> x86/usr/lib/libGLESv1_CL.sousr/lib/libGLESv1_CL.so

> x86/usr/lib/libGLESv1_CM.sousr/lib/libGLESv1_CM.sox86/usr/lib/libGLESv2.so

> usr/lib/libGLESv2.sox86/usr/lib/libscreen.sousr/lib/libscreen.so

> x86/usr/lib/libswblit.sousr/lib/libswblit.sox86/usr/lib/libWFD.so

> usr/lib/libWFD.so- Then i enable 3D graphics on VMWare but i have a

> warning : 3D accelerations is not supported in this guest operating system.

> - On QNX VMWare i run commands :

> login root

> gpu_drv

> screen

> and i have error no gpu support.Now, i download the new image on link

> http://www.qnx.com/download/feature.html?programid=26854 and install it

> for VMWare ? Thanks for helping me.I'm sorry for my bad english

>

> 2015-08-29 21:21 GMT+07:00 Dennis Kellly <community-noreply@qnx.com>:

>

>> Hi Tran-

>>

>> Does this VMware image run? Perhaps you can use it as a model.

>>

>> http://www.qnx.com/download/feature.html?programid=26854

>>

>> Dennis

>>

>>

>>

>> _______________________________________________

>>

>> Qt General

>> http://community.qnx.com/sf/go/post114380

>> To cancel your subscription to this discussion, please e-mail

>> general-qt-unsubscribe@community.qnx.com

>>

>

>

post114381: Re: Screen command failed on QNX 6.6 VMWare

Tran Hung(deleted) — Sat, 29 Aug 2015 15:46:46 GMT

Hi Dannis !

Thank you very much.

- I used QNX SDP 6.6 runtime ISO for VMWare.Links download here :

http://www.qnx.com/download/feature.html?programid=26217

- I installed with many options :

Guest operating systems : Other.Version : Other.

Memory : 2GB

Processors : 4

Hard Disk (IDE) : 20GB

- I install qnx-sdp-6.6 and qnx-sdk-for-apps-and-media for windows host.And

i install patch-660-3875-660-Graphics-GA with applypatch command.

- I copy files to VMWare

Host (under *$QNX_TARGET/*)Virtual machine (under root directory(/) )

etc/system/config/scaling.confetc/system/config/scaling.conf

usr/share/gles/textures/brick_wall.tgausr/share/gles/textures/brick_wall.tga

usr/share/gles/textures/bubble.pngusr/share/gles/textures/bubble.png

usr/share/images/wallpaper.jpgusr/share/images/wallpaper.jpg

x86/bin/screeninfobin/screeninfox86/lib/dll/libwfdcfg-sample.so

lib/dll/libwfdcfg-sample.sox86/lib/dll/screen-gles1.so

lib/dll/screen-gles1.sox86/lib/dll/screen-gles2blt.so

lib/dll/screen-gles2blt.sox86/lib/dll/screen-gles2.solib/dll/screen-gles2.so

x86/lib/dll/screen-sw.solib/dll/screen-sw.sox86/lib/libgestures.so.1

lib/libgestures.so.1x86/lib/libinputevents.so.1lib/libinputevents.so.1

x86/lib/libkalman.so.1lib/libkalman.so.1x86/lib/libmtouch-calib.so.1

lib/libmtouch-calib.so.1x86/lib/libmtouch-devi.so.1lib/libmtouch-devi.so.1

x86/lib/libmtouch-fake.so.1lib/libmtouch-fake.so.1

x86/lib/libmtouch-inject.so.1lib/libmtouch-inject.so.1x86/sbin/gpu_drv

sbin/gpu_drvx86/sbin/screensbin/screenx86/usr/bin/calib-touch

usr/bin/calib-touchx86/usr/bin/display_imageusr/bin/display_image

x86/usr/bin/egl-configsusr/bin/egl-configsx86/usr/bin/eventsusr/bin/events

x86/usr/bin/font-freetypeusr/bin/font-freetypex86/usr/bin/gles1-gears

usr/bin/gles1-gearsx86/usr/bin/gles2-gearsusr/bin/gles2-gears

x86/usr/bin/gles2-mazeusr/bin/gles2-mazex86/usr/bin/gpudbgusr/bin/gpudbg

x86/usr/bin/print-gesturesusr/bin/print-gesturesx86/usr/bin/screenshot

usr/bin/screenshotx86/usr/bin/sw-vsyncusr/bin/sw-vsyncx86/usr/bin/vkey

usr/bin/vkeyx86/usr/bin/yuv-testusr/bin/yuv-test

x86/usr/lib/graphics/vmware/graphics.conf

usr/lib/graphics/vmware/graphics.conf

x86/usr/lib/graphics/vmware/libAtcDecompressor.so

usr/lib/graphics/vmware/libAtcDecompressor.so

x86/usr/lib/graphics/vmware/libAtcDecompressor.so.1

usr/lib/graphics/vmware/libAtcDecompressor.so.1

x86/usr/lib/graphics/vmware/libegl_gallium.so

usr/lib/graphics/vmware/libegl_gallium.so

x86/usr/lib/graphics/vmware/libHwEGL.sousr/lib/graphics/vmware/libHwEGL.so

x86/usr/lib/graphics/vmware/libHwglapi.so

usr/lib/graphics/vmware/libHwglapi.so

x86/usr/lib/graphics/vmware/libHwGLESv1_CM_g.so

usr/lib/graphics/vmware/libHwGLESv1_CM_g.so

x86/usr/lib/graphics/vmware/libHwGLESv1_CM.so

usr/lib/graphics/vmware/libHwGLESv1_CM.so

x86/usr/lib/graphics/vmware/libHwGLESv2.so

usr/lib/graphics/vmware/libHwGLESv2.so

x86/usr/lib/graphics/vmware/libHwGPU.sousr/lib/graphics/vmware/libHwGPU.so

x86/usr/lib/graphics/vmware/libHwWFDvmware.so

usr/lib/graphics/vmware/libHwWFDvmware.so

x86/usr/lib/graphics/vmware/libllvmpipe_drv.so

usr/lib/graphics/vmware/libllvmpipe_drv.so

x86/usr/lib/graphics/vmware/libmesa_texcompress_atc.so

usr/lib/graphics/vmware/libmesa_texcompress_atc.so

x86/usr/lib/graphics/vmware/libmesa_texcompress_pvrt.so

usr/lib/graphics/vmware/libmesa_texcompress_pvrt.so

x86/usr/lib/graphics/vmware/libmesa_texcompress.so

usr/lib/graphics/vmware/libmesa_texcompress.so

x86/usr/lib/graphics/vmware/libpipe_vmwgfx_drv.so

usr/lib/graphics/vmware/libpipe_vmwgfx_drv.so

x86/usr/lib/graphics/vmware/libst_HwGL_g.so

usr/lib/graphics/vmware/libst_HwGL_g.so

x86/usr/lib/graphics/vmware/libst_HwGL.so

usr/lib/graphics/vmware/libst_HwGL.so

x86/usr/lib/graphics/vmware/libvmwsvga.so

usr/lib/graphics/vmware/libvmwsvga.sox86/usr/lib/libEGL.so.1

usr/lib/libEGL.so.1x86/usr/lib/libGLESv1_CL.so.1usr/lib/libGLESv1_CL.so.1

x86/usr/lib/libGLESv1_CM.so.1usr/lib/libGLESv1_CM.so.1

x86/usr/lib/libGLESv2.so.1usr/lib/libGLESv2.so.1x86/usr/lib/libscreen.so.1

usr/lib/libscreen.so.1x86/usr/lib/libswblit.so.1usr/lib/libswblit.so.1

x86/usr/lib/libWFD.so.1usr/lib/libWFD.so.1x86/lib/libgestures.so

lib/libgestures.sox86/lib/libinputevents.solib/libinputevents.so

x86/lib/libkalman.solib/libkalman.sox86/lib/libmtouch-calib.so

lib/libmtouch-calib.sox86/lib/libmtouch-devi.solib/libmtouch-devi.so

x86/lib/libmtouch-fake.solib/libmtouch-fake.sox86/lib/libmtouch-inject.so

lib/libmtouch-inject.sox86/usr/lib/libEGL.sousr/lib/libEGL.so

x86/usr/lib/libGLESv1_CL.sousr/lib/libGLESv1_CL.so

x86/usr/lib/libGLESv1_CM.sousr/lib/libGLESv1_CM.sox86/usr/lib/libGLESv2.so

usr/lib/libGLESv2.sox86/usr/lib/libscreen.sousr/lib/libscreen.so

x86/usr/lib/libswblit.sousr/lib/libswblit.sox86/usr/lib/libWFD.so

usr/lib/libWFD.so- Then i enable 3D graphics on VMWare but i have a warning

: 3D accelerations is not supported in this guest operating system.

- On QNX VMWare i run commands :

login root

gpu_drv

screen

and i have error no gpu support.Now, i download the new image on link

http://www.qnx.com/download/feature.html?programid=26854 and install it for

VMWare ? Thanks for helping me.I'm sorry for my bad english

2015-08-29 21:21 GMT+07:00 Dennis Kellly <community-noreply@qnx.com>:

> Hi Tran-

>

> Does this VMware image run? Perhaps you can use it as a model.

>

> http://www.qnx.com/download/feature.html?programid=26854

>

> Dennis

>

>

>

> _______________________________________________

>

> Qt General

> http://community.qnx.com/sf/go/post114380

> To cancel your subscription to this discussion, please e-mail

> general-qt-unsubscribe@community.qnx.com

>

post114380: Re: Screen command failed on QNX 6.6 VMWare

Dennis Kellly(deleted) — Sat, 29 Aug 2015 14:21:24 GMT

Hi Tran-

Does this VMware image run? Perhaps you can use it as a model.

http://www.qnx.com/download/feature.html?programid=26854

Dennis

post114379: Re: Screen command failed on QNX 6.6 VMWare

Tran Hung(deleted) — Sat, 29 Aug 2015 14:15:34 GMT

Hi James !

Thanks for the help.I tried and failed.

[image: Hình ảnh nội tuyến 1]

I'm trying install QNX 6.6 for VMWare and i installed

patch-660-3875-660-Graphics-GA

[image: Hình ảnh nội tuyến 1]

After, I copied the files in the guide at links

http://www.qnx.com/developers/articles/rel_5948_26.html.

And i enable 3D graphics on VMWare but when i run "screen" commands, i get

error :

[image: Hình ảnh nội tuyến 2]

I recheck graphics on vmware and found a warning :

[image: Hình ảnh nội tuyến 3]

Can you teach me how to enable 3D graphics ? I want to build Qt5 with GUI

for QNX 6.6 VMWare.I installed Qt5.3.1 and QNX SDP.I build a

program successfull.Can you teach me how to run it on QNX 6.6 VMWare ? Can

you help me used through TeamViewer ?

2015-08-26 19:51 GMT+07:00 James McDonnell <community-noreply@qnx.com>:

> Hi Tran,

>

> Try this instead:

>     export GRAPHICS_ROOT=/usr/lib/graphics/vmware

>     export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$GRAPHICS_ROOT

>     gpu_drv

>     screen

>

> James

>

>

>

> _______________________________________________

>

> Qt General

> http://community.qnx.com/sf/go/post114346

> To cancel your subscription to this discussion, please e-mail

> general-qt-unsubscribe@community.qnx.com

>

post114346: Re: Screen command failed on QNX 6.6 VMWare

James McDonnell — Wed, 26 Aug 2015 12:51:24 GMT

Hi Tran,

Try this instead:

    export GRAPHICS_ROOT=/usr/lib/graphics/vmware

    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$GRAPHICS_ROOT

    gpu_drv

    screen

James

post114344: Screen command failed on QNX 6.6 VMWare

Tran Hung(deleted) — Wed, 26 Aug 2015 10:05:29 GMT

Hi all !

In QNX 6.6 i run screen command error Memory fault (core dumped) on QNX 6.6 VMWare.

How to fix it ? Thanks you.

post114169: Re: AnM asked for QT5.3.1 libraries while Qt5.3.0 is installed

siowlim chow(deleted) — Tue, 28 Jul 2015 02:51:22 GMT

By compiling individual apps and then copied the Homescreen apps to the respective directory and finally re-made the sysImage, everything works as it should now.

post114168: Re: AnM asked for QT5.3.1 libraries while Qt5.3.0 is installed

siowlim chow(deleted) — Tue, 28 Jul 2015 02:01:41 GMT

Having recompiled from source Qt5.3.1, the missing error due Qt5.3.1 earlier have not resolved. However, homescreen is still there.

>>skipped missing item: usr/anm/bin/homescreen

The AnM screen is still showing blank after the bootscripts and invocation of all relevant drivers. Attached is the screen display. FYI, the system was running, just without showing anything on screen. How do I know, because I can ssh to it.

Any comments or suggestions please?

post114163: AnM asked for QT5.3.1 libraries while Qt5.3.0 is installed

siowlim chow(deleted) — Mon, 27 Jul 2015 04:35:47 GMT

HI there,

I tried to mksysimage AnM for VMware with the following command.

mksysimage.sh -P AnM -o output_dir -k

"-b base_dir/target/qnx6/x86/boot/sys/ipl-diskpc1" vmware.ext -f

And I have Qt5.3.0 installed. Strangely, during the compilation, it shown the following messages which was looking for 5.3.1 libraries. Of course, they are not available.

Has anyone experienced this before? Does anyone know how to resolve this issues? QNX has only released Qt5.3.0. Does that mean, I would need to install Qt5.3.1?

Any comments or suggestions are very appreciated.

[info]: Generating Archive...

Locating files...

Warning: /home/qws/qnx/6.60/target/qnx6/x86/lib/libmtouch-virtual.so is a symlink file

Warning: /home/qws/qnx/6.60/target/qnx6/x86/lib/libvmmouse.so is a symlink file

Warning: /home/qws/qnx/6.60/target/qnx6/x86/lib/libves-client.so is a symlink file

skipped missing item: lib/libQt5CLucene.so.5.3.1

skipped missing item: lib/libQt5Concurrent.so.5.3.1

skipped missing item: lib/libQt5Core.so.5.3.1

skipped missing item: lib/libQt5Gui.so.5.3.1

skipped missing item: lib/libQt5Help.so.5.3.1

skipped missing item: lib/libQt5MultimediaQuick_p.so.5.3.1

skipped missing item: lib/libQt5Multimedia.so.5.3.1

skipped missing item: lib/libQt5MultimediaWidgets.so.5.3.1

skipped missing item: lib/libQt5Network.so.5.3.1

skipped missing item: lib/libQt5OpenGL.so.5.3.1

skipped missing item: lib/libQt5Positioning.so.5.3.1

skipped missing item: lib/libQt5Qml.so.5.3.1

skipped missing item: lib/libQt5QuickParticles.so.5.3.1

skipped missing item: lib/libQt5Quick.so.5.3.1

skipped missing item: lib/libQt5QuickTest.so.5.3.1

skipped missing item: lib/libQt5QuickWidgets.so.5.3.1

skipped missing item: lib/libQt5Script.so.5.3.1

skipped missing item: lib/libQt5ScriptTools.so.5.3.1

skipped missing item: lib/libQt5Sensors.so.5.3.1

skipped missing item: lib/libQt5Sql.so.5.3.1

skipped missing item: lib/libQt5Svg.so.5.3.1

skipped missing item: lib/libQt5Test.so.5.3.1

skipped missing item: lib/libQt5Widgets.so.5.3.1

skipped missing item: lib/libQt5XmlPatterns.so.5.3.1

skipped missing item: lib/libQt5Xml.so.5.3.1

skipped missing item: plugins/mediaservice/libqtmedia_qnx.so

skipped missing item: usr/anm/bin/homescreen

post114063: How to read this scripts?

siowlim chow(deleted) — Fri, 03 Jul 2015 12:11:01 GMT

The is the deploymment.pri file under qnx660/source/qt/src/MediaPlayer. I am trying to understand how this actually work. See the comments after arrows. The target is x86 QnX, it is neither Android nor Android with no SDK. Does it mean it is Unix?

  isEmpty(target.path) {

        qnx {

            target.path = /tmp/$${TARGET}/bin

        } else {

            target.path = /opt/$${TARGET}/bin

        }

android-no-sdk {               <- For Android with no SDK

    target.path = /data/user/qt

    export(target.path)

    INSTALLS += target

} else:android {                 <- For Android

    x86 {

        target.path = /libs/x86

    } else: armeabi-v7a {

        target.path = /libs/armeabi-v7a

    } else {

        target.path = /libs/armeabi

    }

    export(target.path)

    INSTALLS += target

} else:unix {            <- For Unix.

    isEmpty(target.path) {

        qnx {

            target.path = /tmp/$${TARGET}/bin

        } else {

            target.path = /opt/$${TARGET}/bin

        }

        export(target.path)

    }

    INSTALLS += target

}

export(INSTALLS)

post114052: Qmake not executable - need advice please

siowlim chow(deleted) — Wed, 01 Jul 2015 13:05:35 GMT

I downloaded the Qt binaries from QNX and installed it without getting any errors. I then installed Qt-creator from

Ubuntu repository as well as the qnx-plugin. However, when I was setting up Qt development environment, like Qt version, I chose qt-qnx/Qt-5.3.1-x86/bin/qmake, it responded with qmake not executable. However, I tested it by running the qmake from command line, and it works.

I uninstalled it and reinstalled in different folder. Yet I got the same outcome- qmake not executable. However,

Qtcreator does detect the other qmake in /usr/lib/x86_64-linux-gnu/qt5/bin.

1. Why the former qmake is detected as not executable? how to resolve it?

2. Which qmake should I use? the from from Qnx or the one from Ubuntu? Logically it should be the from Qnx. Otherwise, please let me know why?

Thank you

post114051: Qmake not executable - need advice please

siowlim chow(deleted) — Wed, 01 Jul 2015 12:58:15 GMT

I downloaded the Qt 5.3.1 binaries from QNX and installed it without getting any errors. I then installed Qt-creator from Ubuntu repository as well as the qnx-plugin. However, when I was setting up Qt development environment, like Qt version, I chose qt-qnx/Qt-5.3.1-x86/bin/qmake, it responded qmake not executable. However, I tested it by running the qmake from command line, and it works.

I uninstalled it and reinstalled in different folder. Yet I got the same outcome- qmake not executable. However,

Qtcreator does detect the other qmake in /usr/lib/x86_64-linux-gnu/qt5/bin.

1. Why the former qmake is detected as not executable? how to resolve it?

2. Which qmake should I use? the from from Qnx or the one from Ubuntu? Logically it should be the from Qnx. Otherwise, please let me know why?

Thank you

post113807: Re: Compiling Qt 5.4.0 for QNX

Sandy Kellagher — Wed, 13 May 2015 10:36:10 GMT

Hi Scott,

You may already have solved this since your last post, but the reason moc.exe is failing is that it needs some libs from the mingw distribution.

I had the same problem, and copying libgcc_s_dw2-1.dll, libstdc++-6.dll and libwinpthread-1.dll from the mingw bin directory to the same directory as moc.exe fixed the problem.

Cheers

Sandy

post113702: Re: Application run taking a lot of time

Malte Mundt — Tue, 14 Apr 2015 12:16:03 GMT

> I'm developping a Qt app on Qnx, using Qt open source.

> When I start my app, it takes so much time loading lib etc... (used lib : core

> gui xml sql network printsupport)

Well, while Qt is well suited for Embedded deployment, it is also heavily used in Desktop enviroments with fast HDD/SSDs. I've seen very popular apps like VLC Media Player or Skype - they are using Qt AFAIK - load a long time even on a fast Windows PC. So this is kinda expected and the main question is on which system you are working and from where you are loading. You can't expect very fast loading e.g. from an older SD Card. Getting a newer Class 10 / HC card already might help.

> Is it possible to make Qt load the minimal library needed : core gui for

> example just to display the starting screen... and then load the rest ?

It is possible, but it is not very simple. You would need to dynamically open the needed libraries at runtime instead of letting the linker load them. If there is a "starting screen", maybe it would make sense to use the QNX native 'screen' (graphics subsystem) API to just display this starting screen - this will need very short time. While the screen.. or better said: image, is there, you could then load your main application.

You also could write a different small, invisible application that loads all the needed Qt libraries. When later your real application is being started, the libs will already be in memory. Or they will at least be in the block cache of your devb driver (if you are using one), so make sure the cache is e.g. 64M - sometimes I've seen people trying to save space in the wrong spot and only specify a cache of, e.g., 2M, which doesn't make sense on a system with 1024M of RAM.

Of course, if 'fast boot' is what you need, I'd go a different way and engage directly with QNX. QNX offers a 'CSP', short for Custom Support Plan, which includes development and consulting work of all kind. They can tune your system to boot very fast, and use only the libs you really need. Mind you, QNX has tons of experience in multi-million Automotive projects where fast booting (e.g. in 2s incl. graphics) is needed. By ordering a CSP you can benefit from this huge pool of experience and knowledge.

Cheers!

post113606: Re: Font issues with qt5.3.0 with qnx6.6.0

rafael gonzalez(deleted) — Thu, 26 Mar 2015 10:11:04 GMT

thanks. you are correct i have to set the physical screen dimension not the resolution of the screen.

the letters are now readable.

post113605: Re: Font issues with qt5.3.0 with qnx6.6.0

Malte Mundt — Thu, 26 Mar 2015 09:42:34 GMT

In your script, the setting for the screen size is wrong. It's for a reason that it is called "physical" screen size. You should not enter the resolution, but the screen dimensions in millimeters. Not sure what Qt does with it, but it absolutely does influence the sizes of fonts being rendered!

post113604: Re: Font issues with qt5.3.0 with qnx6.6.0

rafael gonzalez(deleted) — Thu, 26 Mar 2015 09:38:49 GMT

i manually adjusted the properties of the text box and button on my main window.

i tried to modify the stylesheet for the filedialog box but it doesn't do anything.

post113601: Re: Font issues with qt5.3.0 with qnx6.6.0

Dennis Kellly(deleted) — Wed, 25 Mar 2015 21:21:50 GMT

You should be able to adjust the font for the widget containing the text by clicking on the "stylesheet" property in Creator.

post113595: Font issues with qt5.3.0 with qnx6.6.0

rafael gonzalez(deleted) — Wed, 25 Mar 2015 14:54:58 GMT

I have a test application with a button that just opens a file dialog.

all the fonts that get loaded are really small.

how do i fix this?

i have attached a picture of my start up script

and a copy of what it looks like running.

post113519: Application run taking a lot of time

Thilloy Paul — Mon, 09 Mar 2015 09:40:03 GMT

Hello,

I'm developping a Qt app on Qnx, using Qt open source.

When I start my app, it takes so much time loading lib etc... (used lib : core gui xml sql network printsupport)

Is it possible to make Qt load the minimal library needed : core gui for example just to display the starting screen... and then load the rest ?

Regards,

Paul

post113454: Re: Qt 5.2.0 dev env for linux with target binaries/plugins dependent in libstdc++ and not libstdcpp(-ne)

Steven Zajac(deleted) — Mon, 02 Mar 2015 15:14:06 GMT

If anyone else is trying to do this, here is our solution:

Follow the steps as in the Qt 5.2.0 build instructions here: http://community.qnx.com/sf/wiki/do/viewPage/projects.qt/wiki/Qt5.2.0BuildInstructionsForQNXSDKForAppsAndMedia1.0

We installed on Windows.

After running 'configure', and before running 'make', go to your PATH/qtbase/mkspecs/common folder and update the following files to use explicit compiler/linker commands (to compile/link with GNU tools instead of Dinkum), and remove the '-lang-c++' flag wherever found:

g++-base.conf, qcc-base.conf, qcc-base-qnx.conf, qcc-base-qnx-armv7le.conf

Add the '-lstdc++' flag to QMAKE_LIBS in qcc-base-qnx.conf.

In your filesystem, rename the libcpp-ne.so* files found in C:\QNX660\*. That way, Qt won't be able to link against it (because it won't find it).

Now make / make install and hope for the best.

post113375: Re: Qt 5.2.0 dev env for linux with target binaries/plugins dependent in libstdc++ and not libstdcpp(-ne)

Steven Zajac(deleted) — Tue, 24 Feb 2015 22:46:55 GMT

Hello Knowledgeable Forum Browsers and Forum Moderators,

I was able to build Qt 5.2.0 from the supplied package using the instructions here:

http://community.qnx.com/sf/wiki/do/viewPage/projects.qt/wiki/Qt5.2.0BuildInstructionsForQNXSDKForAppsAndMedia1.0

If you are unable to provide Qt binaries that do not depend on the libcpp-ne and/or libcpp libraries, can you tell me how to configure the Qt make to use ONLY the GNU C++ (libstdc++) library?

I've rebuilt Qt numerous times. These have mostly the same configuration as described in the link above (building for Windows). I've added the -no-c++11 flag and have attempted to remove the -platform [arg] flag altogether.

I've also changed some of the make configuration files (/qtbase/mkspecs/common/*.conf) to try and force it to use the GNU flavor compiler/linker.

After building Qt, I see that libcpp-ne is included in at least the Qt5Core library.

I fear I am spinning my wheels and overlooking what could be a simple solution. Can you please point me in the right direction?

Thanks,

Steven Zajac

post113361: Qt 5.2.0 dev env for linux with target binaries/plugins dependent in libstdc++ and not libstdcpp(-ne)

Steven Zajac(deleted) — Fri, 20 Feb 2015 17:09:38 GMT

Hello,

I am using the released binaries for Qt. 5.2.0 on Linux and notice that they are dependent on the libstdcpp library.

The project I am working on consistently depends on the libstdc++ (GNU C++) library.

I've noticed that the Qt libraries depend on the libstdcpp (Dinkum C++) library.

Our Qt application is compiled/linked with the GNU C++ library, but the Dinkum C++ library is pulled in from the applications Qt library dependencies. This is causing run-time failures as two C++ libraries are loaded by the application.

Do you have a Qt 5.2.0 development environment compiled/linked against the GNU C++ library?

I do not have the ability to convert the rest of the project to the Dinkum C++ library.

Thank you,

Steven Zajac

post113272: Re: Compiling Qt 5.4.0 for QNX

Scott Stone — Mon, 09 Feb 2015 17:57:00 GMT

I have the source all compiled for x86 and arm architectures now.  I can compile the code using the command line and deploy to targets.

I tried adding a kit in Qt Creator that I use from QNX with Qt5.3.0.  I cloned the 5.3.0 kit and changed the location of the qmake folder to the 5.4.0 location and added all the proper compilers for the new version.  When I try to build the application,  I get the following error:

make[1]:  *** [realease/moc_tunits.cpp] Error -1073741515

Has anyone added the Qt 5.4.0 build as a kit in Qt Creator succesfully?  I am not sure why I am getting this error or what it means.

Thanks.

post113257: Re: RE: Compiling Qt 5.4.0 for QNX

Grant Courville — Sat, 07 Feb 2015 18:02:19 GMT

It is worth noting that as of Qt 5.4, some new content was introduced that are now licensed under LGPL3 and this may affect your deployment abilities depending on your situation. The LGPL3 Qt content that I am aware of is Qt Canvas3D and Qt Webview. Thought it was worth noting...

More info can be obtained here:

http://blog.qt.io/blog/2014/08/20/adding-lgpl-v3-to-qt/

http://doc.qt.io/qt-5/lgpl.html

http://doc.qt.io/qt-5/licensing.html

http://www.qt.io/download/

post113252: Re: RE: Compiling Qt 5.4.0 for QNX

Scott Stone — Fri, 06 Feb 2015 21:10:58 GMT

Main reason to use 5.4.0 is to standardize all our platforms to one version of Qt. We have code for many OS's and want all to compile without changes.

I have gotten farther, I cleaned my src folder and re copied all the files from the src zip file. I can get Qt to compile, but, am unsure if I did it properly. When I run configure.bat it fails unless I specifically add in a platform command. I used the command line argument -platform win32-g++. Anything else, and the configuration would fail. Is that the proper platform to use since I am building on a windows machine?

Thanks.

post113230: RE: Compiling Qt 5.4.0 for QNX

Malte Mundt — Thu, 05 Feb 2015 10:41:50 GMT

Hey Scott, just curious... what is the great thing in Qt 5.4 that is not in Qt 5.3, which is readily available built and usable out of the box?

> -----Original Message-----

> From: Scott Stone [mailto:community-noreply@qnx.com]

> Sent: Thursday, February 05, 2015 12:52 AM

> To: general-qt

> Subject: Re: Compiling Qt 5.4.0 for QNX

>

> I have gotten configure to succesfully complete now. I had to move the

> path variable for cygwin to the end of the path rather than near the

> beggining.

>

> Now I am trying to make the project. When I execute mingw32-make, I get

> the following warnings and errors:

>

> minggw32-make[2]: Entering directory 'C:/Qt-

> QNX/Qt5.4.0/5.4/Src/qtbase/src' cd tools/bootstrap/ && ( test -e

> Makefile || C:/Qt/QNX/Qt5.4.0/5.4/Src/qtbase/bin/qmake.exe C:/Qt-

> QNX/Qt5.4.0/Src/qtbase/src/tools/bootstrap.pro -o Makefile ) && mingw32-

> make -f Makefile

>

> Project WARNING: You should probably load(qt_build_config) first in

> bootstrap.pro for QBootStrap, as the latter also load()s qt_module.

> Project MESSAGE: Not doing so may lead to qt_module.prf overriding

> compiler/linker options in your .pro file.

> Project MESSAGE: Ignore this warning with CONFIG+=no_qt_module_warning

> if you know what you are doing.

> Project ERROR: Module does not define version.

> Makefile 62: recipe for target 'sub-bootstrap-make_first' failed

>

> Any input as to why qt_build_config did not execute or how to define a

> version would be greatly appreciated at this point.

>

> Thanks.

>

>

>

> _______________________________________________

>

> Qt General

> http://community.qnx.com/sf/go/post113223

> To cancel your subscription to this discussion, please e-mail general-

> qt-unsubscribe@community.qnx.com

post113223: Re: Compiling Qt 5.4.0 for QNX

Scott Stone — Wed, 04 Feb 2015 23:52:25 GMT

I have gotten configure to succesfully complete now. I had to move the path variable for cygwin to the end of the path rather than near the beggining.

Now I am trying to make the project. When I execute mingw32-make, I get the following warnings and errors:

minggw32-make[2]: Entering directory 'C:/Qt-QNX/Qt5.4.0/5.4/Src/qtbase/src' cd tools/bootstrap/ && ( test -e Makefile || C:/Qt/QNX/Qt5.4.0/5.4/Src/qtbase/bin/qmake.exe C:/Qt-QNX/Qt5.4.0/Src/qtbase/src/tools/bootstrap.pro -o Makefile ) && mingw32-make -f Makefile

Project WARNING: You should probably load(qt_build_config) first in bootstrap.pro for QBootStrap, as the latter also load()s qt_module.

Project MESSAGE: Not doing so may lead to qt_module.prf overriding compiler/linker options in your .pro file.

Project MESSAGE: Ignore this warning with CONFIG+=no_qt_module_warning if you know what you are doing.

Project ERROR: Module does not define version.

Makefile 62: recipe for target 'sub-bootstrap-make_first' failed

Any input as to why qt_build_config did not execute or how to define a version would be greatly appreciated at this point.

Thanks.

post113208: Re: Compiling Qt 5.4.0 for QNX

Scott Stone — Tue, 03 Feb 2015 22:40:56 GMT

Thanks for the help.  Commenting out the line in the configure.bat has gottne me farther.

Now, I am running into errors while trying to compile.  I have cygwin installed on my computer which adds another layer ot the process.  If I try to run from the a CMD window, I get an error that says:

   /bin/sh: /c/cygwin/bin/g++: Bad File Number

   Makefile 119: recipe for target 'configure_pch.h/c++' failed

If I run from cygwin, I get an error saying:

    cygppl_c-2.dll cannot open

Any ideas the best way to solve either of these issues?  I am not sure why the CMD prompt version is trying to run cygwin style commands.

Thanks.

Scott.

post113202: Re: Compiling Qt 5.4.0 for QNX

David Pilar — Tue, 03 Feb 2015 14:34:42 GMT

I was able to compile using the following steps:

1) Edit <qt-source-root>/qtbase/configure.bat. Somewhere around line 37 comment out:

if not exist %QTSRC%\.gitignore goto sconf

2)c:\QNX660\qnx660-env.bat

3)configure.bat -xplatform qnx-armle-v7-qcc -opengl es2 -no-cups -no-iconv -skip qtserialport -skip qtwebkit -no-c++11

4)mingw32-make

There was an error about _fopen when I didn't use the "-no-c++11" flag.

This configured and built for me.

post113146: Re: There is anything in QNX6.6 the window manager for qt-apps?

Vova Beliy(deleted) — Thu, 29 Jan 2015 20:52:00 GMT

Thank you.

post113132: Re: UDP messages on a Beagle Bone Black

Malte Mundt — Thu, 29 Jan 2015 10:25:44 GMT

Interesting, thanks for sharing your solution!

post113131: Re: There is anything in QNX6.6 the window manager for qt-apps?

Malte Mundt — Thu, 29 Jan 2015 10:24:32 GMT

> But I would like to the window looked as in Windows XP. On the window have

> been buttons: Minimize, Maximize and Exit. How to do it? In QNX6.5 through -

> qws it all works.

QWS was a part of Qt 4.x that tried to be a Window manager "inside" a Qt application. By nature, a Window manager should not be part of an application itself, instead it should be over and above the applications it manages. With Qt 5, the Qt folks decided to discontinue QWS, because it was a weird design (IMHO) and because most supported Operating Systems have their own window manager.

QNX has "screen", which claims to be a window manager, but the understanding of the term "window" in QNX is different from rest of the world. You can have individual target "framebuffers" for each application, which can result in a kind of "window" but without a frame and without minimize or close buttons. BlackBerry has built a kind of window management on top of that, with apps being able to zoom and with a small area below the app to close it. But that's not part of QNX "screen", AFAIK.

With QNX's strong focus on Automotive and BlackBerry, most "apps" or use cases run in a full screen manner, anyway. The notion of having multiple "Windows" next to each other, with a "taskbar" to minimize them into, is very common only in very few use cases and as such probably has not been a priority at QNX R&D.

If you need to have multiple Qt apps next to each other on screen (?! of course I mean display), with the user being able to close or minimize them, or even drag them around, you have to implement this on your own or engage with QNX Services. I know it seems odd that a modern OS like QNX 6.6 cannot do what Windows 3.11 (and QNX 4.25) could do regarding Window management, but it is what it is. :)

post113129: Compiling Qt 5.4.0 for QNX

Scott Stone — Wed, 28 Jan 2015 23:37:59 GMT

I am trying to compile Qt 5.4 from source on my windows machine. Has anyone been succesful setting up their environment and compiling the libraries? I keep getting errors, and the instructions are very cryptic on Qt's website.

post113128: Re: UDP messages on a Beagle Bone Black

Scott Stone — Wed, 28 Jan 2015 23:35:54 GMT

I solved the issue. For some reason, I needed to use io-pkt-v6-hc as the driver for the ethernet adapter instead of io-pkt-v4-hc. Once I updated the BeagleBone BSP to use the other version, everything worked fine.

post113125: Re: There is anything in QNX6.6 the window manager for qt-apps?

Vova Beliy(deleted) — Wed, 28 Jan 2015 22:01:37 GMT

Thank you, Dennis.

But I would like to the window looked as in Windows XP. On the window have been buttons: Minimize, Maximize and Exit. How to do it? In QNX6.5 through -qws it all works.

Sorry for my English.

post113113: Re: There is anything in QNX6.6 the window manager for qt-apps?

Dennis Kellly(deleted) — Tue, 27 Jan 2015 22:21:39 GMT

From the launchig shell, enter prior to app launch..

# export QT_QPA_PLATFORM=qnx:no-fullscreen

# ./myApp

Or

# ./myApp -platform qnx:no-fullscreen

post113112: There is anything in QNX6.6 the window manager for qt-apps?

Vova Beliy(deleted) — Tue, 27 Jan 2015 22:16:50 GMT

In QNX6.6 when I launch the application through the 'screen', all the windows are stretched to fill the screen. How to get rid of it? There is anything in QNX6.6 the window manager for qt-apps? Such as -qws in QNX6.5.

post113111: How to collect qt-application with OpenGL for QNX6.6?

Vova Beliy(deleted) — Tue, 27 Jan 2015 22:01:59 GMT

How to collect qt-application with OpenGL for QNX6.6?

For example, I take an existing  the application in Qt - hellogl.

To collect it , I used the following commands at the command prompt on Windovs XP:

C:\qnx660\qnx660-env.bat

cd  C:\example\hellogl

C:\Qt\Qt5.3.0\5.3\qnx6-x86\bin\qmake  hellogl.pro

make

But this command (C:\Qt\Qt5.3.0\5.3\qnx6-x86\bin\qmake  hellogl.pro) generates an error

(Project ERROR: This example requires Qt to be configured with -opengl desktop).

What am I doing wrong? How to do it? Needed something append to a file hellogl.pro? Or somehow to configure Qt?

post113075: UDP messages on a Beagle Bone Black

Scott Stone — Fri, 23 Jan 2015 22:48:44 GMT

I have written an application that monitors UDP messages on port 53248 for any ethernet adapter present in a system. It works great with the x86 based QNX VM. I am now trying to deply it on a Beagle Bone Black. I reran qmake using the arm version and built the program again. All the right compilers are used to build for the arm architecture.

When I run the prgram, the readyRead SIGNAL is never fired. Has anyone attempted to use readyRead SIGNAL on ARM architecture? I am baffled as to why the program does not just compile and work? Any suggestions would be greatly appreciated at this point.

Thanks.

post112798: QNX 6.5 development tool setup with QT4.7.4

Krishna Yadav(deleted) — Wed, 31 Dec 2014 13:56:17 GMT

Hello guys,

it is very helpful to me if any one provide me the binary installer link of QNX 6.5. Currently i am using VMware on my

windows PC for QNX 6.5

post112786: QNX 6.6 with QT 5.3 does not support QWidget::setMask() function

john xi — Mon, 29 Dec 2014 02:41:22 GMT

I'm moving open source project QWT 6.1.3 to QNX 6.6 with QT5.3.1, every thing is well, but excepting one slog2info error message: QWidget::setMask() function is not supported on QNX 6.6 platform.

I want to know why QWidget::setMask() function is not supported on QNX 6.6 QT? How to solve this problem?

post112783: Re: Qt5.2 on QNX Neutrino: new UI Core graphics framework headers and libraries

David Vitelli(deleted) — Sun, 28 Dec 2014 20:28:58 GMT

Did you manage to get those files ?

I'm interested too.

post112062: Re: QtHelloWorld abort on x86 Rhodeus SBC

Alessandro Ferrarini(deleted) — Fri, 17 Oct 2014 11:21:41 GMT

I solved my problem.

My CPU doesn't support SSE instructions so I had to compile Qt without SSE support.

post112041: QtHelloWorld abort on x86 Rhodeus SBC

Alessandro Ferrarini(deleted) — Tue, 14 Oct 2014 13:22:39 GMT

Hi,

I installed Qnx6.6 + Qt5.3.0 on my Rhodeus x86 SBC and I tried to execute my Qt demo program QtHelloWorld but says:

QT_MESSAGE_PATTERN: Unknown placeholder %{if

Process 126996 (QtHelloWorld) terminated SIGABRT code=0 by process 126996 value=0.

Abort (core dumped)

I tried also to do the same thing on my vmware machine (with Qnx6.6 + Qt5.3.0) and it works fine.

Can be a graphic driver problem?

I used Screen in both platforms but on vmware I used  the "/usr/lib/graphics/vmware" configuration dir while on x86 I used "/usr/lib/graphics/vesabios".

x86 ENV VARS:

COLUMNS=237

GRAPHICS_ROOT=/usr/lib/graphics/vesabios

HOME=/root

HOSTNAME=localhost

HZ=100

IFS='

'

KSH_VERSION='@(#)PD KSH v5.2.14 99/07/13.2'

LD_LIBRARY_PATH=:./:/proc/boot:/lib:/lib/dll:/usr/lib:/usr/Qt5.3/lib:/usr/lib/graphics/vesabios

LINES=63

LOGNAME=root

MAILCHECK=600

OPTIND=1

PATH=/sbin:/usr/sbin:/proc/boot:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/opt/bin:/opt/sbin

PPID=81935

PROCESSOR=x86

PS1='# '

PS2='> '

PS3='#? '

PS4='+ '

PWD=/root

QML2_IMPORT_PATH=/usr/Qt5.3/qml

QNX_CONFIGURATION=/etc/qnx

QNX_HOST=/

QNX_TARGET=/

QQNX_PHYSICAL_SCREEN_SIZE=305,228

QT_PLUGIN_PATH=/usr/Qt5.3/plugins

RANDOM=26897

SECONDS=5928

SHELL=/bin/sh

SYSNAME=nto

TERM=qansi

TMOUT=0

TMPDIR=/tmp

TTY=/dev/ttyp0

USER=root

_=set

x86 VESABIOS GRAPHICS.CONF

begin khronos

  begin egl display 1

    egl-dlls = libEGLsoftgl.so

    glesv1-dlls = libGLESsoftgl.so

    #glesv1-dlls = libGLESsoftgl-sse2.so

    #glesv1-dlls = libGLESsoftgl-sse4.so

  end egl display

  begin wfd device 1

    wfd-dlls = libWFDvesabios.so

  end wfd device

end khronos

begin winmgr

  begin display internal

    video-mode = 640 x 480 @ 60

  end display

  begin class framebuffer

    display = internal

    pipeline = 1

    format = rgbx8888

    usage = sw

  end class

end winmgr

Can somebody help me?

Thk

post111988: How to compile a Qt5.3 application with Momentics ?

Nicolas Pinault — Wed, 08 Oct 2014 08:28:30 GMT

Hello,

I'd like to add a small GUI to an application already developped with Momentics (SDP6.6.0).

I'd like to keep compiling my application with momentics.

How can I configure my momentics project to add QT5.3 functionnalities ?

Nicolas

post111987: Re: Run Qt 5.3 App on QNX 6.6 target

Nicolas Pinault — Wed, 08 Oct 2014 06:48:29 GMT

Please, forget my previous message.

post111986: Re: Run Qt 5.3 App on QNX 6.6 target

Nicolas Pinault — Wed, 08 Oct 2014 06:40:26 GMT

Hi,

Have you enabled keyboard in scren configuration file ?

Nicolas

post111976: Can't enter numerics from numpad from Qt App

Maximus Besttrump(deleted) — Tue, 07 Oct 2014 15:07:28 GMT

I wrote a Qt app with some LineEdit widgets, but those widgets don't take the numerics from the numpad even when the num lock key is on. The Qt version is 5.3, and the QNX version 6.5. Any help will be appreciated.

post111886: Re: Configuring QNX Touch Screen with QT

Dinakar Babu(deleted) — Fri, 26 Sep 2014 07:04:48 GMT

Hi,

Yes, Touch is working in Photon. But, we are not able to get touch working in Qt.

Our set up is something different. Actually, system which we have is pre-configured with Touch Screen .

As per our observation, Touch screen driver is appears to be binded with input.localhost file under /etc/system/trap.

Because, by default, Touch driver will start by invoking the command in the input.localhost . If we comment the driver command in input.localhost, touch driver does not start. Even after starting the driver manually also, touch is not working.

As per the above points, Touch driver starts only when driver command in input.localhost executes. This file is being invoked by Photon server. So, to run Qt Applicaitons, we need to be in Shell Mode which does not invoke driver command in input.localhost file.

So, finally, touch driver does not work even after we run manually also. Could you please help me with on how can run touch driver without photon in Shell mode for Qt.

post111761: Re: Configuring QNX Touch Screen with QT

Vladimir Minenko(deleted) — Wed, 17 Sep 2014 12:56:02 GMT

It also depends if Qt4 has been build supporting QWS or not. More details on this are available under:

http://qt-project.org/doc/qt-4.8/qt-embedded-running.html

and

http://qt-project.org/doc/qt-4.8/qt-embedded-displaymanagement.html

Generally, QWS has been discontinued with Qt 4.8 even though it is still in the code. From 4.8 on, the QPA architecture shall be used, and Qt5 does not support QWS (Qt Windowing System) anymore and requires a Screen package on QNX

post111757: Re: Configuring QNX Touch Screen with QT

Dennis Kellly(deleted) — Wed, 17 Sep 2014 12:31:52 GMT

Qt4

If already working for photon (assuming x86) and your panel is HID-compliant, enter these commands from external terminal or telnet session (console keyboard will no longer work)

# export QWS_DISPLAY=qnx

# export QWS_KEYBOARD=qnx

# export QWS_MOUSE_PROTO=qnx

# /usr/photon/bin/devi-hid -Pr kbd touch

# ./myQt4Prog -qws

You can replace "touch" with "mouse" to verify mouse works.

If your touch is not HID-compliant, try something like this...

http://community.qnx.com/sf/discussion/do/listPosts/projects.qt/discussion.general.topc20923?_pagenum=4

(you still need the exports)

post111756: Re: Configuring QNX Touch Screen with QT

Vladimir Minenko(deleted) — Wed, 17 Sep 2014 10:49:59 GMT

Which kind of help do you need? There are mandatory settings to configure in Qt for this. If touch works on target natively, it will work in any Qt app as well. The only thing to care of is to make sure that Qt knows how is the physical display surface. Usually, the QNX Screen reports this, but in some instances it does not. In those cases you have to set QQNX_PHYSICAL_SCREEN_SIZE env var with according values, see https://qt-project.org/wiki/QNX-App-development-and-deployment. Anyway, as mentioned, touch would work without this as well. For touch, it is a nice to have, but it also improves they way how well fonts are scaled to the display sizes. Additionally, you should keep in mind that touch is not the same as mouse ;-) See http://qt-project.org/doc/qt-5/qtouchevent.html

post111755: Configuring QNX Touch Screen with QT

Dinakar Babu(deleted) — Wed, 17 Sep 2014 07:20:46 GMT

Hi,

I know how to configure QNX Touch Screen Driver of eGalax with Photon and was able to work with it fine.

But, now I have change my environment to Qt for the same application where touch is required.

So, could any one help me with the step by step procedure to configure QNX6.5 Touch Screen for Qt 4 and QNX 6.6 Touch Screen for Qt 5.3

Thanks in Advance.

Best Regards.

Dinakar.

post111604: QNX 6.6 touch screen setup

qnx1 developer(deleted) — Tue, 02 Sep 2014 03:29:50 GMT

Hello.

I'm trying to use touch screen at QNX 6.6 / Qt5.

I've searched and followed answers and then I'm seeing calib-touch screen now.

But I can't move the cursor or click.

After launching below programs in rc.local, calib-touch program could be run.

But touch doesn't work and cannot calibrate.

With QNX 6.5 / Qt4 touch screen works fine.

Does anyone have any idea what's wrong?

Thanks.

io-usb -duhci -dohci -dehci

io-hid -dusb -degalax

devi-hid kbd touch

drm-intel &

screen &

Here is hidview result:

# hidview

Device Address       : 0

Vendor               : 0x0eef (eGalax Inc.)

Product              : 0x0001

Version              : r1.10

Usage                : Pointer

Device Address       : 1

Vendor               : 0x045e (Microsoft)

Product              : 0x0752 (Wired Keyboard 400)

Version              : r1.10

Usage                : Keyboard

And this is my env variables:

# env

_=/usr/bin/env

SSH_CONNECTION=192.168.100.118 64713 192.168.100.177 22

PATH=/sbin:/usr/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/bin:/opt/sbin:/bin:/sbin:/usr/bin:/usr/sbin

SHELL=/bin/sh

TMPDIR=/tmp

HOSTNAME=localhost

USER=root

PROCESSOR=x86

MAIL=/var/spool/mail/root

LD_LIBRARY_PATH=/prob/boot:/lib:/usr/lib:/lib/dll:/opt/qt5/lib:/opt/qnx6/x86/lib:/opt/qnx6/x86/usr/lib:/opt/qnx6/x86/lib

/dll:/usr/lib/graphics/intel-drm:/opt/qt5/plugins/platforms

QT_DEBUG_PLUGINS=1

HOME=/root

SSH_CLIENT=192.168.100.118 64713 22

QNX_HOST=/

QT_QPA_PLATFORM=qnx:no-fullscreen

QNX_TARGET=/

GRAPHICS_ROOT=/usr/lib/graphics/intel-drm

QQNX_PHYSICAL_SCREEN_SIZE=200,117

TERM=xterm

QML_IMPORT_PATH=/opt/qt5/imports

QML2_IMPORT_PATH=/opt/qt5/qml

QT_PLUGIN_PATH=/opt/qt5/plugins

FONTCONFIG_FILE=/etc/fontconfig/local.conf

QNX_CONFIGURATION=/etc/qnx

SSH_TTY=/dev/ttyp0

SYSNAME=nto

LOGNAME=root

This is my /usr/lib/graphics/intel-drm/graphics.conf:

begin khronos

  begin egl display 1

    egl-dlls = libEGL-mesa.so

    glesv1-dlls = libglapi-mesa.so libGLESv1_CM-mesa.so

    glesv2-dlls = libglapi-mesa.so libGLESv2-mesa.so

  end egl display

  begin wfd device 1

    wfd-dlls = libwfdcfg-sample.so libWFDintel-drm.so

    # Run "drm-probe-displays" to list the available displays and pipelines,

    # and "use $GRAPHICS_ROOT/libWFDintel-drm.so" for more information on

    # these driver-specific settings.

    # Pipeline IDs 1 to 9 are used for DRM CRTCs.  One should be assigned

    # to each display that will be used.

    pipeline1-display = 1

    # Pipeline IDs 10 and above are used for DRM planes.  A plane can only

    # be used on a display with an active CRTC.

    pipeline10-display = 1

  end wfd device

end khronos

begin winmgr

  begin globals

    input = keyboard mouse

    # Adjust the stack size of Screen's resmgr threads.  The default size

    # is insufficient for blitters/compositors using Mesa (e.g., gles2blt).

    blit-config = gles2blt

  end globals

  begin display 1

    video-mode = 1024 x 600 @ 75

    # Adjust the stack size of Screen's composition thread; required when the

    # display's framebuffer uses Mesa (e.g. "usage = gles2"), as noted above.

    cursor = on

    stack-size = 4096  # in units of 1024 bytes

  end display

  begin class framebuffer

    # Be sure to configure the "pipeline%d-display" options (above) so the

    # specified display and pipeline are bindable.  Normally a framebuffer

    # will use a CRTC pipeline.

    display = 1

    pipeline = 1

    format = rgba8888

    usage = gles2blt

  end class

  begin mtouch

    driver = devi

    options = height=600,width=1024

    display = 1

  end mtouch

end winmgr

post111599: Re: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Mon, 01 Sep 2014 08:31:20 GMT

I'm trying to use touch screen at QNX 6.6 / Qt5.

I've followed your answers and then I'm seeing calib-touch screen now.

But I can't move the cursor or click.

After launching below programs in rc.local, calib-touch program could be run.

But touch doesn't work and cannot calibrate.

With QNX 6.5 / Qt4 touch screen works fine.

Do you have any idea what's wrong?

io-usb -duhci -dohci -dehci

io-hid -dusb -degalax

devi-hid kbd touch

drm-intel &

screen &

Here is hidview result:

# hidview

Device Address       : 0

Vendor               : 0x0eef (eGalax Inc.)

Product              : 0x0001

Version              : r1.10

Usage                : Pointer

Device Address       : 1

Vendor               : 0x045e (Microsoft)

Product              : 0x0752 (Wired Keyboard 400)

Version              : r1.10

Usage                : Keyboard

And this is my env variables:

# env

_=/usr/bin/env

SSH_CONNECTION=192.168.100.118 64713 192.168.100.177 22

PATH=/sbin:/usr/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/bin:/opt/sbin:/bin:/sbin:/usr/bin:/usr/sbin

SHELL=/bin/sh

TMPDIR=/tmp

HOSTNAME=localhost

USER=root

PROCESSOR=x86

MAIL=/var/spool/mail/root

LD_LIBRARY_PATH=/prob/boot:/lib:/usr/lib:/lib/dll:/opt/qt5/lib:/opt/qnx6/x86/lib:/opt/qnx6/x86/usr/lib:/opt/qnx6/x86/lib/dll:/usr/lib/graphics/intel-drm:/opt/qt5/plugins/platforms

QT_DEBUG_PLUGINS=1

HOME=/root

SSH_CLIENT=192.168.100.118 64713 22

QNX_HOST=/

QT_QPA_PLATFORM=qnx:no-fullscreen

QNX_TARGET=/

GRAPHICS_ROOT=/usr/lib/graphics/intel-drm

QQNX_PHYSICAL_SCREEN_SIZE=200,117

TERM=xterm

QML_IMPORT_PATH=/opt/qt5/imports

QML2_IMPORT_PATH=/opt/qt5/qml

QT_PLUGIN_PATH=/opt/qt5/plugins

FONTCONFIG_FILE=/etc/fontconfig/local.conf

QNX_CONFIGURATION=/etc/qnx

SSH_TTY=/dev/ttyp0

SYSNAME=nto

LOGNAME=root

This is my /usr/lib/graphics/intel-drm/graphics.conf:

begin khronos

  begin egl display 1

    egl-dlls = libEGL-mesa.so

    glesv1-dlls = libglapi-mesa.so libGLESv1_CM-mesa.so

    glesv2-dlls = libglapi-mesa.so libGLESv2-mesa.so

  end egl display

  begin wfd device 1

    wfd-dlls = libwfdcfg-sample.so libWFDintel-drm.so

    # Run "drm-probe-displays" to list the available displays and pipelines,

    # and "use $GRAPHICS_ROOT/libWFDintel-drm.so" for more information on

    # these driver-specific settings.

    # Pipeline IDs 1 to 9 are used for DRM CRTCs.  One should be assigned

    # to each display that will be used.

    pipeline1-display = 1

    # Pipeline IDs 10 and above are used for DRM planes.  A plane can only

    # be used on a display with an active CRTC.

    pipeline10-display = 1

  end wfd device

end khronos

begin winmgr

  begin globals

    input = keyboard mouse

    # Adjust the stack size of Screen's resmgr threads.  The default size

    # is insufficient for blitters/compositors using Mesa (e.g., gles2blt).

    blit-config = gles2blt

  end globals

  begin display 1

    video-mode = 1024 x 600 @ 75

    # Adjust the stack size of Screen's composition thread; required when the

    # display's framebuffer uses Mesa (e.g. "usage = gles2"), as noted above.

    cursor = on

    stack-size = 4096  # in units of 1024 bytes

  end display

  begin class framebuffer

    # Be sure to configure the "pipeline%d-display" options (above) so the

    # specified display and pipeline are bindable.  Normally a framebuffer

    # will use a CRTC pipeline.

    display = 1

    pipeline = 1

    format = rgba8888

    usage = gles2blt

  end class

  begin mtouch

    driver = devi

    options = height=600,width=1024

    display = 1

  end mtouch

end winmgr

post111597: Re: Font Problem

qnx1 developer(deleted) — Mon, 01 Sep 2014 02:45:59 GMT

http://community.qnx.com/sf/discussion/do/listPosts/projects.qt/discussion.general.topc25527

I think it'll be helpful for your problems.

post111487: Re: Building Qt libraries for Qnx SDP 6.6

Vladimir Minenko(deleted) — Tue, 19 Aug 2014 09:27:08 GMT

First of all, you should consider going to Qt 5.3. No additional patches for Qt are required with 5.3 since all of them have been upstreamed.

Do you have a good reason to use so many options in "configure"? The time when it was needed is over since a while. Today, "configure" is clever enough to determine what is needed and what should be omitted on QNX automatically. Just a name of the target platform would be sufficient for the beginning. Later, you can tune your build with more options if needed.

Note that the name of the ARM target on QNX has been changed in 5.3. It is now "qnx-armle-v7-qcc" instead of "qnx-armv7le-qcc" in 5.2.

https://qt-project.org/wiki/Building-Qt-for-QNX-Neutrino-OS

post111476: Font Problem

yusuf yamak(deleted) — Mon, 18 Aug 2014 17:21:44 GMT

Hi,

If I run qt application on qnx,I get error as following

Fontconfig error: Cannot load default config file

Apllication is open but,fonts aren't shown.

What can I do solve this problem.

Regards.

post111404: Building Qt libraries for Qnx SDP 6.6

Ahmet Bektas(deleted) — Wed, 13 Aug 2014 13:36:54 GMT

Hi,

I try to build qt libraries for Qnx SDP 6.6 but I get an error as follows:

cc: /home/yusuf/qnx660/host/linux/x86/usr/lib/gcc/arm-unknown-nto-qnx6.6.0eabi/4.7.3/cc1plus error 1

make[3]: *** [.obj/qv4value.o] Error 1

make[3]: *** Waiting for unfinished jobs....

make[3]: Leaving directory `/home/yusuf/qt-everywhere-opensource-src-5.2.0/qtdeclarative/src/qml'

make[2]: *** [sub-qml-make_first-ordered] Error 2

make[2]: Leaving directory `/home/yusuf/qt-everywhere-opensource-src-5.2.0/qtdeclarative/src'

make[1]: *** [sub-src-make_first] Error 2

make[1]: Leaving directory `/home/yusuf/qt-everywhere-opensource-src-5.2.0/qtdeclarative'

make: *** [module-qtdeclarative-make_first] Error 2

I run configure script for Qt everywhere 5.2 with following arguments

./configure -prefix /base/qt5-5.2 -release -nomake tests -no-gtkstyle -opengl es2 -egl -no-cups -no-xcb -no-eglfs -no-javascript-jit -no-gtkstyle -no-iconv -xplatform qnx-armv7le-qcc -skip qtserialport -skip qtwebkit

Must I use Qt 5.2.0 source patch for QNX.(Because I use Qnx with Academic License so I can't download this patch) or What is the problem?

Please help me about this problem.

post111358: Re: Problem with QPdfWriter

Thilloy Paul — Mon, 11 Aug 2014 09:49:51 GMT

Never mind... working now that I'm correctly typing it... sorry for my mistake.

post111357: Problem with QPdfWriter

Thilloy Paul — Mon, 11 Aug 2014 09:44:13 GMT

Hello,

I'm trying to use the QPdfWriter class with the latest build of Qt from Qnx (SDP 6.6)

I want to set the Pdf Orientation using setOrientation but the function seems no to be defined :

in QPdfWriter.h the definition of the functions setPageLayout setPageOrientation etc... are encapsuled by #ifdef Q_QDOC which doesn't seem to be defined...

Am I wrong somewhere ??

Regards,

Paul

post111356: Re: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Mon, 11 Aug 2014 08:30:20 GMT

Solution found:

http://community.qnx.com/sf/discussion/do/listPosts/projects.qt/discussion.general.topc25558

Qt I installed was made with fontconfig but my QNX target system doesn't have one.

Download and install fontconfig patch from here:

http://community.qnx.com/sf/frs/do/viewRelease/projects.qt/frs.binpkg.qt_5_3_0_development_environment

and copied libfontconfig.so libfontconfig.so.1 from <qnx660>/target/qnx6/x86/usr/lib/ of tha host(linux) to /usr/lib.

post111347: Re: qt 5.3.1 build

Vladimir Minenko(deleted) — Fri, 08 Aug 2014 11:46:54 GMT

Many things have been improved since 5.2! :-)

post111340: RE: additional libs needed for Qt - my list

Malte Mundt — Thu, 07 Aug 2014 10:18:57 GMT

> Which 3rd party libraries are needed by Qt can be controlled via Qt's

> configure script or via DEFINE statements given to configure. Feel free

> to read the help page of Qt's configure script ("configure -help") to

> find out how to remove some of the dependencies, in case you are

> building Qt on your own.

It's good to know that this is possible. I hope it works. :)

> Could you please elaborate on why you think "no one seems to care which

> libs are really needed and how big they are"? Which libs do you think we

> could get rid of?

The multiple variants of the cpp lib could be reduced to one variant, ideally the smallest/fastest one. ;) And what about libicu & friends? A whopping 20 MB - for what? Well, my mistake... I come from a QNX Photon enviroment where everything fitted into 4 MB. :)

And finally, what about static linking for some libs are only required by one single Qt component (libiconv maybe?)? Static linking would only bring in the functions really required (I assume that platform specific support for NextStep, included in libiconv, is not really needed by Qt?)

Cheers,

- Malte

post111339: Re: qt 5.3.1 build

Sönke Nielsen — Thu, 07 Aug 2014 09:52:23 GMT

The build succes with ./configure -prefix /home/soenke/Qt5.3.1/qnx-armv7le -xplatform qnx-armle-v7-qcc

I've used configure with all the other argumets to build qt 5.2. I've been told they are required and I just took them over to 5.3. It seems they are not required any more...

Thanks

Sönke

post111326: Re: Qt5.3 with QGLWidget components

Jefferson Biernastki(deleted) — Wed, 06 Aug 2014 13:44:44 GMT

Hi,

after some hours i detected the problem. When my layout is generated by UIC it reparent my QGLWidget on addWidget.

Parent A on new QGLWidget.

Parent B on addWidget.

post111323: Re: qt 5.3.1 build

Vladimir Minenko(deleted) — Wed, 06 Aug 2014 09:32:58 GMT

Just by a chance, I retested this my SDP 6.6 with Apps&Media on a 5.3.1 source tar-ball. I did not get your error, but when "-fully-process" is used the build fails in webkit which is known. Do you have a good reason to use "-fully-process"? Other then that there are no build problems. You call of configure is rather complicated. I hope, you know what all options in your configure are doing. Normally, just "-prefix" and "-xplatform" are sufficient. Certainly, using other options helps tuning, but using them blindly is not a good idea... ;-)

Your build problems might also be caused by some leftovers from a previous "configure" call. The well-known "make clean" does not remove all the stuff created by "configure". You need to clean your src folder with "make distclean" to get it really clean.

Compared to 5.2, Qt 5.3 has a new JavaScript engine. I'm sure that is the reason why "-no-javascript-jit" is not provided anymore.

post111313: Re: additional libs needed for Qt - my list

Peter Hartmann(deleted) — Tue, 05 Aug 2014 13:08:34 GMT

On 08/05/2014 11:57 AM, Malte Mundt wrote:

> Note that some of those libs are quite large. Following the "memory is cheap nowadays" approach, no one seems to care which libs are really needed and how big they are.

>

> Additionally, Qt itself is inconsistent linking to C++ libs: you need libcpp.so.5 AND libcpp.so.4 AND libcpp-ne.so.5. But who am I to disagree?;-)

Which 3rd party libraries are needed by Qt can be controlled via Qt's

configure script or via DEFINE statements given to configure. Feel free

to read the help page of Qt's configure script ("configure -help") to

find out how to remove some of the dependencies, in case you are

building Qt on your own.

Could you please elaborate on why you think "no one seems to care which

libs are really needed and how big they are"? Which libs do you think we

could get rid of?

Peter

post111312: qt 5.3.1 build

Sönke Nielsen — Tue, 05 Aug 2014 12:52:52 GMT

qt 5.3.1 build on Linux host/QNX SDP 6.6.0+apps&media failed with

yarr/YarrPattern.cpp:39:29: fatal error: RegExpJitTables.h: No such file or directory

compilation terminated.

My configure arguments are

./configure -prefix /home/soenke/Qt5.3.1/qnx-armv7le -confirm-license -fully-process -xplatform qnx-armle-v7-qcc -no-compile-examples -no-pps -no-dbus -opengl es2 -egl -no-cups -no-xcb -no-eglfs -no-gtkstyle -no-iconv

configure complains when I use "-no-javascript-jit". I've used it for 5.2 but seem to be not supported any more.

A RegExpJitTables.h is located in Src/qtdeclarative/src/qml/RegExpJitTables.h. But using this YarrPattern.cpp results in type mismatch errors later on. So no solution.

Whats wrong?

Sönke

post111310: Qt5.3 with QGLWidget components

Jefferson Biernastki(deleted) — Tue, 05 Aug 2014 12:01:00 GMT

Hi,

is there any limitation using a QGLWidget inside my MainWindow?

When i run my application with a QGLWidget as a component it draws a black box, instead of respecting my clearcolor. If i run this Widget outside of my MainWindow, it works perfectly.

Some examples in Qt requires -opengl desktop make defines, is there any way to do this?

Best regards,

Jefferson Soares Biernastki

post111306: RE: additional libs needed for Qt - my list

Malte Mundt — Tue, 05 Aug 2014 10:13:56 GMT

Wow, looks great, good work!

> -----Original Message-----

> From: Vladimir Minenko [mailto:community-noreply@qnx.com]

> Sent: Tuesday, August 05, 2014 12:08 PM

> To: general-qt

> Subject: Re: additional libs needed for Qt - my list

>

> I'm currently working on an updated version of the platform notes for Qt

> on QNX which contains a section about this. Feel free to comment:

>

> https://codereview.qt-project.org/90653

>

> I think I've got all of them as on your list except libz. libpps and

> libslog2 seem to be optional, since if they are not there, Qt's

> configure will disable according options. Need to check though...

>

>

>

> _______________________________________________

>

> Qt General

> http://community.qnx.com/sf/go/post111305

> To cancel your subscription to this discussion, please e-mail general-

> qt-unsubscribe@community.qnx.com

post111305: Re: additional libs needed for Qt - my list

Vladimir Minenko(deleted) — Tue, 05 Aug 2014 10:08:00 GMT

I'm currently working on an updated version of the platform notes for Qt on QNX which contains a section about this. Feel free to comment:

https://codereview.qt-project.org/90653

I think I've got all of them as on your list except libz. libpps and libslog2 seem to be optional, since if they are not there, Qt's configure will disable according options. Need to check though...

post111304: additional libs needed for Qt - my list

Malte Mundt — Tue, 05 Aug 2014 09:57:28 GMT

Here is the list of additional libs I put into my system to run Qt. Surely helpful if you are building your own!

libcrypto.so.2

libfontconfig.so.1

libfreetype.so.1

libiconv.so.1

libicudata.so.49

libicui18n.so.49

libicuuc.so.49

libpps.so.1

libslog2.so.1

libssl.so.2

libxml2.so.1

libz.so.2

Note that some of those libs are quite large. Following the "memory is cheap nowadays" approach, no one seems to care which libs are really needed and how big they are.

Additionally, Qt itself is inconsistent linking to C++ libs: you need libcpp.so.5 AND libcpp.so.4 AND libcpp-ne.so.5. But who am I to disagree? ;-)

Hope this helps,

- Malte

post111301: Re: Qt 5.3 build from Qnx : unable to run

Thilloy Paul — Mon, 04 Aug 2014 15:14:37 GMT

You got it right !

libfontconfig and libfreetype were missing but after a quick copy and the copy of correct fonts it is now working great :) !

Fonts are much sharper, really nice.

Thank you very much for your help.

Regards

post111299: Re: Qt 5.3 build from Qnx : unable to run

Vladimir Minenko(deleted) — Mon, 04 Aug 2014 13:53:34 GMT

Sorry, I now read your first post more carefully. The build provided by QNX is made with Apps&Media. It is not going to work on a target which does not have it on board. You need to make your own build again if you do not like/need/may use Apps&Media.

post111298: Re: Qt 5.3 build from Qnx : unable to run

Vladimir Minenko(deleted) — Mon, 04 Aug 2014 13:50:17 GMT

Then your build was made with fontconfig, but it is not available on the target. This is strange since you say, you do not use Apps&Media for now. Did you add fontconfig on your own?

post111297: Re: Qt 5.3 build from Qnx : unable to run

Thilloy Paul — Mon, 04 Aug 2014 13:43:01 GMT

It is coming from Qt 4.8 on SDP 6.5

Now we're running on SDP 6.6 (without Apps and Media installed for now)

but the old env var should come from old setup...

with LD_DEBUG set to libs Screen :

libs: load_object: attempt load of libpps.so.1

libs: /proc/boot/libpps.so.1: found; real path:/proc/boot/libpps.so.1

libs: load_elf: Shared library base: 0x78000000

libs: load_elf: libpps.so.1 relro segment is now lazy mapping; 78004000-78005000

libs: load_elf: loaded lib at addr 78000000(text) 78004f00(data)

libs: object libpps.so.1 loaded; real soname: libpps.so.1 loaded from: /proc/boot/libpps.so.1

libs: load_object: attempt load of libPpsLib.so

libs: /mnt/sdhc/rescue/libPpsLib.so: found; real path:/mnt/sdhc/rescue/libPpsLib.so

libs: load_elf: Shared library base: 0x78006000

libs: load_elf: libPpsLib.so relro segment is now lazy mapping; 78008000-78009000

libs: load_elf: loaded lib at addr 78006000(text) 78008f24(data)

libs: object libPpsLib.so loaded; real soname: libPpsLib.so loaded from: /mnt/sdhc/rescue/libPpsLib.so

libs: load_object: attempt load of libRemoteDebugLib.so

libs: /mnt/sdhc/rescue/libRemoteDebugLib.so: found; real path:/mnt/sdhc/rescue/libRemoteDebugLib.so

libs: load_elf: Shared library base: 0x7800a000

libs: load_elf: libRemoteDebugLib.so relro segment is now lazy mapping; 7800d000-7800e000

libs: load_elf: loaded lib at addr 7800a000(text) 7800dcb8(data)

libs: object libRemoteDebugLib.so loaded; real soname: libRemoteDebugLib.so loaded from: /mnt/sdhc/rescue/libRemoteDebugLib.so

libs: load_object: attempt load of libQt5Widgets.so.5

libs: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Widgets.so.5: found; real path:/mnt/sdhc/graphics/opt/qt5/lib/libQt5Widgets.so.5

libs: load_elf: Shared library base: 0x78100000

libs: load_elf: libQt5Widgets.so.5 relro segment is now lazy mapping; 785a6000-785ba000

libs: load_elf: loaded lib at addr 78100000(text) 785a6da0(data)

libs: object libQt5Widgets.so.5 loaded; real soname: libQt5Widgets.so.5 loaded from: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Widgets.so.5

libs: load_object: attempt load of libQt5Network.so.5

libs: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Network.so.5: found; real path:/mnt/sdhc/graphics/opt/qt5/lib/libQt5Network.so.5

libs: load_elf: Shared library base: 0x78600000

libs: load_elf: libQt5Network.so.5 relro segment is now lazy mapping; 78724000-78727000

libs: load_elf: loaded lib at addr 78600000(text) 7872439c(data)

libs: object libQt5Network.so.5 loaded; real soname: libQt5Network.so.5 loaded from: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Network.so.5

libs: load_object: attempt load of libsocket.so.3

libs: /proc/boot/libsocket.so.3: found; real path:/proc/boot/libsocket.so.3

libs: load_elf: Shared library base: 0x78010000

libs: load_elf: libsocket.so.3 relro segment is now lazy mapping; 7802e000-7802f000

libs: load_elf: loaded lib at addr 78010000(text) 7802e6d4(data)

libs: object libsocket.so.3 loaded; real soname: libsocket.so.3 loaded from: /proc/boot/libsocket.so.3

libs: load_object: attempt load of libQt5Sql.so.5

libs: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Sql.so.5: found; real path:/mnt/sdhc/graphics/opt/qt5/lib/libQt5Sql.so.5

libs: load_elf: Shared library base: 0x78040000

libs: load_elf: libQt5Sql.so.5 relro segment is now lazy mapping; 7807b000-7807c000

libs: load_elf: loaded lib at addr 78040000(text) 7807b394(data)

libs: object libQt5Sql.so.5 loaded; real soname: libQt5Sql.so.5 loaded from: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Sql.so.5

libs: load_object: attempt load of libQt5Xml.so.5

libs: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Xml.so.5: found; real path:/mnt/sdhc/graphics/opt/qt5/lib/libQt5Xml.so.5

libs: load_elf: Shared library base: 0x78080000

libs: load_elf: libQt5Xml.so.5 relro segment is now lazy mapping; 780b7000-780b8000

libs: load_elf: loaded lib at addr 78080000(text) 780b74dc(data)

libs: object libQt5Xml.so.5 loaded; real soname: libQt5Xml.so.5 loaded from: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Xml.so.5

libs: load_object: attempt load of libQt5Gui.so.5

libs: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Gui.so.5: found; real path:/mnt/sdhc/graphics/opt/qt5/lib/libQt5Gui.so.5

libs: load_elf: Shared library base: 0x78800000

libs: load_elf: libQt5Gui.so.5 relro segment is now lazy mapping; 78b46000-78b52000

libs: load_elf: loaded lib at addr 78800000(text) 78b46f78(data)

libs: object libQt5Gui.so.5 loaded; real soname: libQt5Gui.so.5 loaded from: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Gui.so.5

libs: load_object: attempt load of libQt5Core.so.5

libs: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Core.so.5: found; real path:/mnt/sdhc/graphics/opt/qt5/lib/libQt5Core.so.5

libs: load_elf: Shared library base: 0x78c00000

libs: load_elf: libQt5Core.so.5 relro segment is now lazy mapping; 78f87000-78f8c000

libs: load_elf: loaded lib at addr 78c00000(text) 78f87904(data)

libs: object libQt5Core.so.5 loaded; real soname: libQt5Core.so.5 loaded from: /mnt/sdhc/graphics/opt/qt5/lib/libQt5Core.so.5

libs: load_object: attempt load of libm.so.2

libs: /proc/boot/libm.so.2: found; real path:/proc/boot/libm.so.2

libs: load_elf: Shared library base: 0x780c0000

libs: load_elf: libm.so.2 relro segment is now lazy mapping; 780e1000-780e2000

libs: load_elf: loaded lib at addr 780c0000(text) 780e1f24(data)

libs: object libm.so.2 loaded; real soname: libm.so.2 loaded from: /proc/boot/libm.so.2

libs: load_object: attempt load of libGLESv2.so.1

libs: /usr/lib/graphics/iMX6X/libGLESv2.so.1: found; real path:/usr/lib/graphics/iMX6X/libGLESv2.so.1

libs: load_elf: Shared library base: 0x78034000

libs: load_elf: libGLESv2.so.1 relro segment is now lazy mapping; 7803c000-7803d000

libs: load_elf: loaded lib at addr 78034000(text) 7803ce88(data)

libs: object libGLESv2.so.1 loaded; real soname: libGLESv2.so.1 loaded from: /usr/lib/graphics/iMX6X/libGLESv2.so.1

libs: load_object: attempt load of libEGL.so.1

libs: /proc/boot/libEGL.so.1: found; real path:/proc/boot/libEGL.so.1

libs: load_elf: Shared library base: 0x780e3000

libs: load_elf: libEGL.so.1 relro segment is now lazy mapping; 780eb000-780ec000

libs: load_elf: loaded lib at addr 780e3000(text) 780ebdfc(data)

libs: object libEGL.so.1 loaded; real soname: libEGL.so.1 loaded from: /proc/boot/libEGL.so.1

libs: load_object: attempt load of libcpp.so.5

libs: /proc/boot/libcpp.so.5: found; real path:/proc/boot/libcpp.so.5

libs: load_elf: Shared library base: 0x78730000

libs: load_elf: libcpp.so.5 relro segment is now lazy mapping; 78782000-78785000

libs: load_elf: loaded lib at addr 78730000(text) 78782ddc(data)

libs: object libcpp.so.5 loaded; real soname: libcpp.so.5 loaded from: /proc/boot/libcpp.so.5

libs: load_object: attempt load of libz.so.2

libs: /proc/boot/libz.so.2: found; real path:/proc/boot/libz.so.2

libs: load_elf: Shared library base: 0x780ed000

libs: load_elf: libz.so.2 relro segment is now lazy mapping; 780fd000-780fe000

libs: load_elf: loaded lib at addr 780ed000(text) 780fde84(data)

libs: object libz.so.2 loaded; real soname: libz.so.2 loaded from: /proc/boot/libz.so.2

libs: load_object: attempt load of libssl.so.2

libs: /usr/lib/libssl.so.2: found; real path:/usr/lib/libssl.so.2

libs: load_elf: Shared library base: 0x785c7000

libs: load_elf: libssl.so.2 relro segment is now lazy mapping; 785f6000-785f8000

libs: load_elf: loaded lib at addr 785c7000(text) 785f66ec(data)

libs: object libssl.so.2 loaded; real soname: libssl.so.2 loaded from: /usr/lib/libssl.so.2

libs: load_object: attempt load of libcrypto.so.2

libs: /usr/lib/libcrypto.so.2: found; real path:/usr/lib/libcrypto.so.2

libs: load_elf: Shared library base: 0x79000000

libs: load_elf: libcrypto.so.2 relro segment is now lazy mapping; 790ef000-790fd000

libs: load_elf: loaded lib at addr 79000000(text) 790efd40(data)

libs: object libcrypto.so.2 loaded; real soname: libcrypto.so.2 loaded from: /usr/lib/libcrypto.so.2

libs: load_object: attempt load of libsqlite3.so.1

libs: /proc/boot/libsqlite3.so.1: found; real path:/proc/boot/libsqlite3.so.1

libs: load_elf: Shared library base: 0x78790000

libs: load_elf: libsqlite3.so.1 relro segment is now lazy mapping; 787f2000-787f3000

libs: load_elf: loaded lib at addr 78790000(text) 787f2488(data)

libs: object libsqlite3.so.1 loaded; real soname: libsqlite3.so.1 loaded from: /proc/boot/libsqlite3.so.1

libs: load_object: attempt load of libslog2.so.1

libs: /proc/boot/libslog2.so.1: found; real path:/proc/boot/libslog2.so.1

libs: load_elf: Shared library base: 0x787f5000

libs: load_elf: libslog2.so.1 relro segment is now lazy mapping; 787fb000-787fc000

libs: load_elf: loaded lib at addr 787f5000(text) 787fbcfc(data)

libs: object libslog2.so.1 loaded; real soname: libslog2.so.1 loaded from: /proc/boot/libslog2.so.1

libs: load_object: attempt load of libicui18n.so.49

libs: /proc/boot/libicui18n.so.49: found; real path:/proc/boot/libicui18n.so.49

libs: load_elf: Shared library base: 0x79200000

libs: load_elf: libicui18n.so.49 relro segment is now lazy mapping; 79302000-79308000

libs: load_elf: loaded lib at addr 79200000(text) 79302b70(data)

libs: object libicui18n.so.49 loaded; real soname: libicui18n.so.49 loaded from: /proc/boot/libicui18n.so.49

libs: load_object: attempt load of libicuuc.so.49

libs: /proc/boot/libicuuc.so.49: found; real path:/proc/boot/libicuuc.so.49

libs: load_elf: Shared library base: 0x79110000

libs: load_elf: libicuuc.so.49 relro segment is now lazy mapping; 791f1000-791fa000

libs: load_elf: loaded lib at addr 79110000(text) 791f1770(data)

libs: object libicuuc.so.49 loaded; real soname: libicuuc.so.49 loaded from: /proc/boot/libicuuc.so.49

libs: load_object: attempt load of libicudata.so.49

libs: /proc/boot/libicudata.so.49: found; real path:/proc/boot/libicudata.so.49

libs: load_elf: Shared library base: 0x79400000

libs: load_elf: libicudata.so.49 relro segment is now lazy mapping; 7a556000-7a557000

libs: load_elf: loaded lib at addr 79400000(text) 7a556f1c(data)

libs: object libicudata.so.49 loaded; real soname: libicudata.so.49 loaded from: /proc/boot/libicudata.so.49

libs: load_object: attempt load of libcpp-ne.so.5

libs: /proc/boot/libcpp-ne.so.5: found; real path:/proc/boot/libcpp-ne.so.5

libs: load_elf: Shared library base: 0x78b60000

libs: load_elf: libcpp-ne.so.5 relro segment is now lazy mapping; 78bac000-78baf000

libs: load_elf: loaded lib at addr 78b60000(text) 78bace18(data)

libs: object libcpp-ne.so.5 loaded; real soname: libcpp-ne.so.5 loaded from: /proc/boot/libcpp-ne.so.5

libs: init: libcpp-ne.so.5 obj->refcount: 1

libs: init: libicudata.so.49 obj->refcount: 1

libs: init: libicuuc.so.49 obj->refcount: 1

libs: init: libicui18n.so.49 obj->refcount: 1

libs: init: libslog2.so.1 obj->refcount: 1

libs: init: libsqlite3.so.1 obj->refcount: 1

libs: init: libcrypto.so.2 obj->refcount: 1

libs: init: libssl.so.2 obj->refcount: 1

libs: init: libz.so.2 obj->refcount: 1

libs: init: libc.so.3 obj->refcount: 1

libs: init: libcpp.so.5 obj->refcount: 1

libs: init: libEGL.so.1 obj->refcount: 1

libs: init: libGLESv2.so.1 obj->refcount: 1

libs: init: libm.so.2 obj->refcount: 1

libs: init: libQt5Core.so.5 obj->refcount: 1

libs: init: libQt5Gui.so.5 obj->refcount: 1

libs: init: libQt5Xml.so.5 obj->refcount: 1

libs: init: libQt5Sql.so.5 obj->refcount: 1

libs: init: libsocket.so.3 obj->refcount: 1

libs: init: libQt5Network.so.5 obj->refcount: 1

libs: init: libQt5Widgets.so.5 obj->refcount: 1

libs: init: libRemoteDebugLib.so obj->refcount: 1

libs: init: libPpsLib.so obj->refcount: 1

libs: init: libpps.so.1 obj->refcount: 1

libs: dlopen("/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so",513)

Mode: LAZY LOCAL

libs: Neither RTLD_GROUP nor RTLD_WORLD specified, assuming RTLD_GROUP | RTLD_WORLD

libs: load_object: attempt load of /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so

libs: /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so: found; real path:/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so

libs: load_elf: Shared library base: 0x79310000

libs: load_elf: libqqnx.so relro segment is now lazy mapping; 793ac000-793b1000

libs: load_elf: loaded lib at addr 79310000(text) 793ac9d8(data)

libs: object /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so loaded; real soname: libqqnx.so loaded from: /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so

libs: load_object: attempt load of libscreen.so.1

libs: /proc/boot/libscreen.so.1: found; real path:/proc/boot/libscreen.so.1

libs: load_elf: Shared library base: 0x78bc0000

libs: load_elf: libscreen.so.1 relro segment is now lazy mapping; 78bd1000-78bd2000

libs: load_elf: loaded lib at addr 78bc0000(text) 78bd1ec4(data)

libs: object libscreen.so.1 loaded; real soname: libscreen.so.1 loaded from: /proc/boot/libscreen.so.1

libs: load_object: attempt load of libfontconfig.so.1

libs: dlopen: Library cannot be found

libs: dlclose(0x8263e30, 1)

You're right it seems that libfontconfig is not found

post111296: Re: RE: Qt 5.3 build from Qnx : unable to run

Vladimir Minenko(deleted) — Mon, 04 Aug 2014 13:33:52 GMT

Good point! But this is valid only for libs loaded by QPA (the "qnx" platform plugin). libfontconfig is loaded esle where.

post111295: Re: Qt 5.3 build from Qnx : unable to run

Vladimir Minenko(deleted) — Mon, 04 Aug 2014 13:31:25 GMT

You usually do not need to set QT_QPA_PLATFORM_PLUGIN_PATH. QT_PLUGIN_PATH should be sufficient. Which SDP are you on? Why is all this QWS* stuff in? I greatly doubt Qt5 will work on QWS... QWS was in use before QPA came up

post111294: RE: Qt 5.3 build from Qnx : unable to run

Malte Mundt — Mon, 04 Aug 2014 13:29:35 GMT

Try LD_DEBUG=libs <name of app> it will show you what libs it's trying to load. I saw the claim "plugin not found" because the system was not smart enough to show what really is missing (e.g. libfontconfig)

> -----Original Message-----

> From: Thilloy Paul [mailto:community-noreply@qnx.com]

> Sent: Monday, August 04, 2014 3:28 PM

> To: general-qt

> Subject: Re: Qt 5.3 build from Qnx : unable to run

>

> The same I posted earlier : /mnt/sdhc/graphics/opt/qt5/plugins

>

> I even tried to put it again in Qt Creator unduer Run Environment

> options... but nothing...

>

>

>

> _______________________________________________

>

> Qt General

> http://community.qnx.com/sf/go/post111293

> To cancel your subscription to this discussion, please e-mail general-

> qt-unsubscribe@community.qnx.com

post111293: Re: Qt 5.3 build from Qnx : unable to run

Thilloy Paul — Mon, 04 Aug 2014 13:28:19 GMT

The same I posted earlier : /mnt/sdhc/graphics/opt/qt5/plugins

I even tried to put it again in Qt Creator unduer Run Environment options... but nothing...

post111292: Re: Qt 5.3 build from Qnx : unable to run

Vladimir Minenko(deleted) — Mon, 04 Aug 2014 13:25:00 GMT

What is the value of the QT_PLUGIN_PATH env var in the shell where you start the app?

post111291: Re: Qt 5.3 build from Qnx : unable to run

Thilloy Paul — Mon, 04 Aug 2014 13:23:56 GMT

Here is my environment variables :

LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll:/lib/dll/font:/mnt/sdhc/rescue:/mnt/sdhc/python32/lib:/usr/lib/graphics/iMX6X:/lib/dll:/proc/boot:/mnt/sdhc/graphics/opt/qt5/lib:/mnt/sdhc/pci

OPTIND=1

PATH=/proc/boot:/bin:/sbin:/opt/bin:/usr/sbin:/usr/bin:/mnt/sdhc/rescue:/mnt/sdhc/python32/bin:/mnt/sdhc/pci

PPID=1

PS1='$(pwd) #'

PS2='> '

PS3='#? '

PS4='+ '

PWD=/

QML2_IMPORT_PATH=/mnt/sdhc/graphics/opt/qt5/imports

QML_IMPORT_PATH=/mnt/sdhc/graphics/opt/qt5/imports

QQNX_PHYSICAL_SCREEN_SIZE=148,46

QT_PLUGIN_PATH=/mnt/sdhc/graphics/opt/qt5/plugins

QT_QPA_FONTDIR=/mnt/sdhc/graphics/opt/qt5/lib/fonts

QT_QPA_PLATFORM_PLUGIN_PATH=/mnt/sdhc/graphics/opt/qt5/plugins/platforms

QT_QWS_FONTDIR=/mnt/sdhc/graphics/opt/qt5/lib/fonts

QWS_DISPLAY=qnx

QWS_KEYBOARD=qnx

QWS_MOUSE_PROTO=qnx

RANDOM=6077

SECONDS=1205

SHELL=/bin/sh

TERM=qansi

TMOUT=0

TMPDIR=/tmp

USER=bee

_=set

bootpath=/mnt/sdhc/rescue

qpath=/mnt/sdhc/graphics/opt/qt5

post111290: Qt 5.3 build from Qnx : unable to run

Thilloy Paul — Mon, 04 Aug 2014 13:13:45 GMT

Hello,

I was working with a personnal compilation of Qt 5.3.

Then I tried Qnx's compilation... impossible to run my application (called Screen) on my imx6 board:

This application failed to start because it could not find or load the Qt platform plugin "qnx".

Here is the output of the console using QT_DEBUG_PLUGINS = 1

-----ONLINE-----

QFactoryLoader::QFactoryLoader() checking directory path "/mnt/sdhc/graphics/opt/qt5/plugins/platforms" ...

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqminimal.so"

Found metadata in lib /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqminimal.so, metadata=

Got keys from plugin meta data ("minimal")

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqoffscreen.so"

Found metadata in lib /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqoffscreen.so, metadata=

Got keys from plugin meta data ("offscreen")

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so"

Found metadata in lib /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so, metadata=

Got keys from plugin meta data ("qnx")

QFactoryLoader::QFactoryLoader() checking directory path "/dev/shmem" ...

QFactoryLoader::QFactoryLoader() looking at "/dev/shmem/inetd.pid"

QElfParser: '/dev/shmem/inetd.pid' is not an ELF object (file too small)

"'/dev/shmem/inetd.pid' is not an ELF object (file too small)"

not a plugin

QFactoryLoader::QFactoryLoader() looking at "/dev/shmem/Screen"

"Plugin verification data mismatch in '/dev/shmem/Screen'"

not a plugin

QFactoryLoader::QFactoryLoader() checking directory path "/mnt/sdhc/graphics/opt/qt5/plugins" ...

loaded library "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so"

QLibraryPrivate::loadPlugin failed on "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so" : "Cannot load library /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so: (Library cannot be found)"

QFactoryLoader::QFactoryLoader() checking directory path "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/platforms" ...

QFactoryLoader::QFactoryLoader() checking directory path "/dev/shmem/platforms" ...

QFactoryLoader::QFactoryLoader() checking directory path "/mnt/sdhc/graphics/opt/qt5/plugins/platforms" ...

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqminimal.so"

Got keys from plugin meta data ("minimal")

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqoffscreen.so"

Got keys from plugin meta data ("offscreen")

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so"

"Cannot load library /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so: (Library cannot be found)"

not a plugin

This application failed to start because it could not find or load the Qt platform plugin "qnx".

Abort (core dumped)

Application finished with exit code 134.

Any ideas ?

Regards,

Paul

post111231: Re: Run Qt 5.3 App on QNX 6.6 target

Kostadin Vardin(deleted) — Fri, 25 Jul 2014 17:33:50 GMT

We have to bear in mind that not all Fonts are under Free License usage!

Qt Creator lists all fonts under "c:Windows/Fonts" directory, but majority of them are licensed to use with Windows distribution.

As Dennis pointed Dejavu is one that works fine and actually this is the Font provided with Qt distribution. Dejavu familiy of fonts is under Free License! And you will not find it under Windows/Fonts directory.

So I think the rule is:-

1) Select a font for particular application. If it is not under Free License, purchase a license for it.

2) Deploy the font to the target, or make it embedded as Resource into Qt application.

post111221: Re: RE: Run Qt 5.3 App on QNX 6.6 target

Vladimir Minenko(deleted) — Fri, 25 Jul 2014 13:08:49 GMT

This is what I meant with "IMHO, this should include a list of OS components and services required for a given framework (here Qt) to run it as expected". Still, IMHO, standard (or "reference") OS images are definitely required. Otherwise, I do not know how to develop and test a 400MB source code package with a very limited number of people...

post111208: RE: Run Qt 5.3 App on QNX 6.6 target

Malte Mundt — Thu, 24 Jul 2014 14:52:27 GMT

A "standard layout" with tons of unknown components isn't a great workaround for lack of documentation. A list of what's required - libs, binaries, enviroment variables, fonts, would be totally sufficient. Embedded designers need to understand what their system actually consists of. "Standard layouts" are the source of most security vulnerabilities in other OSs, let alone bloated memory requirements and slow boot times.

> -----Original Message-----

> From: Vladimir Minenko [mailto:community-noreply@qnx.com]

> Sent: Thursday, July 24, 2014 4:29 PM

> To: general-qt

> Subject: Re: Run Qt 5.3 App on QNX 6.6 target

>

> There should be no need for moving fonts back and forth, when Qt is

> configured to use fontconfig and the "QNX target" has a "standard

> layout".

>

> Generally, the problem is that there is no standard for QNX targets:

> people do their own OS images and get surprised that things stop

> working. Some people see this as an advantage of flexibility, but for

> complex frameworks with tons of equations on the table, like Qt, this

> advantage can quickly become a nightmare. The length of this thread is

> another sign for this. QNX should start standardizing the content and

> configuration of OS images for selected application cases. IMHO, this

> should include a list of OS components and services required for a given

> framework (here Qt) to run it as expected. This issue has already been

> addressed in QNX.

>

> In particular, the recent release of Qt 5.3.0 installers provided here

> was explicitly saying that it can be used for "Qt applications for the

> QNX SDP 6.6 OS and Apps & Media 1.0 software releases". Unfortunately,

> it is did not mention this also includes a certain target OS image which

> is provided as "sample" in Apps & Media 1.0. Qt in that and in any other

> binary build in the future is not guaranteed to work on any target, just

> on those which are close to the one provided in Apps & Media 1.0.

> Anything more generic is just technically not possible...

>

>

>

> _______________________________________________

>

> Qt General

> http://community.qnx.com/sf/go/post111207

> To cancel your subscription to this discussion, please e-mail general-

> qt-unsubscribe@community.qnx.com

post111207: Re: Run Qt 5.3 App on QNX 6.6 target

Vladimir Minenko(deleted) — Thu, 24 Jul 2014 14:29:18 GMT

There should be no need for moving fonts back and forth, when Qt is configured to use fontconfig and the "QNX target" has a "standard layout".

Generally, the problem is that there is no standard for QNX targets: people do their own OS images and get surprised that things stop working. Some people see this as an advantage of flexibility, but for complex frameworks with tons of equations on the table, like Qt, this advantage can quickly become a nightmare. The length of this thread is another sign for this. QNX should start standardizing the content and configuration of OS images for selected application cases. IMHO, this should include a list of OS components and services required for a given framework (here Qt) to run it as expected. This issue has already been addressed in QNX.

In particular, the recent release of Qt 5.3.0 installers provided here was explicitly saying that it can be used for "Qt applications for the QNX SDP 6.6 OS and Apps & Media 1.0 software releases". Unfortunately, it is did not mention this also includes a certain target OS image which is provided as "sample" in Apps & Media 1.0. Qt in that and in any other binary build in the future is not guaranteed to work on any target, just on those which are close to the one provided in Apps & Media 1.0. Anything more generic is just technically not possible...

post111206: Re: Run Qt 5.3 App on QNX 6.6 target

Malte Mundt — Thu, 24 Jul 2014 13:54:18 GMT

> > @Malte. If Qt has been configured for a build using fontconfig, the install

>

> > process does not includes fonts.

>

> Hi Vladimir,

>

> I guess the Qt 5.3 bundle provided here on Foundry27 has been built to use

> fontconfig. So there are no fonts; I guess because on other OSs as soon as you

> say "fontconfig" it is assumed that you have all the fonts required?

>

> So how does this work in practice for QNX now? The new QNX 5.3 installer,

> coming with Qt Creator auto-detecting QNX 6.6 SDP and even including examples

> AND binaries for ARM and x86, is my personal favourite. It gives me "all I

> need", fantastic. Except for the fonts :). So when I build some of the

> examples, they require fonts. Where to go from here?

Ok, it seems some basic fonts are now with QNX SDP 6.6 under /usr/fonts/font_repository. I copied these to my target and in the example I built I now see text. Great.

Cheers,

- Malte

post111205: Re: Run Qt 5.3 App on QNX 6.6 target

Malte Mundt — Thu, 24 Jul 2014 13:05:56 GMT

> @Malte. If Qt has been configured for a build using fontconfig, the install

> process does not includes fonts.

Hi Vladimir,

I guess the Qt 5.3 bundle provided here on Foundry27 has been built to use fontconfig. So there are no fonts; I guess because on other OSs as soon as you say "fontconfig" it is assumed that you have all the fonts required?

So how does this work in practice for QNX now? The new QNX 5.3 installer, coming with Qt Creator auto-detecting QNX 6.6 SDP and even including examples AND binaries for ARM and x86, is my personal favourite. It gives me "all I need", fantastic. Except for the fonts :). So when I build some of the examples, they require fonts. Where to go from here?

Cheers,

- Malte

post111204: Re: Run Qt 5.3 App on QNX 6.6 target

Vladimir Minenko(deleted) — Thu, 24 Jul 2014 12:57:56 GMT

@Malte. If Qt has been configured for a build using fontconfig, the install process does not includes fonts.

post111201: Re: Run Qt 5.3 App on QNX 6.6 target

Dennis Kellly(deleted) — Thu, 24 Jul 2014 11:55:11 GMT

QNX-supplied fonts are under host directory c:\QNX660\target\qnx6\usr\fonts\font_repository\, so using the default fonts.conf will provide "some" fonts.

You should be able to pull Qt-supplied fonts from any Qt distro.

post111199: Re: Run Qt 5.3 App on QNX 6.6 target

Malte Mundt — Thu, 24 Jul 2014 10:05:59 GMT

> Copy C:\qnx660\target\qnx6\etc\fontconfig\fonts.conf to create local.conf

> BUT change the following to use the much richer Qt5 font set...

>           from

>             <dir>/usr/fonts/font_repository</dir>

>           to

>             <dir>/opt/qt5/lib/fonts</dir>

>

With the Qt 5.3 install from this site, it seems fonts are no longer coming with Qt. The directory "fonts" does not exist under lib any more. Where are users supposed to get the fonts from now?

Cheers,

- Malte

post111196: Re: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Thu, 24 Jul 2014 08:08:43 GMT

I ran my 'helloqt' application on the given Vmware image.

It displayed a window properly and that means my 'helloqt' has no problem.

The Vmware image also has Qt binaries in 'opt/qt5' so I've copied Qt 5.3 binaries(entire /opt/qt5 directory) to my QNX target for checking my Qt binaries causes the problem but result is same.

In summary, test program, Qt binaries and QNX screen are good. So the Qt environment of my QNX target might be something wrong.

I'm looking at it but no luck yet. :(

Thanks for the advice.

post111189: Re: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Wed, 23 Jul 2014 23:58:30 GMT

Thanks! I'll find out what's different.

post111188: Re: Run Qt 5.3 App on QNX 6.6 target

Dennis Kellly(deleted) — Wed, 23 Jul 2014 22:54:25 GMT

Glad that fixed it. Handling is inconsistent regarding this... miine works without it.

post111187: Re: Run Qt 5.3 App on QNX 6.6 target

Kostadin Vardin(deleted) — Wed, 23 Jul 2014 22:20:35 GMT

I found the problem.

In graphics.conf file the global input parameter shall include both keyboard and mouse!

Here is the excerpt:

  begin globals

    blit-config = gles2blt

    input = keyboard mouse

    stack-size = 2048

  end globals

Cheers!

post111180: Re: Run Qt 5.3 App on QNX 6.6 target

Kostadin Vardin(deleted) — Wed, 23 Jul 2014 17:09:05 GMT

Here is what hidview captures in "hidview_log.txt".

post111179: Re: Run Qt 5.3 App on QNX 6.6 target

Dennis Kellly(deleted) — Wed, 23 Jul 2014 16:40:36 GMT

Does hidview show the device?

# hidview

HIDD v1.00, v1.00 DDK

Device Address       : 1

Vendor               : 0x413c (DELL)

Product              : 0x2005 (DELL USB Keyboard)

Version              : r1.10

Usage                : Keyboard

Device Address       : 2

Vendor               : 0x045e (Microsoft)

Product              : 0x0040 (Microsoft Wheel Mouse Optical┬«)

Version              : r1.10

Usage                : Mouse

post111178: Re: Run Qt 5.3 App on QNX 6.6 target

Kostadin Vardin(deleted) — Wed, 23 Jul 2014 16:30:58 GMT

Hi Dennis,

I implemented the changes to graphics.conf and also start-up of io-usb and io-hid.

Now I can see the mouse cursor at the center of the screen, but it does not move.

I started "inputck" test program. It captures the keyboard input, but not the mouse.

Kostadin

post111177: keyboard capture on QNX6.5SP1 with Qt5.1

nicolas cumin(deleted) — Wed, 23 Jul 2014 15:23:45 GMT

Hi,

I try to use my usb keyboard with a Qt application.

I use QNX 6.5SP1 with Qt5.1 on iMX6 processeur.

But for the moment when I try to write in a textbox nothing append.

I test with the application hidview-a and I manage to receive data.

It's like Qt not receive screen keyboard event.

Thanks for your answers.

post111173: Re: Run Qt 5.3 App on QNX 6.6 target

Dennis Kellly(deleted) — Wed, 23 Jul 2014 12:00:29 GMT

A working screen/Qt5 VMware image is available at the link below. If you are building for x86, perhaps you can compare it with what you have?

Document

https://drive.google.com/file/d/0B-H5B16bdCbvNGx1bU5XcWFaWkE/edit?usp=sharing

Virtual machine

https://drive.google.com/file/d/0B-H5B16bdCbvb3ZMVXZkNlNDTmc/edit?usp=sharing

IDE workspace for the ifs

https://drive.google.com/file/d/0B-H5B16bdCbveHpHQnhsZ1NhODA/edit?usp=sharing

post111172: Re: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Wed, 23 Jul 2014 11:11:56 GMT

You have more errors than me but there is same error as mine. Good to know it's not only my problem. :)

post111171: Re: Run Qt 5.3 App on QNX 6.6 target

Thilloy Paul — Wed, 23 Jul 2014 09:41:54 GMT

Sorry to jam this thread...perhaps should I open a new one ?

I put QT_DEBUG_PLUGINS to 1 I got :

-----ONLINE-----

QFactoryLoader::QFactoryLoader() checking directory path "/mnt/sdhc/graphics/opt/qt5/plugins/platforms" ...

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqminimal.so"

Found metadata in lib /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqminimal.so, metadata=

Got keys from plugin meta data ("minimal")

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqoffscreen.so"

Found metadata in lib /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqoffscreen.so, metadata=

Got keys from plugin meta data ("offscreen")

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so"

Found metadata in lib /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so, metadata=

Got keys from plugin meta data ("qnx")

QFactoryLoader::QFactoryLoader() checking directory path "/dev/shmem" ...

QFactoryLoader::QFactoryLoader() looking at "/dev/shmem/inetd.pid"

QElfParser: '/dev/shmem/inetd.pid' is not an ELF object (file too small)

"'/dev/shmem/inetd.pid' is not an ELF object (file too small)"

not a plugin

QFactoryLoader::QFactoryLoader() looking at "/dev/shmem/Screen"

"Plugin verification data mismatch in '/dev/shmem/Screen'"

not a plugin

QFactoryLoader::QFactoryLoader() looking at "/dev/shmem/Screen.core"

QElfParser: '/dev/shmem/Screen.core' is an invalid ELF object (shstrtab section header seems to be at 0)

"'/dev/shmem/Screen.core' is an invalid ELF object (shstrtab section header seems to be at 0)"

not a plugin

QFactoryLoader::QFactoryLoader() checking directory path "/mnt/sdhc/graphics/opt/qt5/plugins" ...

loaded library "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so"

QLibraryPrivate::loadPlugin failed on "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so" : "Cannot load library /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so: (Library cannot be found)"

QFactoryLoader::QFactoryLoader() checking directory path "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/platforms" ...

QFactoryLoader::QFactoryLoader() checking directory path "/dev/shmem/platforms" ...

QFactoryLoader::QFactoryLoader() checking directory path "/mnt/sdhc/graphics/opt/qt5/plugins/platforms" ...

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqminimal.so"

Got keys from plugin meta data ("minimal")

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqoffscreen.so"

Got keys from plugin meta data ("offscreen")

QFactoryLoader::QFactoryLoader() looking at "/mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so"

"Cannot load library /mnt/sdhc/graphics/opt/qt5/plugins/platforms/libqqnx.so: (Library cannot be found)"

not a plugin

This application failed to start because it could not find or load the Qt platform plugin "qnx".

post111170: Re: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Wed, 23 Jul 2014 03:33:05 GMT

I'm who have started this thread. I posted my environment variables in first article and it has exact same environment variable you mentioned. Thanks for advice.

post111166: Re: Run Qt 5.3 App on QNX 6.6 target

Dennis Kellly(deleted) — Wed, 23 Jul 2014 01:06:00 GMT

Does your envirnoment include..

QT_PLUGIN_PATH=/opt/qt5/plugins

...assuming you are installed at /opt/qt5.

Also LD_LIBRARY_PATH must include "/opt/qt5/lib"

post111165: Re: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Wed, 23 Jul 2014 01:03:35 GMT

Please ignore error about slogger2.

BTW, there is no way to edit my post?

post111164: Re: Run Qt 5.3 App on QNX 6.6 target

Dennis Kellly(deleted) — Wed, 23 Jul 2014 01:01:22 GMT

Kostadin-

This sequence starts mouse and keyboard..

io-usb -duhci -dohci -dehci

io-hid -dusb

# then start screen

drm_intel_hd

screen

To see the cursor, you must edit your graphics.conf (/usr/lib/graphics/intel-drm/graphics.conf ?) and add

cursor = on

after your "video-mode =" line ... but still between begin and end for "display" - for example

  begin display 2

    video-mode = 800 x 480 @ 60

    cursor = on

    stack-size = 2048

  end display

The attached Qt5 program (for x86) will verify kbd input.

Launch as...

./inputck -platform qnx:no-fullscreen

post111163: Re: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Wed, 23 Jul 2014 01:00:52 GMT

Thanks for reply.

With slogger2 running, it just redirect stdout messages to slog2info. Anyway one error message removed.

I posted additional result with QT_DEBUG_PLUGINS=1 as reply to my post. Thanks again.

post111162: Re: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Wed, 23 Jul 2014 00:51:19 GMT

If I set QT_DEBUG_PLUGINS=1 output is below.

56: Found metadata in lib /opt/qt5/plugins/platforms/libqqnx.so, metadata= ...

...

75: loaded library "/opt/qt5/plugins/platforms/libqqnx.so"

...

78: QLibraryPrivate::loadPlugin failed on "/opt/qt5/plugins/platforms/libqqnx.so" : "Cannot load library /opt/qt5/plugins/platforms/libqqnx.so: (Library cannot be found)"

As output message, looks like some modules found libqqnx.so but QLibraryPrivate didn't.

I'll post additional info if I figure out more about that.

Any help would be appreciated.

<Full output log>

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

QFactoryLoader::QFactoryLoader() checking directory path "/root/qt5test/platforms" ...

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

QFactoryLoader::QFactoryLoader() checking directory path "/opt/qt5/plugins/platforms" ...

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

QFactoryLoader::QFactoryLoader() looking at "/opt/qt5/plugins/platforms/libqminimal.so"

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

Found metadata in lib /opt/qt5/plugins/platforms/libqminimal.so, metadata=

{

    "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.2",

    "MetaData": {

        "Keys": [

            "minimal"

        ]

    },

    "className": "QMinimalIntegrationPlugin",

    "debug": false,

    "version": 328449

}

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

Got keys from plugin meta data ("minimal")

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

QFactoryLoader::QFactoryLoader() looking at "/opt/qt5/plugins/platforms/libqoffscreen.so"

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

Found metadata in lib /opt/qt5/plugins/platforms/libqoffscreen.so, metadata=

{

    "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.2",

    "MetaData": {

        "Keys": [

            "offscreen"

        ]

    },

    "className": "QOffscreenIntegrationPlugin",

    "debug": false,

    "version": 328449

}

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

Got keys from plugin meta data ("offscreen")

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

QFactoryLoader::QFactoryLoader() looking at "/opt/qt5/plugins/platforms/libqqnx.so"

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

Found metadata in lib /opt/qt5/plugins/platforms/libqqnx.so, metadata=

{

    "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.2",

    "MetaData": {

        "Keys": [

            "qnx"

        ]

    },

    "className": "QQnxIntegrationPlugin",

    "debug": false,

    "version": 328449

}

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

Got keys from plugin meta data ("qnx")

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

loaded library "/opt/qt5/plugins/platforms/libqqnx.so"

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

QLibraryPrivate::loadPlugin failed on "/opt/qt5/plugins/platforms/libqqnx.so" : "Cannot load library /opt/qt5/plugins/platforms/libqqnx.so: (Library cannot be found)"

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

This application failed to start because it could not find or load the Qt platform plugin "qnx".

Available platform plugins are: minimal, offscreen, qnx.

Reinstalling the application may fix this problem.

Abort

post111161: Re: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Wed, 23 Jul 2014 00:41:47 GMT

I was on it when I posting. Anyway after setting up /usr/lib/graphics/intel-drm/graphics.conf, gles2-gear displayed properly now. But Qt program output is same. And output is same whether I run drm-intel and screen or not. That's why I thought screen stuff and Qt stuff separately.

post111160: Re: Run Qt 5.3 App on QNX 6.6 target

Kostadin Vardin(deleted) — Tue, 22 Jul 2014 22:54:46 GMT

In addition, please find attached sloginfo_log.txt where you can see screen connected successfully with io-hid, but when I start Qt application there is no Input!

Kostadin Vardin

post111159: Re: Run Qt 5.3 App on QNX 6.6 target

Kostadin Vardin(deleted) — Tue, 22 Jul 2014 22:17:47 GMT

Hi Danis,

Item_1-> Fonts is fixed now based on your instructions.

Still have problem with Item_2-> input.

I am starting io-hid in following way: "io-hid -d usb /dev/io-usb/io-usb"

Before to start screen I have Keyboard input( usb keyboard ).

After screen and Qt app are started, I do not have any Input working( missing mouse cursor ).

Is there any setting for Qt, related to the Input( kbd& mouse )?

Any idea?

Thank you,

Kostadin Vardin

post111158: Re: Run Qt 5.3 App on QNX 6.6 target

Dennis Kellly(deleted) — Tue, 22 Jul 2014 18:35:54 GMT

>>>1) Fonts: Texts are not displayed ( empty boxes for each character ). It appears that font system is not setup properly.

To use the qnx freetype system with Qt, I did the following:

a. Put this in your environment

FONTCONFIG_FILE=/etc/fontconfig/local.conf

b. Create and deploy

/etc/fontconfig/local.conf

Copy C:\qnx660\target\qnx6\etc\fontconfig\fonts.conf to create local.conf

BUT change the following to use the much richer Qt5 font set...

          from

            <dir>/usr/fonts/font_repository</dir>

          to

            <dir>/opt/qt5/lib/fonts</dir>

c. Make sure you have deployed

/usr/lib/libfontconfig.so.1

d. When you build your program, make sure you use a font which is actually on the target.  Qt Creator will present a list of fonts from the windows host!  If you pick a font not on target, results will not be what you want.  You may have to add the font you want from your target to windows (so you can select it).  I always have good results with "Dejavu Sans"

>>>2) Each one of the applications above are logging into slogger2 following:

  - QQNX: failed to open navigator pps, errno=2

  - QQnxVirtualKeyboard: Unable to open ""/pps/services/input/control" for keyboard: No such file or directory

  - QQNX failed to open buttons pps, errno=2

Sorry - you will just have to live with these bogus messages - unless you fix and rebuild your own libraries.  They seem to be vestiges of QNX-CAR2.  Input WILL function even if you see these messages.

post111156: Re: Run Qt 5.3 App on QNX 6.6 target

Kostadin Vardin(deleted) — Tue, 22 Jul 2014 16:49:52 GMT

Hello,

As the topic is hot for me as well,l I decided to jump in.

I have experienced similar problem, but able to start an example application( came with Qt ) and also an application showing just a window with a button(created by myself).

I have following problems:

1) Fonts: Texts are not displayed ( empty boxes for each character ). It appears that font system is not setup properly. Please advise how to setup Qt font system and where to find the fonts.

2) Each one of the applications above are logging into slogger2 following:

  - QQNX: failed to open navigator pps, errno=2

  - QQnxVirtualKeyboard: Unable to open ""/pps/services/input/control" for keyboard: No such file or directory

  - QQNX failed to open buttons pps, errno=2

  Obviously mouse and keyboard are not setup properly and interesting why their services are expected from pps. I have started io-hid1? Please advise.

Thanks in forward,

Kostadin

post111155: Re: Run Qt 5.3 App on QNX 6.6 target

Thilloy Paul — Tue, 22 Jul 2014 16:17:51 GMT

> Hello.

> I'm trying to run Qt widget application on QNX 6.6 target.

> What I've done is below.

> This application failed to start because it could not find or load the Qt

> platform plugin "qnx".

Hello,

I have the same result : trying to run my Qt 5.3 app with your Qt build

post111153: Re: Run Qt 5.3 App on QNX 6.6 target

Dennis Kellly(deleted) — Tue, 22 Jul 2014 11:37:00 GMT

In addiition to the need to start slogger2, you did not mention if you tested screen functionality. Make sure you get correct graphics when you run sw-vsync and gles2-gears.

BTW - you can read messages sent to slooger2 (all Qt debug messages) using slog2info.

post111152: Re: Run Qt 5.3 App on QNX 6.6 target

Vladimir Minenko(deleted) — Tue, 22 Jul 2014 11:34:14 GMT

The root cause has already been posted to the console: the slogger2 service is not running the target. slogger2 is required for all current binary builds of Qt for QNX. Check your OS image build script and add the slogger2 service to the startup.

PS. Unfortunately, you will most probably not find anything via Google on that topic.

post111148: Run Qt 5.3 App on QNX 6.6 target

qnx1 developer(deleted) — Tue, 22 Jul 2014 02:16:06 GMT

Hello.

I'm trying to run Qt widget application on QNX 6.6 target.

What I've done is below.

- Install qt on Ubuntu 12.04 via qt-enterprise-linux-x86-qnx-5.3.1.run downloaded from Qt digia website.

- Setup QNX 6.6 + Qt 5.3, Linux + Qt 5.3 kit on QtCreator.

- Build 'helloqt' program via New Project -> Applications -> Qt Widget Application template without any modification that displays an empty window.

- Run 'helloqt' for linux and it works properly.

- Prepare QNX target with QNX 6.6 SDP + Graphics Patch

- Copy 'helloqt' for QNX to /root/qt5test/ on target.

- Copy below directories to /opt/qt5/ on QNX target.

  <QT_INSTALL_PATH>/5.3/qnx6-x86/lib

  <QT_INSTALL_PATH>/5.3/qnx6-x86/plugins

  <QT_INSTALL_PATH>/5.3/qnx6-x86/qml

- Add below to /root/.profile for environment setting.

  export LD_LIBRARY_PATH=/lib:/usr/lib:/lib/dll:/opt/qt5/lib:/opt/qnx6/x86/lib:/opt/qnx6/x86/usr/lib:/opt/qnx6/x86/lib/dll

  export QQNX_PHYSICAL_SCREEN_SIZE=150,90

  export QT_PLUGIN_PATH=/opt/qt5/plugins

  export QML2_IMPORT_PATH=/opt/qt5/qml

  export GRAPHICS_ROOT=/usr/lib/graphics/intel-drm

- run '/sbin/drm-intel' on QNX target.(my target has graphic processor from intel)

- run 'screen'

- run '/root/qt5test/helloqt'

<Result>

# cd /root/qt5test/

# ./helloqt

slog2_api: cannot connect to slogger2 server...errno=No such file or directory

Error registering slogger2 buffer!

This application failed to start because it could not find or load the Qt platform plugin "qnx".

Available platform plugins are: minimal, offscreen, qnx.

Reinstalling the application may fix this problem.

Abort

#

- Three libraries below exist in '/opt/qt5/plugins/platforms'.

  libqminimal.so

  libqoffscreen.so

  libqqnx.so

- Result is same no matter running drm-intel or screen.

- Below is 'env' result.

_=/usr/bin/env

SSH_CONNECTION=192.168.100.150 62661 192.168.100.177 22

PATH=/sbin:/usr/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/bin:/opt/sbin:/bin:/sbin:/usr/bin:/usr/sbin

SHELL=/bin/sh

TMPDIR=/tmp

HOSTNAME=localhost

USER=root

PROCESSOR=x86

MAIL=/var/spool/mail/root

LD_LIBRARY_PATH=/lib:/usr/lib:/lib/dll:/opt/qt5/lib:/opt/qnx6/x86/lib:/opt/qnx6/x86/usr/lib:/opt/qnx6/x86/lib/dll

HOME=/root

SSH_CLIENT=192.168.100.150 62661 22

QNX_HOST=/

QNX_TARGET=/

GRAPHICS_ROOT=/usr/lib/graphics/intel-drm

QQNX_PHYSICAL_SCREEN_SIZE=150,90

TERM=xterm

QML2_IMPORT_PATH=/opt/qt5/qml

QT_PLUGIN_PATH=/opt/qt5/plugins

QNX_CONFIGURATION=/etc/qnx

SSH_TTY=/dev/ttyp1

SYSNAME=nto

LOGNAME=root

I'd googling but no luck and stuck on this.

Please let me know if any additional information is needed and any suggestions would be appreciated.

post111115: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

Kostadin Vardin(deleted) — Fri, 18 Jul 2014 22:59:27 GMT

Hi all again,

I have problems with unzipping rel7762 : Qt 5.3.0 Development Environment for QNX OS 6.6 (armv7 and x86 targets) file.

I downloaded it twice with Internet Explorer and Chrome, but in both cases experienced the same problem. When trying to unzip got the message as in the attachment.

Please help,

Kostadin Vardin

post111112: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

Kostadin Vardin(deleted) — Fri, 18 Jul 2014 21:16:56 GMT

I was checking almost every day, but just today realized that Qt5.x for QNX6.6 arm and x86 was released.

Thank you,

Kostadin Vardin

post111111: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

Kostadin Vardin(deleted) — Fri, 18 Jul 2014 21:08:53 GMT

When is the target day for release of LGPL version of Qt5.3 for x86? I am not talking for "... Early Access...."

For more than 2 months I have being told that it is in final V&V phase and very soon will be released.

Recently it was published a patch for the Screen and infrastructure. Is that somehow related?

Thank you in forward,

Kostadin Vardin

post111091: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

robort smith — Thu, 17 Jul 2014 13:50:00 GMT

Ok ! It's really a surprise ! Thank you very much!

post111090: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

Grant Courville — Thu, 17 Jul 2014 13:47:09 GMT

Robort, you should now have access to the Qt and the Screen projects now -- just log out and back in to Foundry27.

post111089: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

robort smith — Thu, 17 Jul 2014 13:31:39 GMT

Thank you very much!

post111088: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

Malte Mundt — Thu, 17 Jul 2014 13:30:11 GMT

> Thank you for your reply . But I think the links you posted are inner links ,

> and I can't connect to it

You need to be "member" of the "UI Early Access Project" here on Foundry27.

post111086: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

robort smith — Thu, 17 Jul 2014 13:20:56 GMT

Thank you for your reply . But I think the links you posted are inner links ,and I can't connect to it

post111083: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

Grant Courville — Thu, 17 Jul 2014 12:46:31 GMT

With respect to Qt for QNX 6.5 SP1, we have made QNX Screen available here (non-GA): http://community.qnx.com/sf/frs/do/viewRelease/projects.ui_early_access_program/frs.650sp1_screen.june_2014

We have also pre-compiled Qt for QNX 6.5 SP1 and have this posted here: http://community.qnx.com/sf/frs/do/listReleases/projects.ui_early_access_program/frs.qt_libraries_not_a_qnx_product . This was done as a convenience for our customers and is the LGPL version of Qt. If you would like a fully supported commercial version of Qt 5.x for QNX 6.5 and QNX 6.6, contact Digia and they will be happy to provide this to you.

We (QNX) have ported, optimized and integrated Qt on QNX for a few years now and it is in use by many customers across many markets.

Grant

post111082: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

Gervais Mulongoy — Thu, 17 Jul 2014 11:10:50 GMT

Maybe PtRaw will be more suitable for you?

www.qnx.com/developers/docs/6.5.0_sp1/index.jsp?topic=%2Fcom.qnx.doc.photon_prog_guide%2Fdraw.html

post111081: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

robort smith — Thu, 17 Jul 2014 08:41:53 GMT

Hi ,Malte

Thank you for your reply. And now I am trying to use Photon MicroGUI to show video that input form a camera.But the Photon MicroGUI failed for the Widget " PtImageArea" seems didn't support contents refreshment.

Best Regards,

Robort

post111080: Re: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

Malte Mundt — Thu, 17 Jul 2014 08:15:27 GMT

Hi Robert,

> It's really not convenient to use Qt 4.7 on QNX . When will a IDE will support

> Qt for QNX 6.5 officially?

This is not so much a question of an IDE or of Qt itself. Qt 5.x is running on top of QNX via some kind of OS/HW abstraction layer. Little is known about it - who wrote it, who maintains it, does it make optimal use of QNX... not known, at least not to me. :) But what I know is that it relies on the new Screen Graphics Subsystem, which was officially released with 6.6. For 6.5, there is (was?) a prerelease available via an early access program, but I haven't heard of a release of "Screen" for 6.5 yet.

Regards,

- Malte

post111075: When will Qt 5.3 suppoort QNX 6.5 SP1 ?

robort smith — Thu, 17 Jul 2014 02:09:49 GMT

It's really not convenient to use Qt 4.7 on QNX . When will a IDE will support Qt for QNX 6.5 officially?

post111013: RE: Qt medical demo apps

WS Yeo — Thu, 10 Jul 2014 07:57:02 GMT

Hi,

Maybe the link is wrong.

I could access with this link.

http://community.qnx.com/integration/viewvc/viewvc.cgi/src/qt-everywhere-opensource-src-4.7.1/?root=qt_qnx&system=exsy1001

post111012: Re: Qt medical demo apps

Shiau Suan Choong — Thu, 10 Jul 2014 06:45:51 GMT

Hi,

The link is not working and I cannot browse any files.

http://community.qnx.com, community.qnx.com/integration/viewvc/viewvc.cgi/src/qt-everywhere-opensource-src-4.7.1/?root=qt_qnx&system=exsy1001&js=58808A00698E21201E08BBC3401DF5D0&us=uses096ca7bbb57ed32570473753

post110997: Re: Qt medical demo apps

Dennis Kellly(deleted) — Wed, 09 Jul 2014 13:49:53 GMT

The links on that page under "Source Code" are working - you can browse the repository. So I don't understand your issue.

To download from the repository, the "svn" instructions are pretty clear.

post110995: Qt medical demo apps

Shiau Suan Choong — Wed, 09 Jul 2014 13:39:40 GMT

Hi all,

I am checking on this website:

http://community.qnx.com/sf/wiki/do/viewPage/projects.qt/wiki/Downloads?showDetails=true

and I would like to know how can I download the source from src/qt-everywhere-opensource-src-4.7.1/?

Thanks.

post110994: Re: Keyboard capture : modifiers & keypad

Vladimir Minenko(deleted) — Wed, 09 Jul 2014 13:16:01 GMT

I've just made a simple test app based on a widget template project which filters all key events and also processes all events in the usual way. I've tested it on imx6 sabrelite with the apps and media sample OS image, a US usb keyboard attached and with Qt 5.3.1. All keys incl. modifies are reported as expected.

Not sure if it is about a different keyboard layout or a driver... This escapes my QNX knowledge, but this is not a generic issue in Qt on QNX, unless it is a broken Qt build

{code}

#include "mainwindow.h"

#include "ui_mainwindow.h"

MainWindow::MainWindow(QWidget *parent) :

    QMainWindow(parent),

    ui(new Ui::MainWindow)

{

    ui->setupUi(this);

    installEventFilter(this);

}

bool MainWindow::eventFilter(QObject *obj, QEvent *event)

{

    if (event->type() == QEvent::KeyPress) {

        QKeyEvent *keyEvent = static_cast<QKeyEvent *>(event);

        qDebug("Filered a key press %d", keyEvent->key());

        return false; // keep in the loop for further processing

    } else {

        // standard event processing

        return QObject::eventFilter(obj, event);

    }

}

void MainWindow::keyPressEvent(QKeyEvent *event)

{

    qDebug("Key event received:");

    qDebug() << "\tno modifier pressed: " << event->modifiers().testFlag(Qt::NoModifier);

    qDebug() << "\tkey: " << event->key();

}

MainWindow::~MainWindow()

{

    delete ui;

}

{code}

post110980: Keyboard capture : modifiers & keypad

Thilloy Paul — Tue, 08 Jul 2014 16:11:14 GMT

Hello,

I'm trying to capture keyboards events : it seems that it is impossible to get Alt or AltGr modifiers.

At the same time : NumLock seems to have no effect, if I press a keypad key I always get the non-numeric key ( for example key 9 gives page up).

Is it a problem of keyboard driver ?

I use a usb keyboard on my sabrelite board.

post110900: Re: QDialog always Full screen

Thilloy Paul — Tue, 01 Jul 2014 06:56:53 GMT

As the solution was found in the Qt Bug Tracker thread I post it here also:

the option is -platform qnx:no-fullscreen

Then all windows will be opened normal by default (even main window). If you want FullScreen, then use showFullscreen

post110894: Re: QDialog always Full screen

Thilloy Paul — Mon, 30 Jun 2014 10:02:00 GMT

Oh my bad, sorry, but yes I was using the correct command: MyScreen -qpa qnx:no-fullscreen

Still...it is opening full screen...

post110893: Re: QDialog always Full screen

Vladimir Minenko(deleted) — Mon, 30 Jun 2014 09:54:34 GMT

The correct start command is:

MyScreen -qpa qnx:no-fullscreen

(watch "nofullscreen" vs. "no-fullscreen")

post110892: Re: QDialog always Full screen

Thilloy Paul — Mon, 30 Jun 2014 09:32:54 GMT

So to be correct and clear.... my app is named MyScreen

I should so start my app with > MyScreen -qpa qnx:nofullscreen

then this option set, shouldn't all dialogs opened not in fullscreen mode ?

post110891: Re: QDialog always Full screen

Vladimir Minenko(deleted) — Mon, 30 Jun 2014 09:10:55 GMT

As discussed on the Qt bug tracker all windows, will open in full screen by default, not matter what. This happens on the window level in QPA. Your quote for the related QPA option is not correct: a dash is missing. It should be "-qpa qnx:no-fullscreen"

post110890: Re: QDialog always Full screen

Thilloy Paul — Mon, 30 Jun 2014 08:22:44 GMT

I keep replying to myself as I'm still looking for a solution to my problem...

I posted the Qt::Tool problem on the Qt Bug Tracker... I was replied to launch my app with -qpa qnx:nofullscreen option to force it to be non full screen, but no result so far still the same issue.

Anybody is able to open QDialog which are not fullscreen ?

post110635: Re: QDialog always Full screen

Thilloy Paul — Tue, 10 Jun 2014 07:51:53 GMT

I'm moving this thread up as Qt 5.3 doesn't seem to correct the issue...

I found a QTBUG : https://snusmumriken.qtproject.c.bitbit.net/browse/QTBUG-32433 which seems related... but was apparently fixed...

My problem is a mix between those two because :

- If I don't open the QDialog with the flags Qt::Tool set, my Dialog will be full screen

- If I open with Qt::Tool, the Dialog isn't modal, it can loose focus with a mouse click.

post110623: Re: QDialog always Full screen

Thilloy Paul — Fri, 06 Jun 2014 09:30:43 GMT

My Dialog is opened using exec() ...but I tried show, showNormal... nothing matters I even tried to set a maximum size ... when I get the size with size() I got the correct size...but it doesn't match the one displayed on the screen

post110622: Re: QDialog always Full screen

Sergio Ahumada(deleted) — Fri, 06 Jun 2014 09:06:11 GMT

Hi,

Are you using .show() by any chance? If so, could you please try .showNormal() instead??

Cheers,

Sent from my BlackBerry 10 smartphone.

Original Message

From: Thilloy Paul

Sent: Freitag, 6. Juni 2014 10:57

To: general-qt

Reply To: general-qt@community.qnx.com

Subject: Re: QDialog always Full screen

This is actually part of a bigger problem :

QDialog > always open full screen => so setWindowFlags(Qt::Tool)

but windows with Qt::Tool flag seems to be non modal : it can loose focus if the mouse is pressed somewhere else...

In order to workaround this problem I used to activateWindow() when the focus was lost but this function is not working anymore since 5.3 ...

_______________________________________________

Qt General

http://community.qnx.com/sf/go/post110621

To cancel your subscription to this discussion, please e-mail general-qt-unsubscribe@community.qnx.com

post110621: Re: QDialog always Full screen

Thilloy Paul — Fri, 06 Jun 2014 08:57:22 GMT

This is actually part of a bigger problem :

QDialog > always open full screen => so setWindowFlags(Qt::Tool)

but windows with Qt::Tool flag seems to be non modal : it can loose focus if the mouse is pressed somewhere else...

In order to workaround this problem I used to activateWindow() when the focus was lost but this function is not working anymore since 5.3 ...

post110607: Re: Compiling QT 5.3 for Qnx

Thilloy Paul — Thu, 05 Jun 2014 14:51:01 GMT

Hi,

Thanks Sergio, sure we can use the doc generated by another install of Qt 5.3... but I wanted to avoid installing another version just for the doc.

post110606: Re: Compiling QT 5.3 for Qnx

Sergio Ahumada(deleted) — Thu, 05 Jun 2014 14:43:20 GMT

Hi,

I was able to reproduce this on Linux, so I filed a bug report upstream https://bugreports.qt-project.org/browse/QTBUG-39479

Cheers,

post110605: QDialog always Full screen

Thilloy Paul — Thu, 05 Jun 2014 14:30:57 GMT

Hello,

I want to display a QDialog which only takes a part of my screen...

But if I don't set the window flags to Qt::Tool ... it will always shows Full Screen, not matter what...

Am I missing something ?

Regards,

Paul