From a9f9f034905459bed628d886c3315ded162a9789 Mon Sep 17 00:00:00 2001 From: Sune Vuorela Date: Thu, 25 Jan 2024 16:49:48 +0100 Subject: docs: Use common conventions for shared libs Use common conventions for documentation of shared library version and soversion. In general, the numeric version part is expected to be first component of version, so suggest this in the example code. --- docs/markdown/Build-targets.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/markdown') diff --git a/docs/markdown/Build-targets.md b/docs/markdown/Build-targets.md index 780595cae..a2f9b3291 100644 --- a/docs/markdown/Build-targets.md +++ b/docs/markdown/Build-targets.md @@ -36,7 +36,7 @@ ignored if the library is configured as static at the compile time. ```meson project('shared lib', 'c') -library('mylib', 'source.c', version : '1.2.3', soversion : '0') +library('mylib', 'source.c', version : '1.2.3', soversion : '1') ``` It is common to build a library and then an executable that links -- cgit v1.2.3