Searched refs:man (Results 1 – 3 of 3) sorted by relevance
| /honee/include/ |
| H A D | bc_definition.h | 50 #define PetscOptionsBCDefinition(opt, text, man, name, bc_def, set) \ argument
51 PetscOptionsBCDefinition_Private(PetscOptionsObject, opt, text, man, name, bc_def, set)
52 …Private(PetscOptionItems PetscOptionsObject, const char opt[], const char text[], const char man[],
|
| /honee/src/ |
| H A D | bc_definition.c | 211 …Private(PetscOptionItems PetscOptionsObject, const char opt[], const char text[], const char man[], in PetscOptionsBCDefinition_Private() argument
216 PetscCall(PetscOptionsIntArray(opt, text, man, label_values, &num_label_values, set)); in PetscOptionsBCDefinition_Private()
|
| /honee/ |
| H A D | Doxyfile | 2156 # Configuration options related to the man page output
2159 # If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
2165 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
2169 # The default directory is: man.
2172 MAN_OUTPUT = man
2175 # man pages. In case the manual section does not start with a number, the number
2184 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
2190 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
2191 # will generate one additional man file for each entity documented in the real
2192 # man page(s). These additional files only source the real man page, but without
[all …]
|