OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:documentation
(Results
26 - 50
of
46842
) sorted by null
1
2
3
4
5
6
7
8
9
10
11
>>
/external/libxml2/test/schemas/
570702_0.xsd
8
<xs:
documentation
>Destination Number Length</xs:
documentation
>
19
<xs:
documentation
>destroy flag</xs:
documentation
>
elem0_0.xsd
4
<xsd:
documentation
>
6
</xsd:
documentation
>
nvdcve_0.xsd
8
<xs:
documentation
>This schema defines the structure of the National
20
how to interpret this data. </xs:
documentation
>
24
<xs:
documentation
>The root element of the NVD CVE feed. Multiple "entry" child elements describe specific NVD CVE entries.</xs:
documentation
>
32
<xs:
documentation
>The schema version number supported by the feed.</xs:
documentation
>
37
<xs:
documentation
>The date the feed was generated.</xs:
documentation
>
45
<xs:
documentation
>A CVE entry.</xs:
documentation
>
[
all
...]
/external/llvm/docs/_templates/
indexsidebar.html
2
all
documentation
pages. #}
/external/parameter-framework/upstream/schemas/
FileIncluder.xsd
6
<xs:
documentation
>Element type used to import a root element from a file.</xs:
documentation
>
10
<xs:
documentation
>Path to the file to import.
11
This path may be absolute or relative to the path of the includer file.</xs:
documentation
>
/external/skia/infra/project-config/
project.cfg
1
# For the schema of this file and
documentation
, see ProjectCfg message in
/external/testng/
CHECKLIST
9
doc/
documentation
-main.html
/hardware/intel/common/libmix/mix_audio/
Makefile.am
3
#Uncomment the following line if building
documentation
using gtkdoc
/external/autotest/client/tests/kvm/autotest_control/
rtc.control
5
Documentation
/rtc.txt. It does the functional test of interrupt, alarm and
8
Please refer the kernel
documentation
for details.
/external/autotest/client/tests/rtc/
control
5
Documentation
/rtc.txt. It does the functional test of interrupt, alarm and
8
Please refer the kernel
documentation
for details.
/external/libdaemon/m4/
zp_lynx_doc.m4
1
dnl Macro for enabling LYNX-based
documentation
generation
6
[Turn off lynx usage for
documentation
generation]),,
/external/libmicrohttpd/doc/doxygen/
Makefile.am
4
"Generate
documentation
:\n" \
5
"\tmake full - full
documentation
with dependency graphs (slow)\n" \
/external/libxml2/test/relaxng/
spec1.rng
7
<a:
documentation
>A foo element.</a:
documentation
>
/external/libogg/
CHANGES
6
*
Documentation
updates
14
* Updates to API
documentation
21
*
documentation
fixes and cleanup
34
* new multiplexed Ogg stream
documentation
41
* RFC 3533
documentation
of the format by Silvia Pfeiffer at CSIRO
42
* RFC 3534
documentation
of the application/ogg mime-type by Linus Walleij
/prebuilts/gcc/linux-x86/host/x86_64-w64-mingw32-4.8/lib/gcc/x86_64-w64-mingw32/4.8.3/plugin/include/
target-hooks-macros.h
24
DEFHOOKPODX(NAME, TYPE, INIT): Like DEFHOOKPOD, but share
documentation
45
/* FIXME: For pre-existing hooks, we can't place the
documentation
in the
46
documentation
field here till we get permission from the FSF to include
47
it in GPLed software - the target hook
documentation
is so far only
51
which should contain texinfo markup. If the
documentation
is only available
54
GFDL, but the
documentation
is only available under the GFDL, put the
62
of
documentation
. DEFHOOK_UNDOC takes a DOC string which it ignores, so
63
you can put GPLed
documentation
string there if you have hopes that you
64
can clear the declaration &
documentation
for GFDL distribution later,
66
to turn on the autogeneration of the
documentation
[
all
...]
/external/libxml2/result/schemas/
annot-err_0_0.err
2
./test/schemas/annot-err_0.xsd:7: element annotation: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}annotation': The content is not valid. Expected is (appinfo |
documentation
)*.
5
./test/schemas/annot-err_0.xsd:14: element
documentation
: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}
documentation
': The attribute 'id' is not allowed.
6
./test/schemas/annot-err_0.xsd:14: element
documentation
: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}
documentation
': The attribute 'mothers' is not allowed.
7
./test/schemas/annot-err_0.xsd:14: element
documentation
: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}
documentation
', attribute '{http://www.w3.org/XML/1998/namespace}lang': '*' is not a valid value of the atomic type 'xs:language'.
/external/clang/include/clang/Basic/
Attr.td
10
// The
documentation
is organized by category. Attributes can have category-
11
// specific
documentation
that is collated within the larger document.
21
//
documentation
. Ideally, this category should be used for internal-only
27
//
documentation
. Otherwise, the
documentation
will specify the attribute has
32
// Specifies the
documentation
to be associated with the given category.
33
class
Documentation
{
52
def Undocumented :
Documentation
{
301
// Any
documentation
that should be associated with the attribute. Since an
303
//
Documentation
entry may be listed
[
all
...]
DiagnosticCommentKinds.td
11
let CategoryName = "
Documentation
Issue" in {
18
InGroup<
Documentation
>, DefaultIgnore;
22
InGroup<
Documentation
>, DefaultIgnore;
52
InGroup<
Documentation
>, DefaultIgnore;
56
InGroup<
Documentation
>, DefaultIgnore;
69
InGroup<
Documentation
>, DefaultIgnore;
78
InGroup<
Documentation
>, DefaultIgnore;
85
InGroup<
Documentation
>, DefaultIgnore;
91
InGroup<
Documentation
>, DefaultIgnore;
97
InGroup<
Documentation
>, DefaultIgnore
[
all
...]
/external/llvm/docs/
README.txt
1
LLVM
Documentation
4
LLVM's
documentation
is written in reStructuredText, a lightweight
6
reStructuredText
documentation
should be quite readable in source form, it
7
is mostly meant to be processed by the Sphinx
documentation
generation
18
The mapping between reStructuredText files and generated
documentation
is
21
If you are interested in writing new
documentation
, you will want to read
22
`SphinxQuickstartTemplate.rst` which will get you writing
documentation
29
Building the manpages is similar to building the HTML
documentation
. The
47
The reachability of external links in the
documentation
can be checked by
/external/mesa3d/docs/
sourcedocs.html
5
<title>Source Code
Documentation
</title>
10
<h1>Source Code
Documentation
</h1>
15
produce cross-referenced
documentation
from the Mesa source code.
21
To generate Doxygen
documentation
, download Mesa from CVS, change to
33
run the doxygen scripts, you can read the
documentation
/ndk/docs/
Start_Here.html
2
<title>Native Development Kit
Documentation
</title>
5
<h1>Native Development Kit (NDK)
Documentation
</h1>
7
<p>Most of the
documentation
for the NDK is located on the
9
guides, API reference
documentation
, and other information about the NDK.</p>
11
<p>From this page, you can find
documentation
about several
/external/robolectric/v1/src/main/java/com/xtremelabs/robolectric/shadows/
package.html
17
<h2>Related
Documentation
</h2>
19
For overviews, tutorials, examples, guides, and tool
documentation
, please see:
21
<li><a href="">##### REFER TO NON-SPEC
DOCUMENTATION
HERE #####</a>
/external/antlr/antlr-3.4/runtime/C/doxygen/
runtime.dox
1
/// \page runtime Navigating the C Runtime
Documentation
3
/// If you are familiar with Doxygen generated
documentation
, then the layout of the files, typedefs
22
/// When navigating the source code, find the typedef you want to consult and inspect the
documentation
23
/// for its function pointers, then look at the
documentation
for the default methods that implement
31
/// From here, the
documentation
should be obvious. If it is not, then you could try reading
34
/// C runtime
documentation
.
/external/eigen/doc/
Overview.dox
5
This is the API
documentation
for Eigen3. You can <a href="eigen-doc.tgz">download</a> it as a tgz archive for offline reading.
17
The \b main \b
documentation
is organized into \em chapters covering different domains of features.
18
They are themselves composed of \em user \em manual pages describing the different features in a comprehensive way, and \em reference pages that gives you access to the API
documentation
through the related Eigen's \em modules and \em classes.
20
Under the \subpage UserManual_Generalities section, you will find
documentation
on more general topics such as preprocessor directives, controlling assertions, multi-threading, MKL support, some Eigen's internal insights, and much more...
22
Finally, do not miss the search engine, useful to quickly get to the
documentation
of a given class or function.
24
Want more? Checkout the <a href="unsupported/index.html">\em unsupported \em modules </a>
documentation
.
/external/clang/docs/
doxygen.intro
6
/// This
documentation
describes the @b internal software that makes
13
/// This
documentation
is generated directly from the source code with doxygen.
Completed in 933 milliseconds
1
2
3
4
5
6
7
8
9
10
11
>>