you don't seem to have 'make' or 'qmake' in your PATH
-
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
After that I replaced it into a directory called qt-5.13(replaced via....mv qt-everywhere-src-5.13.1 ~/qt-5.13)
Again, this is not how it works!
You do NOT call configure from the source code directory for out of source builds, but from an empty directory!
Again:# Create an empty directory: mkdir build_qt # Go to that empty directory: cd build_qt # Call configure from the Qt source code directory: ../qt5_sourcecode/configure...@jsulm pwd is qt-5.13,here I need to create directory?if yes ,I created and tried getting
bash : ./configure : No such file or directory
please go through this link https://forum.qt.io/topic/106766/can-we-change-the-compiler-in-qmake/28 I followed this pdf...
-
@jsulm pwd is qt-5.13,here I need to create directory?if yes ,I created and tried getting
bash : ./configure : No such file or directory
please go through this link https://forum.qt.io/topic/106766/can-we-change-the-compiler-in-qmake/28 I followed this pdf...
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
bash : ./configure : No such file or directory
Please read more carefully what I'm writing!
You need to use complete path (or relative) to configure!
That's why I wrote:../qt5_sourcecode/configureYou can use absolute path instead of relative:
PATH_TO_YOUR_QT_SOURCE_DIRECTORY/configure -
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
bash : ./configure : No such file or directory
Please read more carefully what I'm writing!
You need to use complete path (or relative) to configure!
That's why I wrote:../qt5_sourcecode/configureYou can use absolute path instead of relative:
PATH_TO_YOUR_QT_SOURCE_DIRECTORY/configureyes,I gave the hole path /home/beagle/qt-5.13/.configure
its starts configuring but not succeed...
After few minutes its stops with error
/home/beagle/qt-5.13/build_qt/qtbase/bin/qmake: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
-
but libstdc++.so.6 library is present in my system...
location is:
/usr/arm-linux-gnueabihf/lib/libstdc++.so.6
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
is present in my system
It needs to be present in your sysroot since you're cross compiling
-
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
is present in my system
It needs to be present in your sysroot since you're cross compiling
-
when I gave the command below
qmake --version
The result is:
Qmake version 3.1
using Qt version 5.9.5 in /usr/lib/x86_64-linux-gnuIs this any issue?
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
Is this any issue?
No, this is qmake from Qt delivered by Ubuntu.
qmake for your cross compiled Qt will be built when you cross compile Qt, but I don't know why you get that libstdc++ error. -
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
Is this any issue?
No, this is qmake from Qt delivered by Ubuntu.
qmake for your cross compiled Qt will be built when you cross compile Qt, but I don't know why you get that libstdc++ error.@jsulm while getting that error,I inserted below line in my qmake.conf file
QMAKE_LIBDIR=/home/beagle/BBB/sysroot/usr/lib/arm-linux-gnueabihf
after this tried once again for configure...now facing the error
meta.o: file not recognized: File format not recognized
collect2:error: ld returned 1 exit status
Makefile:189: recipe for target '../bin/qmake'failed
make: ***[../bin/qmake] Error1when I checked meta.o file with the command
file meta.o
The result is:
meta.o: ELF 64-bit LSB relocatable,x86-64,version 1(SYSV) ,with debug info,not strippedHere is the attachement
Where other file are 32bit ELF with ARM.....
-
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
How to install this libraries libstdc++.so.6 and libgcc_s.so.1
There is nothing to install: these files are part of your sysroot.
"meta.o: ELF 64-bit LSB relocatable,x86-64,version 1(SYSV) ,with debug info,not stripped" - this file is apparently built for Intel x86_64, not ARM.
Delete the content of the build directory, run configure and build again. And check your configure call (parameter you pass to it).
Take a look at this: https://wiki.qt.io/BeagleBone_Black_Beginners_Guide
-
In addition to @jsulm, delete the build folder itself and re-create it. There might be hidden files created that can still influence.
-
This is the simple question where I am going to ask..
But I want clarification....
I need to configure on my host machine or target machine?(My ans is,on host machine is it correct?)
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
on host machine is it correct?
yes, cross compilation means that you build on host but for target device
-
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
on host machine is it correct?
yes, cross compilation means that you build on host but for target device
-
Hi,
Now I am able to configure,but gettting one warning...please go throught the attachement..
can I proceed next...
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
can I proceed next
If you don't need QDoc then yes you can...
-
Actually,I am cross compiling for embedded beagleboneboard
where I want to execute c,c++ files...for that QDoc is required?
If I want QDoc means,what I do for this?
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
for that QDoc is required?
No, it is only required to build Qt documentation which you do not need to run Qt applications.
"If I want QDoc means,what I do for this?" - read the warning - it already suggests what to do...
-
@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:
for that QDoc is required?
No, it is only required to build Qt documentation which you do not need to run Qt applications.
"If I want QDoc means,what I do for this?" - read the warning - it already suggests what to do...
