93b7043b5f
When libgcrypt is available, libsecret links with it. When dynamic linking is used, there is no problem: libsecret.so has a NEEDED pointing to libgcrypt, so linking an application with -lsecret works fine. However, when doing static linking, you must specify the entire chain of libraries, otherwise you get unresolved symbols errors, such as: host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libsecret-1.a(libsecret_1_la-secret-session.o): In function `request_open_session_aes': build/libsecret-0.18.3/libsecret/secret-session.c:99: undefined reference to `gcry_mpi_release' build/libsecret-0.18.3/libsecret/secret-session.c:101: undefined reference to `gcry_mpi_aprint' build/libsecret-0.18.3/libsecret/secret-session.c:107: undefined reference to `gcry_free' In order to solve this, we simply need to indicate in the Libs.private field of the .pc file that we depend on libgcrypt. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> [Retrieved from: https://git.buildroot.net/buildroot/tree/package/libsecret/0001-libsecret.pc-add-Libs.private-field-for-libgcrypt.patch] Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> |
||
|---|---|---|
| build | ||
| docs | ||
| egg | ||
| libsecret | ||
| po | ||
| tool | ||
| .dir-locals.el | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.ac | ||
| COPYING | ||
| COPYING.TESTS | ||
| libsecret.doap | ||
| Makefile.am | ||
| meson_options.txt | ||
| meson.build | ||
| NEWS | ||
| README.md | ||
libsecret
A GObject-based library for accessing the Secret Service API of the freedesktop.org project, a cross-desktop effort to access passwords, tokens and other types of secrets. libsecret provides a convenient wrapper for these methods so consumers do not have to call the low-level DBus methods.
The actual Secret Service API spec can be found at https://specifications.freedesktop.org/secret-service/.
Building
To build and install libsecret, you can use the following commands:
$ meson _build
$ ninja -C _build
$ ninja -C _build install
Contributing
You can browse the code, issues and more at libsecret's GitLab repository.
If you find a bug in libsecret, please file an issue on the issue tracker. Please try to add reproducible steps and the relevant version of libsecret.
If you want to contribute functionality or bug fixes, please open a Merge Request (MR). For more info on how to do this, see GitLab's help pages on MR's.
If libsecret is not translated in your language or you believe that the current translation has errors, you can join one of the various translation teams in GNOME. Translators do not commit directly to Git, but are advised to use our separate translation infrastructure instead. More info can be found at the translation project wiki page.
Releases
The release tarballs use semantic versioning since 0.19.0, which basically means:
- The major version will be incremented if backward incompatible changes are added
- The minor version will be incremented if new functionality is added in a backward compatible manner
- The patch version will be incremented if only backward compatible bug fixes are added
Note that there is no stable/unstable indication in whether the minor version number is even or odd.