Adding "blueZ" library - linker options where ?
-
@AnneRanch said in Adding "blueZ" library - linker options where ?:
now I need to add path
And what hinders you to add it?
@Christian-Ehrlicher said in Adding "blueZ" library - linker options where ?:
@AnneRanch said in Adding "blueZ" library - linker options where ?:
now I need to add path
And what hinders you to add it?
I cannot "search for "bluetooth" file using "find . -name "bluetooth" I am getting folders , not a file.
-
@Christian-Ehrlicher said in Adding "blueZ" library - linker options where ?:
@AnneRanch said in Adding "blueZ" library - linker options where ?:
now I need to add path
And what hinders you to add it?
I cannot "search for "bluetooth" file using "find . -name "bluetooth" I am getting folders , not a file.
@AnneRanch
Hi
The syntax is like
LIBS += -L/usr/local/lib -lmath
so with big -L we can give the path and with little -l we give the library name.I assume that is what you mean by adding path ?
-
@AnneRanch
Hi
The syntax is like
LIBS += -L/usr/local/lib -lmath
so with big -L we can give the path and with little -l we give the library name.I assume that is what you mean by adding path ?
@mrjj Yes, but the -L path is wrong
-
"I am sooo confused..."
Should
sudo apt-get install libbluetooth-dev
install , by default, into/usr/include/bluetooth ??
How do I get "bluetooth" out of
libbluetooth-dev ?
doesn't GCC works with "static" or "shared" library as oppose of Windows "DLL" ?
And how does .pro
QT bluetooth
fits into scheme of things?
-
"I am sooo confused..."
Should
sudo apt-get install libbluetooth-dev
install , by default, into/usr/include/bluetooth ??
How do I get "bluetooth" out of
libbluetooth-dev ?
doesn't GCC works with "static" or "shared" library as oppose of Windows "DLL" ?
And how does .pro
QT bluetooth
fits into scheme of things?
@AnneRanch said in Adding "blueZ" library - linker options where ?:
libbluetooth-dev
This installs the include files, not the lib itself, so it has no relation to -L.
You need libbluetooth to get the lib and in that package you can see where the lib is installed.
Using the packages of your distribution there is no need to use -L as the lib will be installed in standard libs location. -
@AnneRanch said in Adding "blueZ" library - linker options where ?:
libbluetooth-dev
This installs the include files, not the lib itself, so it has no relation to -L.
You need libbluetooth to get the lib and in that package you can see where the lib is installed.
Using the packages of your distribution there is no need to use -L as the lib will be installed in standard libs location.@jsulm
Sorry , but my problem is in OS itself - it refuses to install libbluetooth-dev for so far unknown reason.Please put this thread on hold until I fix that.
BTW one can install library using menu in .pro file, of course one has to know from where and what. Duh.
Then the -L/-l options are handled by QtCreator itself.
-
Since you installed that library through the package manager, the paths shall already be good and you just have to link to the appropriate library.
Since you are on Linux you can also take advantage of pkg-config and use:
CONFIG += link_pkgconfig PKGCONFIG += bluez -
@AnneRanch said in Adding "blueZ" library - linker options where ?:
Sorry , but my problem is in OS itself - it refuses to install libbluetooth-dev for so far unknown reason.
What exact error do you get ?
-
@AnneRanch said in Adding "blueZ" library - linker options where ?:
Sorry , but my problem is in OS itself - it refuses to install libbluetooth-dev for so far unknown reason.
What exact error do you get ?
@SGaist I am not sure I want to discuss it here in public. Is is rather complex , but if you re interested - is there away I can send it to you private or do you want the link to the "Linux" forum? That wold save me time.
Basically some issue with "grub" unable to "update / upgrade" and consequently "install" also fails. Pretty messy. -
If you have a grub issue then you have a system issue that is unrelated to Qt nor programming so there's indeed something messed up with your computer.
