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

	Commit message (Collapse)	Author	Age	Files	Lines
*	build: Add missing make targets for code coverage	Daiki Ueno	2018-06-14	1	-0/+10
\| \| \| \|	Copied from gnome-keyring.
*	gcr: Implement GcrSshAskpass APIwip/dueno/ssh-askpass	Stef Walter	2018-02-24	1	-0/+2
\| \| \| \| \| \| \|	This allows calling ssh programs like ssh-add or ssh itself, and handling the password prompts. https://bugzilla.gnome.org/show_bug.cgi?id=735873
*	Release version 3.12.03.12.0	Stef Walter	2014-03-23	1	-1/+0
\|
*	Work around for gdbus-codegen bug	Stef Walter	2014-03-23	1	-1/+5
\| \| \| \|	https://bugzilla.gnome.org/show_bug.cgi?id=710133
*	Makefile.am: Implement proper make check-memory target	Stef Walter	2014-03-05	1	-13/+41
\| \| \| \| \|	Uses valgrind to run the tests. Update the tap-driver and tap-gtester pieces to accomodate this.
*	Makefile.am: Build vapi files and use vapi metadata correctly	Stef Walter	2014-03-03	1	-1/+1
\| \| \| \|	Regressed from 9019498dfef15efec4d12eee8becc55781062a30
*	Makefile.am: Single Makefile mode and parallel-tests	Stef Walter	2014-03-03	1	-18/+128
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	gtk-doc doesn't work as an included Makefile so continue to use SUBDIRS with docs/reference/* Run the tests using TAP. Unfortunately the GTest --tap output mode doesn't behave well in the face of failures, and doesn't output a test plan. Use our own tap-driver and tap-compiler for these reasons. This also fixes several builddir != srcdir issues and testing hacks that were sneaking around in the code base. Move the tests into the same directories as the code that it is testing.
*	Release version 3.9.903.9.90	Stef Walter	2013-08-26	1	-1/+2
\|
*	Separate the base and ui parts of the Gcr library more thoroughly.	Stef Walter	2012-12-22	1	-0/+8
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* This is due to gobject introspection not being able to have separate GIRs provide the same namespace, and the desire to conditionally build the GTK+ dependent stuff. * Partially based on a patch by Mathias Hasselmann * Separate GIRs: Gcr and GcrUi * Separate libraries: libgcr-base-3.so and libgcr-ui-3.so. The latter links to the former. * Symlink libgcr-3.so to libgcr-ui-3.so * Expose internal symbols in libgcr-base-3.so so they can be easily shared by libgcr-ui-3.so * Add --without-gtk argument https://bugzilla.gnome.org/show_bug.cgi?id=688678
*	build: Use gnome-common code coverage macros	Philip Withnall	2012-10-03	1	-1/+1
\| \| \| \| \| \| \|	Replace the existing home-grown gcov support with the new code coverage macro from gnome-common 3.6.0. https://bugzilla.gnome.org/show_bug.cgi?id=683211
*	Release version 3.5.33.5.3	Stef Walter	2012-06-25	1	-0/+3
\|
*	Release version 3.3.923.3.92	Stef Walter	2012-03-19	1	-1/+2
\|
*	Add valgrind memory checking and fix up errors	Stef Walter	2011-11-21	1	-14/+8
\| \| \| \| \| \| \| \| \|	* This is especially necessary after migrating to EggBytes since it's reference counted and an easy sourc of memory leaks * Remove threading from testing framework, as gcr isn't threadsafe in all parts. * Fix bugs discovered in memory checking. * Fix up some of the testing stuff.
*	Split the GCR and GCK libraries out of gnome-keyringsplit	Stef Walter	2011-10-06	1	-0/+57
	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.