![]() ![]() This tag specifies the encoding used for all characters in the configuration file that follow. Below is an alphabetical index of the tags that are recognized followed by the descriptions of the tags grouped by category. The configuration options can be divided into several categories. Do this by putting a tag with these paths before the tag, e.g.: = my_config_dir You can also specify a list of directories that should be searched before looking in the current working directory. The include file is searched in the current working directory. You can also include part of a configuration file from another configuration file using a tag as follows: = config_file_name A small example: DOT_PATH = $(YOUR_DOT_PATH) Multiple lines can be concatenated by inserting a backslash ( \) as the last character of a line.Įnvironment variables can be expanded using the pattern $(ENV_VARIABLE_NAME). If the value should contain one or more blanks it must be surrounded by quotes ( "."). For tags that take a list as their argument, the = operator can be used instead of = to append new values to the list. If the same tag is assigned more than once, the last assignment overwrites any earlier assignment. Each statement consists of a TAG_NAME written in capitals, followed by the equal sign ( =) and one or more values. The file essentially consists of a list of assignment statements. Comments begin with the hash character ( #) and ends at the end of the line. Comments beginning with two hash characters ( #) at the end of the configuration file are also kept and placed at the end of the file. Comments beginning with two hash characters ( #) at the beginning of the configuration file are also kept and placed at the beginning of the file. Comments beginning with two hash characters ( #) are kept when updating the configuration file and are placed in front of the TAG they are in front of. Comments may be placed anywhere within the file (except within quotes). The statements in the file are case-sensitive. The file may contain tabs and newlines for formatting purposes. ![]() src/external - a small collection of external code and headers.A configuration file is a free-form ASCII text file with a structure that is similar to that of a Makefile, with the default name Doxyfile.src/xrt/targets - glue code and build logic to produce final binaries.src/xrt/auxiliary - Auxiliary and other larger components, like Tracking and Math.src/xrt/state_trackers/gui - GUI Config Interface, various helper and debug GUI code.src/xrt/state_trackers/oxr - OpenXR state tracker, implements the OpenXR API.src/xrt/compositor - Compositor code for doing distortion and driving the display hardware of a device.src/xrt/include - XRT interfaces defines the internal interfaces of Monado.Here is the documentation for all XRT interfaces used to interact between modules. The key interfaces to begin learning Monado are: Understanding and Writing Targets: Connecting the Pieces - How the components of Monado ( xrt_instance, IPC, OpenXR, etc) are brought together for use.State Trackers consume implementations of these APIs provided by other modules. Monado is architected as a collection of loosely-coupled, internally cohesive components that interact through the internal, abstract "XRT" (XrRunTime) API. Code Style and Conventions - to help you both read and write Monado code.If you are viewing this on the web at, the changelog above also includes a section for changes that have not yet been in a tagged release. Please submit a merge request to fix any such issues you may notice.) (Since they are not maintained in the source code files directly, they may sometimes be slightly out-of-date, so in case of conflict, the code-based documentation is correct. See the "Related Pages" link above for a complete list of these non-code-based documentation pages. Some are linked below in a logical outline, and some documentation comments in code cross-reference these pages. ![]() There are also a number of pages in this site (including this one) that are maintained as fully human-authored Markdown files outside of source code files, but still in the repository in the doc/ directory. (The directory structure matches the top levels of modules, but some are sub-divided further into sub-modules within a directory.) These extracted documentation pages are best browsed through the "Modules" or "Files" links above. This documentation is maintained in part in documentation comments in the code itself, extracted and rendered by Doxygen. It also assumes that you have read README.md: that file also holds getting started information and general documentation. This documentation is intended for developers wanting to dive into the code of Monado. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |