You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: man/lcovrc.5
+53-1Lines changed: 53 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -148,7 +148,21 @@ See the OPTIONS section below for details.
148
148
.br
149
149
#
150
150
.br
151
-
151
+
# include some other config file
152
+
.br
153
+
# e.g, user-specific options. Note the environment variable expansion
154
+
.br
155
+
# config_file = $ENV{HOME}/.user_lcovrc
156
+
.br
157
+
# or project specific - hard-coded from environment variable
158
+
.br
159
+
# config_file = /path/to/myproject/.lcovrc
160
+
.br
161
+
# or in the current run directory
162
+
.br
163
+
# config_file = $ENV{PWD}/.lcovrc
164
+
.br
165
+
.br
152
166
# External style sheet file
153
167
.br
154
168
#genhtml_css_file = gcov.css
@@ -727,6 +741,44 @@ maximum during parallel processing.
727
741
728
742
.SH OPTIONS
729
743
744
+
.BR config_file " ="
745
+
.Ifilename
746
+
.IP
747
+
748
+
Include another config file.
749
+
750
+
Inclusion is equivalent to inserting the text from
751
+
.Ifilename
752
+
at this point in the current file. As a result, settings from the included
753
+
file are processed after earlier settings in the current file, but before later settings from the current file.
754
+
As a result:
755
+
756
+
.BR"Scalar options"
757
+
set earlier in the current file are overridden by settings from the included file, and scalar options from the included file are overridden by later setting in the current file.
758
+
759
+
.BR"Array options"
760
+
from earlier in the current file appear before setting from the included file, and array options from later in the current file appear after.
761
+
762
+
Config file inclusion is recursive: an included config file may include another file - and so on.
763
+
Inclusion loops are not supported and will result in a
764
+
.Iusage
765
+
error.
766
+
767
+
The most common usecase for config file inclusion is so that a site-wide or project-wide options file can include a user-specific or module-specific options file - for example, as
0 commit comments