Good day. You need to write a program that will be launched in Debian on an Orange Pi device. The main code was given to me. For a start, I decided to make it work in Windows. I connected curl libraries to the project, as well as libcrypto and libssl. Everything worked, now you need to achieve the same in Debian. The studio here already, as I understand it, does not fit. I will write in Qt. The questions are:

On the curl website, when downloading the library by the target platform, I chose Debian, as a result, the .deb file was downloaded. As I understand it, they can install the library directly into the system, but not connect it to the project (and on the download page it was said that it was better not to install it, but directly from the system console). How then to connect this library to Qt? With the rest of the libs, I suppose you will have to do the same.

How generally to compile the code in the application under linux? I've never done anything like that before. I’ll google it for now, of course, but maybe someone’s answer will save me a lot of time.

    3 answers 3

    In general, as in Windows ... Install the necessary packages - compiler, IDE, or their headers.

    apt install qtcreator curl libcrypto++6 libcrypto++-dev libssl1.1 libssl-dev cpp

    (packages whose names end with the suffix "-dev" contain * .h files and source code)

      Adding the library to QtCreator is done by editing the .pro CMakeLists.txt file in the project directory. You can read about the file syntax at https://habrahabr.ru/post/155467/

      Or you can register the library in the project parameters in the assembly options.

        The best way to save time is to hire someone who knows at least something to do. But our time is not worth anything, because the tasks are not given to those who can perform them, but to those whose time is worth nothing. And the most annoying thing here is that the one whose time is worth nothing willingly takes to work, thereby maintaining this order.

        Libraries are of two types: for runtime (to run something) and for development (header files + archives of characters with which you can link). For this, almost every library package in Debian has its twin brother with the suffix -dev, which hints at "for developers".

        Qt, some kind of "studio" or another cool IDE with a green "run" button is not necessary at all, you can write code in any text editor like a notebook. The truth is to learn how this "magic green button" collects the code and turns it into a binary - it is much more difficult. For example, automake is often used in Linux, which is often run from the IDE. If you don't like it, there are other build systems. Selection is one of the key features of Linux.

        When the application is finished, to compile it, as with almost any application, you will need to run only the make , perhaps after the configuration script ./configure

        But it is even better not to "write in Qt", but at least try to figure out what it is "Qt", but rather just say: "this job is not in my profile, I will not do it."