xavi/dynstr, branch v0.1.0-rc2 Dynamic string library in C99. https://gitea.privatedns.org/xavi/dynstr/atom?h=v0.1.0-rc2 2023-10-15T23:16:32+00:00 CMakeLists.txt: Stop forcing STATIC library 2023-10-15T23:16:32+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-10-15T23:16:32+00:00 urn:sha1:c4979825b7e71a3499ecc4529313af78a1945ebd Distribution packagers might prefer dynstr as a shared object. Makefile: Fix wrong installation directory 2023-10-15T22:38:23+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-10-15T22:36:44+00:00 urn:sha1:cc9eae6d01a016613eab00c324878c3c4d454445 Libraries are meant to be placed in $PREFIX/lib, and not $PREFIX/bin. Install .pc file 2023-10-15T22:38:06+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-10-15T22:13:24+00:00 urn:sha1:ef14ee964ac098888a662b0a98fd88869d255d86 Support installation 2023-10-02T12:39:43+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-10-02T12:39:43+00:00 urn:sha1:d0d843b7046ced76336604450f8eb78b4decfa09 CMakeLists.txt: add cmake_minimum_required 2023-10-02T12:38:53+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-10-02T12:38:53+00:00 urn:sha1:0e779caae658f118d535e9f0a74f0012eefca9a0 This command is mandatory for all CMake projects. 3.0 was chosen since dynstr does not require any newer CMake features. CMakeLists.txt: Set project language to C 2023-08-02T11:06:08+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-08-02T11:06:08+00:00 urn:sha1:58bd7d93762e7a5eeba17e0cdb527b7f600ddc64 Otherwise, CMake tests the system C++ compiler by default, which is not a requirement for dynstr. Makefile: add clean target 2023-08-01T00:19:13+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-08-01T00:19:13+00:00 urn:sha1:57c9dfcfd0261a1eb0074a3ab85001a342e4cd19 Support POSIX make(1) as build system 2023-05-28T09:36:47+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-05-28T09:36:47+00:00 urn:sha1:5c13c9b8385cb2742f342d4d2f64d4e2d21108ba dynstr.c: Fix memory leak if realloc(3) fails 2023-03-08T00:21:16+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-03-08T00:21:16+00:00 urn:sha1:909d716a1e6d0c03b61b2a73ad3c2bd20fa55cf2 According to C99 ยง7.20.3.4: If memory for the new object cannot be allocated, the old object is not deallocated and its value is unchanged. Therefore, a temporary pointer must be used to ensure the original object can still be deallocated should realloc(3) return a null pointer. dynstr.c: Make zero-initialization portable 2023-03-08T00:19:21+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-03-08T00:19:21+00:00 urn:sha1:8e7557ef7a9a10781c79948afa69294afbdde10a