![]() buckconfig.local files in the project root, Buck reads configuration settings from the following additional locations, some of which are actually directories: buckconfig.local is excluded from version control to allow users to define personal settings, such as personal aliases. buckconfig is a version-controlled file that contains settings that are applicable to all team members, whereas. The root of your project may contain a second configuration file named. ![]() In addition to the semicolon ( ), you can use the pound sign ( #), as a comment character in. Values from other keys can be transcluded into the current key using the following syntax inside the current key value.įor example, to use the. Transclusion of values from one key to another Results in the two strings: foo and -bar Щ the space character between -bar and \u0429 is not interpreted as a separator. For example, if flags is a key value interpreted as a list of items separated by spaces, then ![]() When a key value is parsed as a list instead of a single item, the separator character is interpreted as a separator only when it occurs outside of double quotes. For example, a key value for the list of command-line flags to be passed to a compiler could be represented as a list of the flags separated by spaces: ![]() The syntax is to separate the items in the list using the space ( 0x20) character. Unicode character with code point # (in hex)Īlthough the standard INI format supports only key values that represent a single item, Buck supports key values that represent a list of items. The following escape sequences are supported. buckconfig key value, you can use escape sequences to encode characters that would otherwise be problematic. To ensure that any character can be encoded in a. For information about -config, see the Common Parameters topic. This constraint is because Buck uses the dot character to delimit section names and key names in other contexts such as the -config command-line parameter. These scenarios are examples of when you should be careful not to introduce the dot character in section names. Note that sometimes you might need to define your own custom sections, such as for platform flavors for C++ or Python. For example, the following is not supported- although Buck does not issue a warning or error. ) in section names within Buck configuration files. We do not support the use of the dot character (. Dot character not supported in section names As a result, INI file parsers provided by other languages or libraries are often not able to parse Buck's configuration files successfully. Other INI file parsersĪs mentioned previously, we have extended the INI file parser that Buck uses to parse configuration files. buckconfig implementation supports some modifications to the INI file format these are discussed below. That is, it is divided into sections where each section contains a collection of key names and key values. buckconfig file uses the INI file format. If this occurs, Buck rebuilds those artifacts, which can impact your build time. If your build files are large or you have many build files, this reparsing can impact your build time.Īlso, because configuration settings are sometimes included in the cache keys that Buck uses in its caching system, changes to Buck's configuration can invalidate previously-built artifacts in Buck's caches. If you change the Buck configuration in any of the locations discussed here, it can trigger Buck to reparse your build files the next time you build. Performance impact of Buck configuration changesĬhanges to Buck's configuration can-temporarily-degrade Buck's performance because of how they affect Buck's parsing and caching behavior. Before executing, Buck reads this file to incorporate any customizations it specifies. The root of your project must contain a configuration file named. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |