HTTP library

jenya7

Typically a library like this would have an install target in its Makefile (that derives from the PRO file). Not the case here.

The built library is in the qhttp_build_dir/xbin folder.
The headers needed to compile code to use the library remain in the qhttp/src folder.

You need to install the resulting library and public headers into a system library or include folder.
Alternatively, add the folder to your project:
INCLUDEPATH += /a/path/to/qhttp/src
LIBS += -L/a/path/to/qhttp_build_dir/xbin -lqhttp
Use absolute paths unless you are certain about relative paths.

thank you. it works.

jenya7

@jsulm said in HTTP library:

@jenya7 Please reread what I wrote, I did not write anything about INCLUDEPATH...

I missed -L. :)

jenya7

Now it compiles good. But in run time I get

Starting /home/pi/Projects/build-AgroLogicWidget-Desktop-Debug/AgroLogicWidget...
/home/pi/Projects/build-AgroLogicWidget-Desktop-Debug/AgroLogicWidget: error while loading shared libraries: libqhttp.so.1: cannot open shared object file: No such file or directory

/home/pi/Projects/build-AgroLogicWidget-Desktop-Debug/AgroLogicWidget exited with code 127

JonB

@jenya7
So where is your libqhttp.so.1 and how does your application locate it at runtime? And if it can be found, does running ldd on it reveal any missing dependencies?

jsulm

@jenya7 said in HTTP library:

libqhttp.so.1

Copy it into your build folder (/home/pi/Projects/build-AgroLogicWidget-Desktop-Debug).
As another solution you can also set LD_LIBRARY_PATH=/home/pi/Projects/build-AgroLogicWidget-Desktop-Debug in your Run configuration in QtCreator.

jenya7

@jsulm said in HTTP library:

@jenya7 said in HTTP library:

libqhttp.so.1

Copy it into your build folder (/home/pi/Projects/build-AgroLogicWidget-Desktop-Debug).
As another solution you can also set LD_LIBRARY_PATH=/home/pi/Projects/build-AgroLogicWidget-Desktop-Debug in your Run configuration in QtCreator.

it happens in Debug as well.

jenya7

@JonB said in HTTP library:

@jenya7
So where is your libqhttp.so.1 and how does your application locate it at runtime? And if it can be found, does running ldd on it reveal any missing dependencies?

How do we know which one is missing?

ldd /home/pi/qhttp/xbin/libqhttp.so.1
	linux-vdso.so.1 (0xbef67000)
	/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6f16000)
	libQt5Network.so.5 => /lib/arm-linux-gnueabihf/libQt5Network.so.5 (0xb6d6a000)
	libQt5Core.so.5 => /lib/arm-linux-gnueabihf/libQt5Core.so.5 (0xb68f0000)
	libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb68c6000)
	libatomic.so.1 => /lib/arm-linux-gnueabihf/libatomic.so.1 (0xb68ad000)
	libstdc++.so.6 => /lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb6766000)
	libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb66e4000)
	libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb66b7000)
	libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6569000)
	libz.so.1 => /lib/arm-linux-gnueabihf/libz.so.1 (0xb653e000)
	/lib/ld-linux-armhf.so.3 (0xb6f5c000)
	libicui18n.so.63 => /lib/arm-linux-gnueabihf/libicui18n.so.63 (0xb62f0000)
	libicuuc.so.63 => /lib/arm-linux-gnueabihf/libicuuc.so.63 (0xb616a000)
	libpcre2-16.so.0 => /lib/arm-linux-gnueabihf/libpcre2-16.so.0 (0xb60ee000)
	libdouble-conversion.so.1 => /lib/arm-linux-gnueabihf/libdouble-conversion.so.1 (0xb60ca000)
	libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb60b7000)
	libglib-2.0.so.0 => /lib/arm-linux-gnueabihf/libglib-2.0.so.0 (0xb5fa7000)
	libicudata.so.63 => /lib/arm-linux-gnueabihf/libicudata.so.63 (0xb45a9000)
	libpcre.so.3 => /lib/arm-linux-gnueabihf/libpcre.so.3 (0xb4532000)

JonB

@jenya7
This shows it is not missing any dependencies. So how do you think your application should know to find and load it from /home/pi/qhttp/xbin?

jenya7

@JonB said in HTTP library:

@jenya7
This shows it is not missing any dependencies. So how do you think your application should know to find and load it from /home/pi/qhttp/xbin?

I have

LIBS += -L/home/pi/qhttp/xbin -lqhttp

in pro file

piervalli

@jenya7
Sorry, Why do you want use this library? I checked source code, httpclient does not use Qnetworkmanager but, it sends directly with QTcpSocket.

Thanks

jenya7

@piervalli said in HTTP library:

@jenya7
Sorry, Why do you want use this library? I checked source code, httpclient does not use Qnetworkmanager but, it sends directly with QTcpSocket.

Thanks

I'm not tied to the lib. any lib I can include in my project without having a heart attack will go. do you have one to suggest?

JonB

@jenya7 said in HTTP library:

LIBS += -L/home/pi/qhttp/xbin -lqhttp

This tells the linker where to locate the libqhttp.a file while linking. I am not sure that it puts anything into the executable to tell it to look in that directory for the libqhttp.so file at runtime. See @jsulm's last post earlier on above.

jenya7

@JonB said in HTTP library:

@jenya7 said in HTTP library:

LIBS += -L/home/pi/qhttp/xbin -lqhttp

This tells the linker where to locate the libqhttp.a file while linking. I am not sure that it puts anything into the executable to tell it to look in that directory for the libqhttp.so file at runtime. See @jsulm's last post earlier on above.

There is no libqhttp.so in Debug folder. I don't know how it's linked in run time.

JonB

@jenya7

@JonB said in HTTP library:

See @jsulm's last post earlier on above.

jenya7

well...no luck with the lib. do we have something more user friendly?

jsulm

@jenya7 said in HTTP library:

There is no libqhttp.so in Debug folder

I told you to copy it into your build folder - why don't you simply try that?

jenya7

@jsulm said in HTTP library:

@jenya7 said in HTTP library:

There is no libqhttp.so in Debug folder

I told you to copy it into your build folder - why don't you simply try that?

I tried it of course. never ignore your suggestions :)

jsulm

@jenya7 OK, then change to your build folder and execute

ldd YOUR_EXECUTABLE_FILE_NAME

What is the output?

jenya7

@jsulm said in HTTP library:

@jenya7 OK, then change to your build folder and execute
ldd YOUR_EXECUTABLE_FILE_NAME
What is the output?

 linux-vdso.so.1 (0xbed98000)
	/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6f24000)
	liblgpio.so.1 => /usr/local/lib/liblgpio.so.1 (0xb6ed3000)
	libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6ec0000)
	libQt5MultimediaWidgets.so.5 => /lib/arm-linux-gnueabihf/libQt5MultimediaWidgets.so.5 (0xb6e9b000)
	libpulse-mainloop-glib.so.0 => /lib/arm-linux-gnueabihf/libpulse-mainloop-glib.so.0 (0xb6e87000)
	libpulse.so.0 => /lib/arm-linux-gnueabihf/libpulse.so.0 (0xb6e31000)
	libglib-2.0.so.0 => /lib/arm-linux-gnueabihf/libglib-2.0.so.0 (0xb6d21000)
	libQt5Widgets.so.5 => /lib/arm-linux-gnueabihf/libQt5Widgets.so.5 (0xb67d4000)
	libQt5Multimedia.so.5 => /lib/arm-linux-gnueabihf/libQt5Multimedia.so.5 (0xb66d7000)
	libQt5Gui.so.5 => /lib/arm-linux-gnueabihf/libQt5Gui.so.5 (0xb6257000)
	libQt5Network.so.5 => /lib/arm-linux-gnueabihf/libQt5Network.so.5 (0xb60c4000)
	libQt5Xml.so.5 => /lib/arm-linux-gnueabihf/libQt5Xml.so.5 (0xb6082000)
	libQt5Bluetooth.so.5 => /lib/arm-linux-gnueabihf/libQt5Bluetooth.so.5 (0xb5f90000)
	libQt5Core.so.5 => /lib/arm-linux-gnueabihf/libQt5Core.so.5 (0xb5b16000)
	libGLESv2.so.2 => /lib/arm-linux-gnueabihf/libGLESv2.so.2 (0xb5af7000)
	libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb5acd000)
	libatomic.so.1 => /lib/arm-linux-gnueabihf/libatomic.so.1 (0xb5ab4000)
	libstdc++.so.6 => /lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb596d000)
	libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb58eb000)
	libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb58be000)
	libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb5770000)
	/lib/ld-linux-armhf.so.3 (0xb6f39000)
	libQt5OpenGL.so.5 => /lib/arm-linux-gnueabihf/libQt5OpenGL.so.5 (0xb571c000)
	libpulsecommon-12.2.so => /usr/lib/arm-linux-gnueabihf/pulseaudio/libpulsecommon-12.2.so (0xb569b000)
	libcap.so.2 => /lib/arm-linux-gnueabihf/libcap.so.2 (0xb5686000)
	librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb566f000)
	libdbus-1.so.3 => /lib/arm-linux-gnueabihf/libdbus-1.so.3 (0xb561e000)
	libpcre.so.3 => /lib/arm-linux-gnueabihf/libpcre.so.3 (0xb55a7000)
	libpng16.so.16 => /lib/arm-linux-gnueabihf/libpng16.so.16 (0xb556b000)
	libharfbuzz.so.0 => /lib/arm-linux-gnueabihf/libharfbuzz.so.0 (0xb546d000)
	libz.so.1 => /lib/arm-linux-gnueabihf/libz.so.1 (0xb5442000)
	libQt5DBus.so.5 => /lib/arm-linux-gnueabihf/libQt5DBus.so.5 (0xb53a9000)
	libicui18n.so.63 => /lib/arm-linux-gnueabihf/libicui18n.so.63 (0xb515b000)
	libicuuc.so.63 => /lib/arm-linux-gnueabihf/libicuuc.so.63 (0xb4fd5000)
	libpcre2-16.so.0 => /lib/arm-linux-gnueabihf/libpcre2-16.so.0 (0xb4f59000)
	libdouble-conversion.so.1 => /lib/arm-linux-gnueabihf/libdouble-conversion.so.1 (0xb4f35000)
	libGLdispatch.so.0 => /lib/arm-linux-gnueabihf/libGLdispatch.so.0 (0xb4eb6000)
	libX11-xcb.so.1 => /lib/arm-linux-gnueabihf/libX11-xcb.so.1 (0xb4ea4000)
	libX11.so.6 => /lib/arm-linux-gnueabihf/libX11.so.6 (0xb4d82000)
	libxcb.so.1 => /lib/arm-linux-gnueabihf/libxcb.so.1 (0xb4d53000)
	libICE.so.6 => /lib/arm-linux-gnueabihf/libICE.so.6 (0xb4d2d000)
	libSM.so.6 => /lib/arm-linux-gnueabihf/libSM.so.6 (0xb4d16000)
	libXtst.so.6 => /lib/arm-linux-gnueabihf/libXtst.so.6 (0xb4d01000)
	libsystemd.so.0 => /lib/arm-linux-gnueabihf/libsystemd.so.0 (0xb4c64000)
	libwrap.so.0 => /lib/arm-linux-gnueabihf/libwrap.so.0 (0xb4c4c000)
	libsndfile.so.1 => /lib/arm-linux-gnueabihf/libsndfile.so.1 (0xb4bd0000)
	libasyncns.so.0 => /lib/arm-linux-gnueabihf/libasyncns.so.0 (0xb4bbb000)
	libfreetype.so.6 => /lib/arm-linux-gnueabihf/libfreetype.so.6 (0xb4b18000)
	libgraphite2.so.3 => /lib/arm-linux-gnueabihf/libgraphite2.so.3 (0xb4ae7000)
	libicudata.so.63 => /lib/arm-linux-gnueabihf/libicudata.so.63 (0xb30e9000)
	libXau.so.6 => /lib/arm-linux-gnueabihf/libXau.so.6 (0xb30d6000)
	libXdmcp.so.6 => /lib/arm-linux-gnueabihf/libXdmcp.so.6 (0xb30c1000)
	libbsd.so.0 => /lib/arm-linux-gnueabihf/libbsd.so.0 (0xb3099000)
	libuuid.so.1 => /lib/arm-linux-gnueabihf/libuuid.so.1 (0xb3082000)
	libXext.so.6 => /lib/arm-linux-gnueabihf/libXext.so.6 (0xb3063000)
	libXi.so.6 => /lib/arm-linux-gnueabihf/libXi.so.6 (0xb3045000)
	liblzma.so.5 => /lib/arm-linux-gnueabihf/liblzma.so.5 (0xb3014000)
	liblz4.so.1 => /lib/arm-linux-gnueabihf/liblz4.so.1 (0xb2fe8000)
	libgcrypt.so.20 => /lib/arm-linux-gnueabihf/libgcrypt.so.20 (0xb2f0e000)
	libnsl.so.1 => /lib/arm-linux-gnueabihf/libnsl.so.1 (0xb2eea000)
	libFLAC.so.8 => /lib/arm-linux-gnueabihf/libFLAC.so.8 (0xb2e8a000)
	libogg.so.0 => /lib/arm-linux-gnueabihf/libogg.so.0 (0xb2e75000)
	libvorbis.so.0 => /lib/arm-linux-gnueabihf/libvorbis.so.0 (0xb2e3e000)
	libvorbisenc.so.2 => /lib/arm-linux-gnueabihf/libvorbisenc.so.2 (0xb2dac000)
	libresolv.so.2 => /lib/arm-linux-gnueabihf/libresolv.so.2 (0xb2d88000)
	libgpg-error.so.0 => /lib/arm-linux-gnueabihf/libgpg-error.so.0 (0xb2d5e000)

no obvious warnings

jsulm

@jenya7 I'm confused now: according to this output your app does not link to libqhttp.so.