I am trying to run Manual Examples of Intel pin tool kit 3.5 in x64 architecture using Ubuntu...
but i am unable to build and got errors like
make[1]:Entering directory '/home/desktop/source/tools/ManualExamples' make libs
make[1]:Entering directory '/home/desktop/source/tools/ManualExamples'
make[1]:Nothing to be done for libs
i tried run these samples through command
$ cd source/tools/ManualExamples
$ make inscount0.test TARGET=intel64
Related
I am trying to get the above development system working, I am starting with a Varicsite NANO compute module. I am trying to get QT 5 setup to develop. I have been unable to find a good Debian guide on how to do that. I would eventually want the QT application to run in kiosk mode without the Weston desktop.
I have Debian built using their instructions of building Debian for the IMX8 board. It runs fine Weston comes up on boot.
I have installed the following packages on the target device.
sudo
apache2
php
jq
curl
qtwayland5
gdb
gdbserver
I have attempted to follow their guide on getting QT to work for YOCTO(not Debian) and have not gotten it to work. QT is installed but their Debian build does not come with a full sdk. Nor do they detail all of the packages that need to be installed.
I have also tried following this guide, but it was written for an RPI and X11 not wayland/Weston so some of the steps seem wrong especially in all of the packages it wants you to install.
https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/
Is there a good guide on how to do this, I was thinking of trying to combine the two guides by using his lines to set up rsync and such but I still do not have a full SDK without the right qmake.
My host system is UBUNTU 16.04
I have a desktop(ubuntu 14.04 64 bit) QT application which uses libpqxx(c++ library for Postgres). The GUI app is an interface to the postgress database and does a lot of operations. Now, I am trying to port this application to a raspberry pi3. I started with a test QT app. Used cross-compile tool chain to build the test app on desktop and deployed it on pi. It works like a charm. However, when I follow the same steps to deploy my actual app on pi, its giving me compile time error
fatal error: pqxx/pqxx: No such file directory.
I have the library linked in .pro file via -lpqxx -lpq. I have also installed libpqxx on pi3. It works on my desktop with Qt 5.6.1 GCC 64 bit kit but doesn't work on pi with Rpi3 Qt kit. Please help.
New Edit:
I added pqxx library path in my .pro file. It looks like this now :
target.path = /home/pi
INSTALLS +=target
unix: LIBS += -L$$PWD/../../../../../../usr/local/lib/ -lpqxx
INCLUDEPATH += $$PWD/../../../../../../usr/local/include/pqxx
DEPENDPATH += $$PWD/../../../../../../usr/local/include/pqxx
unix: PRE_TARGETDEPS += $$PWD/../../../../../../usr/local/lib/libpqxx.a
The previous error is gone. However, it gives me this error now:
/home/pragya/ep/PHOENIX/GUI/LUXE_GUI/../../../../../../usr/local/lib//libpqxx.a: error adding symbols: File format not recognized
Any Ideas?
I have built a static x86 Qt5.5 library with VS2013 using:
configure -static -prefix D:\Qt\qt-5.5.0-x86-static -opensource -release -static-runtime -nomake examples -no-compile-examples -static-runtime -nomake tools -no-iconv -qt-zlib -skip qtwebkit -confirm-license -qmake -opengl desktop -no-angle -nomake tests -target xp
After that I used this static library build a static-link exe of my Qml App. It can run everywhere in my windows which has been installed Qt5.5.
Then I used VMware Workstation to install a pure Windows XP SP3 only installed VC2008 runtime not VC2013 runtime.
Firstly, I copy the exe into this XP. It can run but had nothing to show. I need kill it in taskmgr.
Second, I copy all folders in D:\Qt\qt-5.5.0-x86-static\qml to the root dir of my exe, it can run. But it shows me only a blank window with correct window title.
I think I have listen all the advise in Deploying Qt 5 App on Windows. But why the qml parts cannot be compiled into static library? How can I let my app not show blank?
P.S. Even if I use windeployqt to deploy share-link library version of app. It also shows me blank window. But it can run on Windows 7.
The output of qtdiag on my virtual XP:
Qt 5.5.0 (i386-little_endian-ilp32 static release build; by MSVC 2013)
on "windo ws" OS: Windows XP [winnt version 5.1.2600]
Architecture: i386; features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2
Library info: PrefixPath: D:\Qt\qt-5.5.0-x86-static
DocumentationPath: D:\Qt\qt-5.5.0-x86-static\doc HeadersPath:
D:\Qt\qt-5.5.0-x86-static\include LibrariesPath:
D:\Qt\qt-5.5.0-x86-static\lib LibraryExecutablesPath:
D:\Qt\qt-5.5.0-x86-static\bin BinariesPath:
D:\Qt\qt-5.5.0-x86-static\bin PluginsPath:
D:\Qt\qt-5.5.0-x86-static\plugins ImportsPath:
D:\Qt\qt-5.5.0-x86-static\imports Qml2ImportsPath:
D:\Qt\qt-5.5.0-x86-static\qml ArchDataPath:
D:\Qt\qt-5.5.0-x86-static DataPath: D:\Qt\qt-5.5.0-x86-static
TranslationsPath: D:\Qt\qt-5.5.0-x86-static\translations
ExamplesPath: D:\Qt\qt-5.5.0-x86-static\examples TestsPath:
D:\Qt\qt-5.5.0-x86-static\tests SettingsPath:
Standard paths [... denote writable entry]: DesktopLocation:
"Desktop" *C:\Documents and Settings\Administrator\
The final conclusion:
The problem is the graphic driver in my virtual Windows XP. It can run on other real PCs.
But there is a sad problem to static build of QML.
I have found this:
https://forum.qt.io/topic/22035/qml-apps-not-runnable-using-static-build-up-to-qt-5-0-1-release/24
The reason why I need copy such folders Qt QtQuick.2 QtQuick is that those lib cannot be compile-loaded. Even if I add them into .pro file. From Qt 5.0 to Qt 5.5. The official side seems do not like people use QML by static-link. So, it is waste of time to do static build of QML app.
Qt Quick applications need 3d acceleration in order to work. This is based on either OpenGL, DirectX via Angle or some kind of software renderer that comes with the commercial version of Qt. Since you specifically exclude Angle in your config, you need a proper OpenGL driver. Make sure that OpenGL works on your machine. You'll find tools for that.
I don't think that is has something to do with missing C++ standard libraries (VC2013 runtime), because in this case your application would crash during start and not run. Qt Quick graphic issues however often lead to a running black app that is writing warnings to the console.
Further debugging can be done using the qtdiag.exe command line tool that comes with Qt (It comes with the online installer. I don't know where it is when you build from source). It checks for you which graphic driver is used and often can show error messages.
I wanted to migrate my Qt 4 app to use Qt 5 instead. These instructions failed, due to some differences with how MXE builds Qt 5, including the fact that it uses modularised Qt tarballs, instead of one large tarball.
Here are the full instructions:
Get it:
git clone https://github.com/mxe/mxe.git
Install build dependencies
Build Qt 5 for Windows:
cd mxe && make qtbase
This will first build its dependencies and the cross-build tools;
It should take less than an hour on a fast machine with decent internet access.
Due to the new modular nature of Qt 5, various major Qt components are now in different tarballs. The one selected above, qtbase, should give you enough functionality to run ordinary GUI apps, which is all I needed for my own (smallish) app.
If you want to build all of Qt 5 instead, you'll need to run make qt5 (instead of make qtbase). Note that it will take a lot longer to complete, so be sure that you need the extra functionality.
Get to the directory of your app, and run the Qt Makefile generator tool:
<mxe root>/usr/bin/i686-w64-mingw32.static-qmake-qt5
Build your project:
make
You should find the binary in the ./release directory:
wine release/foo.exe
Some notes:
This was tested on my 64-bit Debian 8, and on Windows of course.
The output is a 32-bit static executable, which will work well on 64-bit Windows.
If you want a 64-bit executable, build Qt with:
make MXE_TARGETS=x86_64-w64-mingw32.static qtbase
The default MXE_TARGETS value is i686-w64-mingw32.static.
The git checkout command is not correct. You now have to get their stable branch or it will fail building.
git clone https://github.com/mxe/mxe.git
should be...
git clone -b stable https://github.com/mxe/mxe.git
That alone fixed all my issues with qtbase building but leaving no qt folder when done. Then qt5 target would fail with obscure errors. Deleted folder, checked out stable and it worked flawlessly.
For those who directly want a GCC10 64bit compiled Qt5 (for filesystem lib for example),
Here are the full instructions:
Get it:
git clone https://github.com/mxe/mxe.git
Install build dependencies
Build Qt 5 for Windows with gcc10 64bits plugin activated :
cd mxe && make MXE_TARGETS=x86_64-w64-mingw32.shared MXE_PLUGIN_DIRS=plugins/gcc10 qt5
After 2-3 hours of build you can build your app (in your .pro directory) :
<mxe root>/usr/x86_64-w64-mingw32.shared/qt5/bin/qmake
Export path of compiler & build your project:
export PATH=<mxe root>/usr/bin:$PATH
make
You should find the binary in the ./release directory & start it with wine (or wine64) :
wine foo.exe
I don't really know why, but I needed to add the MXE compiler directory to the wine path because it's couldn't find the DLLs :
WINEPATH="<mxe root>/usr/x86_64-w64-mingw32.shared/bin/" wine64 foo.exe
If you try to do this, for me work fine!
su
mv mxe /opt/mxe
cd /opt/mxe && make
I built a qt application that uses opengl on linux and am trying to build it on windows. I used g++ to make it on linux and am using command line nmake for Visual Studio 2005 to build it on windows. When I tryed to build my application I typed
qmake -makefile app.pro
nmake
The nmake failed and said "bool qt_win_owndc_required"... already defined in QtOpenGld.lib ..
one or more multiply definded symbols found
When I tried building one of the examples (hellogl) with opengl it resulted in the same error message. But when I tried building a different example without opengl it worked fine. Do I need to do something special to build the opengl library correctly? Is there something that I am not thinking of?
Are you running qmake in a Visual Studio 2005 Command prompt?
A google search turned up this post: http://www.delta3d.org/forum/viewtopic.php?showtopic=15723
The guy fixed the problem by rebuilding the source.