libcurl during build missing

[belamu]

During make I get the following error:

make[2]: *** No rule to make target '<parentdir>/ceema/3rdparty/curl/lib/libcurl.so', needed by 'libceema.so.0.0.1'.  Stop.
make[1]: *** [CMakeFiles/Makefile2:118: src/CMakeFiles/ceema.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

I have installed: sudo dnf install libcurl-devel libcurl
I am confused why make needs something from /3rdparty/curl since this directory or submodule does not exist in the repository.

What do I need to make this libcurl.so available?

Sorry to create an issue even though I expect that I need to change something, not ceema. I don't see another way of asking for support.

Btw: to get to this point, the following installations were necessary on Fedora 37:
sudo dnf install openssl-devel libsodium-devel curlpp-devel mbedtls-devel

[hbruintjes]

Try setting the CMake variable USE_OWN_CURL_LIB to OFF (use ccmake) and reconfigure, that should direct it to use the system version of curl.

[belamu]

Thanks! That helped to remove this error. For all usually-not-(c)make-users like me that end up here:
instead of cmake ../ call cmake -DUSE_OWN_CURL_LIB=OFF ../. ccmake is a interactive way of calling cmake where you can set the variable.

The next error with missing libpurple was fixed with sudo dnf install libpurple-devel.

The next error is a missing zip.h. sudo dnf install zipios-devel zipper-devel does not fix this error but sudo dnf install libzip-devel does fix it.

Then the make runs through (with a lot of -Wpessimizing-move warnings!).

[belamu]

I am not sure if I should close this issue because I looks to me as anyone else should get the same error.

[hbruintjes]

Yeah there is a bit of a usability/documentation issue here, so this can be left open (though the project itself mostly has gone into hiatus).

[belamu]

Since I expect my next problem not to be caused by ceema but my missing knowlegde of pidgin, I'll misuse this issue instead of creating a new one:

I read on the general website that I should "install" a plugin by copying the .so file into ~/.purple/plugins. So I copied the created /build/libceema.so and /build/libceema.so.0.0.1 into this directory (which I had to create).
Then I started pidgin but there is no entry Threema under Accounts and ceema is not shown in the list of plugins (Tools-Plugin) and Threema is not in the list of Protocols in the Add Account dialog.

What do I need to do to use ceema in pidgin?

[belamu]

Yeah there is a bit of a usability/documentation issue here, so this can be left open (though the project itself mostly has gone into hiatus).

Too bad. I was happy to see that there is activity on this project because openMittsu hasn't had activity for 1 year and gave errors for me and so I assumed that maybe the Threema API and the data backup format might have changed.

[hbruintjes]

Plugin probably fails to load. Start pidgin with debug logs (-d) to see if you can spot the issue. That's a pidgin thing though.

And yes, the Threema protocol has been extended, which is also why something happened here. It's a fairly niche product though (or so it seems), so not many alternatives around.

[belamu]

The log indeed shows some information:

(19:19:05) plugins: probing ~/.purple/plugins/libceema.so
(19:19:05) plugins: ~/.purple/plugins/libceema.so is not usable because the 'purple_init_plugin' symbol could not be found.  Does the plugin call the PURPLE_INIT_PLUGIN() macro?

grep gives that purple_init_plugin does exist in your source code:
/src/threepl/prpl/threepl.cpp:extern "C" gboolean purple_init_plugin(PurplePlugin *plugin) {
and purple_init_plugin exists in /build/src/libthreepl.so.

[belamu]

It's a fairly niche product though (or so it seems), so not many alternatives around.

For me it's also just one person that keeps me using Threema, otherwise it would be Signal only. That's quite usable on Desktop. No idea about signal plugin for pidgin.

[hbruintjes]

grep gives that purple_init_plugin does exist in your source code: /src/threepl/prpl/threepl.cpp:extern "C" gboolean purple_init_plugin(PurplePlugin *plugin) { and purple_init_plugin exists in /build/src/libthreepl.so.

Can you check that the symbol was exported with nm? Something along the lines of
nm -D /build/src/libthreepl.so | grep init_plugin

Sometimes something can go wrong during linking. Alternatively, check with ldd that all dependencies can be resolved (e.g., ldd /build/src/libthreepl.so)

[belamu]

Can you check that the symbol was exported with nm? Something along the lines of
nm -D /build/src/libthreepl.so | grep init_plugin
Yes, that exists:

% nm -D build/src/libthreepl.so | grep init_plug
00000000002103b6 T purple_init_plugin

Sometimes something can go wrong during linking. Alternatively, check with ldd that all dependencies can be resolved (e.g., ldd /build/src/libthreepl.so)

% ldd build/src/libthreepl.so
        linux-vdso.so.1 (0x00007ffd727dd000)
        libceema.so.0.0.1 => ~/tmp/ceema-threema-pidgin-plugin-builddir/ceema/build/libceema.so.0.0.1 (0x00007f2a7da00000)
        libzip.so.5 => /lib64/libzip.so.5 (0x00007f2a7e370000)
        libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f2a7dec0000)
        libcurl.so.4 => /lib64/libcurl.so.4 (0x00007f2a7d957000)
        libmbedtls.so.14 => /lib64/libmbedtls.so.14 (0x00007f2a7e33c000)
        libsodium.so.23 => /lib64/libsodium.so.23 (0x00007f2a7de67000)
        libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f2a7d600000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f2a7d877000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f2a7e31a000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f2a7d424000)
        libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f2a7e307000)
        liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f2a7d84c000)
        libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f2a7d371000)
        libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007f2a7ce00000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f2a7de4d000)
        libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007f2a7d2d4000)
        libnghttp2.so.14 => /lib64/libnghttp2.so.14 (0x00007f2a7d2a9000)
        libidn2.so.0 => /lib64/libidn2.so.0 (0x00007f2a7d25c000)
        libssh.so.4 => /lib64/libssh.so.4 (0x00007f2a7cd8e000)
        libpsl.so.5 => /lib64/libpsl.so.5 (0x00007f2a7d838000)
        libssl.so.3 => /lib64/libssl.so.3 (0x00007f2a7cceb000)
        libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f2a7cc94000)
        libldap.so.2 => /lib64/libldap.so.2 (0x00007f2a7cc2e000)
        liblber.so.2 => /lib64/liblber.so.2 (0x00007f2a7d24a000)
        libbrotlidec.so.1 => /lib64/libbrotlidec.so.1 (0x00007f2a7e2f4000)
        libmbedx509.so.1 => /lib64/libmbedx509.so.1 (0x00007f2a7cc0b000)
        libmbedcrypto.so.7 => /lib64/libmbedcrypto.so.7 (0x00007f2a7cb85000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f2a7e3b4000)
        libunistring.so.2 => /lib64/libunistring.so.2 (0x00007f2a7c9cd000)
        libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f2a7c8f0000)
        libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f2a7d231000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f2a7d22a000)
        libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f2a7c8df000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f2a7c8d8000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f2a7c8c5000)
        libevent-2.1.so.7 => /lib64/libevent-2.1.so.7 (0x00007f2a7c86c000)
        libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f2a7c84c000)
        libbrotlicommon.so.1 => /lib64/libbrotlicommon.so.1 (0x00007f2a7c829000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f2a7c7fc000)
        libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007f2a7c7c2000)

So it looks as if most went fine. There are two lines without =>: linux-vdso.so.1 and /lib64/ld-linux-x86-64.so.2

I read on the general website that I should "install" a plugin by copying the .so file into ~/.purple/plugins. So I copied the created /build/libceema.so and /build/libceema.so.0.0.1 into this directory (which I had to create).

Did I copy the correct files to the correct place?

[hbruintjes]

Ah, same problem as in #3 I just realized: You need to copy libthreepl.so to the pidgin plugin folder, not libceema. Should fix your issue.

[belamu]

That solves the error shown in the debug log. Now it starts with

(10:00:23) prefs: Reading /home/felix/.purple/prefs.xml
(10:00:23) prefs: Finished reading /home/felix/.purple/prefs.xml
(10:00:23) prefs: purple_prefs_get_path: Unknown pref /pidgin/browsers/command
(10:00:23) dbus: okkk
(10:00:23) plugins: probing /home/felix/.purple/plugins/libthreepl.so
(10:00:24) plugins: probing /usr/lib64/pidgin/timestamp_format.so
...

So "probing" apparently works but it does not show up in the list of Plugins (Menu "Tools"-"Plug Ins") and und "Accounts" there is still only "Manage Accounts", no Threema and when aading a new account, Threema is not listed as a Protocol.
I'll read #3 again more carefully to see if I find anything helpful for me in there. (No, it just worked for @myxor.)

[belamu]

Oh, I'm blind. It did appear in the list of protocols!

[belamu]

The Threema protocol asks for a password. But as far as I am aware, there are no passwords in Threema. What is meant by this password?
I have a data backup and an ID backup. According to your Readme, there should be a menu "Accounts-Threema" but this doesn't show up for me, so that I cannot import my backups. Any idea why? Or is it possible to import the backup somehow via command-line?
As the username I used my Threema-ID.