delta/gnome/gcr.git - gitlab.gnome.org: GNOME/gcr.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	README: s/G_DEBUG_MESSAGES/G_MESSAGES_DEBUG	Dmitry Eremin-Solenikov	2020-01-28	1	-3/+3
\| \| \| \| \| \|	Fix my previous mistake with environment variable name. Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
*	Update README to mention correct environment variables	Dmitry Eremin-Solenikov	2019-10-24	1	-18/+8
\| \| \| \| \| \|	Use G_MESSAGES_DEBUG instead of non-working GCR_DEBUG/GCK_DEBUG. Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
*	Fix up GCR_DEBUG and GCK_DEBUG environment variables	Stef Walter	2012-04-03	1	-0/+37
\| \| \| \| \| \| \| \| \| \| \|	* This is due to the G_MESSAGES_DEBUG change in glib * We manage our own debug categories, so if G_MESSAGES_DEBUG is not being used but GCR_DEBUG or GCK_DEBUG are set we unconditionally print the debug messages. * If G_MESSAGES_DEBUG is being used, then make all the debug messages available to Glib. * Can build with -DGCR_DEBUG=category flags to permanently enable certain categories.
*	Split the GCR and GCK libraries out of gnome-keyringsplit	Stef Walter	2011-10-06	1	-0/+6
	Commits prior to this commit will not build. To build old releases of Gcr or Gck you should use the gnome-keyring git module. This module currently depends on: gtk+ >= 3.0, glib >= 2.28.0, p11-kit >= 0.6, libgcrypt >= 1.2.2 Additionally it requires asn1Parser for building.