Home
last modified time | relevance | path

Searched refs:man (Results 1 – 3 of 3) sorted by relevance

/libCEED/examples/fluids/include/
H A Dbc_definition.h35 #define PetscOptionsBCDefinition(opt, text, man, name, bc_def, set) \ argument
36 PetscOptionsBCDefinition_Private(PetscOptionsObject, opt, text, man, name, bc_def, set)
37 …Private(PetscOptionItems PetscOptionsObject, const char opt[], const char text[], const char man[],
/libCEED/examples/fluids/src/
H A Dbc_definition.c94 …Private(PetscOptionItems PetscOptionsObject, const char opt[], const char text[], const char man[], in PetscOptionsBCDefinition_Private() argument
99 PetscCall(PetscOptionsIntArray(opt, text, man, label_values, &num_label_values, set)); in PetscOptionsBCDefinition_Private()
/libCEED/
H A DDoxyfile2108 # Configuration options related to the man page output
2111 # If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
2117 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
2121 # The default directory is: man.
2124 MAN_OUTPUT = man
2127 # man pages. In case the manual section does not start with a number, the number
2136 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
2142 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
2143 # will generate one additional man file for each entity documented in the real
2144 # man page(s). These additional files only source the real man page, but without
[all …]