diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/_sphinx_javascript_frameworks_compat.js b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/_sphinx_javascript_frameworks_compat.js new file mode 100644 index 0000000000000000000000000000000000000000..8549469dc29fac0cbf16d10355e3313897cb3752 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/_sphinx_javascript_frameworks_compat.js @@ -0,0 +1,134 @@ +/* + * _sphinx_javascript_frameworks_compat.js + * ~~~~~~~~~~ + * + * Compatability shim for jQuery and underscores.js. + * + * WILL BE REMOVED IN Sphinx 6.0 + * xref RemovedInSphinx60Warning + * + */ + +/** + * select a different prefix for underscore + */ +$u = _.noConflict(); + + +/** + * small helper function to urldecode strings + * + * See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/decodeURIComponent#Decoding_query_parameters_from_a_URL + */ +jQuery.urldecode = function(x) { + if (!x) { + return x + } + return decodeURIComponent(x.replace(/\+/g, ' ')); +}; + +/** + * small helper function to urlencode strings + */ +jQuery.urlencode = encodeURIComponent; + +/** + * This function returns the parsed url parameters of the + * current request. Multiple values per key are supported, + * it will always return arrays of strings for the value parts. + */ +jQuery.getQueryParameters = function(s) { + if (typeof s === 'undefined') + s = document.location.search; + var parts = s.substr(s.indexOf('?') + 1).split('&'); + var result = {}; + for (var i = 0; i < parts.length; i++) { + var tmp = parts[i].split('=', 2); + var key = jQuery.urldecode(tmp[0]); + var value = jQuery.urldecode(tmp[1]); + if (key in result) + result[key].push(value); + else + result[key] = [value]; + } + return result; +}; + +/** + * highlight a given string on a jquery object by wrapping it in + * span elements with the given class name. + */ +jQuery.fn.highlightText = function(text, className) { + function highlight(node, addItems) { + if (node.nodeType === 3) { + var val = node.nodeValue; + var pos = val.toLowerCase().indexOf(text); + if (pos >= 0 && + !jQuery(node.parentNode).hasClass(className) && + !jQuery(node.parentNode).hasClass("nohighlight")) { + var span; + var isInSVG = jQuery(node).closest("body, svg, foreignObject").is("svg"); + if (isInSVG) { + span = document.createElementNS("http://www.w3.org/2000/svg", "tspan"); + } else { + span = document.createElement("span"); + span.className = className; + } + span.appendChild(document.createTextNode(val.substr(pos, text.length))); + node.parentNode.insertBefore(span, node.parentNode.insertBefore( + document.createTextNode(val.substr(pos + text.length)), + node.nextSibling)); + node.nodeValue = val.substr(0, pos); + if (isInSVG) { + var rect = document.createElementNS("http://www.w3.org/2000/svg", "rect"); + var bbox = node.parentElement.getBBox(); + rect.x.baseVal.value = bbox.x; + rect.y.baseVal.value = bbox.y; + rect.width.baseVal.value = bbox.width; + rect.height.baseVal.value = bbox.height; + rect.setAttribute('class', className); + addItems.push({ + "parent": node.parentNode, + "target": rect}); + } + } + } + else if (!jQuery(node).is("button, select, textarea")) { + jQuery.each(node.childNodes, function() { + highlight(this, addItems); + }); + } + } + var addItems = []; + var result = this.each(function() { + highlight(this, addItems); + }); + for (var i = 0; i < addItems.length; ++i) { + jQuery(addItems[i].parent).before(addItems[i].target); + } + return result; +}; + +/* + * backward compatibility for jQuery.browser + * This will be supported until firefox bug is fixed. + */ +if (!jQuery.browser) { + jQuery.uaMatch = function(ua) { + ua = ua.toLowerCase(); + + var match = /(chrome)[ \/]([\w.]+)/.exec(ua) || + /(webkit)[ \/]([\w.]+)/.exec(ua) || + /(opera)(?:.*version|)[ \/]([\w.]+)/.exec(ua) || + /(msie) ([\w.]+)/.exec(ua) || + ua.indexOf("compatible") < 0 && /(mozilla)(?:.*? rv:([\w.]+)|)/.exec(ua) || + []; + + return { + browser: match[ 1 ] || "", + version: match[ 2 ] || "0" + }; + }; + jQuery.browser = {}; + jQuery.browser[jQuery.uaMatch(navigator.userAgent).browser] = true; +} diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/basic.css b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/basic.css new file mode 100644 index 0000000000000000000000000000000000000000..4e9a9f1faca4a263f4cb13711058d9456d38dc60 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/basic.css @@ -0,0 +1,900 @@ +/* + * basic.css + * ~~~~~~~~~ + * + * Sphinx stylesheet -- basic theme. + * + * :copyright: Copyright 2007-2022 by the Sphinx team, see AUTHORS. + * :license: BSD, see LICENSE for details. + * + */ + +/* -- main layout ----------------------------------------------------------- */ + +div.clearer { + clear: both; +} + +div.section::after { + display: block; + content: ''; + clear: left; +} + +/* -- relbar ---------------------------------------------------------------- */ + +div.related { + width: 100%; + font-size: 90%; +} + +div.related h3 { + display: none; +} + +div.related ul { + margin: 0; + padding: 0 0 0 10px; + list-style: none; +} + +div.related li { + display: inline; +} + +div.related li.right { + float: right; + margin-right: 5px; +} + +/* -- sidebar --------------------------------------------------------------- */ + +div.sphinxsidebarwrapper { + padding: 10px 5px 0 10px; +} + +div.sphinxsidebar { + float: left; + width: 230px; + margin-left: -100%; + font-size: 90%; + word-wrap: break-word; + overflow-wrap : break-word; +} + +div.sphinxsidebar ul { + list-style: none; +} + +div.sphinxsidebar ul ul, +div.sphinxsidebar ul.want-points { + margin-left: 20px; + list-style: square; +} + +div.sphinxsidebar ul ul { + margin-top: 0; + margin-bottom: 0; +} + +div.sphinxsidebar form { + margin-top: 10px; +} + +div.sphinxsidebar input { + border: 1px solid #98dbcc; + font-family: sans-serif; + font-size: 1em; +} + +div.sphinxsidebar #searchbox form.search { + overflow: hidden; +} + +div.sphinxsidebar #searchbox input[type="text"] { + float: left; + width: 80%; + padding: 0.25em; + box-sizing: border-box; +} + +div.sphinxsidebar #searchbox input[type="submit"] { + float: left; + width: 20%; + border-left: none; + padding: 0.25em; + box-sizing: border-box; +} + + +img { + border: 0; + max-width: 100%; +} + +/* -- search page ----------------------------------------------------------- */ + +ul.search { + margin: 10px 0 0 20px; + padding: 0; +} + +ul.search li { + padding: 5px 0 5px 20px; + background-image: url(file.png); + background-repeat: no-repeat; + background-position: 0 7px; +} + +ul.search li a { + font-weight: bold; +} + +ul.search li p.context { + color: #888; + margin: 2px 0 0 30px; + text-align: left; +} + +ul.keywordmatches li.goodmatch a { + font-weight: bold; +} + +/* -- index page ------------------------------------------------------------ */ + +table.contentstable { + width: 90%; + margin-left: auto; + margin-right: auto; +} + +table.contentstable p.biglink { + line-height: 150%; +} + +a.biglink { + font-size: 1.3em; +} + +span.linkdescr { + font-style: italic; + padding-top: 5px; + font-size: 90%; +} + +/* -- general index --------------------------------------------------------- */ + +table.indextable { + width: 100%; +} + +table.indextable td { + text-align: left; + vertical-align: top; +} + +table.indextable ul { + margin-top: 0; + margin-bottom: 0; + list-style-type: none; +} + +table.indextable > tbody > tr > td > ul { + padding-left: 0em; +} + +table.indextable tr.pcap { + height: 10px; +} + +table.indextable tr.cap { + margin-top: 10px; + background-color: #f2f2f2; +} + +img.toggler { + margin-right: 3px; + margin-top: 3px; + cursor: pointer; +} + +div.modindex-jumpbox { + border-top: 1px solid #ddd; + border-bottom: 1px solid #ddd; + margin: 1em 0 1em 0; + padding: 0.4em; +} + +div.genindex-jumpbox { + border-top: 1px solid #ddd; + border-bottom: 1px solid #ddd; + margin: 1em 0 1em 0; + padding: 0.4em; +} + +/* -- domain module index --------------------------------------------------- */ + +table.modindextable td { + padding: 2px; + border-collapse: collapse; +} + +/* -- general body styles --------------------------------------------------- */ + +div.body { + min-width: 360px; + max-width: 800px; +} + +div.body p, div.body dd, div.body li, div.body blockquote { + -moz-hyphens: auto; + -ms-hyphens: auto; + -webkit-hyphens: auto; + hyphens: auto; +} + +a.headerlink { + visibility: hidden; +} + +h1:hover > a.headerlink, +h2:hover > a.headerlink, +h3:hover > a.headerlink, +h4:hover > a.headerlink, +h5:hover > a.headerlink, +h6:hover > a.headerlink, +dt:hover > a.headerlink, +caption:hover > a.headerlink, +p.caption:hover > a.headerlink, +div.code-block-caption:hover > a.headerlink { + visibility: visible; +} + +div.body p.caption { + text-align: inherit; +} + +div.body td { + text-align: left; +} + +.first { + margin-top: 0 !important; +} + +p.rubric { + margin-top: 30px; + font-weight: bold; +} + +img.align-left, figure.align-left, .figure.align-left, object.align-left { + clear: left; + float: left; + margin-right: 1em; +} + +img.align-right, figure.align-right, .figure.align-right, object.align-right { + clear: right; + float: right; + margin-left: 1em; +} + +img.align-center, figure.align-center, .figure.align-center, object.align-center { + display: block; + margin-left: auto; + margin-right: auto; +} + +img.align-default, figure.align-default, .figure.align-default { + display: block; + margin-left: auto; + margin-right: auto; +} + +.align-left { + text-align: left; +} + +.align-center { + text-align: center; +} + +.align-default { + text-align: center; +} + +.align-right { + text-align: right; +} + +/* -- sidebars -------------------------------------------------------------- */ + +div.sidebar, +aside.sidebar { + margin: 0 0 0.5em 1em; + border: 1px solid #ddb; + padding: 7px; + background-color: #ffe; + width: 40%; + float: right; + clear: right; + overflow-x: auto; +} + +p.sidebar-title { + font-weight: bold; +} +nav.contents, +aside.topic, +div.admonition, div.topic, blockquote { + clear: left; +} + +/* -- topics ---------------------------------------------------------------- */ +nav.contents, +aside.topic, +div.topic { + border: 1px solid #ccc; + padding: 7px; + margin: 10px 0 10px 0; +} + +p.topic-title { + font-size: 1.1em; + font-weight: bold; + margin-top: 10px; +} + +/* -- admonitions ----------------------------------------------------------- */ + +div.admonition { + margin-top: 10px; + margin-bottom: 10px; + padding: 7px; +} + +div.admonition dt { + font-weight: bold; +} + +p.admonition-title { + margin: 0px 10px 5px 0px; + font-weight: bold; +} + +div.body p.centered { + text-align: center; + margin-top: 25px; +} + +/* -- content of sidebars/topics/admonitions -------------------------------- */ + +div.sidebar > :last-child, +aside.sidebar > :last-child, +nav.contents > :last-child, +aside.topic > :last-child, +div.topic > :last-child, +div.admonition > :last-child { + margin-bottom: 0; +} + +div.sidebar::after, +aside.sidebar::after, +nav.contents::after, +aside.topic::after, +div.topic::after, +div.admonition::after, +blockquote::after { + display: block; + content: ''; + clear: both; +} + +/* -- tables ---------------------------------------------------------------- */ + +table.docutils { + margin-top: 10px; + margin-bottom: 10px; + border: 0; + border-collapse: collapse; +} + +table.align-center { + margin-left: auto; + margin-right: auto; +} + +table.align-default { + margin-left: auto; + margin-right: auto; +} + +table caption span.caption-number { + font-style: italic; +} + +table caption span.caption-text { +} + +table.docutils td, table.docutils th { + padding: 1px 8px 1px 5px; + border-top: 0; + border-left: 0; + border-right: 0; + border-bottom: 1px solid #aaa; +} + +th { + text-align: left; + padding-right: 5px; +} + +table.citation { + border-left: solid 1px gray; + margin-left: 1px; +} + +table.citation td { + border-bottom: none; +} + +th > :first-child, +td > :first-child { + margin-top: 0px; +} + +th > :last-child, +td > :last-child { + margin-bottom: 0px; +} + +/* -- figures --------------------------------------------------------------- */ + +div.figure, figure { + margin: 0.5em; + padding: 0.5em; +} + +div.figure p.caption, figcaption { + padding: 0.3em; +} + +div.figure p.caption span.caption-number, +figcaption span.caption-number { + font-style: italic; +} + +div.figure p.caption span.caption-text, +figcaption span.caption-text { +} + +/* -- field list styles ----------------------------------------------------- */ + +table.field-list td, table.field-list th { + border: 0 !important; +} + +.field-list ul { + margin: 0; + padding-left: 1em; +} + +.field-list p { + margin: 0; +} + +.field-name { + -moz-hyphens: manual; + -ms-hyphens: manual; + -webkit-hyphens: manual; + hyphens: manual; +} + +/* -- hlist styles ---------------------------------------------------------- */ + +table.hlist { + margin: 1em 0; +} + +table.hlist td { + vertical-align: top; +} + +/* -- object description styles --------------------------------------------- */ + +.sig { + font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace; +} + +.sig-name, code.descname { + background-color: transparent; + font-weight: bold; +} + +.sig-name { + font-size: 1.1em; +} + +code.descname { + font-size: 1.2em; +} + +.sig-prename, code.descclassname { + background-color: transparent; +} + +.optional { + font-size: 1.3em; +} + +.sig-paren { + font-size: larger; +} + +.sig-param.n { + font-style: italic; +} + +/* C++ specific styling */ + +.sig-inline.c-texpr, +.sig-inline.cpp-texpr { + font-family: unset; +} + +.sig.c .k, .sig.c .kt, +.sig.cpp .k, .sig.cpp .kt { + color: #0033B3; +} + +.sig.c .m, +.sig.cpp .m { + color: #1750EB; +} + +.sig.c .s, .sig.c .sc, +.sig.cpp .s, .sig.cpp .sc { + color: #067D17; +} + + +/* -- other body styles ----------------------------------------------------- */ + +ol.arabic { + list-style: decimal; +} + +ol.loweralpha { + list-style: lower-alpha; +} + +ol.upperalpha { + list-style: upper-alpha; +} + +ol.lowerroman { + list-style: lower-roman; +} + +ol.upperroman { + list-style: upper-roman; +} + +:not(li) > ol > li:first-child > :first-child, +:not(li) > ul > li:first-child > :first-child { + margin-top: 0px; +} + +:not(li) > ol > li:last-child > :last-child, +:not(li) > ul > li:last-child > :last-child { + margin-bottom: 0px; +} + +ol.simple ol p, +ol.simple ul p, +ul.simple ol p, +ul.simple ul p { + margin-top: 0; +} + +ol.simple > li:not(:first-child) > p, +ul.simple > li:not(:first-child) > p { + margin-top: 0; +} + +ol.simple p, +ul.simple p { + margin-bottom: 0; +} +aside.footnote > span, +div.citation > span { + float: left; +} +aside.footnote > span:last-of-type, +div.citation > span:last-of-type { + padding-right: 0.5em; +} +aside.footnote > p { + margin-left: 2em; +} +div.citation > p { + margin-left: 4em; +} +aside.footnote > p:last-of-type, +div.citation > p:last-of-type { + margin-bottom: 0em; +} +aside.footnote > p:last-of-type:after, +div.citation > p:last-of-type:after { + content: ""; + clear: both; +} + +dl.field-list { + display: grid; + grid-template-columns: fit-content(30%) auto; +} + +dl.field-list > dt { + font-weight: bold; + word-break: break-word; + padding-left: 0.5em; + padding-right: 5px; +} + +dl.field-list > dd { + padding-left: 0.5em; + margin-top: 0em; + margin-left: 0em; + margin-bottom: 0em; +} + +dl { + margin-bottom: 15px; +} + +dd > :first-child { + margin-top: 0px; +} + +dd ul, dd table { + margin-bottom: 10px; +} + +dd { + margin-top: 3px; + margin-bottom: 10px; + margin-left: 30px; +} + +dl > dd:last-child, +dl > dd:last-child > :last-child { + margin-bottom: 0; +} + +dt:target, span.highlighted { + background-color: #fbe54e; +} + +rect.highlighted { + fill: #fbe54e; +} + +dl.glossary dt { + font-weight: bold; + font-size: 1.1em; +} + +.versionmodified { + font-style: italic; +} + +.system-message { + background-color: #fda; + padding: 5px; + border: 3px solid red; +} + +.footnote:target { + background-color: #ffa; +} + +.line-block { + display: block; + margin-top: 1em; + margin-bottom: 1em; +} + +.line-block .line-block { + margin-top: 0; + margin-bottom: 0; + margin-left: 1.5em; +} + +.guilabel, .menuselection { + font-family: sans-serif; +} + +.accelerator { + text-decoration: underline; +} + +.classifier { + font-style: oblique; +} + +.classifier:before { + font-style: normal; + margin: 0 0.5em; + content: ":"; + display: inline-block; +} + +abbr, acronym { + border-bottom: dotted 1px; + cursor: help; +} + +/* -- code displays --------------------------------------------------------- */ + +pre { + overflow: auto; + overflow-y: hidden; /* fixes display issues on Chrome browsers */ +} + +pre, div[class*="highlight-"] { + clear: both; +} + +span.pre { + -moz-hyphens: none; + -ms-hyphens: none; + -webkit-hyphens: none; + hyphens: none; + white-space: nowrap; +} + +div[class*="highlight-"] { + margin: 1em 0; +} + +td.linenos pre { + border: 0; + background-color: transparent; + color: #aaa; +} + +table.highlighttable { + display: block; +} + +table.highlighttable tbody { + display: block; +} + +table.highlighttable tr { + display: flex; +} + +table.highlighttable td { + margin: 0; + padding: 0; +} + +table.highlighttable td.linenos { + padding-right: 0.5em; +} + +table.highlighttable td.code { + flex: 1; + overflow: hidden; +} + +.highlight .hll { + display: block; +} + +div.highlight pre, +table.highlighttable pre { + margin: 0; +} + +div.code-block-caption + div { + margin-top: 0; +} + +div.code-block-caption { + margin-top: 1em; + padding: 2px 5px; + font-size: small; +} + +div.code-block-caption code { + background-color: transparent; +} + +table.highlighttable td.linenos, +span.linenos, +div.highlight span.gp { /* gp: Generic.Prompt */ + user-select: none; + -webkit-user-select: text; /* Safari fallback only */ + -webkit-user-select: none; /* Chrome/Safari */ + -moz-user-select: none; /* Firefox */ + -ms-user-select: none; /* IE10+ */ +} + +div.code-block-caption span.caption-number { + padding: 0.1em 0.3em; + font-style: italic; +} + +div.code-block-caption span.caption-text { +} + +div.literal-block-wrapper { + margin: 1em 0; +} + +code.xref, a code { + background-color: transparent; + font-weight: bold; +} + +h1 code, h2 code, h3 code, h4 code, h5 code, h6 code { + background-color: transparent; +} + +.viewcode-link { + float: right; +} + +.viewcode-back { + float: right; + font-family: sans-serif; +} + +div.viewcode-block:target { + margin: -1px -10px; + padding: 0 10px; +} + +/* -- math display ---------------------------------------------------------- */ + +img.math { + vertical-align: middle; +} + +div.body div.math p { + text-align: center; +} + +span.eqno { + float: right; +} + +span.eqno a.headerlink { + position: absolute; + z-index: 1; +} + +div.math:hover a.headerlink { + visibility: visible; +} + +/* -- printout stylesheet --------------------------------------------------- */ + +@media print { + div.document, + div.documentwrapper, + div.bodywrapper { + margin: 0 !important; + width: 100%; + } + + div.sphinxsidebar, + div.related, + div.footer, + #top-link { + display: none; + } +} \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/classic.css b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/classic.css new file mode 100644 index 0000000000000000000000000000000000000000..3a6854a58ba454142f59689c9a71c04ae7d216c9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/classic.css @@ -0,0 +1,269 @@ +/* + * classic.css_t + * ~~~~~~~~~~~~~ + * + * Sphinx stylesheet -- classic theme. + * + * :copyright: Copyright 2007-2022 by the Sphinx team, see AUTHORS. + * :license: BSD, see LICENSE for details. + * + */ + +@import url("basic.css"); + +/* -- page layout ----------------------------------------------------------- */ + +html { + /* CSS hack for macOS's scrollbar (see #1125) */ + background-color: #FFFFFF; +} + +body { + font-family: sans-serif; + font-size: 100%; + background-color: #00182d; + color: #000; + margin: 0; + padding: 0; +} + +div.document { + display: flex; + background-color: #e4ece8; +} + +div.documentwrapper { + float: left; + width: 100%; +} + +div.bodywrapper { + margin: 0 0 0 230px; +} + +div.body { + background-color: #ffffff; + color: #444444; + padding: 0 20px 30px 20px; +} + +div.footer { + color: #ffffff; + width: 100%; + padding: 9px 0 9px 0; + text-align: center; + font-size: 75%; +} + +div.footer a { + color: #ffffff; + text-decoration: underline; +} + +div.related { + background-color: #00529b; + line-height: 30px; + color: #ffffff; +} + +div.related a { + color: #ffffff; +} + +div.sphinxsidebar { +} + +div.sphinxsidebar h3 { + font-family: 'Trebuchet MS', sans-serif; + color: #333333; + font-size: 1.4em; + font-weight: normal; + margin: 0; + padding: 0; +} + +div.sphinxsidebar h3 a { + color: #333333; +} + +div.sphinxsidebar h4 { + font-family: 'Trebuchet MS', sans-serif; + color: #333333; + font-size: 1.3em; + font-weight: normal; + margin: 5px 0 0 0; + padding: 0; +} + +div.sphinxsidebar p { + color: #333333; +} + +div.sphinxsidebar p.topless { + margin: 5px 10px 10px 10px; +} + +div.sphinxsidebar ul { + margin: 10px; + padding: 0; + color: #333333; +} + +div.sphinxsidebar a { + color: #00a94f; +} + +div.sphinxsidebar input { + border: 1px solid #00a94f; + font-family: sans-serif; + font-size: 1em; +} + + + +/* -- hyperlink styles ------------------------------------------------------ */ + +a { + color: #2b63a8; + text-decoration: none; +} + +a:visited { + color: #2b63a8; + text-decoration: none; +} + +a:hover { + text-decoration: underline; +} + + + +/* -- body styles ----------------------------------------------------------- */ + +div.body h1, +div.body h2, +div.body h3, +div.body h4, +div.body h5, +div.body h6 { + font-family: 'Trebuchet MS', sans-serif; + background-color: #f2f2f2; + font-weight: normal; + color: #003564; + border-bottom: 1px solid #ccc; + margin: 20px -20px 10px -20px; + padding: 3px 0 3px 10px; +} + +div.body h1 { margin-top: 0; font-size: 200%; } +div.body h2 { font-size: 160%; } +div.body h3 { font-size: 140%; } +div.body h4 { font-size: 120%; } +div.body h5 { font-size: 110%; } +div.body h6 { font-size: 100%; } + +a.headerlink { + color: #3d8ff2; + font-size: 0.8em; + padding: 0 4px 0 4px; + text-decoration: none; +} + +a.headerlink:hover { + background-color: #3d8ff2; + color: white; +} + +div.body p, div.body dd, div.body li, div.body blockquote { + text-align: justify; + line-height: 130%; +} + +div.admonition p.admonition-title + p { + display: inline; +} + +div.admonition p { + margin-bottom: 5px; +} + +div.admonition pre { + margin-bottom: 5px; +} + +div.admonition ul, div.admonition ol { + margin-bottom: 5px; +} + +div.note { + background-color: #eee; + border: 1px solid #ccc; +} + +div.seealso { + background-color: #ffc; + border: 1px solid #ff6; +} +nav.contents, +aside.topic, + +div.topic { + background-color: #eee; +} + +div.warning { + background-color: #ffe4e4; + border: 1px solid #f66; +} + +p.admonition-title { + display: inline; +} + +p.admonition-title:after { + content: ":"; +} + +pre { + padding: 5px; + background-color: #eeeeee; + color: #333333; + line-height: 120%; + border: 1px solid #ac9; + border-left: none; + border-right: none; +} + +code { + background-color: #ecf0f3; + padding: 0 1px 0 1px; + font-size: 0.95em; +} + +th, dl.field-list > dt { + background-color: #ede; +} + +.warning code { + background: #efc2c2; +} + +.note code { + background: #d6d6d6; +} + +.viewcode-back { + font-family: sans-serif; +} + +div.viewcode-block:target { + background-color: #f4debf; + border-top: 1px solid #ac9; + border-bottom: 1px solid #ac9; +} + +div.code-block-caption { + color: #efefef; + background-color: #1c4e63; +} \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/cmake-favicon.ico b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/cmake-favicon.ico new file mode 100644 index 0000000000000000000000000000000000000000..ae529f54e7c4a75f5e6fa0e97c8672c77e7d2901 Binary files /dev/null and b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/cmake-favicon.ico differ diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/cmake.css b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/cmake.css new file mode 100644 index 0000000000000000000000000000000000000000..6303cb1cdefe49d2bf43b08bd080d543e05ad023 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/cmake.css @@ -0,0 +1,86 @@ +/* Import the Sphinx theme style. */ +@import url("default.css"); + +/* Wrap sidebar content even within words so that long + document names do not escape sidebar borders. */ +div.sphinxsidebarwrapper { + word-wrap: break-word; +} + +/* Make links inside parsed-literal blocks more obvious + by using a background color and increased line spacing + to make them look boxed. */ +.literal-block { + line-height: 1.4; +} +.literal-block a.reference.internal { + background-color: #dfdfdf; +} + +/* Apply
 style (from classic.css) to signature directive argument. */
+.signature .sig {
+  padding: 5px;
+  background-color: #eeeeee;
+  color: #333333;
+  line-height: 120%;
+  border: 1px solid #ac9;
+  border-left: none;
+  border-right: none;
+}
+
+/* Add additional styling to signature directive argument. */
+.signature .sig {
+  margin-bottom: 5px;
+  padding-left: calc(5px + 3em);
+  text-indent: -3em;
+  font-family: monospace;
+}
+
+.signature .sig .code.sig-name {
+  font-weight: normal;
+}
+
+/* Implement non-breaking spaces in signatures. */
+.nbsp {
+  white-space: nowrap;
+}
+
+/* Add hanging indent to version-{added,changed} content. */
+div .versionadded > *,
+div .versionchanged > * {
+  padding-left: 2em;
+}
+
+div.versionadded > :first-child,
+div.versionchanged > :first-child {
+  text-indent: -2em;
+}
+
+/* Remove unwanted margin in case list item contains a div-wrapping
+   directive like `.. versionadded` or `.. deprecated`. */
+dd > :first-child > p {
+  margin-top: 0px;
+}
+
+div.outdated {
+  background-color: #f0f0c0;
+  color: black;
+  font-size: 90%;
+  padding-bottom: 5px;
+  padding-left: 2px;
+  padding-right: 2px;
+  padding-top: 5px;
+  text-align: center;
+  width: 100%;
+}
+
+/* Revert style to the inherited (normal text) for `:guide:` links */
+code.xref.cmake-guide {
+  font-size: inherit;
+  font-family: inherit;
+  font-weight: inherit;
+  padding: inherit;
+}
+code.xref.cmake-guide span.pre {
+  white-space: inherit;
+}
diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/default.css b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/default.css
new file mode 100644
index 0000000000000000000000000000000000000000..81b9363634e0fd7a2651282abc4408ffec371df0
--- /dev/null
+++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/default.css
@@ -0,0 +1 @@
+@import url("classic.css");
diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/doctools.js b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/doctools.js
new file mode 100644
index 0000000000000000000000000000000000000000..527b876ca636d9a23d0cb3cc73ff6355b94fd7da
--- /dev/null
+++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/doctools.js
@@ -0,0 +1,156 @@
+/*
+ * doctools.js
+ * ~~~~~~~~~~~
+ *
+ * Base JavaScript utilities for all Sphinx HTML documentation.
+ *
+ * :copyright: Copyright 2007-2022 by the Sphinx team, see AUTHORS.
+ * :license: BSD, see LICENSE for details.
+ *
+ */
+"use strict";
+
+const BLACKLISTED_KEY_CONTROL_ELEMENTS = new Set([
+  "TEXTAREA",
+  "INPUT",
+  "SELECT",
+  "BUTTON",
+]);
+
+const _ready = (callback) => {
+  if (document.readyState !== "loading") {
+    callback();
+  } else {
+    document.addEventListener("DOMContentLoaded", callback);
+  }
+};
+
+/**
+ * Small JavaScript module for the documentation.
+ */
+const Documentation = {
+  init: () => {
+    Documentation.initDomainIndexTable();
+    Documentation.initOnKeyListeners();
+  },
+
+  /**
+   * i18n support
+   */
+  TRANSLATIONS: {},
+  PLURAL_EXPR: (n) => (n === 1 ? 0 : 1),
+  LOCALE: "unknown",
+
+  // gettext and ngettext don't access this so that the functions
+  // can safely bound to a different name (_ = Documentation.gettext)
+  gettext: (string) => {
+    const translated = Documentation.TRANSLATIONS[string];
+    switch (typeof translated) {
+      case "undefined":
+        return string; // no translation
+      case "string":
+        return translated; // translation exists
+      default:
+        return translated[0]; // (singular, plural) translation tuple exists
+    }
+  },
+
+  ngettext: (singular, plural, n) => {
+    const translated = Documentation.TRANSLATIONS[singular];
+    if (typeof translated !== "undefined")
+      return translated[Documentation.PLURAL_EXPR(n)];
+    return n === 1 ? singular : plural;
+  },
+
+  addTranslations: (catalog) => {
+    Object.assign(Documentation.TRANSLATIONS, catalog.messages);
+    Documentation.PLURAL_EXPR = new Function(
+      "n",
+      `return (${catalog.plural_expr})`
+    );
+    Documentation.LOCALE = catalog.locale;
+  },
+
+  /**
+   * helper function to focus on search bar
+   */
+  focusSearchBar: () => {
+    document.querySelectorAll("input[name=q]")[0]?.focus();
+  },
+
+  /**
+   * Initialise the domain index toggle buttons
+   */
+  initDomainIndexTable: () => {
+    const toggler = (el) => {
+      const idNumber = el.id.substr(7);
+      const toggledRows = document.querySelectorAll(`tr.cg-${idNumber}`);
+      if (el.src.substr(-9) === "minus.png") {
+        el.src = `${el.src.substr(0, el.src.length - 9)}plus.png`;
+        toggledRows.forEach((el) => (el.style.display = "none"));
+      } else {
+        el.src = `${el.src.substr(0, el.src.length - 8)}minus.png`;
+        toggledRows.forEach((el) => (el.style.display = ""));
+      }
+    };
+
+    const togglerElements = document.querySelectorAll("img.toggler");
+    togglerElements.forEach((el) =>
+      el.addEventListener("click", (event) => toggler(event.currentTarget))
+    );
+    togglerElements.forEach((el) => (el.style.display = ""));
+    if (DOCUMENTATION_OPTIONS.COLLAPSE_INDEX) togglerElements.forEach(toggler);
+  },
+
+  initOnKeyListeners: () => {
+    // only install a listener if it is really needed
+    if (
+      !DOCUMENTATION_OPTIONS.NAVIGATION_WITH_KEYS &&
+      !DOCUMENTATION_OPTIONS.ENABLE_SEARCH_SHORTCUTS
+    )
+      return;
+
+    document.addEventListener("keydown", (event) => {
+      // bail for input elements
+      if (BLACKLISTED_KEY_CONTROL_ELEMENTS.has(document.activeElement.tagName)) return;
+      // bail with special keys
+      if (event.altKey || event.ctrlKey || event.metaKey) return;
+
+      if (!event.shiftKey) {
+        switch (event.key) {
+          case "ArrowLeft":
+            if (!DOCUMENTATION_OPTIONS.NAVIGATION_WITH_KEYS) break;
+
+            const prevLink = document.querySelector('link[rel="prev"]');
+            if (prevLink && prevLink.href) {
+              window.location.href = prevLink.href;
+              event.preventDefault();
+            }
+            break;
+          case "ArrowRight":
+            if (!DOCUMENTATION_OPTIONS.NAVIGATION_WITH_KEYS) break;
+
+            const nextLink = document.querySelector('link[rel="next"]');
+            if (nextLink && nextLink.href) {
+              window.location.href = nextLink.href;
+              event.preventDefault();
+            }
+            break;
+        }
+      }
+
+      // some keyboard layouts may need Shift to get /
+      switch (event.key) {
+        case "/":
+          if (!DOCUMENTATION_OPTIONS.ENABLE_SEARCH_SHORTCUTS) break;
+          Documentation.focusSearchBar();
+          event.preventDefault();
+      }
+    });
+  },
+};
+
+// quick alias for translations
+const _ = Documentation.gettext;
+
+_ready(Documentation.init);
diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/documentation_options.js b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/documentation_options.js
new file mode 100644
index 0000000000000000000000000000000000000000..0e830e0c1c82eabfdbd89cf38dbc14d22762ea1e
--- /dev/null
+++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/documentation_options.js
@@ -0,0 +1,14 @@
+var DOCUMENTATION_OPTIONS = {
+    URL_ROOT: document.getElementById("documentation_options").getAttribute('data-url_root'),
+    VERSION: '3.27.9',
+    LANGUAGE: 'en',
+    COLLAPSE_INDEX: false,
+    BUILDER: 'html',
+    FILE_SUFFIX: '.html',
+    LINK_SUFFIX: '.html',
+    HAS_SOURCE: true,
+    SOURCELINK_SUFFIX: '.txt',
+    NAVIGATION_WITH_KEYS: false,
+    SHOW_SEARCH_SUMMARY: true,
+    ENABLE_SEARCH_SHORTCUTS: true,
+};
\ No newline at end of file
diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/jquery-3.6.0.js b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/jquery-3.6.0.js
new file mode 100644
index 0000000000000000000000000000000000000000..fc6c299b73e792ef288e785c22393a5df9dded4b
--- /dev/null
+++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/_static/jquery-3.6.0.js
@@ -0,0 +1,10881 @@
+/*!
+ * jQuery JavaScript Library v3.6.0
+ * https://jquery.com/
+ *
+ * Includes Sizzle.js
+ * https://sizzlejs.com/
+ *
+ * Copyright OpenJS Foundation and other contributors
+ * Released under the MIT license
+ * https://jquery.org/license
+ *
+ * Date: 2021-03-02T17:08Z
+ */
+( function( global, factory ) {
+
+	"use strict";
+
+	if ( typeof module === "object" && typeof module.exports === "object" ) {
+
+		// For CommonJS and CommonJS-like environments where a proper `window`
+		// is present, execute the factory and get jQuery.
+		// For environments that do not have a `window` with a `document`
+		// (such as Node.js), expose a factory as module.exports.
+		// This accentuates the need for the creation of a real `window`.
+		// e.g. var jQuery = require("jquery")(window);
+		// See ticket #14549 for more info.
+		module.exports = global.document ?
+			factory( global, true ) :
+			function( w ) {
+				if ( !w.document ) {
+					throw new Error( "jQuery requires a window with a document" );
+				}
+				return factory( w );
+			};
+	} else {
+		factory( global );
+	}
+
+// Pass this if window is not defined yet
+} )( typeof window !== "undefined" ? window : this, function( window, noGlobal ) {
+
+// Edge <= 12 - 13+, Firefox <=18 - 45+, IE 10 - 11, Safari 5.1 - 9+, iOS 6 - 9.1
+// throw exceptions when non-strict code (e.g., ASP.NET 4.5) accesses strict mode
+// arguments.callee.caller (trac-13335). But as of jQuery 3.0 (2016), strict mode should be common
+// enough that all such attempts are guarded in a try block.
+"use strict";
+
+var arr = [];
+
+var getProto = Object.getPrototypeOf;
+
+var slice = arr.slice;
+
+var flat = arr.flat ? function( array ) {
+	return arr.flat.call( array );
+} : function( array ) {
+	return arr.concat.apply( [], array );
+};
+
+
+var push = arr.push;
+
+var indexOf = arr.indexOf;
+
+var class2type = {};
+
+var toString = class2type.toString;
+
+var hasOwn = class2type.hasOwnProperty;
+
+var fnToString = hasOwn.toString;
+
+var ObjectFunctionString = fnToString.call( Object );
+
+var support = {};
+
+var isFunction = function isFunction( obj ) {
+
+		// Support: Chrome <=57, Firefox <=52
+		// In some browsers, typeof returns "function" for HTML  elements
+		// (i.e., `typeof document.createElement( "object" ) === "function"`).
+		// We don't want to classify *any* DOM node as a function.
+		// Support: QtWeb <=3.8.5, WebKit <=534.34, wkhtmltopdf tool <=0.12.5
+		// Plus for old WebKit, typeof returns "function" for HTML collections
+		// (e.g., `typeof document.getElementsByTagName("div") === "function"`). (gh-4756)
+		return typeof obj === "function" && typeof obj.nodeType !== "number" &&
+			typeof obj.item !== "function";
+	};
+
+
+var isWindow = function isWindow( obj ) {
+		return obj != null && obj === obj.window;
+	};
+
+
+var document = window.document;
+
+
+
+	var preservedScriptAttributes = {
+		type: true,
+		src: true,
+		nonce: true,
+		noModule: true
+	};
+
+	function DOMEval( code, node, doc ) {
+		doc = doc || document;
+
+		var i, val,
+			script = doc.createElement( "script" );
+
+		script.text = code;
+		if ( node ) {
+			for ( i in preservedScriptAttributes ) {
+
+				// Support: Firefox 64+, Edge 18+
+				// Some browsers don't support the "nonce" property on scripts.
+				// On the other hand, just using `getAttribute` is not enough as
+				// the `nonce` attribute is reset to an empty string whenever it
+				// becomes browsing-context connected.
+				// See https://github.com/whatwg/html/issues/2369
+				// See https://html.spec.whatwg.org/#nonce-attributes
+				// The `node.getAttribute` check was added for the sake of
+				// `jQuery.globalEval` so that it can fake a nonce-containing node
+				// via an object.
+				val = node[ i ] || node.getAttribute && node.getAttribute( i );
+				if ( val ) {
+					script.setAttribute( i, val );
+				}
+			}
+		}
+		doc.head.appendChild( script ).parentNode.removeChild( script );
+	}
+
+
+function toType( obj ) {
+	if ( obj == null ) {
+		return obj + "";
+	}
+
+	// Support: Android <=2.3 only (functionish RegExp)
+	return typeof obj === "object" || typeof obj === "function" ?
+		class2type[ toString.call( obj ) ] || "object" :
+		typeof obj;
+}
+/* global Symbol */
+// Defining this global in .eslintrc.json would create a danger of using the global
+// unguarded in another place, it seems safer to define global only for this module
+
+
+
+var
+	version = "3.6.0",
+
+	// Define a local copy of jQuery
+	jQuery = function( selector, context ) {
+
+		// The jQuery object is actually just the init constructor 'enhanced'
+		// Need init if jQuery is called (just allow error to be thrown if not included)
+		return new jQuery.fn.init( selector, context );
+	};
+
+jQuery.fn = jQuery.prototype = {
+
+	// The current version of jQuery being used
+	jquery: version,
+
+	constructor: jQuery,
+
+	// The default length of a jQuery object is 0
+	length: 0,
+
+	toArray: function() {
+		return slice.call( this );
+	},
+
+	// Get the Nth element in the matched element set OR
+	// Get the whole matched element set as a clean array
+	get: function( num ) {
+
+		// Return all the elements in a clean array
+		if ( num == null ) {
+			return slice.call( this );
+		}
+
+		// Return just the one element from the set
+		return num < 0 ? this[ num + this.length ] : this[ num ];
+	},
+
+	// Take an array of elements and push it onto the stack
+	// (returning the new matched element set)
+	pushStack: function( elems ) {
+
+		// Build a new jQuery matched element set
+		var ret = jQuery.merge( this.constructor(), elems );
+
+		// Add the old object onto the stack (as a reference)
+		ret.prevObject = this;
+
+		// Return the newly-formed element set
+		return ret;
+	},
+
+	// Execute a callback for every element in the matched set.
+	each: function( callback ) {
+		return jQuery.each( this, callback );
+	},
+
+	map: function( callback ) {
+		return this.pushStack( jQuery.map( this, function( elem, i ) {
+			return callback.call( elem, i, elem );
+		} ) );
+	},
+
+	slice: function() {
+		return this.pushStack( slice.apply( this, arguments ) );
+	},
+
+	first: function() {
+		return this.eq( 0 );
+	},
+
+	last: function() {
+		return this.eq( -1 );
+	},
+
+	even: function() {
+		return this.pushStack( jQuery.grep( this, function( _elem, i ) {
+			return ( i + 1 ) % 2;
+		} ) );
+	},
+
+	odd: function() {
+		return this.pushStack( jQuery.grep( this, function( _elem, i ) {
+			return i % 2;
+		} ) );
+	},
+
+	eq: function( i ) {
+		var len = this.length,
+			j = +i + ( i < 0 ? len : 0 );
+		return this.pushStack( j >= 0 && j < len ? [ this[ j ] ] : [] );
+	},
+
+	end: function() {
+		return this.prevObject || this.constructor();
+	},
+
+	// For internal use only.
+	// Behaves like an Array's method, not like a jQuery method.
+	push: push,
+	sort: arr.sort,
+	splice: arr.splice
+};
+
+jQuery.extend = jQuery.fn.extend = function() {
+	var options, name, src, copy, copyIsArray, clone,
+		target = arguments[ 0 ] || {},
+		i = 1,
+		length = arguments.length,
+		deep = false;
+
+	// Handle a deep copy situation
+	if ( typeof target === "boolean" ) {
+		deep = target;
+
+		// Skip the boolean and the target
+		target = arguments[ i ] || {};
+		i++;
+	}
+
+	// Handle case when target is a string or something (possible in deep copy)
+	if ( typeof target !== "object" && !isFunction( target ) ) {
+		target = {};
+	}
+
+	// Extend jQuery itself if only one argument is passed
+	if ( i === length ) {
+		target = this;
+		i--;
+	}
+
+	for ( ; i < length; i++ ) {
+
+		// Only deal with non-null/undefined values
+		if ( ( options = arguments[ i ] ) != null ) {
+
+			// Extend the base object
+			for ( name in options ) {
+				copy = options[ name ];
+
+				// Prevent Object.prototype pollution
+				// Prevent never-ending loop
+				if ( name === "__proto__" || target === copy ) {
+					continue;
+				}
+
+				// Recurse if we're merging plain objects or arrays
+				if ( deep && copy && ( jQuery.isPlainObject( copy ) ||
+					( copyIsArray = Array.isArray( copy ) ) ) ) {
+					src = target[ name ];
+
+					// Ensure proper type for the source value
+					if ( copyIsArray && !Array.isArray( src ) ) {
+						clone = [];
+					} else if ( !copyIsArray && !jQuery.isPlainObject( src ) ) {
+						clone = {};
+					} else {
+						clone = src;
+					}
+					copyIsArray = false;
+
+					// Never move original objects, clone them
+					target[ name ] = jQuery.extend( deep, clone, copy );
+
+				// Don't bring in undefined values
+				} else if ( copy !== undefined ) {
+					target[ name ] = copy;
+				}
+			}
+		}
+	}
+
+	// Return the modified object
+	return target;
+};
+
+jQuery.extend( {
+
+	// Unique for each copy of jQuery on the page
+	expando: "jQuery" + ( version + Math.random() ).replace( /\D/g, "" ),
+
+	// Assume jQuery is ready without the ready module
+	isReady: true,
+
+	error: function( msg ) {
+		throw new Error( msg );
+	},
+
+	noop: function() {},
+
+	isPlainObject: function( obj ) {
+		var proto, Ctor;
+
+		// Detect obvious negatives
+		// Use toString instead of jQuery.type to catch host objects
+		if ( !obj || toString.call( obj ) !== "[object Object]" ) {
+			return false;
+		}
+
+		proto = getProto( obj );
+
+		// Objects with no prototype (e.g., `Object.create( null )`) are plain
+		if ( !proto ) {
+			return true;
+		}
+
+		// Objects with prototype are plain iff they were constructed by a global Object function
+		Ctor = hasOwn.call( proto, "constructor" ) && proto.constructor;
+		return typeof Ctor === "function" && fnToString.call( Ctor ) === ObjectFunctionString;
+	},
+
+	isEmptyObject: function( obj ) {
+		var name;
+
+		for ( name in obj ) {
+			return false;
+		}
+		return true;
+	},
+
+	// Evaluates a script in a provided context; falls back to the global one
+	// if not specified.
+	globalEval: function( code, options, doc ) {
+		DOMEval( code, { nonce: options && options.nonce }, doc );
+	},
+
+	each: function( obj, callback ) {
+		var length, i = 0;
+
+		if ( isArrayLike( obj ) ) {
+			length = obj.length;
+			for ( ; i < length; i++ ) {
+				if ( callback.call( obj[ i ], i, obj[ i ] ) === false ) {
+					break;
+				}
+			}
+		} else {
+			for ( i in obj ) {
+				if ( callback.call( obj[ i ], i, obj[ i ] ) === false ) {
+					break;
+				}
+			}
+		}
+
+		return obj;
+	},
+
+	// results is for internal usage only
+	makeArray: function( arr, results ) {
+		var ret = results || [];
+
+		if ( arr != null ) {
+			if ( isArrayLike( Object( arr ) ) ) {
+				jQuery.merge( ret,
+					typeof arr === "string" ?
+						[ arr ] : arr
+				);
+			} else {
+				push.call( ret, arr );
+			}
+		}
+
+		return ret;
+	},
+
+	inArray: function( elem, arr, i ) {
+		return arr == null ? -1 : indexOf.call( arr, elem, i );
+	},
+
+	// Support: Android <=4.0 only, PhantomJS 1 only
+	// push.apply(_, arraylike) throws on ancient WebKit
+	merge: function( first, second ) {
+		var len = +second.length,
+			j = 0,
+			i = first.length;
+
+		for ( ; j < len; j++ ) {
+			first[ i++ ] = second[ j ];
+		}
+
+		first.length = i;
+
+		return first;
+	},
+
+	grep: function( elems, callback, invert ) {
+		var callbackInverse,
+			matches = [],
+			i = 0,
+			length = elems.length,
+			callbackExpect = !invert;
+
+		// Go through the array, only saving the items
+		// that pass the validator function
+		for ( ; i < length; i++ ) {
+			callbackInverse = !callback( elems[ i ], i );
+			if ( callbackInverse !== callbackExpect ) {
+				matches.push( elems[ i ] );
+			}
+		}
+
+		return matches;
+	},
+
+	// arg is for internal usage only
+	map: function( elems, callback, arg ) {
+		var length, value,
+			i = 0,
+			ret = [];
+
+		// Go through the array, translating each of the items to their new values
+		if ( isArrayLike( elems ) ) {
+			length = elems.length;
+			for ( ; i < length; i++ ) {
+				value = callback( elems[ i ], i, arg );
+
+				if ( value != null ) {
+					ret.push( value );
+				}
+			}
+
+		// Go through every key on the object,
+		} else {
+			for ( i in elems ) {
+				value = callback( elems[ i ], i, arg );
+
+				if ( value != null ) {
+					ret.push( value );
+				}
+			}
+		}
+
+		// Flatten any nested arrays
+		return flat( ret );
+	},
+
+	// A global GUID counter for objects
+	guid: 1,
+
+	// jQuery.support is not used in Core but other projects attach their
+	// properties to it so it needs to exist.
+	support: support
+} );
+
+if ( typeof Symbol === "function" ) {
+	jQuery.fn[ Symbol.iterator ] = arr[ Symbol.iterator ];
+}
+
+// Populate the class2type map
+jQuery.each( "Boolean Number String Function Array Date RegExp Object Error Symbol".split( " " ),
+	function( _i, name ) {
+		class2type[ "[object " + name + "]" ] = name.toLowerCase();
+	} );
+
+function isArrayLike( obj ) {
+
+	// Support: real iOS 8.2 only (not reproducible in simulator)
+	// `in` check used to prevent JIT error (gh-2145)
+	// hasOwn isn't used here due to false negatives
+	// regarding Nodelist length in IE
+	var length = !!obj && "length" in obj && obj.length,
+		type = toType( obj );
+
+	if ( isFunction( obj ) || isWindow( obj ) ) {
+		return false;
+	}
+
+	return type === "array" || length === 0 ||
+		typeof length === "number" && length > 0 && ( length - 1 ) in obj;
+}
+var Sizzle =
+/*!
+ * Sizzle CSS Selector Engine v2.3.6
+ * https://sizzlejs.com/
+ *
+ * Copyright JS Foundation and other contributors
+ * Released under the MIT license
+ * https://js.foundation/
+ *
+ * Date: 2021-02-16
+ */
+( function( window ) {
+var i,
+	support,
+	Expr,
+	getText,
+	isXML,
+	tokenize,
+	compile,
+	select,
+	outermostContext,
+	sortInput,
+	hasDuplicate,
+
+	// Local document vars
+	setDocument,
+	document,
+	docElem,
+	documentIsHTML,
+	rbuggyQSA,
+	rbuggyMatches,
+	matches,
+	contains,
+
+	// Instance-specific data
+	expando = "sizzle" + 1 * new Date(),
+	preferredDoc = window.document,
+	dirruns = 0,
+	done = 0,
+	classCache = createCache(),
+	tokenCache = createCache(),
+	compilerCache = createCache(),
+	nonnativeSelectorCache = createCache(),
+	sortOrder = function( a, b ) {
+		if ( a === b ) {
+			hasDuplicate = true;
+		}
+		return 0;
+	},
+
+	// Instance methods
+	hasOwn = ( {} ).hasOwnProperty,
+	arr = [],
+	pop = arr.pop,
+	pushNative = arr.push,
+	push = arr.push,
+	slice = arr.slice,
+
+	// Use a stripped-down indexOf as it's faster than native
+	// https://jsperf.com/thor-indexof-vs-for/5
+	indexOf = function( list, elem ) {
+		var i = 0,
+			len = list.length;
+		for ( ; i < len; i++ ) {
+			if ( list[ i ] === elem ) {
+				return i;
+			}
+		}
+		return -1;
+	},
+
+	booleans = "checked|selected|async|autofocus|autoplay|controls|defer|disabled|hidden|" +
+		"ismap|loop|multiple|open|readonly|required|scoped",
+
+	// Regular expressions
+
+	// http://www.w3.org/TR/css3-selectors/#whitespace
+	whitespace = "[\\x20\\t\\r\\n\\f]",
+
+	// https://www.w3.org/TR/css-syntax-3/#ident-token-diagram
+	identifier = "(?:\\\\[\\da-fA-F]{1,6}" + whitespace +
+		"?|\\\\[^\\r\\n\\f]|[\\w-]|[^\0-\\x7f])+",
+
+	// Attribute selectors: http://www.w3.org/TR/selectors/#attribute-selectors
+	attributes = "\\[" + whitespace + "*(" + identifier + ")(?:" + whitespace +
+
+		// Operator (capture 2)
+		"*([*^$|!~]?=)" + whitespace +
+
+		// "Attribute values must be CSS identifiers [capture 5]
+		// or strings [capture 3 or capture 4]"
+		"*(?:'((?:\\\\.|[^\\\\'])*)'|\"((?:\\\\.|[^\\\\\"])*)\"|(" + identifier + "))|)" +
+		whitespace + "*\\]",
+
+	pseudos = ":(" + identifier + ")(?:\\((" +
+
+		// To reduce the number of selectors needing tokenize in the preFilter, prefer arguments:
+		// 1. quoted (capture 3; capture 4 or capture 5)
+		"('((?:\\\\.|[^\\\\'])*)'|\"((?:\\\\.|[^\\\\\"])*)\")|" +
+
+		// 2. simple (capture 6)
+		"((?:\\\\.|[^\\\\()[\\]]|" + attributes + ")*)|" +
+
+		// 3. anything else (capture 2)
+		".*" +
+		")\\)|)",
+
+	// Leading and non-escaped trailing whitespace, capturing some non-whitespace characters preceding the latter
+	rwhitespace = new RegExp( whitespace + "+", "g" ),
+	rtrim = new RegExp( "^" + whitespace + "+|((?:^|[^\\\\])(?:\\\\.)*)" +
+		whitespace + "+$", "g" ),
+
+	rcomma = new RegExp( "^" + whitespace + "*," + whitespace + "*" ),
+	rcombinators = new RegExp( "^" + whitespace + "*([>+~]|" + whitespace + ")" + whitespace +
+		"*" ),
+	rdescend = new RegExp( whitespace + "|>" ),
+
+	rpseudo = new RegExp( pseudos ),
+	ridentifier = new RegExp( "^" + identifier + "$" ),
+
+	matchExpr = {
+		"ID": new RegExp( "^#(" + identifier + ")" ),
+		"CLASS": new RegExp( "^\\.(" + identifier + ")" ),
+		"TAG": new RegExp( "^(" + identifier + "|[*])" ),
+		"ATTR": new RegExp( "^" + attributes ),
+		"PSEUDO": new RegExp( "^" + pseudos ),
+		"CHILD": new RegExp( "^:(only|first|last|nth|nth-last)-(child|of-type)(?:\\(" +
+			whitespace + "*(even|odd|(([+-]|)(\\d*)n|)" + whitespace + "*(?:([+-]|)" +
+			whitespace + "*(\\d+)|))" + whitespace + "*\\)|)", "i" ),
+		"bool": new RegExp( "^(?:" + booleans + ")$", "i" ),
+
+		// For use in libraries implementing .is()
+		// We use this for POS matching in `select`
+		"needsContext": new RegExp( "^" + whitespace +
+			"*[>+~]|:(even|odd|eq|gt|lt|nth|first|last)(?:\\(" + whitespace +
+			"*((?:-\\d)?\\d*)" + whitespace + "*\\)|)(?=[^-]|$)", "i" )
+	},
+
+	rhtml = /HTML$/i,
+	rinputs = /^(?:input|select|textarea|button)$/i,
+	rheader = /^h\d$/i,
+
+	rnative = /^[^{]+\{\s*\[native \w/,
+
+	// Easily-parseable/retrievable ID or TAG or CLASS selectors
+	rquickExpr = /^(?:#([\w-]+)|(\w+)|\.([\w-]+))$/,
+
+	rsibling = /[+~]/,
+
+	// CSS escapes
+	// http://www.w3.org/TR/CSS21/syndata.html#escaped-characters
+	runescape = new RegExp( "\\\\[\\da-fA-F]{1,6}" + whitespace + "?|\\\\([^\\r\\n\\f])", "g" ),
+	funescape = function( escape, nonHex ) {
+		var high = "0x" + escape.slice( 1 ) - 0x10000;
+
+		return nonHex ?
+
+			// Strip the backslash prefix from a non-hex escape sequence
+			nonHex :
+
+			// Replace a hexadecimal escape sequence with the encoded Unicode code point
+			// Support: IE <=11+
+			// For values outside the Basic Multilingual Plane (BMP), manually construct a
+			// surrogate pair
+			high < 0 ?
+				String.fromCharCode( high + 0x10000 ) :
+				String.fromCharCode( high >> 10 | 0xD800, high & 0x3FF | 0xDC00 );
+	},
+
+	// CSS string/identifier serialization
+	// https://drafts.csswg.org/cssom/#common-serializing-idioms
+	rcssescape = /([\0-\x1f\x7f]|^-?\d)|^-$|[^\0-\x1f\x7f-\uFFFF\w-]/g,
+	fcssescape = function( ch, asCodePoint ) {
+		if ( asCodePoint ) {
+
+			// U+0000 NULL becomes U+FFFD REPLACEMENT CHARACTER
+			if ( ch === "\0" ) {
+				return "\uFFFD";
+			}
+
+			// Control characters and (dependent upon position) numbers get escaped as code points
+			return ch.slice( 0, -1 ) + "\\" +
+				ch.charCodeAt( ch.length - 1 ).toString( 16 ) + " ";
+		}
+
+		// Other potentially-special ASCII characters get backslash-escaped
+		return "\\" + ch;
+	},
+
+	// Used for iframes
+	// See setDocument()
+	// Removing the function wrapper causes a "Permission Denied"
+	// error in IE
+	unloadHandler = function() {
+		setDocument();
+	},
+
+	inDisabledFieldset = addCombinator(
+		function( elem ) {
+			return elem.disabled === true && elem.nodeName.toLowerCase() === "fieldset";
+		},
+		{ dir: "parentNode", next: "legend" }
+	);
+
+// Optimize for push.apply( _, NodeList )
+try {
+	push.apply(
+		( arr = slice.call( preferredDoc.childNodes ) ),
+		preferredDoc.childNodes
+	);
+
+	// Support: Android<4.0
+	// Detect silently failing push.apply
+	// eslint-disable-next-line no-unused-expressions
+	arr[ preferredDoc.childNodes.length ].nodeType;
+} catch ( e ) {
+	push = { apply: arr.length ?
+
+		// Leverage slice if possible
+		function( target, els ) {
+			pushNative.apply( target, slice.call( els ) );
+		} :
+
+		// Support: IE<9
+		// Otherwise append directly
+		function( target, els ) {
+			var j = target.length,
+				i = 0;
+
+			// Can't trust NodeList.length
+			while ( ( target[ j++ ] = els[ i++ ] ) ) {}
+			target.length = j - 1;
+		}
+	};
+}
+
+function Sizzle( selector, context, results, seed ) {
+	var m, i, elem, nid, match, groups, newSelector,
+		newContext = context && context.ownerDocument,
+
+		// nodeType defaults to 9, since context defaults to document
+		nodeType = context ? context.nodeType : 9;
+
+	results = results || [];
+
+	// Return early from calls with invalid selector or context
+	if ( typeof selector !== "string" || !selector ||
+		nodeType !== 1 && nodeType !== 9 && nodeType !== 11 ) {
+
+		return results;
+	}
+
+	// Try to shortcut find operations (as opposed to filters) in HTML documents
+	if ( !seed ) {
+		setDocument( context );
+		context = context || document;
+
+		if ( documentIsHTML ) {
+
+			// If the selector is sufficiently simple, try using a "get*By*" DOM method
+			// (excepting DocumentFragment context, where the methods don't exist)
+			if ( nodeType !== 11 && ( match = rquickExpr.exec( selector ) ) ) {
+
+				// ID selector
+				if ( ( m = match[ 1 ] ) ) {
+
+					// Document context
+					if ( nodeType === 9 ) {
+						if ( ( elem = context.getElementById( m ) ) ) {
+
+							// Support: IE, Opera, Webkit
+							// TODO: identify versions
+							// getElementById can match elements by name instead of ID
+							if ( elem.id === m ) {
+								results.push( elem );
+								return results;
+							}
+						} else {
+							return results;
+						}
+
+					// Element context
+					} else {
+
+						// Support: IE, Opera, Webkit
+						// TODO: identify versions
+						// getElementById can match elements by name instead of ID
+						if ( newContext && ( elem = newContext.getElementById( m ) ) &&
+							contains( context, elem ) &&
+							elem.id === m ) {
+
+							results.push( elem );
+							return results;
+						}
+					}
+
+				// Type selector
+				} else if ( match[ 2 ] ) {
+					push.apply( results, context.getElementsByTagName( selector ) );
+					return results;
+
+				// Class selector
+				} else if ( ( m = match[ 3 ] ) && support.getElementsByClassName &&
+					context.getElementsByClassName ) {
+
+					push.apply( results, context.getElementsByClassName( m ) );
+					return results;
+				}
+			}
+
+			// Take advantage of querySelectorAll
+			if ( support.qsa &&
+				!nonnativeSelectorCache[ selector + " " ] &&
+				( !rbuggyQSA || !rbuggyQSA.test( selector ) ) &&
+
+				// Support: IE 8 only
+				// Exclude object elements
+				( nodeType !== 1 || context.nodeName.toLowerCase() !== "object" ) ) {
+
+				newSelector = selector;
+				newContext = context;
+
+				// qSA considers elements outside a scoping root when evaluating child or
+				// descendant combinators, which is not what we want.
+				// In such cases, we work around the behavior by prefixing every selector in the
+				// list with an ID selector referencing the scope context.
+				// The technique has to be used as well when a leading combinator is used
+				// as such selectors are not recognized by querySelectorAll.
+				// Thanks to Andrew Dupont for this technique.
+				if ( nodeType === 1 &&
+					( rdescend.test( selector ) || rcombinators.test( selector ) ) ) {
+
+					// Expand context for sibling selectors
+					newContext = rsibling.test( selector ) && testContext( context.parentNode ) ||
+						context;
+
+					// We can use :scope instead of the ID hack if the browser
+					// supports it & if we're not changing the context.
+					if ( newContext !== context || !support.scope ) {
+
+						// Capture the context ID, setting it first if necessary
+						if ( ( nid = context.getAttribute( "id" ) ) ) {
+							nid = nid.replace( rcssescape, fcssescape );
+						} else {
+							context.setAttribute( "id", ( nid = expando ) );
+						}
+					}
+
+					// Prefix every selector in the list
+					groups = tokenize( selector );
+					i = groups.length;
+					while ( i-- ) {
+						groups[ i ] = ( nid ? "#" + nid : ":scope" ) + " " +
+							toSelector( groups[ i ] );
+					}
+					newSelector = groups.join( "," );
+				}
+
+				try {
+					push.apply( results,
+						newContext.querySelectorAll( newSelector )
+					);
+					return results;
+				} catch ( qsaError ) {
+					nonnativeSelectorCache( selector, true );
+				} finally {
+					if ( nid === expando ) {
+						context.removeAttribute( "id" );
+					}
+				}
+			}
+		}
+	}
+
+	// All others
+	return select( selector.replace( rtrim, "$1" ), context, results, seed );
+}
+
+/**
+ * Create key-value caches of limited size
+ * @returns {function(string, object)} Returns the Object data after storing it on itself with
+ *	property name the (space-suffixed) string and (if the cache is larger than Expr.cacheLength)
+ *	deleting the oldest entry
+ */
+function createCache() {
+	var keys = [];
+
+	function cache( key, value ) {
+
+		// Use (key + " ") to avoid collision with native prototype properties (see Issue #157)
+		if ( keys.push( key + " " ) > Expr.cacheLength ) {
+
+			// Only keep the most recent entries
+			delete cache[ keys.shift() ];
+		}
+		return ( cache[ key + " " ] = value );
+	}
+	return cache;
+}
+
+/**
+ * Mark a function for special use by Sizzle
+ * @param {Function} fn The function to mark
+ */
+function markFunction( fn ) {
+	fn[ expando ] = true;
+	return fn;
+}
+
+/**
+ * Support testing using an element
+ * @param {Function} fn Passed the created element and returns a boolean result
+ */
+function assert( fn ) {
+	var el = document.createElement( "fieldset" );
+
+	try {
+		return !!fn( el );
+	} catch ( e ) {
+		return false;
+	} finally {
+
+		// Remove from its parent by default
+		if ( el.parentNode ) {
+			el.parentNode.removeChild( el );
+		}
+
+		// release memory in IE
+		el = null;
+	}
+}
+
+/**
+ * Adds the same handler for all of the specified attrs
+ * @param {String} attrs Pipe-separated list of attributes
+ * @param {Function} handler The method that will be applied
+ */
+function addHandle( attrs, handler ) {
+	var arr = attrs.split( "|" ),
+		i = arr.length;
+
+	while ( i-- ) {
+		Expr.attrHandle[ arr[ i ] ] = handler;
+	}
+}
+
+/**
+ * Checks document order of two siblings
+ * @param {Element} a
+ * @param {Element} b
+ * @returns {Number} Returns less than 0 if a precedes b, greater than 0 if a follows b
+ */
+function siblingCheck( a, b ) {
+	var cur = b && a,
+		diff = cur && a.nodeType === 1 && b.nodeType === 1 &&
+			a.sourceIndex - b.sourceIndex;
+
+	// Use IE sourceIndex if available on both nodes
+	if ( diff ) {
+		return diff;
+	}
+
+	// Check if b follows a
+	if ( cur ) {
+		while ( ( cur = cur.nextSibling ) ) {
+			if ( cur === b ) {
+				return -1;
+			}
+		}
+	}
+
+	return a ? 1 : -1;
+}
+
+/**
+ * Returns a function to use in pseudos for input types
+ * @param {String} type
+ */
+function createInputPseudo( type ) {
+	return function( elem ) {
+		var name = elem.nodeName.toLowerCase();
+		return name === "input" && elem.type === type;
+	};
+}
+
+/**
+ * Returns a function to use in pseudos for buttons
+ * @param {String} type
+ */
+function createButtonPseudo( type ) {
+	return function( elem ) {
+		var name = elem.nodeName.toLowerCase();
+		return ( name === "input" || name === "button" ) && elem.type === type;
+	};
+}
+
+/**
+ * Returns a function to use in pseudos for :enabled/:disabled
+ * @param {Boolean} disabled true for :disabled; false for :enabled
+ */
+function createDisabledPseudo( disabled ) {
+
+	// Known :disabled false positives: fieldset[disabled] > legend:nth-of-type(n+2) :can-disable
+	return function( elem ) {
+
+		// Only certain elements can match :enabled or :disabled
+		// https://html.spec.whatwg.org/multipage/scripting.html#selector-enabled
+		// https://html.spec.whatwg.org/multipage/scripting.html#selector-disabled
+		if ( "form" in elem ) {
+
+			// Check for inherited disabledness on relevant non-disabled elements:
+			// * listed form-associated elements in a disabled fieldset
+			//   https://html.spec.whatwg.org/multipage/forms.html#category-listed
+			//   https://html.spec.whatwg.org/multipage/forms.html#concept-fe-disabled
+			// * option elements in a disabled optgroup
+			//   https://html.spec.whatwg.org/multipage/forms.html#concept-option-disabled
+			// All such elements have a "form" property.
+			if ( elem.parentNode && elem.disabled === false ) {
+
+				// Option elements defer to a parent optgroup if present
+				if ( "label" in elem ) {
+					if ( "label" in elem.parentNode ) {
+						return elem.parentNode.disabled === disabled;
+					} else {
+						return elem.disabled === disabled;
+					}
+				}
+
+				// Support: IE 6 - 11
+				// Use the isDisabled shortcut property to check for disabled fieldset ancestors
+				return elem.isDisabled === disabled ||
+
+					// Where there is no isDisabled, check manually
+					/* jshint -W018 */
+					elem.isDisabled !== !disabled &&
+					inDisabledFieldset( elem ) === disabled;
+			}
+
+			return elem.disabled === disabled;
+
+		// Try to winnow out elements that can't be disabled before trusting the disabled property.
+		// Some victims get caught in our net (label, legend, menu, track), but it shouldn't
+		// even exist on them, let alone have a boolean value.
+		} else if ( "label" in elem ) {
+			return elem.disabled === disabled;
+		}
+
+		// Remaining elements are neither :enabled nor :disabled
+		return false;
+	};
+}
+
+/**
+ * Returns a function to use in pseudos for positionals
+ * @param {Function} fn
+ */
+function createPositionalPseudo( fn ) {
+	return markFunction( function( argument ) {
+		argument = +argument;
+		return markFunction( function( seed, matches ) {
+			var j,
+				matchIndexes = fn( [], seed.length, argument ),
+				i = matchIndexes.length;
+
+			// Match elements found at the specified indexes
+			while ( i-- ) {
+				if ( seed[ ( j = matchIndexes[ i ] ) ] ) {
+					seed[ j ] = !( matches[ j ] = seed[ j ] );
+				}
+			}
+		} );
+	} );
+}
+
+/**
+ * Checks a node for validity as a Sizzle context
+ * @param {Element|Object=} context
+ * @returns {Element|Object|Boolean} The input node if acceptable, otherwise a falsy value
+ */
+function testContext( context ) {
+	return context && typeof context.getElementsByTagName !== "undefined" && context;
+}
+
+// Expose support vars for convenience
+support = Sizzle.support = {};
+
+/**
+ * Detects XML nodes
+ * @param {Element|Object} elem An element or a document
+ * @returns {Boolean} True iff elem is a non-HTML XML node
+ */
+isXML = Sizzle.isXML = function( elem ) {
+	var namespace = elem && elem.namespaceURI,
+		docElem = elem && ( elem.ownerDocument || elem ).documentElement;
+
+	// Support: IE <=8
+	// Assume HTML when documentElement doesn't yet exist, such as inside loading iframes
+	// https://bugs.jquery.com/ticket/4833
+	return !rhtml.test( namespace || docElem && docElem.nodeName || "HTML" );
+};
+
+/**
+ * Sets document-related variables once based on the current document
+ * @param {Element|Object} [doc] An element or document object to use to set the document
+ * @returns {Object} Returns the current document
+ */
+setDocument = Sizzle.setDocument = function( node ) {
+	var hasCompare, subWindow,
+		doc = node ? node.ownerDocument || node : preferredDoc;
+
+	// Return early if doc is invalid or already selected
+	// Support: IE 11+, Edge 17 - 18+
+	// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+	// two documents; shallow comparisons work.
+	// eslint-disable-next-line eqeqeq
+	if ( doc == document || doc.nodeType !== 9 || !doc.documentElement ) {
+		return document;
+	}
+
+	// Update global variables
+	document = doc;
+	docElem = document.documentElement;
+	documentIsHTML = !isXML( document );
+
+	// Support: IE 9 - 11+, Edge 12 - 18+
+	// Accessing iframe documents after unload throws "permission denied" errors (jQuery #13936)
+	// Support: IE 11+, Edge 17 - 18+
+	// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+	// two documents; shallow comparisons work.
+	// eslint-disable-next-line eqeqeq
+	if ( preferredDoc != document &&
+		( subWindow = document.defaultView ) && subWindow.top !== subWindow ) {
+
+		// Support: IE 11, Edge
+		if ( subWindow.addEventListener ) {
+			subWindow.addEventListener( "unload", unloadHandler, false );
+
+		// Support: IE 9 - 10 only
+		} else if ( subWindow.attachEvent ) {
+			subWindow.attachEvent( "onunload", unloadHandler );
+		}
+	}
+
+	// Support: IE 8 - 11+, Edge 12 - 18+, Chrome <=16 - 25 only, Firefox <=3.6 - 31 only,
+	// Safari 4 - 5 only, Opera <=11.6 - 12.x only
+	// IE/Edge & older browsers don't support the :scope pseudo-class.
+	// Support: Safari 6.0 only
+	// Safari 6.0 supports :scope but it's an alias of :root there.
+	support.scope = assert( function( el ) {
+		docElem.appendChild( el ).appendChild( document.createElement( "div" ) );
+		return typeof el.querySelectorAll !== "undefined" &&
+			!el.querySelectorAll( ":scope fieldset div" ).length;
+	} );
+
+	/* Attributes
+	---------------------------------------------------------------------- */
+
+	// Support: IE<8
+	// Verify that getAttribute really returns attributes and not properties
+	// (excepting IE8 booleans)
+	support.attributes = assert( function( el ) {
+		el.className = "i";
+		return !el.getAttribute( "className" );
+	} );
+
+	/* getElement(s)By*
+	---------------------------------------------------------------------- */
+
+	// Check if getElementsByTagName("*") returns only elements
+	support.getElementsByTagName = assert( function( el ) {
+		el.appendChild( document.createComment( "" ) );
+		return !el.getElementsByTagName( "*" ).length;
+	} );
+
+	// Support: IE<9
+	support.getElementsByClassName = rnative.test( document.getElementsByClassName );
+
+	// Support: IE<10
+	// Check if getElementById returns elements by name
+	// The broken getElementById methods don't pick up programmatically-set names,
+	// so use a roundabout getElementsByName test
+	support.getById = assert( function( el ) {
+		docElem.appendChild( el ).id = expando;
+		return !document.getElementsByName || !document.getElementsByName( expando ).length;
+	} );
+
+	// ID filter and find
+	if ( support.getById ) {
+		Expr.filter[ "ID" ] = function( id ) {
+			var attrId = id.replace( runescape, funescape );
+			return function( elem ) {
+				return elem.getAttribute( "id" ) === attrId;
+			};
+		};
+		Expr.find[ "ID" ] = function( id, context ) {
+			if ( typeof context.getElementById !== "undefined" && documentIsHTML ) {
+				var elem = context.getElementById( id );
+				return elem ? [ elem ] : [];
+			}
+		};
+	} else {
+		Expr.filter[ "ID" ] =  function( id ) {
+			var attrId = id.replace( runescape, funescape );
+			return function( elem ) {
+				var node = typeof elem.getAttributeNode !== "undefined" &&
+					elem.getAttributeNode( "id" );
+				return node && node.value === attrId;
+			};
+		};
+
+		// Support: IE 6 - 7 only
+		// getElementById is not reliable as a find shortcut
+		Expr.find[ "ID" ] = function( id, context ) {
+			if ( typeof context.getElementById !== "undefined" && documentIsHTML ) {
+				var node, i, elems,
+					elem = context.getElementById( id );
+
+				if ( elem ) {
+
+					// Verify the id attribute
+					node = elem.getAttributeNode( "id" );
+					if ( node && node.value === id ) {
+						return [ elem ];
+					}
+
+					// Fall back on getElementsByName
+					elems = context.getElementsByName( id );
+					i = 0;
+					while ( ( elem = elems[ i++ ] ) ) {
+						node = elem.getAttributeNode( "id" );
+						if ( node && node.value === id ) {
+							return [ elem ];
+						}
+					}
+				}
+
+				return [];
+			}
+		};
+	}
+
+	// Tag
+	Expr.find[ "TAG" ] = support.getElementsByTagName ?
+		function( tag, context ) {
+			if ( typeof context.getElementsByTagName !== "undefined" ) {
+				return context.getElementsByTagName( tag );
+
+			// DocumentFragment nodes don't have gEBTN
+			} else if ( support.qsa ) {
+				return context.querySelectorAll( tag );
+			}
+		} :
+
+		function( tag, context ) {
+			var elem,
+				tmp = [],
+				i = 0,
+
+				// By happy coincidence, a (broken) gEBTN appears on DocumentFragment nodes too
+				results = context.getElementsByTagName( tag );
+
+			// Filter out possible comments
+			if ( tag === "*" ) {
+				while ( ( elem = results[ i++ ] ) ) {
+					if ( elem.nodeType === 1 ) {
+						tmp.push( elem );
+					}
+				}
+
+				return tmp;
+			}
+			return results;
+		};
+
+	// Class
+	Expr.find[ "CLASS" ] = support.getElementsByClassName && function( className, context ) {
+		if ( typeof context.getElementsByClassName !== "undefined" && documentIsHTML ) {
+			return context.getElementsByClassName( className );
+		}
+	};
+
+	/* QSA/matchesSelector
+	---------------------------------------------------------------------- */
+
+	// QSA and matchesSelector support
+
+	// matchesSelector(:active) reports false when true (IE9/Opera 11.5)
+	rbuggyMatches = [];
+
+	// qSa(:focus) reports false when true (Chrome 21)
+	// We allow this because of a bug in IE8/9 that throws an error
+	// whenever `document.activeElement` is accessed on an iframe
+	// So, we allow :focus to pass through QSA all the time to avoid the IE error
+	// See https://bugs.jquery.com/ticket/13378
+	rbuggyQSA = [];
+
+	if ( ( support.qsa = rnative.test( document.querySelectorAll ) ) ) {
+
+		// Build QSA regex
+		// Regex strategy adopted from Diego Perini
+		assert( function( el ) {
+
+			var input;
+
+			// Select is set to empty string on purpose
+			// This is to test IE's treatment of not explicitly
+			// setting a boolean content attribute,
+			// since its presence should be enough
+			// https://bugs.jquery.com/ticket/12359
+			docElem.appendChild( el ).innerHTML = "" +
+				"";
+
+			// Support: IE8, Opera 11-12.16
+			// Nothing should be selected when empty strings follow ^= or $= or *=
+			// The test attribute must be unknown in Opera but "safe" for WinRT
+			// https://msdn.microsoft.com/en-us/library/ie/hh465388.aspx#attribute_section
+			if ( el.querySelectorAll( "[msallowcapture^='']" ).length ) {
+				rbuggyQSA.push( "[*^$]=" + whitespace + "*(?:''|\"\")" );
+			}
+
+			// Support: IE8
+			// Boolean attributes and "value" are not treated correctly
+			if ( !el.querySelectorAll( "[selected]" ).length ) {
+				rbuggyQSA.push( "\\[" + whitespace + "*(?:value|" + booleans + ")" );
+			}
+
+			// Support: Chrome<29, Android<4.4, Safari<7.0+, iOS<7.0+, PhantomJS<1.9.8+
+			if ( !el.querySelectorAll( "[id~=" + expando + "-]" ).length ) {
+				rbuggyQSA.push( "~=" );
+			}
+
+			// Support: IE 11+, Edge 15 - 18+
+			// IE 11/Edge don't find elements on a `[name='']` query in some cases.
+			// Adding a temporary attribute to the document before the selection works
+			// around the issue.
+			// Interestingly, IE 10 & older don't seem to have the issue.
+			input = document.createElement( "input" );
+			input.setAttribute( "name", "" );
+			el.appendChild( input );
+			if ( !el.querySelectorAll( "[name='']" ).length ) {
+				rbuggyQSA.push( "\\[" + whitespace + "*name" + whitespace + "*=" +
+					whitespace + "*(?:''|\"\")" );
+			}
+
+			// Webkit/Opera - :checked should return selected option elements
+			// http://www.w3.org/TR/2011/REC-css3-selectors-20110929/#checked
+			// IE8 throws error here and will not see later tests
+			if ( !el.querySelectorAll( ":checked" ).length ) {
+				rbuggyQSA.push( ":checked" );
+			}
+
+			// Support: Safari 8+, iOS 8+
+			// https://bugs.webkit.org/show_bug.cgi?id=136851
+			// In-page `selector#id sibling-combinator selector` fails
+			if ( !el.querySelectorAll( "a#" + expando + "+*" ).length ) {
+				rbuggyQSA.push( ".#.+[+~]" );
+			}
+
+			// Support: Firefox <=3.6 - 5 only
+			// Old Firefox doesn't throw on a badly-escaped identifier.
+			el.querySelectorAll( "\\\f" );
+			rbuggyQSA.push( "[\\r\\n\\f]" );
+		} );
+
+		assert( function( el ) {
+			el.innerHTML = "" +
+				"";
+
+			// Support: Windows 8 Native Apps
+			// The type and name attributes are restricted during .innerHTML assignment
+			var input = document.createElement( "input" );
+			input.setAttribute( "type", "hidden" );
+			el.appendChild( input ).setAttribute( "name", "D" );
+
+			// Support: IE8
+			// Enforce case-sensitivity of name attribute
+			if ( el.querySelectorAll( "[name=d]" ).length ) {
+				rbuggyQSA.push( "name" + whitespace + "*[*^$|!~]?=" );
+			}
+
+			// FF 3.5 - :enabled/:disabled and hidden elements (hidden elements are still enabled)
+			// IE8 throws error here and will not see later tests
+			if ( el.querySelectorAll( ":enabled" ).length !== 2 ) {
+				rbuggyQSA.push( ":enabled", ":disabled" );
+			}
+
+			// Support: IE9-11+
+			// IE's :disabled selector does not pick up the children of disabled fieldsets
+			docElem.appendChild( el ).disabled = true;
+			if ( el.querySelectorAll( ":disabled" ).length !== 2 ) {
+				rbuggyQSA.push( ":enabled", ":disabled" );
+			}
+
+			// Support: Opera 10 - 11 only
+			// Opera 10-11 does not throw on post-comma invalid pseudos
+			el.querySelectorAll( "*,:x" );
+			rbuggyQSA.push( ",.*:" );
+		} );
+	}
+
+	if ( ( support.matchesSelector = rnative.test( ( matches = docElem.matches ||
+		docElem.webkitMatchesSelector ||
+		docElem.mozMatchesSelector ||
+		docElem.oMatchesSelector ||
+		docElem.msMatchesSelector ) ) ) ) {
+
+		assert( function( el ) {
+
+			// Check to see if it's possible to do matchesSelector
+			// on a disconnected node (IE 9)
+			support.disconnectedMatch = matches.call( el, "*" );
+
+			// This should fail with an exception
+			// Gecko does not error, returns false instead
+			matches.call( el, "[s!='']:x" );
+			rbuggyMatches.push( "!=", pseudos );
+		} );
+	}
+
+	rbuggyQSA = rbuggyQSA.length && new RegExp( rbuggyQSA.join( "|" ) );
+	rbuggyMatches = rbuggyMatches.length && new RegExp( rbuggyMatches.join( "|" ) );
+
+	/* Contains
+	---------------------------------------------------------------------- */
+	hasCompare = rnative.test( docElem.compareDocumentPosition );
+
+	// Element contains another
+	// Purposefully self-exclusive
+	// As in, an element does not contain itself
+	contains = hasCompare || rnative.test( docElem.contains ) ?
+		function( a, b ) {
+			var adown = a.nodeType === 9 ? a.documentElement : a,
+				bup = b && b.parentNode;
+			return a === bup || !!( bup && bup.nodeType === 1 && (
+				adown.contains ?
+					adown.contains( bup ) :
+					a.compareDocumentPosition && a.compareDocumentPosition( bup ) & 16
+			) );
+		} :
+		function( a, b ) {
+			if ( b ) {
+				while ( ( b = b.parentNode ) ) {
+					if ( b === a ) {
+						return true;
+					}
+				}
+			}
+			return false;
+		};
+
+	/* Sorting
+	---------------------------------------------------------------------- */
+
+	// Document order sorting
+	sortOrder = hasCompare ?
+	function( a, b ) {
+
+		// Flag for duplicate removal
+		if ( a === b ) {
+			hasDuplicate = true;
+			return 0;
+		}
+
+		// Sort on method existence if only one input has compareDocumentPosition
+		var compare = !a.compareDocumentPosition - !b.compareDocumentPosition;
+		if ( compare ) {
+			return compare;
+		}
+
+		// Calculate position if both inputs belong to the same document
+		// Support: IE 11+, Edge 17 - 18+
+		// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+		// two documents; shallow comparisons work.
+		// eslint-disable-next-line eqeqeq
+		compare = ( a.ownerDocument || a ) == ( b.ownerDocument || b ) ?
+			a.compareDocumentPosition( b ) :
+
+			// Otherwise we know they are disconnected
+			1;
+
+		// Disconnected nodes
+		if ( compare & 1 ||
+			( !support.sortDetached && b.compareDocumentPosition( a ) === compare ) ) {
+
+			// Choose the first element that is related to our preferred document
+			// Support: IE 11+, Edge 17 - 18+
+			// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+			// two documents; shallow comparisons work.
+			// eslint-disable-next-line eqeqeq
+			if ( a == document || a.ownerDocument == preferredDoc &&
+				contains( preferredDoc, a ) ) {
+				return -1;
+			}
+
+			// Support: IE 11+, Edge 17 - 18+
+			// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+			// two documents; shallow comparisons work.
+			// eslint-disable-next-line eqeqeq
+			if ( b == document || b.ownerDocument == preferredDoc &&
+				contains( preferredDoc, b ) ) {
+				return 1;
+			}
+
+			// Maintain original order
+			return sortInput ?
+				( indexOf( sortInput, a ) - indexOf( sortInput, b ) ) :
+				0;
+		}
+
+		return compare & 4 ? -1 : 1;
+	} :
+	function( a, b ) {
+
+		// Exit early if the nodes are identical
+		if ( a === b ) {
+			hasDuplicate = true;
+			return 0;
+		}
+
+		var cur,
+			i = 0,
+			aup = a.parentNode,
+			bup = b.parentNode,
+			ap = [ a ],
+			bp = [ b ];
+
+		// Parentless nodes are either documents or disconnected
+		if ( !aup || !bup ) {
+
+			// Support: IE 11+, Edge 17 - 18+
+			// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+			// two documents; shallow comparisons work.
+			/* eslint-disable eqeqeq */
+			return a == document ? -1 :
+				b == document ? 1 :
+				/* eslint-enable eqeqeq */
+				aup ? -1 :
+				bup ? 1 :
+				sortInput ?
+				( indexOf( sortInput, a ) - indexOf( sortInput, b ) ) :
+				0;
+
+		// If the nodes are siblings, we can do a quick check
+		} else if ( aup === bup ) {
+			return siblingCheck( a, b );
+		}
+
+		// Otherwise we need full lists of their ancestors for comparison
+		cur = a;
+		while ( ( cur = cur.parentNode ) ) {
+			ap.unshift( cur );
+		}
+		cur = b;
+		while ( ( cur = cur.parentNode ) ) {
+			bp.unshift( cur );
+		}
+
+		// Walk down the tree looking for a discrepancy
+		while ( ap[ i ] === bp[ i ] ) {
+			i++;
+		}
+
+		return i ?
+
+			// Do a sibling check if the nodes have a common ancestor
+			siblingCheck( ap[ i ], bp[ i ] ) :
+
+			// Otherwise nodes in our document sort first
+			// Support: IE 11+, Edge 17 - 18+
+			// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+			// two documents; shallow comparisons work.
+			/* eslint-disable eqeqeq */
+			ap[ i ] == preferredDoc ? -1 :
+			bp[ i ] == preferredDoc ? 1 :
+			/* eslint-enable eqeqeq */
+			0;
+	};
+
+	return document;
+};
+
+Sizzle.matches = function( expr, elements ) {
+	return Sizzle( expr, null, null, elements );
+};
+
+Sizzle.matchesSelector = function( elem, expr ) {
+	setDocument( elem );
+
+	if ( support.matchesSelector && documentIsHTML &&
+		!nonnativeSelectorCache[ expr + " " ] &&
+		( !rbuggyMatches || !rbuggyMatches.test( expr ) ) &&
+		( !rbuggyQSA     || !rbuggyQSA.test( expr ) ) ) {
+
+		try {
+			var ret = matches.call( elem, expr );
+
+			// IE 9's matchesSelector returns false on disconnected nodes
+			if ( ret || support.disconnectedMatch ||
+
+				// As well, disconnected nodes are said to be in a document
+				// fragment in IE 9
+				elem.document && elem.document.nodeType !== 11 ) {
+				return ret;
+			}
+		} catch ( e ) {
+			nonnativeSelectorCache( expr, true );
+		}
+	}
+
+	return Sizzle( expr, document, null, [ elem ] ).length > 0;
+};
+
+Sizzle.contains = function( context, elem ) {
+
+	// Set document vars if needed
+	// Support: IE 11+, Edge 17 - 18+
+	// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+	// two documents; shallow comparisons work.
+	// eslint-disable-next-line eqeqeq
+	if ( ( context.ownerDocument || context ) != document ) {
+		setDocument( context );
+	}
+	return contains( context, elem );
+};
+
+Sizzle.attr = function( elem, name ) {
+
+	// Set document vars if needed
+	// Support: IE 11+, Edge 17 - 18+
+	// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+	// two documents; shallow comparisons work.
+	// eslint-disable-next-line eqeqeq
+	if ( ( elem.ownerDocument || elem ) != document ) {
+		setDocument( elem );
+	}
+
+	var fn = Expr.attrHandle[ name.toLowerCase() ],
+
+		// Don't get fooled by Object.prototype properties (jQuery #13807)
+		val = fn && hasOwn.call( Expr.attrHandle, name.toLowerCase() ) ?
+			fn( elem, name, !documentIsHTML ) :
+			undefined;
+
+	return val !== undefined ?
+		val :
+		support.attributes || !documentIsHTML ?
+			elem.getAttribute( name ) :
+			( val = elem.getAttributeNode( name ) ) && val.specified ?
+				val.value :
+				null;
+};
+
+Sizzle.escape = function( sel ) {
+	return ( sel + "" ).replace( rcssescape, fcssescape );
+};
+
+Sizzle.error = function( msg ) {
+	throw new Error( "Syntax error, unrecognized expression: " + msg );
+};
+
+/**
+ * Document sorting and removing duplicates
+ * @param {ArrayLike} results
+ */
+Sizzle.uniqueSort = function( results ) {
+	var elem,
+		duplicates = [],
+		j = 0,
+		i = 0;
+
+	// Unless we *know* we can detect duplicates, assume their presence
+	hasDuplicate = !support.detectDuplicates;
+	sortInput = !support.sortStable && results.slice( 0 );
+	results.sort( sortOrder );
+
+	if ( hasDuplicate ) {
+		while ( ( elem = results[ i++ ] ) ) {
+			if ( elem === results[ i ] ) {
+				j = duplicates.push( i );
+			}
+		}
+		while ( j-- ) {
+			results.splice( duplicates[ j ], 1 );
+		}
+	}
+
+	// Clear input after sorting to release objects
+	// See https://github.com/jquery/sizzle/pull/225
+	sortInput = null;
+
+	return results;
+};
+
+/**
+ * Utility function for retrieving the text value of an array of DOM nodes
+ * @param {Array|Element} elem
+ */
+getText = Sizzle.getText = function( elem ) {
+	var node,
+		ret = "",
+		i = 0,
+		nodeType = elem.nodeType;
+
+	if ( !nodeType ) {
+
+		// If no nodeType, this is expected to be an array
+		while ( ( node = elem[ i++ ] ) ) {
+
+			// Do not traverse comment nodes
+			ret += getText( node );
+		}
+	} else if ( nodeType === 1 || nodeType === 9 || nodeType === 11 ) {
+
+		// Use textContent for elements
+		// innerText usage removed for consistency of new lines (jQuery #11153)
+		if ( typeof elem.textContent === "string" ) {
+			return elem.textContent;
+		} else {
+
+			// Traverse its children
+			for ( elem = elem.firstChild; elem; elem = elem.nextSibling ) {
+				ret += getText( elem );
+			}
+		}
+	} else if ( nodeType === 3 || nodeType === 4 ) {
+		return elem.nodeValue;
+	}
+
+	// Do not include comment or processing instruction nodes
+
+	return ret;
+};
+
+Expr = Sizzle.selectors = {
+
+	// Can be adjusted by the user
+	cacheLength: 50,
+
+	createPseudo: markFunction,
+
+	match: matchExpr,
+
+	attrHandle: {},
+
+	find: {},
+
+	relative: {
+		">": { dir: "parentNode", first: true },
+		" ": { dir: "parentNode" },
+		"+": { dir: "previousSibling", first: true },
+		"~": { dir: "previousSibling" }
+	},
+
+	preFilter: {
+		"ATTR": function( match ) {
+			match[ 1 ] = match[ 1 ].replace( runescape, funescape );
+
+			// Move the given value to match[3] whether quoted or unquoted
+			match[ 3 ] = ( match[ 3 ] || match[ 4 ] ||
+				match[ 5 ] || "" ).replace( runescape, funescape );
+
+			if ( match[ 2 ] === "~=" ) {
+				match[ 3 ] = " " + match[ 3 ] + " ";
+			}
+
+			return match.slice( 0, 4 );
+		},
+
+		"CHILD": function( match ) {
+
+			/* matches from matchExpr["CHILD"]
+				1 type (only|nth|...)
+				2 what (child|of-type)
+				3 argument (even|odd|\d*|\d*n([+-]\d+)?|...)
+				4 xn-component of xn+y argument ([+-]?\d*n|)
+				5 sign of xn-component
+				6 x of xn-component
+				7 sign of y-component
+				8 y of y-component
+			*/
+			match[ 1 ] = match[ 1 ].toLowerCase();
+
+			if ( match[ 1 ].slice( 0, 3 ) === "nth" ) {
+
+				// nth-* requires argument
+				if ( !match[ 3 ] ) {
+					Sizzle.error( match[ 0 ] );
+				}
+
+				// numeric x and y parameters for Expr.filter.CHILD
+				// remember that false/true cast respectively to 0/1
+				match[ 4 ] = +( match[ 4 ] ?
+					match[ 5 ] + ( match[ 6 ] || 1 ) :
+					2 * ( match[ 3 ] === "even" || match[ 3 ] === "odd" ) );
+				match[ 5 ] = +( ( match[ 7 ] + match[ 8 ] ) || match[ 3 ] === "odd" );
+
+				// other types prohibit arguments
+			} else if ( match[ 3 ] ) {
+				Sizzle.error( match[ 0 ] );
+			}
+
+			return match;
+		},
+
+		"PSEUDO": function( match ) {
+			var excess,
+				unquoted = !match[ 6 ] && match[ 2 ];
+
+			if ( matchExpr[ "CHILD" ].test( match[ 0 ] ) ) {
+				return null;
+			}
+
+			// Accept quoted arguments as-is
+			if ( match[ 3 ] ) {
+				match[ 2 ] = match[ 4 ] || match[ 5 ] || "";
+
+			// Strip excess characters from unquoted arguments
+			} else if ( unquoted && rpseudo.test( unquoted ) &&
+
+				// Get excess from tokenize (recursively)
+				( excess = tokenize( unquoted, true ) ) &&
+
+				// advance to the next closing parenthesis
+				( excess = unquoted.indexOf( ")", unquoted.length - excess ) - unquoted.length ) ) {
+
+				// excess is a negative index
+				match[ 0 ] = match[ 0 ].slice( 0, excess );
+				match[ 2 ] = unquoted.slice( 0, excess );
+			}
+
+			// Return only captures needed by the pseudo filter method (type and argument)
+			return match.slice( 0, 3 );
+		}
+	},
+
+	filter: {
+
+		"TAG": function( nodeNameSelector ) {
+			var nodeName = nodeNameSelector.replace( runescape, funescape ).toLowerCase();
+			return nodeNameSelector === "*" ?
+				function() {
+					return true;
+				} :
+				function( elem ) {
+					return elem.nodeName && elem.nodeName.toLowerCase() === nodeName;
+				};
+		},
+
+		"CLASS": function( className ) {
+			var pattern = classCache[ className + " " ];
+
+			return pattern ||
+				( pattern = new RegExp( "(^|" + whitespace +
+					")" + className + "(" + whitespace + "|$)" ) ) && classCache(
+						className, function( elem ) {
+							return pattern.test(
+								typeof elem.className === "string" && elem.className ||
+								typeof elem.getAttribute !== "undefined" &&
+									elem.getAttribute( "class" ) ||
+								""
+							);
+				} );
+		},
+
+		"ATTR": function( name, operator, check ) {
+			return function( elem ) {
+				var result = Sizzle.attr( elem, name );
+
+				if ( result == null ) {
+					return operator === "!=";
+				}
+				if ( !operator ) {
+					return true;
+				}
+
+				result += "";
+
+				/* eslint-disable max-len */
+
+				return operator === "=" ? result === check :
+					operator === "!=" ? result !== check :
+					operator === "^=" ? check && result.indexOf( check ) === 0 :
+					operator === "*=" ? check && result.indexOf( check ) > -1 :
+					operator === "$=" ? check && result.slice( -check.length ) === check :
+					operator === "~=" ? ( " " + result.replace( rwhitespace, " " ) + " " ).indexOf( check ) > -1 :
+					operator === "|=" ? result === check || result.slice( 0, check.length + 1 ) === check + "-" :
+					false;
+				/* eslint-enable max-len */
+
+			};
+		},
+
+		"CHILD": function( type, what, _argument, first, last ) {
+			var simple = type.slice( 0, 3 ) !== "nth",
+				forward = type.slice( -4 ) !== "last",
+				ofType = what === "of-type";
+
+			return first === 1 && last === 0 ?
+
+				// Shortcut for :nth-*(n)
+				function( elem ) {
+					return !!elem.parentNode;
+				} :
+
+				function( elem, _context, xml ) {
+					var cache, uniqueCache, outerCache, node, nodeIndex, start,
+						dir = simple !== forward ? "nextSibling" : "previousSibling",
+						parent = elem.parentNode,
+						name = ofType && elem.nodeName.toLowerCase(),
+						useCache = !xml && !ofType,
+						diff = false;
+
+					if ( parent ) {
+
+						// :(first|last|only)-(child|of-type)
+						if ( simple ) {
+							while ( dir ) {
+								node = elem;
+								while ( ( node = node[ dir ] ) ) {
+									if ( ofType ?
+										node.nodeName.toLowerCase() === name :
+										node.nodeType === 1 ) {
+
+										return false;
+									}
+								}
+
+								// Reverse direction for :only-* (if we haven't yet done so)
+								start = dir = type === "only" && !start && "nextSibling";
+							}
+							return true;
+						}
+
+						start = [ forward ? parent.firstChild : parent.lastChild ];
+
+						// non-xml :nth-child(...) stores cache data on `parent`
+						if ( forward && useCache ) {
+
+							// Seek `elem` from a previously-cached index
+
+							// ...in a gzip-friendly way
+							node = parent;
+							outerCache = node[ expando ] || ( node[ expando ] = {} );
+
+							// Support: IE <9 only
+							// Defend against cloned attroperties (jQuery gh-1709)
+							uniqueCache = outerCache[ node.uniqueID ] ||
+								( outerCache[ node.uniqueID ] = {} );
+
+							cache = uniqueCache[ type ] || [];
+							nodeIndex = cache[ 0 ] === dirruns && cache[ 1 ];
+							diff = nodeIndex && cache[ 2 ];
+							node = nodeIndex && parent.childNodes[ nodeIndex ];
+
+							while ( ( node = ++nodeIndex && node && node[ dir ] ||
+
+								// Fallback to seeking `elem` from the start
+								( diff = nodeIndex = 0 ) || start.pop() ) ) {
+
+								// When found, cache indexes on `parent` and break
+								if ( node.nodeType === 1 && ++diff && node === elem ) {
+									uniqueCache[ type ] = [ dirruns, nodeIndex, diff ];
+									break;
+								}
+							}
+
+						} else {
+
+							// Use previously-cached element index if available
+							if ( useCache ) {
+
+								// ...in a gzip-friendly way
+								node = elem;
+								outerCache = node[ expando ] || ( node[ expando ] = {} );
+
+								// Support: IE <9 only
+								// Defend against cloned attroperties (jQuery gh-1709)
+								uniqueCache = outerCache[ node.uniqueID ] ||
+									( outerCache[ node.uniqueID ] = {} );
+
+								cache = uniqueCache[ type ] || [];
+								nodeIndex = cache[ 0 ] === dirruns && cache[ 1 ];
+								diff = nodeIndex;
+							}
+
+							// xml :nth-child(...)
+							// or :nth-last-child(...) or :nth(-last)?-of-type(...)
+							if ( diff === false ) {
+
+								// Use the same loop as above to seek `elem` from the start
+								while ( ( node = ++nodeIndex && node && node[ dir ] ||
+									( diff = nodeIndex = 0 ) || start.pop() ) ) {
+
+									if ( ( ofType ?
+										node.nodeName.toLowerCase() === name :
+										node.nodeType === 1 ) &&
+										++diff ) {
+
+										// Cache the index of each encountered element
+										if ( useCache ) {
+											outerCache = node[ expando ] ||
+												( node[ expando ] = {} );
+
+											// Support: IE <9 only
+											// Defend against cloned attroperties (jQuery gh-1709)
+											uniqueCache = outerCache[ node.uniqueID ] ||
+												( outerCache[ node.uniqueID ] = {} );
+
+											uniqueCache[ type ] = [ dirruns, diff ];
+										}
+
+										if ( node === elem ) {
+											break;
+										}
+									}
+								}
+							}
+						}
+
+						// Incorporate the offset, then check against cycle size
+						diff -= last;
+						return diff === first || ( diff % first === 0 && diff / first >= 0 );
+					}
+				};
+		},
+
+		"PSEUDO": function( pseudo, argument ) {
+
+			// pseudo-class names are case-insensitive
+			// http://www.w3.org/TR/selectors/#pseudo-classes
+			// Prioritize by case sensitivity in case custom pseudos are added with uppercase letters
+			// Remember that setFilters inherits from pseudos
+			var args,
+				fn = Expr.pseudos[ pseudo ] || Expr.setFilters[ pseudo.toLowerCase() ] ||
+					Sizzle.error( "unsupported pseudo: " + pseudo );
+
+			// The user may use createPseudo to indicate that
+			// arguments are needed to create the filter function
+			// just as Sizzle does
+			if ( fn[ expando ] ) {
+				return fn( argument );
+			}
+
+			// But maintain support for old signatures
+			if ( fn.length > 1 ) {
+				args = [ pseudo, pseudo, "", argument ];
+				return Expr.setFilters.hasOwnProperty( pseudo.toLowerCase() ) ?
+					markFunction( function( seed, matches ) {
+						var idx,
+							matched = fn( seed, argument ),
+							i = matched.length;
+						while ( i-- ) {
+							idx = indexOf( seed, matched[ i ] );
+							seed[ idx ] = !( matches[ idx ] = matched[ i ] );
+						}
+					} ) :
+					function( elem ) {
+						return fn( elem, 0, args );
+					};
+			}
+
+			return fn;
+		}
+	},
+
+	pseudos: {
+
+		// Potentially complex pseudos
+		"not": markFunction( function( selector ) {
+
+			// Trim the selector passed to compile
+			// to avoid treating leading and trailing
+			// spaces as combinators
+			var input = [],
+				results = [],
+				matcher = compile( selector.replace( rtrim, "$1" ) );
+
+			return matcher[ expando ] ?
+				markFunction( function( seed, matches, _context, xml ) {
+					var elem,
+						unmatched = matcher( seed, null, xml, [] ),
+						i = seed.length;
+
+					// Match elements unmatched by `matcher`
+					while ( i-- ) {
+						if ( ( elem = unmatched[ i ] ) ) {
+							seed[ i ] = !( matches[ i ] = elem );
+						}
+					}
+				} ) :
+				function( elem, _context, xml ) {
+					input[ 0 ] = elem;
+					matcher( input, null, xml, results );
+
+					// Don't keep the element (issue #299)
+					input[ 0 ] = null;
+					return !results.pop();
+				};
+		} ),
+
+		"has": markFunction( function( selector ) {
+			return function( elem ) {
+				return Sizzle( selector, elem ).length > 0;
+			};
+		} ),
+
+		"contains": markFunction( function( text ) {
+			text = text.replace( runescape, funescape );
+			return function( elem ) {
+				return ( elem.textContent || getText( elem ) ).indexOf( text ) > -1;
+			};
+		} ),
+
+		// "Whether an element is represented by a :lang() selector
+		// is based solely on the element's language value
+		// being equal to the identifier C,
+		// or beginning with the identifier C immediately followed by "-".
+		// The matching of C against the element's language value is performed case-insensitively.
+		// The identifier C does not have to be a valid language name."
+		// http://www.w3.org/TR/selectors/#lang-pseudo
+		"lang": markFunction( function( lang ) {
+
+			// lang value must be a valid identifier
+			if ( !ridentifier.test( lang || "" ) ) {
+				Sizzle.error( "unsupported lang: " + lang );
+			}
+			lang = lang.replace( runescape, funescape ).toLowerCase();
+			return function( elem ) {
+				var elemLang;
+				do {
+					if ( ( elemLang = documentIsHTML ?
+						elem.lang :
+						elem.getAttribute( "xml:lang" ) || elem.getAttribute( "lang" ) ) ) {
+
+						elemLang = elemLang.toLowerCase();
+						return elemLang === lang || elemLang.indexOf( lang + "-" ) === 0;
+					}
+				} while ( ( elem = elem.parentNode ) && elem.nodeType === 1 );
+				return false;
+			};
+		} ),
+
+		// Miscellaneous
+		"target": function( elem ) {
+			var hash = window.location && window.location.hash;
+			return hash && hash.slice( 1 ) === elem.id;
+		},
+
+		"root": function( elem ) {
+			return elem === docElem;
+		},
+
+		"focus": function( elem ) {
+			return elem === document.activeElement &&
+				( !document.hasFocus || document.hasFocus() ) &&
+				!!( elem.type || elem.href || ~elem.tabIndex );
+		},
+
+		// Boolean properties
+		"enabled": createDisabledPseudo( false ),
+		"disabled": createDisabledPseudo( true ),
+
+		"checked": function( elem ) {
+
+			// In CSS3, :checked should return both checked and selected elements
+			// http://www.w3.org/TR/2011/REC-css3-selectors-20110929/#checked
+			var nodeName = elem.nodeName.toLowerCase();
+			return ( nodeName === "input" && !!elem.checked ) ||
+				( nodeName === "option" && !!elem.selected );
+		},
+
+		"selected": function( elem ) {
+
+			// Accessing this property makes selected-by-default
+			// options in Safari work properly
+			if ( elem.parentNode ) {
+				// eslint-disable-next-line no-unused-expressions
+				elem.parentNode.selectedIndex;
+			}
+
+			return elem.selected === true;
+		},
+
+		// Contents
+		"empty": function( elem ) {
+
+			// http://www.w3.org/TR/selectors/#empty-pseudo
+			// :empty is negated by element (1) or content nodes (text: 3; cdata: 4; entity ref: 5),
+			//   but not by others (comment: 8; processing instruction: 7; etc.)
+			// nodeType < 6 works because attributes (2) do not appear as children
+			for ( elem = elem.firstChild; elem; elem = elem.nextSibling ) {
+				if ( elem.nodeType < 6 ) {
+					return false;
+				}
+			}
+			return true;
+		},
+
+		"parent": function( elem ) {
+			return !Expr.pseudos[ "empty" ]( elem );
+		},
+
+		// Element/input types
+		"header": function( elem ) {
+			return rheader.test( elem.nodeName );
+		},
+
+		"input": function( elem ) {
+			return rinputs.test( elem.nodeName );
+		},
+
+		"button": function( elem ) {
+			var name = elem.nodeName.toLowerCase();
+			return name === "input" && elem.type === "button" || name === "button";
+		},
+
+		"text": function( elem ) {
+			var attr;
+			return elem.nodeName.toLowerCase() === "input" &&
+				elem.type === "text" &&
+
+				// Support: IE<8
+				// New HTML5 attribute values (e.g., "search") appear with elem.type === "text"
+				( ( attr = elem.getAttribute( "type" ) ) == null ||
+					attr.toLowerCase() === "text" );
+		},
+
+		// Position-in-collection
+		"first": createPositionalPseudo( function() {
+			return [ 0 ];
+		} ),
+
+		"last": createPositionalPseudo( function( _matchIndexes, length ) {
+			return [ length - 1 ];
+		} ),
+
+		"eq": createPositionalPseudo( function( _matchIndexes, length, argument ) {
+			return [ argument < 0 ? argument + length : argument ];
+		} ),
+
+		"even": createPositionalPseudo( function( matchIndexes, length ) {
+			var i = 0;
+			for ( ; i < length; i += 2 ) {
+				matchIndexes.push( i );
+			}
+			return matchIndexes;
+		} ),
+
+		"odd": createPositionalPseudo( function( matchIndexes, length ) {
+			var i = 1;
+			for ( ; i < length; i += 2 ) {
+				matchIndexes.push( i );
+			}
+			return matchIndexes;
+		} ),
+
+		"lt": createPositionalPseudo( function( matchIndexes, length, argument ) {
+			var i = argument < 0 ?
+				argument + length :
+				argument > length ?
+					length :
+					argument;
+			for ( ; --i >= 0; ) {
+				matchIndexes.push( i );
+			}
+			return matchIndexes;
+		} ),
+
+		"gt": createPositionalPseudo( function( matchIndexes, length, argument ) {
+			var i = argument < 0 ? argument + length : argument;
+			for ( ; ++i < length; ) {
+				matchIndexes.push( i );
+			}
+			return matchIndexes;
+		} )
+	}
+};
+
+Expr.pseudos[ "nth" ] = Expr.pseudos[ "eq" ];
+
+// Add button/input type pseudos
+for ( i in { radio: true, checkbox: true, file: true, password: true, image: true } ) {
+	Expr.pseudos[ i ] = createInputPseudo( i );
+}
+for ( i in { submit: true, reset: true } ) {
+	Expr.pseudos[ i ] = createButtonPseudo( i );
+}
+
+// Easy API for creating new setFilters
+function setFilters() {}
+setFilters.prototype = Expr.filters = Expr.pseudos;
+Expr.setFilters = new setFilters();
+
+tokenize = Sizzle.tokenize = function( selector, parseOnly ) {
+	var matched, match, tokens, type,
+		soFar, groups, preFilters,
+		cached = tokenCache[ selector + " " ];
+
+	if ( cached ) {
+		return parseOnly ? 0 : cached.slice( 0 );
+	}
+
+	soFar = selector;
+	groups = [];
+	preFilters = Expr.preFilter;
+
+	while ( soFar ) {
+
+		// Comma and first run
+		if ( !matched || ( match = rcomma.exec( soFar ) ) ) {
+			if ( match ) {
+
+				// Don't consume trailing commas as valid
+				soFar = soFar.slice( match[ 0 ].length ) || soFar;
+			}
+			groups.push( ( tokens = [] ) );
+		}
+
+		matched = false;
+
+		// Combinators
+		if ( ( match = rcombinators.exec( soFar ) ) ) {
+			matched = match.shift();
+			tokens.push( {
+				value: matched,
+
+				// Cast descendant combinators to space
+				type: match[ 0 ].replace( rtrim, " " )
+			} );
+			soFar = soFar.slice( matched.length );
+		}
+
+		// Filters
+		for ( type in Expr.filter ) {
+			if ( ( match = matchExpr[ type ].exec( soFar ) ) && ( !preFilters[ type ] ||
+				( match = preFilters[ type ]( match ) ) ) ) {
+				matched = match.shift();
+				tokens.push( {
+					value: matched,
+					type: type,
+					matches: match
+				} );
+				soFar = soFar.slice( matched.length );
+			}
+		}
+
+		if ( !matched ) {
+			break;
+		}
+	}
+
+	// Return the length of the invalid excess
+	// if we're just parsing
+	// Otherwise, throw an error or return tokens
+	return parseOnly ?
+		soFar.length :
+		soFar ?
+			Sizzle.error( selector ) :
+
+			// Cache the tokens
+			tokenCache( selector, groups ).slice( 0 );
+};
+
+function toSelector( tokens ) {
+	var i = 0,
+		len = tokens.length,
+		selector = "";
+	for ( ; i < len; i++ ) {
+		selector += tokens[ i ].value;
+	}
+	return selector;
+}
+
+function addCombinator( matcher, combinator, base ) {
+	var dir = combinator.dir,
+		skip = combinator.next,
+		key = skip || dir,
+		checkNonElements = base && key === "parentNode",
+		doneName = done++;
+
+	return combinator.first ?
+
+		// Check against closest ancestor/preceding element
+		function( elem, context, xml ) {
+			while ( ( elem = elem[ dir ] ) ) {
+				if ( elem.nodeType === 1 || checkNonElements ) {
+					return matcher( elem, context, xml );
+				}
+			}
+			return false;
+		} :
+
+		// Check against all ancestor/preceding elements
+		function( elem, context, xml ) {
+			var oldCache, uniqueCache, outerCache,
+				newCache = [ dirruns, doneName ];
+
+			// We can't set arbitrary data on XML nodes, so they don't benefit from combinator caching
+			if ( xml ) {
+				while ( ( elem = elem[ dir ] ) ) {
+					if ( elem.nodeType === 1 || checkNonElements ) {
+						if ( matcher( elem, context, xml ) ) {
+							return true;
+						}
+					}
+				}
+			} else {
+				while ( ( elem = elem[ dir ] ) ) {
+					if ( elem.nodeType === 1 || checkNonElements ) {
+						outerCache = elem[ expando ] || ( elem[ expando ] = {} );
+
+						// Support: IE <9 only
+						// Defend against cloned attroperties (jQuery gh-1709)
+						uniqueCache = outerCache[ elem.uniqueID ] ||
+							( outerCache[ elem.uniqueID ] = {} );
+
+						if ( skip && skip === elem.nodeName.toLowerCase() ) {
+							elem = elem[ dir ] || elem;
+						} else if ( ( oldCache = uniqueCache[ key ] ) &&
+							oldCache[ 0 ] === dirruns && oldCache[ 1 ] === doneName ) {
+
+							// Assign to newCache so results back-propagate to previous elements
+							return ( newCache[ 2 ] = oldCache[ 2 ] );
+						} else {
+
+							// Reuse newcache so results back-propagate to previous elements
+							uniqueCache[ key ] = newCache;
+
+							// A match means we're done; a fail means we have to keep checking
+							if ( ( newCache[ 2 ] = matcher( elem, context, xml ) ) ) {
+								return true;
+							}
+						}
+					}
+				}
+			}
+			return false;
+		};
+}
+
+function elementMatcher( matchers ) {
+	return matchers.length > 1 ?
+		function( elem, context, xml ) {
+			var i = matchers.length;
+			while ( i-- ) {
+				if ( !matchers[ i ]( elem, context, xml ) ) {
+					return false;
+				}
+			}
+			return true;
+		} :
+		matchers[ 0 ];
+}
+
+function multipleContexts( selector, contexts, results ) {
+	var i = 0,
+		len = contexts.length;
+	for ( ; i < len; i++ ) {
+		Sizzle( selector, contexts[ i ], results );
+	}
+	return results;
+}
+
+function condense( unmatched, map, filter, context, xml ) {
+	var elem,
+		newUnmatched = [],
+		i = 0,
+		len = unmatched.length,
+		mapped = map != null;
+
+	for ( ; i < len; i++ ) {
+		if ( ( elem = unmatched[ i ] ) ) {
+			if ( !filter || filter( elem, context, xml ) ) {
+				newUnmatched.push( elem );
+				if ( mapped ) {
+					map.push( i );
+				}
+			}
+		}
+	}
+
+	return newUnmatched;
+}
+
+function setMatcher( preFilter, selector, matcher, postFilter, postFinder, postSelector ) {
+	if ( postFilter && !postFilter[ expando ] ) {
+		postFilter = setMatcher( postFilter );
+	}
+	if ( postFinder && !postFinder[ expando ] ) {
+		postFinder = setMatcher( postFinder, postSelector );
+	}
+	return markFunction( function( seed, results, context, xml ) {
+		var temp, i, elem,
+			preMap = [],
+			postMap = [],
+			preexisting = results.length,
+
+			// Get initial elements from seed or context
+			elems = seed || multipleContexts(
+				selector || "*",
+				context.nodeType ? [ context ] : context,
+				[]
+			),
+
+			// Prefilter to get matcher input, preserving a map for seed-results synchronization
+			matcherIn = preFilter && ( seed || !selector ) ?
+				condense( elems, preMap, preFilter, context, xml ) :
+				elems,
+
+			matcherOut = matcher ?
+
+				// If we have a postFinder, or filtered seed, or non-seed postFilter or preexisting results,
+				postFinder || ( seed ? preFilter : preexisting || postFilter ) ?
+
+					// ...intermediate processing is necessary
+					[] :
+
+					// ...otherwise use results directly
+					results :
+				matcherIn;
+
+		// Find primary matches
+		if ( matcher ) {
+			matcher( matcherIn, matcherOut, context, xml );
+		}
+
+		// Apply postFilter
+		if ( postFilter ) {
+			temp = condense( matcherOut, postMap );
+			postFilter( temp, [], context, xml );
+
+			// Un-match failing elements by moving them back to matcherIn
+			i = temp.length;
+			while ( i-- ) {
+				if ( ( elem = temp[ i ] ) ) {
+					matcherOut[ postMap[ i ] ] = !( matcherIn[ postMap[ i ] ] = elem );
+				}
+			}
+		}
+
+		if ( seed ) {
+			if ( postFinder || preFilter ) {
+				if ( postFinder ) {
+
+					// Get the final matcherOut by condensing this intermediate into postFinder contexts
+					temp = [];
+					i = matcherOut.length;
+					while ( i-- ) {
+						if ( ( elem = matcherOut[ i ] ) ) {
+
+							// Restore matcherIn since elem is not yet a final match
+							temp.push( ( matcherIn[ i ] = elem ) );
+						}
+					}
+					postFinder( null, ( matcherOut = [] ), temp, xml );
+				}
+
+				// Move matched elements from seed to results to keep them synchronized
+				i = matcherOut.length;
+				while ( i-- ) {
+					if ( ( elem = matcherOut[ i ] ) &&
+						( temp = postFinder ? indexOf( seed, elem ) : preMap[ i ] ) > -1 ) {
+
+						seed[ temp ] = !( results[ temp ] = elem );
+					}
+				}
+			}
+
+		// Add elements to results, through postFinder if defined
+		} else {
+			matcherOut = condense(
+				matcherOut === results ?
+					matcherOut.splice( preexisting, matcherOut.length ) :
+					matcherOut
+			);
+			if ( postFinder ) {
+				postFinder( null, results, matcherOut, xml );
+			} else {
+				push.apply( results, matcherOut );
+			}
+		}
+	} );
+}
+
+function matcherFromTokens( tokens ) {
+	var checkContext, matcher, j,
+		len = tokens.length,
+		leadingRelative = Expr.relative[ tokens[ 0 ].type ],
+		implicitRelative = leadingRelative || Expr.relative[ " " ],
+		i = leadingRelative ? 1 : 0,
+
+		// The foundational matcher ensures that elements are reachable from top-level context(s)
+		matchContext = addCombinator( function( elem ) {
+			return elem === checkContext;
+		}, implicitRelative, true ),
+		matchAnyContext = addCombinator( function( elem ) {
+			return indexOf( checkContext, elem ) > -1;
+		}, implicitRelative, true ),
+		matchers = [ function( elem, context, xml ) {
+			var ret = ( !leadingRelative && ( xml || context !== outermostContext ) ) || (
+				( checkContext = context ).nodeType ?
+					matchContext( elem, context, xml ) :
+					matchAnyContext( elem, context, xml ) );
+
+			// Avoid hanging onto element (issue #299)
+			checkContext = null;
+			return ret;
+		} ];
+
+	for ( ; i < len; i++ ) {
+		if ( ( matcher = Expr.relative[ tokens[ i ].type ] ) ) {
+			matchers = [ addCombinator( elementMatcher( matchers ), matcher ) ];
+		} else {
+			matcher = Expr.filter[ tokens[ i ].type ].apply( null, tokens[ i ].matches );
+
+			// Return special upon seeing a positional matcher
+			if ( matcher[ expando ] ) {
+
+				// Find the next relative operator (if any) for proper handling
+				j = ++i;
+				for ( ; j < len; j++ ) {
+					if ( Expr.relative[ tokens[ j ].type ] ) {
+						break;
+					}
+				}
+				return setMatcher(
+					i > 1 && elementMatcher( matchers ),
+					i > 1 && toSelector(
+
+					// If the preceding token was a descendant combinator, insert an implicit any-element `*`
+					tokens
+						.slice( 0, i - 1 )
+						.concat( { value: tokens[ i - 2 ].type === " " ? "*" : "" } )
+					).replace( rtrim, "$1" ),
+					matcher,
+					i < j && matcherFromTokens( tokens.slice( i, j ) ),
+					j < len && matcherFromTokens( ( tokens = tokens.slice( j ) ) ),
+					j < len && toSelector( tokens )
+				);
+			}
+			matchers.push( matcher );
+		}
+	}
+
+	return elementMatcher( matchers );
+}
+
+function matcherFromGroupMatchers( elementMatchers, setMatchers ) {
+	var bySet = setMatchers.length > 0,
+		byElement = elementMatchers.length > 0,
+		superMatcher = function( seed, context, xml, results, outermost ) {
+			var elem, j, matcher,
+				matchedCount = 0,
+				i = "0",
+				unmatched = seed && [],
+				setMatched = [],
+				contextBackup = outermostContext,
+
+				// We must always have either seed elements or outermost context
+				elems = seed || byElement && Expr.find[ "TAG" ]( "*", outermost ),
+
+				// Use integer dirruns iff this is the outermost matcher
+				dirrunsUnique = ( dirruns += contextBackup == null ? 1 : Math.random() || 0.1 ),
+				len = elems.length;
+
+			if ( outermost ) {
+
+				// Support: IE 11+, Edge 17 - 18+
+				// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+				// two documents; shallow comparisons work.
+				// eslint-disable-next-line eqeqeq
+				outermostContext = context == document || context || outermost;
+			}
+
+			// Add elements passing elementMatchers directly to results
+			// Support: IE<9, Safari
+			// Tolerate NodeList properties (IE: "length"; Safari: ) matching elements by id
+			for ( ; i !== len && ( elem = elems[ i ] ) != null; i++ ) {
+				if ( byElement && elem ) {
+					j = 0;
+
+					// Support: IE 11+, Edge 17 - 18+
+					// IE/Edge sometimes throw a "Permission denied" error when strict-comparing
+					// two documents; shallow comparisons work.
+					// eslint-disable-next-line eqeqeq
+					if ( !context && elem.ownerDocument != document ) {
+						setDocument( elem );
+						xml = !documentIsHTML;
+					}
+					while ( ( matcher = elementMatchers[ j++ ] ) ) {
+						if ( matcher( elem, context || document, xml ) ) {
+							results.push( elem );
+							break;
+						}
+					}
+					if ( outermost ) {
+						dirruns = dirrunsUnique;
+					}
+				}
+
+				// Track unmatched elements for set filters
+				if ( bySet ) {
+
+					// They will have gone through all possible matchers
+					if ( ( elem = !matcher && elem ) ) {
+						matchedCount--;
+					}
+
+					// Lengthen the array for every element, matched or not
+					if ( seed ) {
+						unmatched.push( elem );
+					}
+				}
+			}
+
+			// `i` is now the count of elements visited above, and adding it to `matchedCount`
+			// makes the latter nonnegative.
+			matchedCount += i;
+
+			// Apply set filters to unmatched elements
+			// NOTE: This can be skipped if there are no unmatched elements (i.e., `matchedCount`
+			// equals `i`), unless we didn't visit _any_ elements in the above loop because we have
+			// no element matchers and no seed.
+			// Incrementing an initially-string "0" `i` allows `i` to remain a string only in that
+			// case, which will result in a "00" `matchedCount` that differs from `i` but is also
+			// numerically zero.
+			if ( bySet && i !== matchedCount ) {
+				j = 0;
+				while ( ( matcher = setMatchers[ j++ ] ) ) {
+					matcher( unmatched, setMatched, context, xml );
+				}
+
+				if ( seed ) {
+
+					// Reintegrate element matches to eliminate the need for sorting
+					if ( matchedCount > 0 ) {
+						while ( i-- ) {
+							if ( !( unmatched[ i ] || setMatched[ i ] ) ) {
+								setMatched[ i ] = pop.call( results );
+							}
+						}
+					}
+
+					// Discard index placeholder values to get only actual matches
+					setMatched = condense( setMatched );
+				}
+
+				// Add matches to results
+				push.apply( results, setMatched );
+
+				// Seedless set matches succeeding multiple successful matchers stipulate sorting
+				if ( outermost && !seed && setMatched.length > 0 &&
+					( matchedCount + setMatchers.length ) > 1 ) {
+
+					Sizzle.uniqueSort( results );
+				}
+			}
+
+			// Override manipulation of globals by nested matchers
+			if ( outermost ) {
+				dirruns = dirrunsUnique;
+				outermostContext = contextBackup;
+			}
+
+			return unmatched;
+		};
+
+	return bySet ?
+		markFunction( superMatcher ) :
+		superMatcher;
+}
+
+compile = Sizzle.compile = function( selector, match /* Internal Use Only */ ) {
+	var i,
+		setMatchers = [],
+		elementMatchers = [],
+		cached = compilerCache[ selector + " " ];
+
+	if ( !cached ) {
+
+		// Generate a function of recursive functions that can be used to check each element
+		if ( !match ) {
+			match = tokenize( selector );
+		}
+		i = match.length;
+		while ( i-- ) {
+			cached = matcherFromTokens( match[ i ] );
+			if ( cached[ expando ] ) {
+				setMatchers.push( cached );
+			} else {
+				elementMatchers.push( cached );
+			}
+		}
+
+		// Cache the compiled function
+		cached = compilerCache(
+			selector,
+			matcherFromGroupMatchers( elementMatchers, setMatchers )
+		);
+
+		// Save selector and tokenization
+		cached.selector = selector;
+	}
+	return cached;
+};
+
+/**
+ * A low-level selection function that works with Sizzle's compiled
+ *  selector functions
+ * @param {String|Function} selector A selector or a pre-compiled
+ *  selector function built with Sizzle.compile
+ * @param {Element} context
+ * @param {Array} [results]
+ * @param {Array} [seed] A set of elements to match against
+ */
+select = Sizzle.select = function( selector, context, results, seed ) {
+	var i, tokens, token, type, find,
+		compiled = typeof selector === "function" && selector,
+		match = !seed && tokenize( ( selector = compiled.selector || selector ) );
+
+	results = results || [];
+
+	// Try to minimize operations if there is only one selector in the list and no seed
+	// (the latter of which guarantees us context)
+	if ( match.length === 1 ) {
+
+		// Reduce context if the leading compound selector is an ID
+		tokens = match[ 0 ] = match[ 0 ].slice( 0 );
+		if ( tokens.length > 2 && ( token = tokens[ 0 ] ).type === "ID" &&
+			context.nodeType === 9 && documentIsHTML && Expr.relative[ tokens[ 1 ].type ] ) {
+
+			context = ( Expr.find[ "ID" ]( token.matches[ 0 ]
+				.replace( runescape, funescape ), context ) || [] )[ 0 ];
+			if ( !context ) {
+				return results;
+
+			// Precompiled matchers will still verify ancestry, so step up a level
+			} else if ( compiled ) {
+				context = context.parentNode;
+			}
+
+			selector = selector.slice( tokens.shift().value.length );
+		}
+
+		// Fetch a seed set for right-to-left matching
+		i = matchExpr[ "needsContext" ].test( selector ) ? 0 : tokens.length;
+		while ( i-- ) {
+			token = tokens[ i ];
+
+			// Abort if we hit a combinator
+			if ( Expr.relative[ ( type = token.type ) ] ) {
+				break;
+			}
+			if ( ( find = Expr.find[ type ] ) ) {
+
+				// Search, expanding context for leading sibling combinators
+				if ( ( seed = find(
+					token.matches[ 0 ].replace( runescape, funescape ),
+					rsibling.test( tokens[ 0 ].type ) && testContext( context.parentNode ) ||
+						context
+				) ) ) {
+
+					// If seed is empty or no tokens remain, we can return early
+					tokens.splice( i, 1 );
+					selector = seed.length && toSelector( tokens );
+					if ( !selector ) {
+						push.apply( results, seed );
+						return results;
+					}
+
+					break;
+				}
+			}
+		}
+	}
+
+	// Compile and execute a filtering function if one is not provided
+	// Provide `match` to avoid retokenization if we modified the selector above
+	( compiled || compile( selector, match ) )(
+		seed,
+		context,
+		!documentIsHTML,
+		results,
+		!context || rsibling.test( selector ) && testContext( context.parentNode ) || context
+	);
+	return results;
+};
+
+// One-time assignments
+
+// Sort stability
+support.sortStable = expando.split( "" ).sort( sortOrder ).join( "" ) === expando;
+
+// Support: Chrome 14-35+
+// Always assume duplicates if they aren't passed to the comparison function
+support.detectDuplicates = !!hasDuplicate;
+
+// Initialize against the default document
+setDocument();
+
+// Support: Webkit<537.32 - Safari 6.0.3/Chrome 25 (fixed in Chrome 27)
+// Detached nodes confoundingly follow *each other*
+support.sortDetached = assert( function( el ) {
+
+	// Should return 1, but returns 4 (following)
+	return el.compareDocumentPosition( document.createElement( "fieldset" ) ) & 1;
+} );
+
+// Support: IE<8
+// Prevent attribute/property "interpolation"
+// https://msdn.microsoft.com/en-us/library/ms536429%28VS.85%29.aspx
+if ( !assert( function( el ) {
+	el.innerHTML = "";
+	return el.firstChild.getAttribute( "href" ) === "#";
+} ) ) {
+	addHandle( "type|href|height|width", function( elem, name, isXML ) {
+		if ( !isXML ) {
+			return elem.getAttribute( name, name.toLowerCase() === "type" ? 1 : 2 );
+		}
+	} );
+}
+
+// Support: IE<9
+// Use defaultValue in place of getAttribute("value")
+if ( !support.attributes || !assert( function( el ) {
+	el.innerHTML = "";
+	el.firstChild.setAttribute( "value", "" );
+	return el.firstChild.getAttribute( "value" ) === "";
+} ) ) {
+	addHandle( "value", function( elem, _name, isXML ) {
+		if ( !isXML && elem.nodeName.toLowerCase() === "input" ) {
+			return elem.defaultValue;
+		}
+	} );
+}
+
+// Support: IE<9
+// Use getAttributeNode to fetch booleans when getAttribute lies
+if ( !assert( function( el ) {
+	return el.getAttribute( "disabled" ) == null;
+} ) ) {
+	addHandle( booleans, function( elem, name, isXML ) {
+		var val;
+		if ( !isXML ) {
+			return elem[ name ] === true ? name.toLowerCase() :
+				( val = elem.getAttributeNode( name ) ) && val.specified ?
+					val.value :
+					null;
+		}
+	} );
+}
+
+return Sizzle;
+
+} )( window );
+
+
+
+jQuery.find = Sizzle;
+jQuery.expr = Sizzle.selectors;
+
+// Deprecated
+jQuery.expr[ ":" ] = jQuery.expr.pseudos;
+jQuery.uniqueSort = jQuery.unique = Sizzle.uniqueSort;
+jQuery.text = Sizzle.getText;
+jQuery.isXMLDoc = Sizzle.isXML;
+jQuery.contains = Sizzle.contains;
+jQuery.escapeSelector = Sizzle.escape;
+
+
+
+
+var dir = function( elem, dir, until ) {
+	var matched = [],
+		truncate = until !== undefined;
+
+	while ( ( elem = elem[ dir ] ) && elem.nodeType !== 9 ) {
+		if ( elem.nodeType === 1 ) {
+			if ( truncate && jQuery( elem ).is( until ) ) {
+				break;
+			}
+			matched.push( elem );
+		}
+	}
+	return matched;
+};
+
+
+var siblings = function( n, elem ) {
+	var matched = [];
+
+	for ( ; n; n = n.nextSibling ) {
+		if ( n.nodeType === 1 && n !== elem ) {
+			matched.push( n );
+		}
+	}
+
+	return matched;
+};
+
+
+var rneedsContext = jQuery.expr.match.needsContext;
+
+
+
+function nodeName( elem, name ) {
+
+	return elem.nodeName && elem.nodeName.toLowerCase() === name.toLowerCase();
+
+}
+var rsingleTag = ( /^<([a-z][^\/\0>:\x20\t\r\n\f]*)[\x20\t\r\n\f]*\/?>(?:<\/\1>|)$/i );
+
+
+
+// Implement the identical functionality for filter and not
+function winnow( elements, qualifier, not ) {
+	if ( isFunction( qualifier ) ) {
+		return jQuery.grep( elements, function( elem, i ) {
+			return !!qualifier.call( elem, i, elem ) !== not;
+		} );
+	}
+
+	// Single element
+	if ( qualifier.nodeType ) {
+		return jQuery.grep( elements, function( elem ) {
+			return ( elem === qualifier ) !== not;
+		} );
+	}
+
+	// Arraylike of elements (jQuery, arguments, Array)
+	if ( typeof qualifier !== "string" ) {
+		return jQuery.grep( elements, function( elem ) {
+			return ( indexOf.call( qualifier, elem ) > -1 ) !== not;
+		} );
+	}
+
+	// Filtered directly for both simple and complex selectors
+	return jQuery.filter( qualifier, elements, not );
+}
+
+jQuery.filter = function( expr, elems, not ) {
+	var elem = elems[ 0 ];
+
+	if ( not ) {
+		expr = ":not(" + expr + ")";
+	}
+
+	if ( elems.length === 1 && elem.nodeType === 1 ) {
+		return jQuery.find.matchesSelector( elem, expr ) ? [ elem ] : [];
+	}
+
+	return jQuery.find.matches( expr, jQuery.grep( elems, function( elem ) {
+		return elem.nodeType === 1;
+	} ) );
+};
+
+jQuery.fn.extend( {
+	find: function( selector ) {
+		var i, ret,
+			len = this.length,
+			self = this;
+
+		if ( typeof selector !== "string" ) {
+			return this.pushStack( jQuery( selector ).filter( function() {
+				for ( i = 0; i < len; i++ ) {
+					if ( jQuery.contains( self[ i ], this ) ) {
+						return true;
+					}
+				}
+			} ) );
+		}
+
+		ret = this.pushStack( [] );
+
+		for ( i = 0; i < len; i++ ) {
+			jQuery.find( selector, self[ i ], ret );
+		}
+
+		return len > 1 ? jQuery.uniqueSort( ret ) : ret;
+	},
+	filter: function( selector ) {
+		return this.pushStack( winnow( this, selector || [], false ) );
+	},
+	not: function( selector ) {
+		return this.pushStack( winnow( this, selector || [], true ) );
+	},
+	is: function( selector ) {
+		return !!winnow(
+			this,
+
+			// If this is a positional/relative selector, check membership in the returned set
+			// so $("p:first").is("p:last") won't return true for a doc with two "p".
+			typeof selector === "string" && rneedsContext.test( selector ) ?
+				jQuery( selector ) :
+				selector || [],
+			false
+		).length;
+	}
+} );
+
+
+// Initialize a jQuery object
+
+
+// A central reference to the root jQuery(document)
+var rootjQuery,
+
+	// A simple way to check for HTML strings
+	// Prioritize #id over  to avoid XSS via location.hash (#9521)
+	// Strict HTML recognition (#11290: must start with <)
+	// Shortcut simple #id case for speed
+	rquickExpr = /^(?:\s*(<[\w\W]+>)[^>]*|#([\w-]+))$/,
+
+	init = jQuery.fn.init = function( selector, context, root ) {
+		var match, elem;
+
+		// HANDLE: $(""), $(null), $(undefined), $(false)
+		if ( !selector ) {
+			return this;
+		}
+
+		// Method init() accepts an alternate rootjQuery
+		// so migrate can support jQuery.sub (gh-2101)
+		root = root || rootjQuery;
+
+		// Handle HTML strings
+		if ( typeof selector === "string" ) {
+			if ( selector[ 0 ] === "<" &&
+				selector[ selector.length - 1 ] === ">" &&
+				selector.length >= 3 ) {
+
+				// Assume that strings that start and end with <> are HTML and skip the regex check
+				match = [ null, selector, null ];
+
+			} else {
+				match = rquickExpr.exec( selector );
+			}
+
+			// Match html or make sure no context is specified for #id
+			if ( match && ( match[ 1 ] || !context ) ) {
+
+				// HANDLE: $(html) -> $(array)
+				if ( match[ 1 ] ) {
+					context = context instanceof jQuery ? context[ 0 ] : context;
+
+					// Option to run scripts is true for back-compat
+					// Intentionally let the error be thrown if parseHTML is not present
+					jQuery.merge( this, jQuery.parseHTML(
+						match[ 1 ],
+						context && context.nodeType ? context.ownerDocument || context : document,
+						true
+					) );
+
+					// HANDLE: $(html, props)
+					if ( rsingleTag.test( match[ 1 ] ) && jQuery.isPlainObject( context ) ) {
+						for ( match in context ) {
+
+							// Properties of context are called as methods if possible
+							if ( isFunction( this[ match ] ) ) {
+								this[ match ]( context[ match ] );
+
+							// ...and otherwise set as attributes
+							} else {
+								this.attr( match, context[ match ] );
+							}
+						}
+					}
+
+					return this;
+
+				// HANDLE: $(#id)
+				} else {
+					elem = document.getElementById( match[ 2 ] );
+
+					if ( elem ) {
+
+						// Inject the element directly into the jQuery object
+						this[ 0 ] = elem;
+						this.length = 1;
+					}
+					return this;
+				}
+
+			// HANDLE: $(expr, $(...))
+			} else if ( !context || context.jquery ) {
+				return ( context || root ).find( selector );
+
+			// HANDLE: $(expr, context)
+			// (which is just equivalent to: $(context).find(expr)
+			} else {
+				return this.constructor( context ).find( selector );
+			}
+
+		// HANDLE: $(DOMElement)
+		} else if ( selector.nodeType ) {
+			this[ 0 ] = selector;
+			this.length = 1;
+			return this;
+
+		// HANDLE: $(function)
+		// Shortcut for document ready
+		} else if ( isFunction( selector ) ) {
+			return root.ready !== undefined ?
+				root.ready( selector ) :
+
+				// Execute immediately if ready is not present
+				selector( jQuery );
+		}
+
+		return jQuery.makeArray( selector, this );
+	};
+
+// Give the init function the jQuery prototype for later instantiation
+init.prototype = jQuery.fn;
+
+// Initialize central reference
+rootjQuery = jQuery( document );
+
+
+var rparentsprev = /^(?:parents|prev(?:Until|All))/,
+
+	// Methods guaranteed to produce a unique set when starting from a unique set
+	guaranteedUnique = {
+		children: true,
+		contents: true,
+		next: true,
+		prev: true
+	};
+
+jQuery.fn.extend( {
+	has: function( target ) {
+		var targets = jQuery( target, this ),
+			l = targets.length;
+
+		return this.filter( function() {
+			var i = 0;
+			for ( ; i < l; i++ ) {
+				if ( jQuery.contains( this, targets[ i ] ) ) {
+					return true;
+				}
+			}
+		} );
+	},
+
+	closest: function( selectors, context ) {
+		var cur,
+			i = 0,
+			l = this.length,
+			matched = [],
+			targets = typeof selectors !== "string" && jQuery( selectors );
+
+		// Positional selectors never match, since there's no _selection_ context
+		if ( !rneedsContext.test( selectors ) ) {
+			for ( ; i < l; i++ ) {
+				for ( cur = this[ i ]; cur && cur !== context; cur = cur.parentNode ) {
+
+					// Always skip document fragments
+					if ( cur.nodeType < 11 && ( targets ?
+						targets.index( cur ) > -1 :
+
+						// Don't pass non-elements to Sizzle
+						cur.nodeType === 1 &&
+							jQuery.find.matchesSelector( cur, selectors ) ) ) {
+
+						matched.push( cur );
+						break;
+					}
+				}
+			}
+		}
+
+		return this.pushStack( matched.length > 1 ? jQuery.uniqueSort( matched ) : matched );
+	},
+
+	// Determine the position of an element within the set
+	index: function( elem ) {
+
+		// No argument, return index in parent
+		if ( !elem ) {
+			return ( this[ 0 ] && this[ 0 ].parentNode ) ? this.first().prevAll().length : -1;
+		}
+
+		// Index in selector
+		if ( typeof elem === "string" ) {
+			return indexOf.call( jQuery( elem ), this[ 0 ] );
+		}
+
+		// Locate the position of the desired element
+		return indexOf.call( this,
+
+			// If it receives a jQuery object, the first element is used
+			elem.jquery ? elem[ 0 ] : elem
+		);
+	},
+
+	add: function( selector, context ) {
+		return this.pushStack(
+			jQuery.uniqueSort(
+				jQuery.merge( this.get(), jQuery( selector, context ) )
+			)
+		);
+	},
+
+	addBack: function( selector ) {
+		return this.add( selector == null ?
+			this.prevObject : this.prevObject.filter( selector )
+		);
+	}
+} );
+
+function sibling( cur, dir ) {
+	while ( ( cur = cur[ dir ] ) && cur.nodeType !== 1 ) {}
+	return cur;
+}
+
+jQuery.each( {
+	parent: function( elem ) {
+		var parent = elem.parentNode;
+		return parent && parent.nodeType !== 11 ? parent : null;
+	},
+	parents: function( elem ) {
+		return dir( elem, "parentNode" );
+	},
+	parentsUntil: function( elem, _i, until ) {
+		return dir( elem, "parentNode", until );
+	},
+	next: function( elem ) {
+		return sibling( elem, "nextSibling" );
+	},
+	prev: function( elem ) {
+		return sibling( elem, "previousSibling" );
+	},
+	nextAll: function( elem ) {
+		return dir( elem, "nextSibling" );
+	},
+	prevAll: function( elem ) {
+		return dir( elem, "previousSibling" );
+	},
+	nextUntil: function( elem, _i, until ) {
+		return dir( elem, "nextSibling", until );
+	},
+	prevUntil: function( elem, _i, until ) {
+		return dir( elem, "previousSibling", until );
+	},
+	siblings: function( elem ) {
+		return siblings( ( elem.parentNode || {} ).firstChild, elem );
+	},
+	children: function( elem ) {
+		return siblings( elem.firstChild );
+	},
+	contents: function( elem ) {
+		if ( elem.contentDocument != null &&
+
+			// Support: IE 11+
+			//  elements with no `data` attribute has an object
+			// `contentDocument` with a `null` prototype.
+			getProto( elem.contentDocument ) ) {
+
+			return elem.contentDocument;
+		}
+
+		// Support: IE 9 - 11 only, iOS 7 only, Android Browser <=4.3 only
+		// Treat the template element as a regular one in browsers that
+		// don't support it.
+		if ( nodeName( elem, "template" ) ) {
+			elem = elem.content || elem;
+		}
+
+		return jQuery.merge( [], elem.childNodes );
+	}
+}, function( name, fn ) {
+	jQuery.fn[ name ] = function( until, selector ) {
+		var matched = jQuery.map( this, fn, until );
+
+		if ( name.slice( -5 ) !== "Until" ) {
+			selector = until;
+		}
+
+		if ( selector && typeof selector === "string" ) {
+			matched = jQuery.filter( selector, matched );
+		}
+
+		if ( this.length > 1 ) {
+
+			// Remove duplicates
+			if ( !guaranteedUnique[ name ] ) {
+				jQuery.uniqueSort( matched );
+			}
+
+			// Reverse order for parents* and prev-derivatives
+			if ( rparentsprev.test( name ) ) {
+				matched.reverse();
+			}
+		}
+
+		return this.pushStack( matched );
+	};
+} );
+var rnothtmlwhite = ( /[^\x20\t\r\n\f]+/g );
+
+
+
+// Convert String-formatted options into Object-formatted ones
+function createOptions( options ) {
+	var object = {};
+	jQuery.each( options.match( rnothtmlwhite ) || [], function( _, flag ) {
+		object[ flag ] = true;
+	} );
+	return object;
+}
+
+/*
+ * Create a callback list using the following parameters:
+ *
+ *	options: an optional list of space-separated options that will change how
+ *			the callback list behaves or a more traditional option object
+ *
+ * By default a callback list will act like an event callback list and can be
+ * "fired" multiple times.
+ *
+ * Possible options:
+ *
+ *	once:			will ensure the callback list can only be fired once (like a Deferred)
+ *
+ *	memory:			will keep track of previous values and will call any callback added
+ *					after the list has been fired right away with the latest "memorized"
+ *					values (like a Deferred)
+ *
+ *	unique:			will ensure a callback can only be added once (no duplicate in the list)
+ *
+ *	stopOnFalse:	interrupt callings when a callback returns false
+ *
+ */
+jQuery.Callbacks = function( options ) {
+
+	// Convert options from String-formatted to Object-formatted if needed
+	// (we check in cache first)
+	options = typeof options === "string" ?
+		createOptions( options ) :
+		jQuery.extend( {}, options );
+
+	var // Flag to know if list is currently firing
+		firing,
+
+		// Last fire value for non-forgettable lists
+		memory,
+
+		// Flag to know if list was already fired
+		fired,
+
+		// Flag to prevent firing
+		locked,
+
+		// Actual callback list
+		list = [],
+
+		// Queue of execution data for repeatable lists
+		queue = [],
+
+		// Index of currently firing callback (modified by add/remove as needed)
+		firingIndex = -1,
+
+		// Fire callbacks
+		fire = function() {
+
+			// Enforce single-firing
+			locked = locked || options.once;
+
+			// Execute callbacks for all pending executions,
+			// respecting firingIndex overrides and runtime changes
+			fired = firing = true;
+			for ( ; queue.length; firingIndex = -1 ) {
+				memory = queue.shift();
+				while ( ++firingIndex < list.length ) {
+
+					// Run callback and check for early termination
+					if ( list[ firingIndex ].apply( memory[ 0 ], memory[ 1 ] ) === false &&
+						options.stopOnFalse ) {
+
+						// Jump to end and forget the data so .add doesn't re-fire
+						firingIndex = list.length;
+						memory = false;
+					}
+				}
+			}
+
+			// Forget the data if we're done with it
+			if ( !options.memory ) {
+				memory = false;
+			}
+
+			firing = false;
+
+			// Clean up if we're done firing for good
+			if ( locked ) {
+
+				// Keep an empty list if we have data for future add calls
+				if ( memory ) {
+					list = [];
+
+				// Otherwise, this object is spent
+				} else {
+					list = "";
+				}
+			}
+		},
+
+		// Actual Callbacks object
+		self = {
+
+			// Add a callback or a collection of callbacks to the list
+			add: function() {
+				if ( list ) {
+
+					// If we have memory from a past run, we should fire after adding
+					if ( memory && !firing ) {
+						firingIndex = list.length - 1;
+						queue.push( memory );
+					}
+
+					( function add( args ) {
+						jQuery.each( args, function( _, arg ) {
+							if ( isFunction( arg ) ) {
+								if ( !options.unique || !self.has( arg ) ) {
+									list.push( arg );
+								}
+							} else if ( arg && arg.length && toType( arg ) !== "string" ) {
+
+								// Inspect recursively
+								add( arg );
+							}
+						} );
+					} )( arguments );
+
+					if ( memory && !firing ) {
+						fire();
+					}
+				}
+				return this;
+			},
+
+			// Remove a callback from the list
+			remove: function() {
+				jQuery.each( arguments, function( _, arg ) {
+					var index;
+					while ( ( index = jQuery.inArray( arg, list, index ) ) > -1 ) {
+						list.splice( index, 1 );
+
+						// Handle firing indexes
+						if ( index <= firingIndex ) {
+							firingIndex--;
+						}
+					}
+				} );
+				return this;
+			},
+
+			// Check if a given callback is in the list.
+			// If no argument is given, return whether or not list has callbacks attached.
+			has: function( fn ) {
+				return fn ?
+					jQuery.inArray( fn, list ) > -1 :
+					list.length > 0;
+			},
+
+			// Remove all callbacks from the list
+			empty: function() {
+				if ( list ) {
+					list = [];
+				}
+				return this;
+			},
+
+			// Disable .fire and .add
+			// Abort any current/pending executions
+			// Clear all callbacks and values
+			disable: function() {
+				locked = queue = [];
+				list = memory = "";
+				return this;
+			},
+			disabled: function() {
+				return !list;
+			},
+
+			// Disable .fire
+			// Also disable .add unless we have memory (since it would have no effect)
+			// Abort any pending executions
+			lock: function() {
+				locked = queue = [];
+				if ( !memory && !firing ) {
+					list = memory = "";
+				}
+				return this;
+			},
+			locked: function() {
+				return !!locked;
+			},
+
+			// Call all callbacks with the given context and arguments
+			fireWith: function( context, args ) {
+				if ( !locked ) {
+					args = args || [];
+					args = [ context, args.slice ? args.slice() : args ];
+					queue.push( args );
+					if ( !firing ) {
+						fire();
+					}
+				}
+				return this;
+			},
+
+			// Call all the callbacks with the given arguments
+			fire: function() {
+				self.fireWith( this, arguments );
+				return this;
+			},
+
+			// To know if the callbacks have already been called at least once
+			fired: function() {
+				return !!fired;
+			}
+		};
+
+	return self;
+};
+
+
+function Identity( v ) {
+	return v;
+}
+function Thrower( ex ) {
+	throw ex;
+}
+
+function adoptValue( value, resolve, reject, noValue ) {
+	var method;
+
+	try {
+
+		// Check for promise aspect first to privilege synchronous behavior
+		if ( value && isFunction( ( method = value.promise ) ) ) {
+			method.call( value ).done( resolve ).fail( reject );
+
+		// Other thenables
+		} else if ( value && isFunction( ( method = value.then ) ) ) {
+			method.call( value, resolve, reject );
+
+		// Other non-thenables
+		} else {
+
+			// Control `resolve` arguments by letting Array#slice cast boolean `noValue` to integer:
+			// * false: [ value ].slice( 0 ) => resolve( value )
+			// * true: [ value ].slice( 1 ) => resolve()
+			resolve.apply( undefined, [ value ].slice( noValue ) );
+		}
+
+	// For Promises/A+, convert exceptions into rejections
+	// Since jQuery.when doesn't unwrap thenables, we can skip the extra checks appearing in
+	// Deferred#then to conditionally suppress rejection.
+	} catch ( value ) {
+
+		// Support: Android 4.0 only
+		// Strict mode functions invoked without .call/.apply get global-object context
+		reject.apply( undefined, [ value ] );
+	}
+}
+
+jQuery.extend( {
+
+	Deferred: function( func ) {
+		var tuples = [
+
+				// action, add listener, callbacks,
+				// ... .then handlers, argument index, [final state]
+				[ "notify", "progress", jQuery.Callbacks( "memory" ),
+					jQuery.Callbacks( "memory" ), 2 ],
+				[ "resolve", "done", jQuery.Callbacks( "once memory" ),
+					jQuery.Callbacks( "once memory" ), 0, "resolved" ],
+				[ "reject", "fail", jQuery.Callbacks( "once memory" ),
+					jQuery.Callbacks( "once memory" ), 1, "rejected" ]
+			],
+			state = "pending",
+			promise = {
+				state: function() {
+					return state;
+				},
+				always: function() {
+					deferred.done( arguments ).fail( arguments );
+					return this;
+				},
+				"catch": function( fn ) {
+					return promise.then( null, fn );
+				},
+
+				// Keep pipe for back-compat
+				pipe: function( /* fnDone, fnFail, fnProgress */ ) {
+					var fns = arguments;
+
+					return jQuery.Deferred( function( newDefer ) {
+						jQuery.each( tuples, function( _i, tuple ) {
+
+							// Map tuples (progress, done, fail) to arguments (done, fail, progress)
+							var fn = isFunction( fns[ tuple[ 4 ] ] ) && fns[ tuple[ 4 ] ];
+
+							// deferred.progress(function() { bind to newDefer or newDefer.notify })
+							// deferred.done(function() { bind to newDefer or newDefer.resolve })
+							// deferred.fail(function() { bind to newDefer or newDefer.reject })
+							deferred[ tuple[ 1 ] ]( function() {
+								var returned = fn && fn.apply( this, arguments );
+								if ( returned && isFunction( returned.promise ) ) {
+									returned.promise()
+										.progress( newDefer.notify )
+										.done( newDefer.resolve )
+										.fail( newDefer.reject );
+								} else {
+									newDefer[ tuple[ 0 ] + "With" ](
+										this,
+										fn ? [ returned ] : arguments
+									);
+								}
+							} );
+						} );
+						fns = null;
+					} ).promise();
+				},
+				then: function( onFulfilled, onRejected, onProgress ) {
+					var maxDepth = 0;
+					function resolve( depth, deferred, handler, special ) {
+						return function() {
+							var that = this,
+								args = arguments,
+								mightThrow = function() {
+									var returned, then;
+
+									// Support: Promises/A+ section 2.3.3.3.3
+									// https://promisesaplus.com/#point-59
+									// Ignore double-resolution attempts
+									if ( depth < maxDepth ) {
+										return;
+									}
+
+									returned = handler.apply( that, args );
+
+									// Support: Promises/A+ section 2.3.1
+									// https://promisesaplus.com/#point-48
+									if ( returned === deferred.promise() ) {
+										throw new TypeError( "Thenable self-resolution" );
+									}
+
+									// Support: Promises/A+ sections 2.3.3.1, 3.5
+									// https://promisesaplus.com/#point-54
+									// https://promisesaplus.com/#point-75
+									// Retrieve `then` only once
+									then = returned &&
+
+										// Support: Promises/A+ section 2.3.4
+										// https://promisesaplus.com/#point-64
+										// Only check objects and functions for thenability
+										( typeof returned === "object" ||
+											typeof returned === "function" ) &&
+										returned.then;
+
+									// Handle a returned thenable
+									if ( isFunction( then ) ) {
+
+										// Special processors (notify) just wait for resolution
+										if ( special ) {
+											then.call(
+												returned,
+												resolve( maxDepth, deferred, Identity, special ),
+												resolve( maxDepth, deferred, Thrower, special )
+											);
+
+										// Normal processors (resolve) also hook into progress
+										} else {
+
+											// ...and disregard older resolution values
+											maxDepth++;
+
+											then.call(
+												returned,
+												resolve( maxDepth, deferred, Identity, special ),
+												resolve( maxDepth, deferred, Thrower, special ),
+												resolve( maxDepth, deferred, Identity,
+													deferred.notifyWith )
+											);
+										}
+
+									// Handle all other returned values
+									} else {
+
+										// Only substitute handlers pass on context
+										// and multiple values (non-spec behavior)
+										if ( handler !== Identity ) {
+											that = undefined;
+											args = [ returned ];
+										}
+
+										// Process the value(s)
+										// Default process is resolve
+										( special || deferred.resolveWith )( that, args );
+									}
+								},
+
+								// Only normal processors (resolve) catch and reject exceptions
+								process = special ?
+									mightThrow :
+									function() {
+										try {
+											mightThrow();
+										} catch ( e ) {
+
+											if ( jQuery.Deferred.exceptionHook ) {
+												jQuery.Deferred.exceptionHook( e,
+													process.stackTrace );
+											}
+
+											// Support: Promises/A+ section 2.3.3.3.4.1
+											// https://promisesaplus.com/#point-61
+											// Ignore post-resolution exceptions
+											if ( depth + 1 >= maxDepth ) {
+
+												// Only substitute handlers pass on context
+												// and multiple values (non-spec behavior)
+												if ( handler !== Thrower ) {
+													that = undefined;
+													args = [ e ];
+												}
+
+												deferred.rejectWith( that, args );
+											}
+										}
+									};
+
+							// Support: Promises/A+ section 2.3.3.3.1
+							// https://promisesaplus.com/#point-57
+							// Re-resolve promises immediately to dodge false rejection from
+							// subsequent errors
+							if ( depth ) {
+								process();
+							} else {
+
+								// Call an optional hook to record the stack, in case of exception
+								// since it's otherwise lost when execution goes async
+								if ( jQuery.Deferred.getStackHook ) {
+									process.stackTrace = jQuery.Deferred.getStackHook();
+								}
+								window.setTimeout( process );
+							}
+						};
+					}
+
+					return jQuery.Deferred( function( newDefer ) {
+
+						// progress_handlers.add( ... )
+						tuples[ 0 ][ 3 ].add(
+							resolve(
+								0,
+								newDefer,
+								isFunction( onProgress ) ?
+									onProgress :
+									Identity,
+								newDefer.notifyWith
+							)
+						);
+
+						// fulfilled_handlers.add( ... )
+						tuples[ 1 ][ 3 ].add(
+							resolve(
+								0,
+								newDefer,
+								isFunction( onFulfilled ) ?
+									onFulfilled :
+									Identity
+							)
+						);
+
+						// rejected_handlers.add( ... )
+						tuples[ 2 ][ 3 ].add(
+							resolve(
+								0,
+								newDefer,
+								isFunction( onRejected ) ?
+									onRejected :
+									Thrower
+							)
+						);
+					} ).promise();
+				},
+
+				// Get a promise for this deferred
+				// If obj is provided, the promise aspect is added to the object
+				promise: function( obj ) {
+					return obj != null ? jQuery.extend( obj, promise ) : promise;
+				}
+			},
+			deferred = {};
+
+		// Add list-specific methods
+		jQuery.each( tuples, function( i, tuple ) {
+			var list = tuple[ 2 ],
+				stateString = tuple[ 5 ];
+
+			// promise.progress = list.add
+			// promise.done = list.add
+			// promise.fail = list.add
+			promise[ tuple[ 1 ] ] = list.add;
+
+			// Handle state
+			if ( stateString ) {
+				list.add(
+					function() {
+
+						// state = "resolved" (i.e., fulfilled)
+						// state = "rejected"
+						state = stateString;
+					},
+
+					// rejected_callbacks.disable
+					// fulfilled_callbacks.disable
+					tuples[ 3 - i ][ 2 ].disable,
+
+					// rejected_handlers.disable
+					// fulfilled_handlers.disable
+					tuples[ 3 - i ][ 3 ].disable,
+
+					// progress_callbacks.lock
+					tuples[ 0 ][ 2 ].lock,
+
+					// progress_handlers.lock
+					tuples[ 0 ][ 3 ].lock
+				);
+			}
+
+			// progress_handlers.fire
+			// fulfilled_handlers.fire
+			// rejected_handlers.fire
+			list.add( tuple[ 3 ].fire );
+
+			// deferred.notify = function() { deferred.notifyWith(...) }
+			// deferred.resolve = function() { deferred.resolveWith(...) }
+			// deferred.reject = function() { deferred.rejectWith(...) }
+			deferred[ tuple[ 0 ] ] = function() {
+				deferred[ tuple[ 0 ] + "With" ]( this === deferred ? undefined : this, arguments );
+				return this;
+			};
+
+			// deferred.notifyWith = list.fireWith
+			// deferred.resolveWith = list.fireWith
+			// deferred.rejectWith = list.fireWith
+			deferred[ tuple[ 0 ] + "With" ] = list.fireWith;
+		} );
+
+		// Make the deferred a promise
+		promise.promise( deferred );
+
+		// Call given func if any
+		if ( func ) {
+			func.call( deferred, deferred );
+		}
+
+		// All done!
+		return deferred;
+	},
+
+	// Deferred helper
+	when: function( singleValue ) {
+		var
+
+			// count of uncompleted subordinates
+			remaining = arguments.length,
+
+			// count of unprocessed arguments
+			i = remaining,
+
+			// subordinate fulfillment data
+			resolveContexts = Array( i ),
+			resolveValues = slice.call( arguments ),
+
+			// the primary Deferred
+			primary = jQuery.Deferred(),
+
+			// subordinate callback factory
+			updateFunc = function( i ) {
+				return function( value ) {
+					resolveContexts[ i ] = this;
+					resolveValues[ i ] = arguments.length > 1 ? slice.call( arguments ) : value;
+					if ( !( --remaining ) ) {
+						primary.resolveWith( resolveContexts, resolveValues );
+					}
+				};
+			};
+
+		// Single- and empty arguments are adopted like Promise.resolve
+		if ( remaining <= 1 ) {
+			adoptValue( singleValue, primary.done( updateFunc( i ) ).resolve, primary.reject,
+				!remaining );
+
+			// Use .then() to unwrap secondary thenables (cf. gh-3000)
+			if ( primary.state() === "pending" ||
+				isFunction( resolveValues[ i ] && resolveValues[ i ].then ) ) {
+
+				return primary.then();
+			}
+		}
+
+		// Multiple arguments are aggregated like Promise.all array elements
+		while ( i-- ) {
+			adoptValue( resolveValues[ i ], updateFunc( i ), primary.reject );
+		}
+
+		return primary.promise();
+	}
+} );
+
+
+// These usually indicate a programmer mistake during development,
+// warn about them ASAP rather than swallowing them by default.
+var rerrorNames = /^(Eval|Internal|Range|Reference|Syntax|Type|URI)Error$/;
+
+jQuery.Deferred.exceptionHook = function( error, stack ) {
+
+	// Support: IE 8 - 9 only
+	// Console exists when dev tools are open, which can happen at any time
+	if ( window.console && window.console.warn && error && rerrorNames.test( error.name ) ) {
+		window.console.warn( "jQuery.Deferred exception: " + error.message, error.stack, stack );
+	}
+};
+
+
+
+
+jQuery.readyException = function( error ) {
+	window.setTimeout( function() {
+		throw error;
+	} );
+};
+
+
+
+
+// The deferred used on DOM ready
+var readyList = jQuery.Deferred();
+
+jQuery.fn.ready = function( fn ) {
+
+	readyList
+		.then( fn )
+
+		// Wrap jQuery.readyException in a function so that the lookup
+		// happens at the time of error handling instead of callback
+		// registration.
+		.catch( function( error ) {
+			jQuery.readyException( error );
+		} );
+
+	return this;
+};
+
+jQuery.extend( {
+
+	// Is the DOM ready to be used? Set to true once it occurs.
+	isReady: false,
+
+	// A counter to track how many items to wait for before
+	// the ready event fires. See #6781
+	readyWait: 1,
+
+	// Handle when the DOM is ready
+	ready: function( wait ) {
+
+		// Abort if there are pending holds or we're already ready
+		if ( wait === true ? --jQuery.readyWait : jQuery.isReady ) {
+			return;
+		}
+
+		// Remember that the DOM is ready
+		jQuery.isReady = true;
+
+		// If a normal DOM Ready event fired, decrement, and wait if need be
+		if ( wait !== true && --jQuery.readyWait > 0 ) {
+			return;
+		}
+
+		// If there are functions bound, to execute
+		readyList.resolveWith( document, [ jQuery ] );
+	}
+} );
+
+jQuery.ready.then = readyList.then;
+
+// The ready event handler and self cleanup method
+function completed() {
+	document.removeEventListener( "DOMContentLoaded", completed );
+	window.removeEventListener( "load", completed );
+	jQuery.ready();
+}
+
+// Catch cases where $(document).ready() is called
+// after the browser event has already occurred.
+// Support: IE <=9 - 10 only
+// Older IE sometimes signals "interactive" too soon
+if ( document.readyState === "complete" ||
+	( document.readyState !== "loading" && !document.documentElement.doScroll ) ) {
+
+	// Handle it asynchronously to allow scripts the opportunity to delay ready
+	window.setTimeout( jQuery.ready );
+
+} else {
+
+	// Use the handy event callback
+	document.addEventListener( "DOMContentLoaded", completed );
+
+	// A fallback to window.onload, that will always work
+	window.addEventListener( "load", completed );
+}
+
+
+
+
+// Multifunctional method to get and set values of a collection
+// The value/s can optionally be executed if it's a function
+var access = function( elems, fn, key, value, chainable, emptyGet, raw ) {
+	var i = 0,
+		len = elems.length,
+		bulk = key == null;
+
+	// Sets many values
+	if ( toType( key ) === "object" ) {
+		chainable = true;
+		for ( i in key ) {
+			access( elems, fn, i, key[ i ], true, emptyGet, raw );
+		}
+
+	// Sets one value
+	} else if ( value !== undefined ) {
+		chainable = true;
+
+		if ( !isFunction( value ) ) {
+			raw = true;
+		}
+
+		if ( bulk ) {
+
+			// Bulk operations run against the entire set
+			if ( raw ) {
+				fn.call( elems, value );
+				fn = null;
+
+			// ...except when executing function values
+			} else {
+				bulk = fn;
+				fn = function( elem, _key, value ) {
+					return bulk.call( jQuery( elem ), value );
+				};
+			}
+		}
+
+		if ( fn ) {
+			for ( ; i < len; i++ ) {
+				fn(
+					elems[ i ], key, raw ?
+						value :
+						value.call( elems[ i ], i, fn( elems[ i ], key ) )
+				);
+			}
+		}
+	}
+
+	if ( chainable ) {
+		return elems;
+	}
+
+	// Gets
+	if ( bulk ) {
+		return fn.call( elems );
+	}
+
+	return len ? fn( elems[ 0 ], key ) : emptyGet;
+};
+
+
+// Matches dashed string for camelizing
+var rmsPrefix = /^-ms-/,
+	rdashAlpha = /-([a-z])/g;
+
+// Used by camelCase as callback to replace()
+function fcamelCase( _all, letter ) {
+	return letter.toUpperCase();
+}
+
+// Convert dashed to camelCase; used by the css and data modules
+// Support: IE <=9 - 11, Edge 12 - 15
+// Microsoft forgot to hump their vendor prefix (#9572)
+function camelCase( string ) {
+	return string.replace( rmsPrefix, "ms-" ).replace( rdashAlpha, fcamelCase );
+}
+var acceptData = function( owner ) {
+
+	// Accepts only:
+	//  - Node
+	//    - Node.ELEMENT_NODE
+	//    - Node.DOCUMENT_NODE
+	//  - Object
+	//    - Any
+	return owner.nodeType === 1 || owner.nodeType === 9 || !( +owner.nodeType );
+};
+
+
+
+
+function Data() {
+	this.expando = jQuery.expando + Data.uid++;
+}
+
+Data.uid = 1;
+
+Data.prototype = {
+
+	cache: function( owner ) {
+
+		// Check if the owner object already has a cache
+		var value = owner[ this.expando ];
+
+		// If not, create one
+		if ( !value ) {
+			value = {};
+
+			// We can accept data for non-element nodes in modern browsers,
+			// but we should not, see #8335.
+			// Always return an empty object.
+			if ( acceptData( owner ) ) {
+
+				// If it is a node unlikely to be stringify-ed or looped over
+				// use plain assignment
+				if ( owner.nodeType ) {
+					owner[ this.expando ] = value;
+
+				// Otherwise secure it in a non-enumerable property
+				// configurable must be true to allow the property to be
+				// deleted when data is removed
+				} else {
+					Object.defineProperty( owner, this.expando, {
+						value: value,
+						configurable: true
+					} );
+				}
+			}
+		}
+
+		return value;
+	},
+	set: function( owner, data, value ) {
+		var prop,
+			cache = this.cache( owner );
+
+		// Handle: [ owner, key, value ] args
+		// Always use camelCase key (gh-2257)
+		if ( typeof data === "string" ) {
+			cache[ camelCase( data ) ] = value;
+
+		// Handle: [ owner, { properties } ] args
+		} else {
+
+			// Copy the properties one-by-one to the cache object
+			for ( prop in data ) {
+				cache[ camelCase( prop ) ] = data[ prop ];
+			}
+		}
+		return cache;
+	},
+	get: function( owner, key ) {
+		return key === undefined ?
+			this.cache( owner ) :
+
+			// Always use camelCase key (gh-2257)
+			owner[ this.expando ] && owner[ this.expando ][ camelCase( key ) ];
+	},
+	access: function( owner, key, value ) {
+
+		// In cases where either:
+		//
+		//   1. No key was specified
+		//   2. A string key was specified, but no value provided
+		//
+		// Take the "read" path and allow the get method to determine
+		// which value to return, respectively either:
+		//
+		//   1. The entire cache object
+		//   2. The data stored at the key
+		//
+		if ( key === undefined ||
+				( ( key && typeof key === "string" ) && value === undefined ) ) {
+
+			return this.get( owner, key );
+		}
+
+		// When the key is not a string, or both a key and value
+		// are specified, set or extend (existing objects) with either:
+		//
+		//   1. An object of properties
+		//   2. A key and value
+		//
+		this.set( owner, key, value );
+
+		// Since the "set" path can have two possible entry points
+		// return the expected data based on which path was taken[*]
+		return value !== undefined ? value : key;
+	},
+	remove: function( owner, key ) {
+		var i,
+			cache = owner[ this.expando ];
+
+		if ( cache === undefined ) {
+			return;
+		}
+
+		if ( key !== undefined ) {
+
+			// Support array or space separated string of keys
+			if ( Array.isArray( key ) ) {
+
+				// If key is an array of keys...
+				// We always set camelCase keys, so remove that.
+				key = key.map( camelCase );
+			} else {
+				key = camelCase( key );
+
+				// If a key with the spaces exists, use it.
+				// Otherwise, create an array by matching non-whitespace
+				key = key in cache ?
+					[ key ] :
+					( key.match( rnothtmlwhite ) || [] );
+			}
+
+			i = key.length;
+
+			while ( i-- ) {
+				delete cache[ key[ i ] ];
+			}
+		}
+
+		// Remove the expando if there's no more data
+		if ( key === undefined || jQuery.isEmptyObject( cache ) ) {
+
+			// Support: Chrome <=35 - 45
+			// Webkit & Blink performance suffers when deleting properties
+			// from DOM nodes, so set to undefined instead
+			// https://bugs.chromium.org/p/chromium/issues/detail?id=378607 (bug restricted)
+			if ( owner.nodeType ) {
+				owner[ this.expando ] = undefined;
+			} else {
+				delete owner[ this.expando ];
+			}
+		}
+	},
+	hasData: function( owner ) {
+		var cache = owner[ this.expando ];
+		return cache !== undefined && !jQuery.isEmptyObject( cache );
+	}
+};
+var dataPriv = new Data();
+
+var dataUser = new Data();
+
+
+
+//	Implementation Summary
+//
+//	1. Enforce API surface and semantic compatibility with 1.9.x branch
+//	2. Improve the module's maintainability by reducing the storage
+//		paths to a single mechanism.
+//	3. Use the same single mechanism to support "private" and "user" data.
+//	4. _Never_ expose "private" data to user code (TODO: Drop _data, _removeData)
+//	5. Avoid exposing implementation details on user objects (eg. expando properties)
+//	6. Provide a clear path for implementation upgrade to WeakMap in 2014
+
+var rbrace = /^(?:\{[\w\W]*\}|\[[\w\W]*\])$/,
+	rmultiDash = /[A-Z]/g;
+
+function getData( data ) {
+	if ( data === "true" ) {
+		return true;
+	}
+
+	if ( data === "false" ) {
+		return false;
+	}
+
+	if ( data === "null" ) {
+		return null;
+	}
+
+	// Only convert to a number if it doesn't change the string
+	if ( data === +data + "" ) {
+		return +data;
+	}
+
+	if ( rbrace.test( data ) ) {
+		return JSON.parse( data );
+	}
+
+	return data;
+}
+
+function dataAttr( elem, key, data ) {
+	var name;
+
+	// If nothing was found internally, try to fetch any
+	// data from the HTML5 data-* attribute
+	if ( data === undefined && elem.nodeType === 1 ) {
+		name = "data-" + key.replace( rmultiDash, "-$&" ).toLowerCase();
+		data = elem.getAttribute( name );
+
+		if ( typeof data === "string" ) {
+			try {
+				data = getData( data );
+			} catch ( e ) {}
+
+			// Make sure we set the data so it isn't changed later
+			dataUser.set( elem, key, data );
+		} else {
+			data = undefined;
+		}
+	}
+	return data;
+}
+
+jQuery.extend( {
+	hasData: function( elem ) {
+		return dataUser.hasData( elem ) || dataPriv.hasData( elem );
+	},
+
+	data: function( elem, name, data ) {
+		return dataUser.access( elem, name, data );
+	},
+
+	removeData: function( elem, name ) {
+		dataUser.remove( elem, name );
+	},
+
+	// TODO: Now that all calls to _data and _removeData have been replaced
+	// with direct calls to dataPriv methods, these can be deprecated.
+	_data: function( elem, name, data ) {
+		return dataPriv.access( elem, name, data );
+	},
+
+	_removeData: function( elem, name ) {
+		dataPriv.remove( elem, name );
+	}
+} );
+
+jQuery.fn.extend( {
+	data: function( key, value ) {
+		var i, name, data,
+			elem = this[ 0 ],
+			attrs = elem && elem.attributes;
+
+		// Gets all values
+		if ( key === undefined ) {
+			if ( this.length ) {
+				data = dataUser.get( elem );
+
+				if ( elem.nodeType === 1 && !dataPriv.get( elem, "hasDataAttrs" ) ) {
+					i = attrs.length;
+					while ( i-- ) {
+
+						// Support: IE 11 only
+						// The attrs elements can be null (#14894)
+						if ( attrs[ i ] ) {
+							name = attrs[ i ].name;
+							if ( name.indexOf( "data-" ) === 0 ) {
+								name = camelCase( name.slice( 5 ) );
+								dataAttr( elem, name, data[ name ] );
+							}
+						}
+					}
+					dataPriv.set( elem, "hasDataAttrs", true );
+				}
+			}
+
+			return data;
+		}
+
+		// Sets multiple values
+		if ( typeof key === "object" ) {
+			return this.each( function() {
+				dataUser.set( this, key );
+			} );
+		}
+
+		return access( this, function( value ) {
+			var data;
+
+			// The calling jQuery object (element matches) is not empty
+			// (and therefore has an element appears at this[ 0 ]) and the
+			// `value` parameter was not undefined. An empty jQuery object
+			// will result in `undefined` for elem = this[ 0 ] which will
+			// throw an exception if an attempt to read a data cache is made.
+			if ( elem && value === undefined ) {
+
+				// Attempt to get data from the cache
+				// The key will always be camelCased in Data
+				data = dataUser.get( elem, key );
+				if ( data !== undefined ) {
+					return data;
+				}
+
+				// Attempt to "discover" the data in
+				// HTML5 custom data-* attrs
+				data = dataAttr( elem, key );
+				if ( data !== undefined ) {
+					return data;
+				}
+
+				// We tried really hard, but the data doesn't exist.
+				return;
+			}
+
+			// Set the data...
+			this.each( function() {
+
+				// We always store the camelCased key
+				dataUser.set( this, key, value );
+			} );
+		}, null, value, arguments.length > 1, null, true );
+	},
+
+	removeData: function( key ) {
+		return this.each( function() {
+			dataUser.remove( this, key );
+		} );
+	}
+} );
+
+
+jQuery.extend( {
+	queue: function( elem, type, data ) {
+		var queue;
+
+		if ( elem ) {
+			type = ( type || "fx" ) + "queue";
+			queue = dataPriv.get( elem, type );
+
+			// Speed up dequeue by getting out quickly if this is just a lookup
+			if ( data ) {
+				if ( !queue || Array.isArray( data ) ) {
+					queue = dataPriv.access( elem, type, jQuery.makeArray( data ) );
+				} else {
+					queue.push( data );
+				}
+			}
+			return queue || [];
+		}
+	},
+
+	dequeue: function( elem, type ) {
+		type = type || "fx";
+
+		var queue = jQuery.queue( elem, type ),
+			startLength = queue.length,
+			fn = queue.shift(),
+			hooks = jQuery._queueHooks( elem, type ),
+			next = function() {
+				jQuery.dequeue( elem, type );
+			};
+
+		// If the fx queue is dequeued, always remove the progress sentinel
+		if ( fn === "inprogress" ) {
+			fn = queue.shift();
+			startLength--;
+		}
+
+		if ( fn ) {
+
+			// Add a progress sentinel to prevent the fx queue from being
+			// automatically dequeued
+			if ( type === "fx" ) {
+				queue.unshift( "inprogress" );
+			}
+
+			// Clear up the last queue stop function
+			delete hooks.stop;
+			fn.call( elem, next, hooks );
+		}
+
+		if ( !startLength && hooks ) {
+			hooks.empty.fire();
+		}
+	},
+
+	// Not public - generate a queueHooks object, or return the current one
+	_queueHooks: function( elem, type ) {
+		var key = type + "queueHooks";
+		return dataPriv.get( elem, key ) || dataPriv.access( elem, key, {
+			empty: jQuery.Callbacks( "once memory" ).add( function() {
+				dataPriv.remove( elem, [ type + "queue", key ] );
+			} )
+		} );
+	}
+} );
+
+jQuery.fn.extend( {
+	queue: function( type, data ) {
+		var setter = 2;
+
+		if ( typeof type !== "string" ) {
+			data = type;
+			type = "fx";
+			setter--;
+		}
+
+		if ( arguments.length < setter ) {
+			return jQuery.queue( this[ 0 ], type );
+		}
+
+		return data === undefined ?
+			this :
+			this.each( function() {
+				var queue = jQuery.queue( this, type, data );
+
+				// Ensure a hooks for this queue
+				jQuery._queueHooks( this, type );
+
+				if ( type === "fx" && queue[ 0 ] !== "inprogress" ) {
+					jQuery.dequeue( this, type );
+				}
+			} );
+	},
+	dequeue: function( type ) {
+		return this.each( function() {
+			jQuery.dequeue( this, type );
+		} );
+	},
+	clearQueue: function( type ) {
+		return this.queue( type || "fx", [] );
+	},
+
+	// Get a promise resolved when queues of a certain type
+	// are emptied (fx is the type by default)
+	promise: function( type, obj ) {
+		var tmp,
+			count = 1,
+			defer = jQuery.Deferred(),
+			elements = this,
+			i = this.length,
+			resolve = function() {
+				if ( !( --count ) ) {
+					defer.resolveWith( elements, [ elements ] );
+				}
+			};
+
+		if ( typeof type !== "string" ) {
+			obj = type;
+			type = undefined;
+		}
+		type = type || "fx";
+
+		while ( i-- ) {
+			tmp = dataPriv.get( elements[ i ], type + "queueHooks" );
+			if ( tmp && tmp.empty ) {
+				count++;
+				tmp.empty.add( resolve );
+			}
+		}
+		resolve();
+		return defer.promise( obj );
+	}
+} );
+var pnum = ( /[+-]?(?:\d*\.|)\d+(?:[eE][+-]?\d+|)/ ).source;
+
+var rcssNum = new RegExp( "^(?:([+-])=|)(" + pnum + ")([a-z%]*)$", "i" );
+
+
+var cssExpand = [ "Top", "Right", "Bottom", "Left" ];
+
+var documentElement = document.documentElement;
+
+
+
+	var isAttached = function( elem ) {
+			return jQuery.contains( elem.ownerDocument, elem );
+		},
+		composed = { composed: true };
+
+	// Support: IE 9 - 11+, Edge 12 - 18+, iOS 10.0 - 10.2 only
+	// Check attachment across shadow DOM boundaries when possible (gh-3504)
+	// Support: iOS 10.0-10.2 only
+	// Early iOS 10 versions support `attachShadow` but not `getRootNode`,
+	// leading to errors. We need to check for `getRootNode`.
+	if ( documentElement.getRootNode ) {
+		isAttached = function( elem ) {
+			return jQuery.contains( elem.ownerDocument, elem ) ||
+				elem.getRootNode( composed ) === elem.ownerDocument;
+		};
+	}
+var isHiddenWithinTree = function( elem, el ) {
+
+		// isHiddenWithinTree might be called from jQuery#filter function;
+		// in that case, element will be second argument
+		elem = el || elem;
+
+		// Inline style trumps all
+		return elem.style.display === "none" ||
+			elem.style.display === "" &&
+
+			// Otherwise, check computed style
+			// Support: Firefox <=43 - 45
+			// Disconnected elements can have computed display: none, so first confirm that elem is
+			// in the document.
+			isAttached( elem ) &&
+
+			jQuery.css( elem, "display" ) === "none";
+	};
+
+
+
+function adjustCSS( elem, prop, valueParts, tween ) {
+	var adjusted, scale,
+		maxIterations = 20,
+		currentValue = tween ?
+			function() {
+				return tween.cur();
+			} :
+			function() {
+				return jQuery.css( elem, prop, "" );
+			},
+		initial = currentValue(),
+		unit = valueParts && valueParts[ 3 ] || ( jQuery.cssNumber[ prop ] ? "" : "px" ),
+
+		// Starting value computation is required for potential unit mismatches
+		initialInUnit = elem.nodeType &&
+			( jQuery.cssNumber[ prop ] || unit !== "px" && +initial ) &&
+			rcssNum.exec( jQuery.css( elem, prop ) );
+
+	if ( initialInUnit && initialInUnit[ 3 ] !== unit ) {
+
+		// Support: Firefox <=54
+		// Halve the iteration target value to prevent interference from CSS upper bounds (gh-2144)
+		initial = initial / 2;
+
+		// Trust units reported by jQuery.css
+		unit = unit || initialInUnit[ 3 ];
+
+		// Iteratively approximate from a nonzero starting point
+		initialInUnit = +initial || 1;
+
+		while ( maxIterations-- ) {
+
+			// Evaluate and update our best guess (doubling guesses that zero out).
+			// Finish if the scale equals or crosses 1 (making the old*new product non-positive).
+			jQuery.style( elem, prop, initialInUnit + unit );
+			if ( ( 1 - scale ) * ( 1 - ( scale = currentValue() / initial || 0.5 ) ) <= 0 ) {
+				maxIterations = 0;
+			}
+			initialInUnit = initialInUnit / scale;
+
+		}
+
+		initialInUnit = initialInUnit * 2;
+		jQuery.style( elem, prop, initialInUnit + unit );
+
+		// Make sure we update the tween properties later on
+		valueParts = valueParts || [];
+	}
+
+	if ( valueParts ) {
+		initialInUnit = +initialInUnit || +initial || 0;
+
+		// Apply relative offset (+=/-=) if specified
+		adjusted = valueParts[ 1 ] ?
+			initialInUnit + ( valueParts[ 1 ] + 1 ) * valueParts[ 2 ] :
+			+valueParts[ 2 ];
+		if ( tween ) {
+			tween.unit = unit;
+			tween.start = initialInUnit;
+			tween.end = adjusted;
+		}
+	}
+	return adjusted;
+}
+
+
+var defaultDisplayMap = {};
+
+function getDefaultDisplay( elem ) {
+	var temp,
+		doc = elem.ownerDocument,
+		nodeName = elem.nodeName,
+		display = defaultDisplayMap[ nodeName ];
+
+	if ( display ) {
+		return display;
+	}
+
+	temp = doc.body.appendChild( doc.createElement( nodeName ) );
+	display = jQuery.css( temp, "display" );
+
+	temp.parentNode.removeChild( temp );
+
+	if ( display === "none" ) {
+		display = "block";
+	}
+	defaultDisplayMap[ nodeName ] = display;
+
+	return display;
+}
+
+function showHide( elements, show ) {
+	var display, elem,
+		values = [],
+		index = 0,
+		length = elements.length;
+
+	// Determine new display value for elements that need to change
+	for ( ; index < length; index++ ) {
+		elem = elements[ index ];
+		if ( !elem.style ) {
+			continue;
+		}
+
+		display = elem.style.display;
+		if ( show ) {
+
+			// Since we force visibility upon cascade-hidden elements, an immediate (and slow)
+			// check is required in this first loop unless we have a nonempty display value (either
+			// inline or about-to-be-restored)
+			if ( display === "none" ) {
+				values[ index ] = dataPriv.get( elem, "display" ) || null;
+				if ( !values[ index ] ) {
+					elem.style.display = "";
+				}
+			}
+			if ( elem.style.display === "" && isHiddenWithinTree( elem ) ) {
+				values[ index ] = getDefaultDisplay( elem );
+			}
+		} else {
+			if ( display !== "none" ) {
+				values[ index ] = "none";
+
+				// Remember what we're overwriting
+				dataPriv.set( elem, "display", display );
+			}
+		}
+	}
+
+	// Set the display of the elements in a second loop to avoid constant reflow
+	for ( index = 0; index < length; index++ ) {
+		if ( values[ index ] != null ) {
+			elements[ index ].style.display = values[ index ];
+		}
+	}
+
+	return elements;
+}
+
+jQuery.fn.extend( {
+	show: function() {
+		return showHide( this, true );
+	},
+	hide: function() {
+		return showHide( this );
+	},
+	toggle: function( state ) {
+		if ( typeof state === "boolean" ) {
+			return state ? this.show() : this.hide();
+		}
+
+		return this.each( function() {
+			if ( isHiddenWithinTree( this ) ) {
+				jQuery( this ).show();
+			} else {
+				jQuery( this ).hide();
+			}
+		} );
+	}
+} );
+var rcheckableType = ( /^(?:checkbox|radio)$/i );
+
+var rtagName = ( /<([a-z][^\/\0>\x20\t\r\n\f]*)/i );
+
+var rscriptType = ( /^$|^module$|\/(?:java|ecma)script/i );
+
+
+
+( function() {
+	var fragment = document.createDocumentFragment(),
+		div = fragment.appendChild( document.createElement( "div" ) ),
+		input = document.createElement( "input" );
+
+	// Support: Android 4.0 - 4.3 only
+	// Check state lost if the name is set (#11217)
+	// Support: Windows Web Apps (WWA)
+	// `name` and `type` must use .setAttribute for WWA (#14901)
+	input.setAttribute( "type", "radio" );
+	input.setAttribute( "checked", "checked" );
+	input.setAttribute( "name", "t" );
+
+	div.appendChild( input );
+
+	// Support: Android <=4.1 only
+	// Older WebKit doesn't clone checked state correctly in fragments
+	support.checkClone = div.cloneNode( true ).cloneNode( true ).lastChild.checked;
+
+	// Support: IE <=11 only
+	// Make sure textarea (and checkbox) defaultValue is properly cloned
+	div.innerHTML = "";
+	support.noCloneChecked = !!div.cloneNode( true ).lastChild.defaultValue;
+
+	// Support: IE <=9 only
+	// IE <=9 replaces ";
+	support.option = !!div.lastChild;
+} )();
+
+
+// We have to close these tags to support XHTML (#13200)
+var wrapMap = {
+
+	// XHTML parsers do not magically insert elements in the
+	// same way that tag soup parsers do. So we cannot shorten
+	// this by omitting  or other required elements.
+	thead: [ 1, "", "
" ], + col: [ 2, "", "
" ], + tr: [ 2, "", "
" ], + td: [ 3, "", "
" ], + + _default: [ 0, "", "" ] +}; + +wrapMap.tbody = wrapMap.tfoot = wrapMap.colgroup = wrapMap.caption = wrapMap.thead; +wrapMap.th = wrapMap.td; + +// Support: IE <=9 only +if ( !support.option ) { + wrapMap.optgroup = wrapMap.option = [ 1, "" ]; +} + + +function getAll( context, tag ) { + + // Support: IE <=9 - 11 only + // Use typeof to avoid zero-argument method invocation on host objects (#15151) + var ret; + + if ( typeof context.getElementsByTagName !== "undefined" ) { + ret = context.getElementsByTagName( tag || "*" ); + + } else if ( typeof context.querySelectorAll !== "undefined" ) { + ret = context.querySelectorAll( tag || "*" ); + + } else { + ret = []; + } + + if ( tag === undefined || tag && nodeName( context, tag ) ) { + return jQuery.merge( [ context ], ret ); + } + + return ret; +} + + +// Mark scripts as having already been evaluated +function setGlobalEval( elems, refElements ) { + var i = 0, + l = elems.length; + + for ( ; i < l; i++ ) { + dataPriv.set( + elems[ i ], + "globalEval", + !refElements || dataPriv.get( refElements[ i ], "globalEval" ) + ); + } +} + + +var rhtml = /<|&#?\w+;/; + +function buildFragment( elems, context, scripts, selection, ignored ) { + var elem, tmp, tag, wrap, attached, j, + fragment = context.createDocumentFragment(), + nodes = [], + i = 0, + l = elems.length; + + for ( ; i < l; i++ ) { + elem = elems[ i ]; + + if ( elem || elem === 0 ) { + + // Add nodes directly + if ( toType( elem ) === "object" ) { + + // Support: Android <=4.0 only, PhantomJS 1 only + // push.apply(_, arraylike) throws on ancient WebKit + jQuery.merge( nodes, elem.nodeType ? [ elem ] : elem ); + + // Convert non-html into a text node + } else if ( !rhtml.test( elem ) ) { + nodes.push( context.createTextNode( elem ) ); + + // Convert html into DOM nodes + } else { + tmp = tmp || fragment.appendChild( context.createElement( "div" ) ); + + // Deserialize a standard representation + tag = ( rtagName.exec( elem ) || [ "", "" ] )[ 1 ].toLowerCase(); + wrap = wrapMap[ tag ] || wrapMap._default; + tmp.innerHTML = wrap[ 1 ] + jQuery.htmlPrefilter( elem ) + wrap[ 2 ]; + + // Descend through wrappers to the right content + j = wrap[ 0 ]; + while ( j-- ) { + tmp = tmp.lastChild; + } + + // Support: Android <=4.0 only, PhantomJS 1 only + // push.apply(_, arraylike) throws on ancient WebKit + jQuery.merge( nodes, tmp.childNodes ); + + // Remember the top-level container + tmp = fragment.firstChild; + + // Ensure the created nodes are orphaned (#12392) + tmp.textContent = ""; + } + } + } + + // Remove wrapper from fragment + fragment.textContent = ""; + + i = 0; + while ( ( elem = nodes[ i++ ] ) ) { + + // Skip elements already in the context collection (trac-4087) + if ( selection && jQuery.inArray( elem, selection ) > -1 ) { + if ( ignored ) { + ignored.push( elem ); + } + continue; + } + + attached = isAttached( elem ); + + // Append to fragment + tmp = getAll( fragment.appendChild( elem ), "script" ); + + // Preserve script evaluation history + if ( attached ) { + setGlobalEval( tmp ); + } + + // Capture executables + if ( scripts ) { + j = 0; + while ( ( elem = tmp[ j++ ] ) ) { + if ( rscriptType.test( elem.type || "" ) ) { + scripts.push( elem ); + } + } + } + } + + return fragment; +} + + +var rtypenamespace = /^([^.]*)(?:\.(.+)|)/; + +function returnTrue() { + return true; +} + +function returnFalse() { + return false; +} + +// Support: IE <=9 - 11+ +// focus() and blur() are asynchronous, except when they are no-op. +// So expect focus to be synchronous when the element is already active, +// and blur to be synchronous when the element is not already active. +// (focus and blur are always synchronous in other supported browsers, +// this just defines when we can count on it). +function expectSync( elem, type ) { + return ( elem === safeActiveElement() ) === ( type === "focus" ); +} + +// Support: IE <=9 only +// Accessing document.activeElement can throw unexpectedly +// https://bugs.jquery.com/ticket/13393 +function safeActiveElement() { + try { + return document.activeElement; + } catch ( err ) { } +} + +function on( elem, types, selector, data, fn, one ) { + var origFn, type; + + // Types can be a map of types/handlers + if ( typeof types === "object" ) { + + // ( types-Object, selector, data ) + if ( typeof selector !== "string" ) { + + // ( types-Object, data ) + data = data || selector; + selector = undefined; + } + for ( type in types ) { + on( elem, type, selector, data, types[ type ], one ); + } + return elem; + } + + if ( data == null && fn == null ) { + + // ( types, fn ) + fn = selector; + data = selector = undefined; + } else if ( fn == null ) { + if ( typeof selector === "string" ) { + + // ( types, selector, fn ) + fn = data; + data = undefined; + } else { + + // ( types, data, fn ) + fn = data; + data = selector; + selector = undefined; + } + } + if ( fn === false ) { + fn = returnFalse; + } else if ( !fn ) { + return elem; + } + + if ( one === 1 ) { + origFn = fn; + fn = function( event ) { + + // Can use an empty set, since event contains the info + jQuery().off( event ); + return origFn.apply( this, arguments ); + }; + + // Use same guid so caller can remove using origFn + fn.guid = origFn.guid || ( origFn.guid = jQuery.guid++ ); + } + return elem.each( function() { + jQuery.event.add( this, types, fn, data, selector ); + } ); +} + +/* + * Helper functions for managing events -- not part of the public interface. + * Props to Dean Edwards' addEvent library for many of the ideas. + */ +jQuery.event = { + + global: {}, + + add: function( elem, types, handler, data, selector ) { + + var handleObjIn, eventHandle, tmp, + events, t, handleObj, + special, handlers, type, namespaces, origType, + elemData = dataPriv.get( elem ); + + // Only attach events to objects that accept data + if ( !acceptData( elem ) ) { + return; + } + + // Caller can pass in an object of custom data in lieu of the handler + if ( handler.handler ) { + handleObjIn = handler; + handler = handleObjIn.handler; + selector = handleObjIn.selector; + } + + // Ensure that invalid selectors throw exceptions at attach time + // Evaluate against documentElement in case elem is a non-element node (e.g., document) + if ( selector ) { + jQuery.find.matchesSelector( documentElement, selector ); + } + + // Make sure that the handler has a unique ID, used to find/remove it later + if ( !handler.guid ) { + handler.guid = jQuery.guid++; + } + + // Init the element's event structure and main handler, if this is the first + if ( !( events = elemData.events ) ) { + events = elemData.events = Object.create( null ); + } + if ( !( eventHandle = elemData.handle ) ) { + eventHandle = elemData.handle = function( e ) { + + // Discard the second event of a jQuery.event.trigger() and + // when an event is called after a page has unloaded + return typeof jQuery !== "undefined" && jQuery.event.triggered !== e.type ? + jQuery.event.dispatch.apply( elem, arguments ) : undefined; + }; + } + + // Handle multiple events separated by a space + types = ( types || "" ).match( rnothtmlwhite ) || [ "" ]; + t = types.length; + while ( t-- ) { + tmp = rtypenamespace.exec( types[ t ] ) || []; + type = origType = tmp[ 1 ]; + namespaces = ( tmp[ 2 ] || "" ).split( "." ).sort(); + + // There *must* be a type, no attaching namespace-only handlers + if ( !type ) { + continue; + } + + // If event changes its type, use the special event handlers for the changed type + special = jQuery.event.special[ type ] || {}; + + // If selector defined, determine special event api type, otherwise given type + type = ( selector ? special.delegateType : special.bindType ) || type; + + // Update special based on newly reset type + special = jQuery.event.special[ type ] || {}; + + // handleObj is passed to all event handlers + handleObj = jQuery.extend( { + type: type, + origType: origType, + data: data, + handler: handler, + guid: handler.guid, + selector: selector, + needsContext: selector && jQuery.expr.match.needsContext.test( selector ), + namespace: namespaces.join( "." ) + }, handleObjIn ); + + // Init the event handler queue if we're the first + if ( !( handlers = events[ type ] ) ) { + handlers = events[ type ] = []; + handlers.delegateCount = 0; + + // Only use addEventListener if the special events handler returns false + if ( !special.setup || + special.setup.call( elem, data, namespaces, eventHandle ) === false ) { + + if ( elem.addEventListener ) { + elem.addEventListener( type, eventHandle ); + } + } + } + + if ( special.add ) { + special.add.call( elem, handleObj ); + + if ( !handleObj.handler.guid ) { + handleObj.handler.guid = handler.guid; + } + } + + // Add to the element's handler list, delegates in front + if ( selector ) { + handlers.splice( handlers.delegateCount++, 0, handleObj ); + } else { + handlers.push( handleObj ); + } + + // Keep track of which events have ever been used, for event optimization + jQuery.event.global[ type ] = true; + } + + }, + + // Detach an event or set of events from an element + remove: function( elem, types, handler, selector, mappedTypes ) { + + var j, origCount, tmp, + events, t, handleObj, + special, handlers, type, namespaces, origType, + elemData = dataPriv.hasData( elem ) && dataPriv.get( elem ); + + if ( !elemData || !( events = elemData.events ) ) { + return; + } + + // Once for each type.namespace in types; type may be omitted + types = ( types || "" ).match( rnothtmlwhite ) || [ "" ]; + t = types.length; + while ( t-- ) { + tmp = rtypenamespace.exec( types[ t ] ) || []; + type = origType = tmp[ 1 ]; + namespaces = ( tmp[ 2 ] || "" ).split( "." ).sort(); + + // Unbind all events (on this namespace, if provided) for the element + if ( !type ) { + for ( type in events ) { + jQuery.event.remove( elem, type + types[ t ], handler, selector, true ); + } + continue; + } + + special = jQuery.event.special[ type ] || {}; + type = ( selector ? special.delegateType : special.bindType ) || type; + handlers = events[ type ] || []; + tmp = tmp[ 2 ] && + new RegExp( "(^|\\.)" + namespaces.join( "\\.(?:.*\\.|)" ) + "(\\.|$)" ); + + // Remove matching events + origCount = j = handlers.length; + while ( j-- ) { + handleObj = handlers[ j ]; + + if ( ( mappedTypes || origType === handleObj.origType ) && + ( !handler || handler.guid === handleObj.guid ) && + ( !tmp || tmp.test( handleObj.namespace ) ) && + ( !selector || selector === handleObj.selector || + selector === "**" && handleObj.selector ) ) { + handlers.splice( j, 1 ); + + if ( handleObj.selector ) { + handlers.delegateCount--; + } + if ( special.remove ) { + special.remove.call( elem, handleObj ); + } + } + } + + // Remove generic event handler if we removed something and no more handlers exist + // (avoids potential for endless recursion during removal of special event handlers) + if ( origCount && !handlers.length ) { + if ( !special.teardown || + special.teardown.call( elem, namespaces, elemData.handle ) === false ) { + + jQuery.removeEvent( elem, type, elemData.handle ); + } + + delete events[ type ]; + } + } + + // Remove data and the expando if it's no longer used + if ( jQuery.isEmptyObject( events ) ) { + dataPriv.remove( elem, "handle events" ); + } + }, + + dispatch: function( nativeEvent ) { + + var i, j, ret, matched, handleObj, handlerQueue, + args = new Array( arguments.length ), + + // Make a writable jQuery.Event from the native event object + event = jQuery.event.fix( nativeEvent ), + + handlers = ( + dataPriv.get( this, "events" ) || Object.create( null ) + )[ event.type ] || [], + special = jQuery.event.special[ event.type ] || {}; + + // Use the fix-ed jQuery.Event rather than the (read-only) native event + args[ 0 ] = event; + + for ( i = 1; i < arguments.length; i++ ) { + args[ i ] = arguments[ i ]; + } + + event.delegateTarget = this; + + // Call the preDispatch hook for the mapped type, and let it bail if desired + if ( special.preDispatch && special.preDispatch.call( this, event ) === false ) { + return; + } + + // Determine handlers + handlerQueue = jQuery.event.handlers.call( this, event, handlers ); + + // Run delegates first; they may want to stop propagation beneath us + i = 0; + while ( ( matched = handlerQueue[ i++ ] ) && !event.isPropagationStopped() ) { + event.currentTarget = matched.elem; + + j = 0; + while ( ( handleObj = matched.handlers[ j++ ] ) && + !event.isImmediatePropagationStopped() ) { + + // If the event is namespaced, then each handler is only invoked if it is + // specially universal or its namespaces are a superset of the event's. + if ( !event.rnamespace || handleObj.namespace === false || + event.rnamespace.test( handleObj.namespace ) ) { + + event.handleObj = handleObj; + event.data = handleObj.data; + + ret = ( ( jQuery.event.special[ handleObj.origType ] || {} ).handle || + handleObj.handler ).apply( matched.elem, args ); + + if ( ret !== undefined ) { + if ( ( event.result = ret ) === false ) { + event.preventDefault(); + event.stopPropagation(); + } + } + } + } + } + + // Call the postDispatch hook for the mapped type + if ( special.postDispatch ) { + special.postDispatch.call( this, event ); + } + + return event.result; + }, + + handlers: function( event, handlers ) { + var i, handleObj, sel, matchedHandlers, matchedSelectors, + handlerQueue = [], + delegateCount = handlers.delegateCount, + cur = event.target; + + // Find delegate handlers + if ( delegateCount && + + // Support: IE <=9 + // Black-hole SVG instance trees (trac-13180) + cur.nodeType && + + // Support: Firefox <=42 + // Suppress spec-violating clicks indicating a non-primary pointer button (trac-3861) + // https://www.w3.org/TR/DOM-Level-3-Events/#event-type-click + // Support: IE 11 only + // ...but not arrow key "clicks" of radio inputs, which can have `button` -1 (gh-2343) + !( event.type === "click" && event.button >= 1 ) ) { + + for ( ; cur !== this; cur = cur.parentNode || this ) { + + // Don't check non-elements (#13208) + // Don't process clicks on disabled elements (#6911, #8165, #11382, #11764) + if ( cur.nodeType === 1 && !( event.type === "click" && cur.disabled === true ) ) { + matchedHandlers = []; + matchedSelectors = {}; + for ( i = 0; i < delegateCount; i++ ) { + handleObj = handlers[ i ]; + + // Don't conflict with Object.prototype properties (#13203) + sel = handleObj.selector + " "; + + if ( matchedSelectors[ sel ] === undefined ) { + matchedSelectors[ sel ] = handleObj.needsContext ? + jQuery( sel, this ).index( cur ) > -1 : + jQuery.find( sel, this, null, [ cur ] ).length; + } + if ( matchedSelectors[ sel ] ) { + matchedHandlers.push( handleObj ); + } + } + if ( matchedHandlers.length ) { + handlerQueue.push( { elem: cur, handlers: matchedHandlers } ); + } + } + } + } + + // Add the remaining (directly-bound) handlers + cur = this; + if ( delegateCount < handlers.length ) { + handlerQueue.push( { elem: cur, handlers: handlers.slice( delegateCount ) } ); + } + + return handlerQueue; + }, + + addProp: function( name, hook ) { + Object.defineProperty( jQuery.Event.prototype, name, { + enumerable: true, + configurable: true, + + get: isFunction( hook ) ? + function() { + if ( this.originalEvent ) { + return hook( this.originalEvent ); + } + } : + function() { + if ( this.originalEvent ) { + return this.originalEvent[ name ]; + } + }, + + set: function( value ) { + Object.defineProperty( this, name, { + enumerable: true, + configurable: true, + writable: true, + value: value + } ); + } + } ); + }, + + fix: function( originalEvent ) { + return originalEvent[ jQuery.expando ] ? + originalEvent : + new jQuery.Event( originalEvent ); + }, + + special: { + load: { + + // Prevent triggered image.load events from bubbling to window.load + noBubble: true + }, + click: { + + // Utilize native event to ensure correct state for checkable inputs + setup: function( data ) { + + // For mutual compressibility with _default, replace `this` access with a local var. + // `|| data` is dead code meant only to preserve the variable through minification. + var el = this || data; + + // Claim the first handler + if ( rcheckableType.test( el.type ) && + el.click && nodeName( el, "input" ) ) { + + // dataPriv.set( el, "click", ... ) + leverageNative( el, "click", returnTrue ); + } + + // Return false to allow normal processing in the caller + return false; + }, + trigger: function( data ) { + + // For mutual compressibility with _default, replace `this` access with a local var. + // `|| data` is dead code meant only to preserve the variable through minification. + var el = this || data; + + // Force setup before triggering a click + if ( rcheckableType.test( el.type ) && + el.click && nodeName( el, "input" ) ) { + + leverageNative( el, "click" ); + } + + // Return non-false to allow normal event-path propagation + return true; + }, + + // For cross-browser consistency, suppress native .click() on links + // Also prevent it if we're currently inside a leveraged native-event stack + _default: function( event ) { + var target = event.target; + return rcheckableType.test( target.type ) && + target.click && nodeName( target, "input" ) && + dataPriv.get( target, "click" ) || + nodeName( target, "a" ); + } + }, + + beforeunload: { + postDispatch: function( event ) { + + // Support: Firefox 20+ + // Firefox doesn't alert if the returnValue field is not set. + if ( event.result !== undefined && event.originalEvent ) { + event.originalEvent.returnValue = event.result; + } + } + } + } +}; + +// Ensure the presence of an event listener that handles manually-triggered +// synthetic events by interrupting progress until reinvoked in response to +// *native* events that it fires directly, ensuring that state changes have +// already occurred before other listeners are invoked. +function leverageNative( el, type, expectSync ) { + + // Missing expectSync indicates a trigger call, which must force setup through jQuery.event.add + if ( !expectSync ) { + if ( dataPriv.get( el, type ) === undefined ) { + jQuery.event.add( el, type, returnTrue ); + } + return; + } + + // Register the controller as a special universal handler for all event namespaces + dataPriv.set( el, type, false ); + jQuery.event.add( el, type, { + namespace: false, + handler: function( event ) { + var notAsync, result, + saved = dataPriv.get( this, type ); + + if ( ( event.isTrigger & 1 ) && this[ type ] ) { + + // Interrupt processing of the outer synthetic .trigger()ed event + // Saved data should be false in such cases, but might be a leftover capture object + // from an async native handler (gh-4350) + if ( !saved.length ) { + + // Store arguments for use when handling the inner native event + // There will always be at least one argument (an event object), so this array + // will not be confused with a leftover capture object. + saved = slice.call( arguments ); + dataPriv.set( this, type, saved ); + + // Trigger the native event and capture its result + // Support: IE <=9 - 11+ + // focus() and blur() are asynchronous + notAsync = expectSync( this, type ); + this[ type ](); + result = dataPriv.get( this, type ); + if ( saved !== result || notAsync ) { + dataPriv.set( this, type, false ); + } else { + result = {}; + } + if ( saved !== result ) { + + // Cancel the outer synthetic event + event.stopImmediatePropagation(); + event.preventDefault(); + + // Support: Chrome 86+ + // In Chrome, if an element having a focusout handler is blurred by + // clicking outside of it, it invokes the handler synchronously. If + // that handler calls `.remove()` on the element, the data is cleared, + // leaving `result` undefined. We need to guard against this. + return result && result.value; + } + + // If this is an inner synthetic event for an event with a bubbling surrogate + // (focus or blur), assume that the surrogate already propagated from triggering the + // native event and prevent that from happening again here. + // This technically gets the ordering wrong w.r.t. to `.trigger()` (in which the + // bubbling surrogate propagates *after* the non-bubbling base), but that seems + // less bad than duplication. + } else if ( ( jQuery.event.special[ type ] || {} ).delegateType ) { + event.stopPropagation(); + } + + // If this is a native event triggered above, everything is now in order + // Fire an inner synthetic event with the original arguments + } else if ( saved.length ) { + + // ...and capture the result + dataPriv.set( this, type, { + value: jQuery.event.trigger( + + // Support: IE <=9 - 11+ + // Extend with the prototype to reset the above stopImmediatePropagation() + jQuery.extend( saved[ 0 ], jQuery.Event.prototype ), + saved.slice( 1 ), + this + ) + } ); + + // Abort handling of the native event + event.stopImmediatePropagation(); + } + } + } ); +} + +jQuery.removeEvent = function( elem, type, handle ) { + + // This "if" is needed for plain objects + if ( elem.removeEventListener ) { + elem.removeEventListener( type, handle ); + } +}; + +jQuery.Event = function( src, props ) { + + // Allow instantiation without the 'new' keyword + if ( !( this instanceof jQuery.Event ) ) { + return new jQuery.Event( src, props ); + } + + // Event object + if ( src && src.type ) { + this.originalEvent = src; + this.type = src.type; + + // Events bubbling up the document may have been marked as prevented + // by a handler lower down the tree; reflect the correct value. + this.isDefaultPrevented = src.defaultPrevented || + src.defaultPrevented === undefined && + + // Support: Android <=2.3 only + src.returnValue === false ? + returnTrue : + returnFalse; + + // Create target properties + // Support: Safari <=6 - 7 only + // Target should not be a text node (#504, #13143) + this.target = ( src.target && src.target.nodeType === 3 ) ? + src.target.parentNode : + src.target; + + this.currentTarget = src.currentTarget; + this.relatedTarget = src.relatedTarget; + + // Event type + } else { + this.type = src; + } + + // Put explicitly provided properties onto the event object + if ( props ) { + jQuery.extend( this, props ); + } + + // Create a timestamp if incoming event doesn't have one + this.timeStamp = src && src.timeStamp || Date.now(); + + // Mark it as fixed + this[ jQuery.expando ] = true; +}; + +// jQuery.Event is based on DOM3 Events as specified by the ECMAScript Language Binding +// https://www.w3.org/TR/2003/WD-DOM-Level-3-Events-20030331/ecma-script-binding.html +jQuery.Event.prototype = { + constructor: jQuery.Event, + isDefaultPrevented: returnFalse, + isPropagationStopped: returnFalse, + isImmediatePropagationStopped: returnFalse, + isSimulated: false, + + preventDefault: function() { + var e = this.originalEvent; + + this.isDefaultPrevented = returnTrue; + + if ( e && !this.isSimulated ) { + e.preventDefault(); + } + }, + stopPropagation: function() { + var e = this.originalEvent; + + this.isPropagationStopped = returnTrue; + + if ( e && !this.isSimulated ) { + e.stopPropagation(); + } + }, + stopImmediatePropagation: function() { + var e = this.originalEvent; + + this.isImmediatePropagationStopped = returnTrue; + + if ( e && !this.isSimulated ) { + e.stopImmediatePropagation(); + } + + this.stopPropagation(); + } +}; + +// Includes all common event props including KeyEvent and MouseEvent specific props +jQuery.each( { + altKey: true, + bubbles: true, + cancelable: true, + changedTouches: true, + ctrlKey: true, + detail: true, + eventPhase: true, + metaKey: true, + pageX: true, + pageY: true, + shiftKey: true, + view: true, + "char": true, + code: true, + charCode: true, + key: true, + keyCode: true, + button: true, + buttons: true, + clientX: true, + clientY: true, + offsetX: true, + offsetY: true, + pointerId: true, + pointerType: true, + screenX: true, + screenY: true, + targetTouches: true, + toElement: true, + touches: true, + which: true +}, jQuery.event.addProp ); + +jQuery.each( { focus: "focusin", blur: "focusout" }, function( type, delegateType ) { + jQuery.event.special[ type ] = { + + // Utilize native event if possible so blur/focus sequence is correct + setup: function() { + + // Claim the first handler + // dataPriv.set( this, "focus", ... ) + // dataPriv.set( this, "blur", ... ) + leverageNative( this, type, expectSync ); + + // Return false to allow normal processing in the caller + return false; + }, + trigger: function() { + + // Force setup before trigger + leverageNative( this, type ); + + // Return non-false to allow normal event-path propagation + return true; + }, + + // Suppress native focus or blur as it's already being fired + // in leverageNative. + _default: function() { + return true; + }, + + delegateType: delegateType + }; +} ); + +// Create mouseenter/leave events using mouseover/out and event-time checks +// so that event delegation works in jQuery. +// Do the same for pointerenter/pointerleave and pointerover/pointerout +// +// Support: Safari 7 only +// Safari sends mouseenter too often; see: +// https://bugs.chromium.org/p/chromium/issues/detail?id=470258 +// for the description of the bug (it existed in older Chrome versions as well). +jQuery.each( { + mouseenter: "mouseover", + mouseleave: "mouseout", + pointerenter: "pointerover", + pointerleave: "pointerout" +}, function( orig, fix ) { + jQuery.event.special[ orig ] = { + delegateType: fix, + bindType: fix, + + handle: function( event ) { + var ret, + target = this, + related = event.relatedTarget, + handleObj = event.handleObj; + + // For mouseenter/leave call the handler if related is outside the target. + // NB: No relatedTarget if the mouse left/entered the browser window + if ( !related || ( related !== target && !jQuery.contains( target, related ) ) ) { + event.type = handleObj.origType; + ret = handleObj.handler.apply( this, arguments ); + event.type = fix; + } + return ret; + } + }; +} ); + +jQuery.fn.extend( { + + on: function( types, selector, data, fn ) { + return on( this, types, selector, data, fn ); + }, + one: function( types, selector, data, fn ) { + return on( this, types, selector, data, fn, 1 ); + }, + off: function( types, selector, fn ) { + var handleObj, type; + if ( types && types.preventDefault && types.handleObj ) { + + // ( event ) dispatched jQuery.Event + handleObj = types.handleObj; + jQuery( types.delegateTarget ).off( + handleObj.namespace ? + handleObj.origType + "." + handleObj.namespace : + handleObj.origType, + handleObj.selector, + handleObj.handler + ); + return this; + } + if ( typeof types === "object" ) { + + // ( types-object [, selector] ) + for ( type in types ) { + this.off( type, selector, types[ type ] ); + } + return this; + } + if ( selector === false || typeof selector === "function" ) { + + // ( types [, fn] ) + fn = selector; + selector = undefined; + } + if ( fn === false ) { + fn = returnFalse; + } + return this.each( function() { + jQuery.event.remove( this, types, fn, selector ); + } ); + } +} ); + + +var + + // Support: IE <=10 - 11, Edge 12 - 13 only + // In IE/Edge using regex groups here causes severe slowdowns. + // See https://connect.microsoft.com/IE/feedback/details/1736512/ + rnoInnerhtml = /\s*$/g; + +// Prefer a tbody over its parent table for containing new rows +function manipulationTarget( elem, content ) { + if ( nodeName( elem, "table" ) && + nodeName( content.nodeType !== 11 ? content : content.firstChild, "tr" ) ) { + + return jQuery( elem ).children( "tbody" )[ 0 ] || elem; + } + + return elem; +} + +// Replace/restore the type attribute of script elements for safe DOM manipulation +function disableScript( elem ) { + elem.type = ( elem.getAttribute( "type" ) !== null ) + "/" + elem.type; + return elem; +} +function restoreScript( elem ) { + if ( ( elem.type || "" ).slice( 0, 5 ) === "true/" ) { + elem.type = elem.type.slice( 5 ); + } else { + elem.removeAttribute( "type" ); + } + + return elem; +} + +function cloneCopyEvent( src, dest ) { + var i, l, type, pdataOld, udataOld, udataCur, events; + + if ( dest.nodeType !== 1 ) { + return; + } + + // 1. Copy private data: events, handlers, etc. + if ( dataPriv.hasData( src ) ) { + pdataOld = dataPriv.get( src ); + events = pdataOld.events; + + if ( events ) { + dataPriv.remove( dest, "handle events" ); + + for ( type in events ) { + for ( i = 0, l = events[ type ].length; i < l; i++ ) { + jQuery.event.add( dest, type, events[ type ][ i ] ); + } + } + } + } + + // 2. Copy user data + if ( dataUser.hasData( src ) ) { + udataOld = dataUser.access( src ); + udataCur = jQuery.extend( {}, udataOld ); + + dataUser.set( dest, udataCur ); + } +} + +// Fix IE bugs, see support tests +function fixInput( src, dest ) { + var nodeName = dest.nodeName.toLowerCase(); + + // Fails to persist the checked state of a cloned checkbox or radio button. + if ( nodeName === "input" && rcheckableType.test( src.type ) ) { + dest.checked = src.checked; + + // Fails to return the selected option to the default selected state when cloning options + } else if ( nodeName === "input" || nodeName === "textarea" ) { + dest.defaultValue = src.defaultValue; + } +} + +function domManip( collection, args, callback, ignored ) { + + // Flatten any nested arrays + args = flat( args ); + + var fragment, first, scripts, hasScripts, node, doc, + i = 0, + l = collection.length, + iNoClone = l - 1, + value = args[ 0 ], + valueIsFunction = isFunction( value ); + + // We can't cloneNode fragments that contain checked, in WebKit + if ( valueIsFunction || + ( l > 1 && typeof value === "string" && + !support.checkClone && rchecked.test( value ) ) ) { + return collection.each( function( index ) { + var self = collection.eq( index ); + if ( valueIsFunction ) { + args[ 0 ] = value.call( this, index, self.html() ); + } + domManip( self, args, callback, ignored ); + } ); + } + + if ( l ) { + fragment = buildFragment( args, collection[ 0 ].ownerDocument, false, collection, ignored ); + first = fragment.firstChild; + + if ( fragment.childNodes.length === 1 ) { + fragment = first; + } + + // Require either new content or an interest in ignored elements to invoke the callback + if ( first || ignored ) { + scripts = jQuery.map( getAll( fragment, "script" ), disableScript ); + hasScripts = scripts.length; + + // Use the original fragment for the last item + // instead of the first because it can end up + // being emptied incorrectly in certain situations (#8070). + for ( ; i < l; i++ ) { + node = fragment; + + if ( i !== iNoClone ) { + node = jQuery.clone( node, true, true ); + + // Keep references to cloned scripts for later restoration + if ( hasScripts ) { + + // Support: Android <=4.0 only, PhantomJS 1 only + // push.apply(_, arraylike) throws on ancient WebKit + jQuery.merge( scripts, getAll( node, "script" ) ); + } + } + + callback.call( collection[ i ], node, i ); + } + + if ( hasScripts ) { + doc = scripts[ scripts.length - 1 ].ownerDocument; + + // Reenable scripts + jQuery.map( scripts, restoreScript ); + + // Evaluate executable scripts on first document insertion + for ( i = 0; i < hasScripts; i++ ) { + node = scripts[ i ]; + if ( rscriptType.test( node.type || "" ) && + !dataPriv.access( node, "globalEval" ) && + jQuery.contains( doc, node ) ) { + + if ( node.src && ( node.type || "" ).toLowerCase() !== "module" ) { + + // Optional AJAX dependency, but won't run scripts if not present + if ( jQuery._evalUrl && !node.noModule ) { + jQuery._evalUrl( node.src, { + nonce: node.nonce || node.getAttribute( "nonce" ) + }, doc ); + } + } else { + DOMEval( node.textContent.replace( rcleanScript, "" ), node, doc ); + } + } + } + } + } + } + + return collection; +} + +function remove( elem, selector, keepData ) { + var node, + nodes = selector ? jQuery.filter( selector, elem ) : elem, + i = 0; + + for ( ; ( node = nodes[ i ] ) != null; i++ ) { + if ( !keepData && node.nodeType === 1 ) { + jQuery.cleanData( getAll( node ) ); + } + + if ( node.parentNode ) { + if ( keepData && isAttached( node ) ) { + setGlobalEval( getAll( node, "script" ) ); + } + node.parentNode.removeChild( node ); + } + } + + return elem; +} + +jQuery.extend( { + htmlPrefilter: function( html ) { + return html; + }, + + clone: function( elem, dataAndEvents, deepDataAndEvents ) { + var i, l, srcElements, destElements, + clone = elem.cloneNode( true ), + inPage = isAttached( elem ); + + // Fix IE cloning issues + if ( !support.noCloneChecked && ( elem.nodeType === 1 || elem.nodeType === 11 ) && + !jQuery.isXMLDoc( elem ) ) { + + // We eschew Sizzle here for performance reasons: https://jsperf.com/getall-vs-sizzle/2 + destElements = getAll( clone ); + srcElements = getAll( elem ); + + for ( i = 0, l = srcElements.length; i < l; i++ ) { + fixInput( srcElements[ i ], destElements[ i ] ); + } + } + + // Copy the events from the original to the clone + if ( dataAndEvents ) { + if ( deepDataAndEvents ) { + srcElements = srcElements || getAll( elem ); + destElements = destElements || getAll( clone ); + + for ( i = 0, l = srcElements.length; i < l; i++ ) { + cloneCopyEvent( srcElements[ i ], destElements[ i ] ); + } + } else { + cloneCopyEvent( elem, clone ); + } + } + + // Preserve script evaluation history + destElements = getAll( clone, "script" ); + if ( destElements.length > 0 ) { + setGlobalEval( destElements, !inPage && getAll( elem, "script" ) ); + } + + // Return the cloned set + return clone; + }, + + cleanData: function( elems ) { + var data, elem, type, + special = jQuery.event.special, + i = 0; + + for ( ; ( elem = elems[ i ] ) !== undefined; i++ ) { + if ( acceptData( elem ) ) { + if ( ( data = elem[ dataPriv.expando ] ) ) { + if ( data.events ) { + for ( type in data.events ) { + if ( special[ type ] ) { + jQuery.event.remove( elem, type ); + + // This is a shortcut to avoid jQuery.event.remove's overhead + } else { + jQuery.removeEvent( elem, type, data.handle ); + } + } + } + + // Support: Chrome <=35 - 45+ + // Assign undefined instead of using delete, see Data#remove + elem[ dataPriv.expando ] = undefined; + } + if ( elem[ dataUser.expando ] ) { + + // Support: Chrome <=35 - 45+ + // Assign undefined instead of using delete, see Data#remove + elem[ dataUser.expando ] = undefined; + } + } + } + } +} ); + +jQuery.fn.extend( { + detach: function( selector ) { + return remove( this, selector, true ); + }, + + remove: function( selector ) { + return remove( this, selector ); + }, + + text: function( value ) { + return access( this, function( value ) { + return value === undefined ? + jQuery.text( this ) : + this.empty().each( function() { + if ( this.nodeType === 1 || this.nodeType === 11 || this.nodeType === 9 ) { + this.textContent = value; + } + } ); + }, null, value, arguments.length ); + }, + + append: function() { + return domManip( this, arguments, function( elem ) { + if ( this.nodeType === 1 || this.nodeType === 11 || this.nodeType === 9 ) { + var target = manipulationTarget( this, elem ); + target.appendChild( elem ); + } + } ); + }, + + prepend: function() { + return domManip( this, arguments, function( elem ) { + if ( this.nodeType === 1 || this.nodeType === 11 || this.nodeType === 9 ) { + var target = manipulationTarget( this, elem ); + target.insertBefore( elem, target.firstChild ); + } + } ); + }, + + before: function() { + return domManip( this, arguments, function( elem ) { + if ( this.parentNode ) { + this.parentNode.insertBefore( elem, this ); + } + } ); + }, + + after: function() { + return domManip( this, arguments, function( elem ) { + if ( this.parentNode ) { + this.parentNode.insertBefore( elem, this.nextSibling ); + } + } ); + }, + + empty: function() { + var elem, + i = 0; + + for ( ; ( elem = this[ i ] ) != null; i++ ) { + if ( elem.nodeType === 1 ) { + + // Prevent memory leaks + jQuery.cleanData( getAll( elem, false ) ); + + // Remove any remaining nodes + elem.textContent = ""; + } + } + + return this; + }, + + clone: function( dataAndEvents, deepDataAndEvents ) { + dataAndEvents = dataAndEvents == null ? false : dataAndEvents; + deepDataAndEvents = deepDataAndEvents == null ? dataAndEvents : deepDataAndEvents; + + return this.map( function() { + return jQuery.clone( this, dataAndEvents, deepDataAndEvents ); + } ); + }, + + html: function( value ) { + return access( this, function( value ) { + var elem = this[ 0 ] || {}, + i = 0, + l = this.length; + + if ( value === undefined && elem.nodeType === 1 ) { + return elem.innerHTML; + } + + // See if we can take a shortcut and just use innerHTML + if ( typeof value === "string" && !rnoInnerhtml.test( value ) && + !wrapMap[ ( rtagName.exec( value ) || [ "", "" ] )[ 1 ].toLowerCase() ] ) { + + value = jQuery.htmlPrefilter( value ); + + try { + for ( ; i < l; i++ ) { + elem = this[ i ] || {}; + + // Remove element nodes and prevent memory leaks + if ( elem.nodeType === 1 ) { + jQuery.cleanData( getAll( elem, false ) ); + elem.innerHTML = value; + } + } + + elem = 0; + + // If using innerHTML throws an exception, use the fallback method + } catch ( e ) {} + } + + if ( elem ) { + this.empty().append( value ); + } + }, null, value, arguments.length ); + }, + + replaceWith: function() { + var ignored = []; + + // Make the changes, replacing each non-ignored context element with the new content + return domManip( this, arguments, function( elem ) { + var parent = this.parentNode; + + if ( jQuery.inArray( this, ignored ) < 0 ) { + jQuery.cleanData( getAll( this ) ); + if ( parent ) { + parent.replaceChild( elem, this ); + } + } + + // Force callback invocation + }, ignored ); + } +} ); + +jQuery.each( { + appendTo: "append", + prependTo: "prepend", + insertBefore: "before", + insertAfter: "after", + replaceAll: "replaceWith" +}, function( name, original ) { + jQuery.fn[ name ] = function( selector ) { + var elems, + ret = [], + insert = jQuery( selector ), + last = insert.length - 1, + i = 0; + + for ( ; i <= last; i++ ) { + elems = i === last ? this : this.clone( true ); + jQuery( insert[ i ] )[ original ]( elems ); + + // Support: Android <=4.0 only, PhantomJS 1 only + // .get() because push.apply(_, arraylike) throws on ancient WebKit + push.apply( ret, elems.get() ); + } + + return this.pushStack( ret ); + }; +} ); +var rnumnonpx = new RegExp( "^(" + pnum + ")(?!px)[a-z%]+$", "i" ); + +var getStyles = function( elem ) { + + // Support: IE <=11 only, Firefox <=30 (#15098, #14150) + // IE throws on elements created in popups + // FF meanwhile throws on frame elements through "defaultView.getComputedStyle" + var view = elem.ownerDocument.defaultView; + + if ( !view || !view.opener ) { + view = window; + } + + return view.getComputedStyle( elem ); + }; + +var swap = function( elem, options, callback ) { + var ret, name, + old = {}; + + // Remember the old values, and insert the new ones + for ( name in options ) { + old[ name ] = elem.style[ name ]; + elem.style[ name ] = options[ name ]; + } + + ret = callback.call( elem ); + + // Revert the old values + for ( name in options ) { + elem.style[ name ] = old[ name ]; + } + + return ret; +}; + + +var rboxStyle = new RegExp( cssExpand.join( "|" ), "i" ); + + + +( function() { + + // Executing both pixelPosition & boxSizingReliable tests require only one layout + // so they're executed at the same time to save the second computation. + function computeStyleTests() { + + // This is a singleton, we need to execute it only once + if ( !div ) { + return; + } + + container.style.cssText = "position:absolute;left:-11111px;width:60px;" + + "margin-top:1px;padding:0;border:0"; + div.style.cssText = + "position:relative;display:block;box-sizing:border-box;overflow:scroll;" + + "margin:auto;border:1px;padding:1px;" + + "width:60%;top:1%"; + documentElement.appendChild( container ).appendChild( div ); + + var divStyle = window.getComputedStyle( div ); + pixelPositionVal = divStyle.top !== "1%"; + + // Support: Android 4.0 - 4.3 only, Firefox <=3 - 44 + reliableMarginLeftVal = roundPixelMeasures( divStyle.marginLeft ) === 12; + + // Support: Android 4.0 - 4.3 only, Safari <=9.1 - 10.1, iOS <=7.0 - 9.3 + // Some styles come back with percentage values, even though they shouldn't + div.style.right = "60%"; + pixelBoxStylesVal = roundPixelMeasures( divStyle.right ) === 36; + + // Support: IE 9 - 11 only + // Detect misreporting of content dimensions for box-sizing:border-box elements + boxSizingReliableVal = roundPixelMeasures( divStyle.width ) === 36; + + // Support: IE 9 only + // Detect overflow:scroll screwiness (gh-3699) + // Support: Chrome <=64 + // Don't get tricked when zoom affects offsetWidth (gh-4029) + div.style.position = "absolute"; + scrollboxSizeVal = roundPixelMeasures( div.offsetWidth / 3 ) === 12; + + documentElement.removeChild( container ); + + // Nullify the div so it wouldn't be stored in the memory and + // it will also be a sign that checks already performed + div = null; + } + + function roundPixelMeasures( measure ) { + return Math.round( parseFloat( measure ) ); + } + + var pixelPositionVal, boxSizingReliableVal, scrollboxSizeVal, pixelBoxStylesVal, + reliableTrDimensionsVal, reliableMarginLeftVal, + container = document.createElement( "div" ), + div = document.createElement( "div" ); + + // Finish early in limited (non-browser) environments + if ( !div.style ) { + return; + } + + // Support: IE <=9 - 11 only + // Style of cloned element affects source element cloned (#8908) + div.style.backgroundClip = "content-box"; + div.cloneNode( true ).style.backgroundClip = ""; + support.clearCloneStyle = div.style.backgroundClip === "content-box"; + + jQuery.extend( support, { + boxSizingReliable: function() { + computeStyleTests(); + return boxSizingReliableVal; + }, + pixelBoxStyles: function() { + computeStyleTests(); + return pixelBoxStylesVal; + }, + pixelPosition: function() { + computeStyleTests(); + return pixelPositionVal; + }, + reliableMarginLeft: function() { + computeStyleTests(); + return reliableMarginLeftVal; + }, + scrollboxSize: function() { + computeStyleTests(); + return scrollboxSizeVal; + }, + + // Support: IE 9 - 11+, Edge 15 - 18+ + // IE/Edge misreport `getComputedStyle` of table rows with width/height + // set in CSS while `offset*` properties report correct values. + // Behavior in IE 9 is more subtle than in newer versions & it passes + // some versions of this test; make sure not to make it pass there! + // + // Support: Firefox 70+ + // Only Firefox includes border widths + // in computed dimensions. (gh-4529) + reliableTrDimensions: function() { + var table, tr, trChild, trStyle; + if ( reliableTrDimensionsVal == null ) { + table = document.createElement( "table" ); + tr = document.createElement( "tr" ); + trChild = document.createElement( "div" ); + + table.style.cssText = "position:absolute;left:-11111px;border-collapse:separate"; + tr.style.cssText = "border:1px solid"; + + // Support: Chrome 86+ + // Height set through cssText does not get applied. + // Computed height then comes back as 0. + tr.style.height = "1px"; + trChild.style.height = "9px"; + + // Support: Android 8 Chrome 86+ + // In our bodyBackground.html iframe, + // display for all div elements is set to "inline", + // which causes a problem only in Android 8 Chrome 86. + // Ensuring the div is display: block + // gets around this issue. + trChild.style.display = "block"; + + documentElement + .appendChild( table ) + .appendChild( tr ) + .appendChild( trChild ); + + trStyle = window.getComputedStyle( tr ); + reliableTrDimensionsVal = ( parseInt( trStyle.height, 10 ) + + parseInt( trStyle.borderTopWidth, 10 ) + + parseInt( trStyle.borderBottomWidth, 10 ) ) === tr.offsetHeight; + + documentElement.removeChild( table ); + } + return reliableTrDimensionsVal; + } + } ); +} )(); + + +function curCSS( elem, name, computed ) { + var width, minWidth, maxWidth, ret, + + // Support: Firefox 51+ + // Retrieving style before computed somehow + // fixes an issue with getting wrong values + // on detached elements + style = elem.style; + + computed = computed || getStyles( elem ); + + // getPropertyValue is needed for: + // .css('filter') (IE 9 only, #12537) + // .css('--customProperty) (#3144) + if ( computed ) { + ret = computed.getPropertyValue( name ) || computed[ name ]; + + if ( ret === "" && !isAttached( elem ) ) { + ret = jQuery.style( elem, name ); + } + + // A tribute to the "awesome hack by Dean Edwards" + // Android Browser returns percentage for some values, + // but width seems to be reliably pixels. + // This is against the CSSOM draft spec: + // https://drafts.csswg.org/cssom/#resolved-values + if ( !support.pixelBoxStyles() && rnumnonpx.test( ret ) && rboxStyle.test( name ) ) { + + // Remember the original values + width = style.width; + minWidth = style.minWidth; + maxWidth = style.maxWidth; + + // Put in the new values to get a computed value out + style.minWidth = style.maxWidth = style.width = ret; + ret = computed.width; + + // Revert the changed values + style.width = width; + style.minWidth = minWidth; + style.maxWidth = maxWidth; + } + } + + return ret !== undefined ? + + // Support: IE <=9 - 11 only + // IE returns zIndex value as an integer. + ret + "" : + ret; +} + + +function addGetHookIf( conditionFn, hookFn ) { + + // Define the hook, we'll check on the first run if it's really needed. + return { + get: function() { + if ( conditionFn() ) { + + // Hook not needed (or it's not possible to use it due + // to missing dependency), remove it. + delete this.get; + return; + } + + // Hook needed; redefine it so that the support test is not executed again. + return ( this.get = hookFn ).apply( this, arguments ); + } + }; +} + + +var cssPrefixes = [ "Webkit", "Moz", "ms" ], + emptyStyle = document.createElement( "div" ).style, + vendorProps = {}; + +// Return a vendor-prefixed property or undefined +function vendorPropName( name ) { + + // Check for vendor prefixed names + var capName = name[ 0 ].toUpperCase() + name.slice( 1 ), + i = cssPrefixes.length; + + while ( i-- ) { + name = cssPrefixes[ i ] + capName; + if ( name in emptyStyle ) { + return name; + } + } +} + +// Return a potentially-mapped jQuery.cssProps or vendor prefixed property +function finalPropName( name ) { + var final = jQuery.cssProps[ name ] || vendorProps[ name ]; + + if ( final ) { + return final; + } + if ( name in emptyStyle ) { + return name; + } + return vendorProps[ name ] = vendorPropName( name ) || name; +} + + +var + + // Swappable if display is none or starts with table + // except "table", "table-cell", or "table-caption" + // See here for display values: https://developer.mozilla.org/en-US/docs/CSS/display + rdisplayswap = /^(none|table(?!-c[ea]).+)/, + rcustomProp = /^--/, + cssShow = { position: "absolute", visibility: "hidden", display: "block" }, + cssNormalTransform = { + letterSpacing: "0", + fontWeight: "400" + }; + +function setPositiveNumber( _elem, value, subtract ) { + + // Any relative (+/-) values have already been + // normalized at this point + var matches = rcssNum.exec( value ); + return matches ? + + // Guard against undefined "subtract", e.g., when used as in cssHooks + Math.max( 0, matches[ 2 ] - ( subtract || 0 ) ) + ( matches[ 3 ] || "px" ) : + value; +} + +function boxModelAdjustment( elem, dimension, box, isBorderBox, styles, computedVal ) { + var i = dimension === "width" ? 1 : 0, + extra = 0, + delta = 0; + + // Adjustment may not be necessary + if ( box === ( isBorderBox ? "border" : "content" ) ) { + return 0; + } + + for ( ; i < 4; i += 2 ) { + + // Both box models exclude margin + if ( box === "margin" ) { + delta += jQuery.css( elem, box + cssExpand[ i ], true, styles ); + } + + // If we get here with a content-box, we're seeking "padding" or "border" or "margin" + if ( !isBorderBox ) { + + // Add padding + delta += jQuery.css( elem, "padding" + cssExpand[ i ], true, styles ); + + // For "border" or "margin", add border + if ( box !== "padding" ) { + delta += jQuery.css( elem, "border" + cssExpand[ i ] + "Width", true, styles ); + + // But still keep track of it otherwise + } else { + extra += jQuery.css( elem, "border" + cssExpand[ i ] + "Width", true, styles ); + } + + // If we get here with a border-box (content + padding + border), we're seeking "content" or + // "padding" or "margin" + } else { + + // For "content", subtract padding + if ( box === "content" ) { + delta -= jQuery.css( elem, "padding" + cssExpand[ i ], true, styles ); + } + + // For "content" or "padding", subtract border + if ( box !== "margin" ) { + delta -= jQuery.css( elem, "border" + cssExpand[ i ] + "Width", true, styles ); + } + } + } + + // Account for positive content-box scroll gutter when requested by providing computedVal + if ( !isBorderBox && computedVal >= 0 ) { + + // offsetWidth/offsetHeight is a rounded sum of content, padding, scroll gutter, and border + // Assuming integer scroll gutter, subtract the rest and round down + delta += Math.max( 0, Math.ceil( + elem[ "offset" + dimension[ 0 ].toUpperCase() + dimension.slice( 1 ) ] - + computedVal - + delta - + extra - + 0.5 + + // If offsetWidth/offsetHeight is unknown, then we can't determine content-box scroll gutter + // Use an explicit zero to avoid NaN (gh-3964) + ) ) || 0; + } + + return delta; +} + +function getWidthOrHeight( elem, dimension, extra ) { + + // Start with computed style + var styles = getStyles( elem ), + + // To avoid forcing a reflow, only fetch boxSizing if we need it (gh-4322). + // Fake content-box until we know it's needed to know the true value. + boxSizingNeeded = !support.boxSizingReliable() || extra, + isBorderBox = boxSizingNeeded && + jQuery.css( elem, "boxSizing", false, styles ) === "border-box", + valueIsBorderBox = isBorderBox, + + val = curCSS( elem, dimension, styles ), + offsetProp = "offset" + dimension[ 0 ].toUpperCase() + dimension.slice( 1 ); + + // Support: Firefox <=54 + // Return a confounding non-pixel value or feign ignorance, as appropriate. + if ( rnumnonpx.test( val ) ) { + if ( !extra ) { + return val; + } + val = "auto"; + } + + + // Support: IE 9 - 11 only + // Use offsetWidth/offsetHeight for when box sizing is unreliable. + // In those cases, the computed value can be trusted to be border-box. + if ( ( !support.boxSizingReliable() && isBorderBox || + + // Support: IE 10 - 11+, Edge 15 - 18+ + // IE/Edge misreport `getComputedStyle` of table rows with width/height + // set in CSS while `offset*` properties report correct values. + // Interestingly, in some cases IE 9 doesn't suffer from this issue. + !support.reliableTrDimensions() && nodeName( elem, "tr" ) || + + // Fall back to offsetWidth/offsetHeight when value is "auto" + // This happens for inline elements with no explicit setting (gh-3571) + val === "auto" || + + // Support: Android <=4.1 - 4.3 only + // Also use offsetWidth/offsetHeight for misreported inline dimensions (gh-3602) + !parseFloat( val ) && jQuery.css( elem, "display", false, styles ) === "inline" ) && + + // Make sure the element is visible & connected + elem.getClientRects().length ) { + + isBorderBox = jQuery.css( elem, "boxSizing", false, styles ) === "border-box"; + + // Where available, offsetWidth/offsetHeight approximate border box dimensions. + // Where not available (e.g., SVG), assume unreliable box-sizing and interpret the + // retrieved value as a content box dimension. + valueIsBorderBox = offsetProp in elem; + if ( valueIsBorderBox ) { + val = elem[ offsetProp ]; + } + } + + // Normalize "" and auto + val = parseFloat( val ) || 0; + + // Adjust for the element's box model + return ( val + + boxModelAdjustment( + elem, + dimension, + extra || ( isBorderBox ? "border" : "content" ), + valueIsBorderBox, + styles, + + // Provide the current computed size to request scroll gutter calculation (gh-3589) + val + ) + ) + "px"; +} + +jQuery.extend( { + + // Add in style property hooks for overriding the default + // behavior of getting and setting a style property + cssHooks: { + opacity: { + get: function( elem, computed ) { + if ( computed ) { + + // We should always get a number back from opacity + var ret = curCSS( elem, "opacity" ); + return ret === "" ? "1" : ret; + } + } + } + }, + + // Don't automatically add "px" to these possibly-unitless properties + cssNumber: { + "animationIterationCount": true, + "columnCount": true, + "fillOpacity": true, + "flexGrow": true, + "flexShrink": true, + "fontWeight": true, + "gridArea": true, + "gridColumn": true, + "gridColumnEnd": true, + "gridColumnStart": true, + "gridRow": true, + "gridRowEnd": true, + "gridRowStart": true, + "lineHeight": true, + "opacity": true, + "order": true, + "orphans": true, + "widows": true, + "zIndex": true, + "zoom": true + }, + + // Add in properties whose names you wish to fix before + // setting or getting the value + cssProps: {}, + + // Get and set the style property on a DOM Node + style: function( elem, name, value, extra ) { + + // Don't set styles on text and comment nodes + if ( !elem || elem.nodeType === 3 || elem.nodeType === 8 || !elem.style ) { + return; + } + + // Make sure that we're working with the right name + var ret, type, hooks, + origName = camelCase( name ), + isCustomProp = rcustomProp.test( name ), + style = elem.style; + + // Make sure that we're working with the right name. We don't + // want to query the value if it is a CSS custom property + // since they are user-defined. + if ( !isCustomProp ) { + name = finalPropName( origName ); + } + + // Gets hook for the prefixed version, then unprefixed version + hooks = jQuery.cssHooks[ name ] || jQuery.cssHooks[ origName ]; + + // Check if we're setting a value + if ( value !== undefined ) { + type = typeof value; + + // Convert "+=" or "-=" to relative numbers (#7345) + if ( type === "string" && ( ret = rcssNum.exec( value ) ) && ret[ 1 ] ) { + value = adjustCSS( elem, name, ret ); + + // Fixes bug #9237 + type = "number"; + } + + // Make sure that null and NaN values aren't set (#7116) + if ( value == null || value !== value ) { + return; + } + + // If a number was passed in, add the unit (except for certain CSS properties) + // The isCustomProp check can be removed in jQuery 4.0 when we only auto-append + // "px" to a few hardcoded values. + if ( type === "number" && !isCustomProp ) { + value += ret && ret[ 3 ] || ( jQuery.cssNumber[ origName ] ? "" : "px" ); + } + + // background-* props affect original clone's values + if ( !support.clearCloneStyle && value === "" && name.indexOf( "background" ) === 0 ) { + style[ name ] = "inherit"; + } + + // If a hook was provided, use that value, otherwise just set the specified value + if ( !hooks || !( "set" in hooks ) || + ( value = hooks.set( elem, value, extra ) ) !== undefined ) { + + if ( isCustomProp ) { + style.setProperty( name, value ); + } else { + style[ name ] = value; + } + } + + } else { + + // If a hook was provided get the non-computed value from there + if ( hooks && "get" in hooks && + ( ret = hooks.get( elem, false, extra ) ) !== undefined ) { + + return ret; + } + + // Otherwise just get the value from the style object + return style[ name ]; + } + }, + + css: function( elem, name, extra, styles ) { + var val, num, hooks, + origName = camelCase( name ), + isCustomProp = rcustomProp.test( name ); + + // Make sure that we're working with the right name. We don't + // want to modify the value if it is a CSS custom property + // since they are user-defined. + if ( !isCustomProp ) { + name = finalPropName( origName ); + } + + // Try prefixed name followed by the unprefixed name + hooks = jQuery.cssHooks[ name ] || jQuery.cssHooks[ origName ]; + + // If a hook was provided get the computed value from there + if ( hooks && "get" in hooks ) { + val = hooks.get( elem, true, extra ); + } + + // Otherwise, if a way to get the computed value exists, use that + if ( val === undefined ) { + val = curCSS( elem, name, styles ); + } + + // Convert "normal" to computed value + if ( val === "normal" && name in cssNormalTransform ) { + val = cssNormalTransform[ name ]; + } + + // Make numeric if forced or a qualifier was provided and val looks numeric + if ( extra === "" || extra ) { + num = parseFloat( val ); + return extra === true || isFinite( num ) ? num || 0 : val; + } + + return val; + } +} ); + +jQuery.each( [ "height", "width" ], function( _i, dimension ) { + jQuery.cssHooks[ dimension ] = { + get: function( elem, computed, extra ) { + if ( computed ) { + + // Certain elements can have dimension info if we invisibly show them + // but it must have a current display style that would benefit + return rdisplayswap.test( jQuery.css( elem, "display" ) ) && + + // Support: Safari 8+ + // Table columns in Safari have non-zero offsetWidth & zero + // getBoundingClientRect().width unless display is changed. + // Support: IE <=11 only + // Running getBoundingClientRect on a disconnected node + // in IE throws an error. + ( !elem.getClientRects().length || !elem.getBoundingClientRect().width ) ? + swap( elem, cssShow, function() { + return getWidthOrHeight( elem, dimension, extra ); + } ) : + getWidthOrHeight( elem, dimension, extra ); + } + }, + + set: function( elem, value, extra ) { + var matches, + styles = getStyles( elem ), + + // Only read styles.position if the test has a chance to fail + // to avoid forcing a reflow. + scrollboxSizeBuggy = !support.scrollboxSize() && + styles.position === "absolute", + + // To avoid forcing a reflow, only fetch boxSizing if we need it (gh-3991) + boxSizingNeeded = scrollboxSizeBuggy || extra, + isBorderBox = boxSizingNeeded && + jQuery.css( elem, "boxSizing", false, styles ) === "border-box", + subtract = extra ? + boxModelAdjustment( + elem, + dimension, + extra, + isBorderBox, + styles + ) : + 0; + + // Account for unreliable border-box dimensions by comparing offset* to computed and + // faking a content-box to get border and padding (gh-3699) + if ( isBorderBox && scrollboxSizeBuggy ) { + subtract -= Math.ceil( + elem[ "offset" + dimension[ 0 ].toUpperCase() + dimension.slice( 1 ) ] - + parseFloat( styles[ dimension ] ) - + boxModelAdjustment( elem, dimension, "border", false, styles ) - + 0.5 + ); + } + + // Convert to pixels if value adjustment is needed + if ( subtract && ( matches = rcssNum.exec( value ) ) && + ( matches[ 3 ] || "px" ) !== "px" ) { + + elem.style[ dimension ] = value; + value = jQuery.css( elem, dimension ); + } + + return setPositiveNumber( elem, value, subtract ); + } + }; +} ); + +jQuery.cssHooks.marginLeft = addGetHookIf( support.reliableMarginLeft, + function( elem, computed ) { + if ( computed ) { + return ( parseFloat( curCSS( elem, "marginLeft" ) ) || + elem.getBoundingClientRect().left - + swap( elem, { marginLeft: 0 }, function() { + return elem.getBoundingClientRect().left; + } ) + ) + "px"; + } + } +); + +// These hooks are used by animate to expand properties +jQuery.each( { + margin: "", + padding: "", + border: "Width" +}, function( prefix, suffix ) { + jQuery.cssHooks[ prefix + suffix ] = { + expand: function( value ) { + var i = 0, + expanded = {}, + + // Assumes a single number if not a string + parts = typeof value === "string" ? value.split( " " ) : [ value ]; + + for ( ; i < 4; i++ ) { + expanded[ prefix + cssExpand[ i ] + suffix ] = + parts[ i ] || parts[ i - 2 ] || parts[ 0 ]; + } + + return expanded; + } + }; + + if ( prefix !== "margin" ) { + jQuery.cssHooks[ prefix + suffix ].set = setPositiveNumber; + } +} ); + +jQuery.fn.extend( { + css: function( name, value ) { + return access( this, function( elem, name, value ) { + var styles, len, + map = {}, + i = 0; + + if ( Array.isArray( name ) ) { + styles = getStyles( elem ); + len = name.length; + + for ( ; i < len; i++ ) { + map[ name[ i ] ] = jQuery.css( elem, name[ i ], false, styles ); + } + + return map; + } + + return value !== undefined ? + jQuery.style( elem, name, value ) : + jQuery.css( elem, name ); + }, name, value, arguments.length > 1 ); + } +} ); + + +function Tween( elem, options, prop, end, easing ) { + return new Tween.prototype.init( elem, options, prop, end, easing ); +} +jQuery.Tween = Tween; + +Tween.prototype = { + constructor: Tween, + init: function( elem, options, prop, end, easing, unit ) { + this.elem = elem; + this.prop = prop; + this.easing = easing || jQuery.easing._default; + this.options = options; + this.start = this.now = this.cur(); + this.end = end; + this.unit = unit || ( jQuery.cssNumber[ prop ] ? "" : "px" ); + }, + cur: function() { + var hooks = Tween.propHooks[ this.prop ]; + + return hooks && hooks.get ? + hooks.get( this ) : + Tween.propHooks._default.get( this ); + }, + run: function( percent ) { + var eased, + hooks = Tween.propHooks[ this.prop ]; + + if ( this.options.duration ) { + this.pos = eased = jQuery.easing[ this.easing ]( + percent, this.options.duration * percent, 0, 1, this.options.duration + ); + } else { + this.pos = eased = percent; + } + this.now = ( this.end - this.start ) * eased + this.start; + + if ( this.options.step ) { + this.options.step.call( this.elem, this.now, this ); + } + + if ( hooks && hooks.set ) { + hooks.set( this ); + } else { + Tween.propHooks._default.set( this ); + } + return this; + } +}; + +Tween.prototype.init.prototype = Tween.prototype; + +Tween.propHooks = { + _default: { + get: function( tween ) { + var result; + + // Use a property on the element directly when it is not a DOM element, + // or when there is no matching style property that exists. + if ( tween.elem.nodeType !== 1 || + tween.elem[ tween.prop ] != null && tween.elem.style[ tween.prop ] == null ) { + return tween.elem[ tween.prop ]; + } + + // Passing an empty string as a 3rd parameter to .css will automatically + // attempt a parseFloat and fallback to a string if the parse fails. + // Simple values such as "10px" are parsed to Float; + // complex values such as "rotate(1rad)" are returned as-is. + result = jQuery.css( tween.elem, tween.prop, "" ); + + // Empty strings, null, undefined and "auto" are converted to 0. + return !result || result === "auto" ? 0 : result; + }, + set: function( tween ) { + + // Use step hook for back compat. + // Use cssHook if its there. + // Use .style if available and use plain properties where available. + if ( jQuery.fx.step[ tween.prop ] ) { + jQuery.fx.step[ tween.prop ]( tween ); + } else if ( tween.elem.nodeType === 1 && ( + jQuery.cssHooks[ tween.prop ] || + tween.elem.style[ finalPropName( tween.prop ) ] != null ) ) { + jQuery.style( tween.elem, tween.prop, tween.now + tween.unit ); + } else { + tween.elem[ tween.prop ] = tween.now; + } + } + } +}; + +// Support: IE <=9 only +// Panic based approach to setting things on disconnected nodes +Tween.propHooks.scrollTop = Tween.propHooks.scrollLeft = { + set: function( tween ) { + if ( tween.elem.nodeType && tween.elem.parentNode ) { + tween.elem[ tween.prop ] = tween.now; + } + } +}; + +jQuery.easing = { + linear: function( p ) { + return p; + }, + swing: function( p ) { + return 0.5 - Math.cos( p * Math.PI ) / 2; + }, + _default: "swing" +}; + +jQuery.fx = Tween.prototype.init; + +// Back compat <1.8 extension point +jQuery.fx.step = {}; + + + + +var + fxNow, inProgress, + rfxtypes = /^(?:toggle|show|hide)$/, + rrun = /queueHooks$/; + +function schedule() { + if ( inProgress ) { + if ( document.hidden === false && window.requestAnimationFrame ) { + window.requestAnimationFrame( schedule ); + } else { + window.setTimeout( schedule, jQuery.fx.interval ); + } + + jQuery.fx.tick(); + } +} + +// Animations created synchronously will run synchronously +function createFxNow() { + window.setTimeout( function() { + fxNow = undefined; + } ); + return ( fxNow = Date.now() ); +} + +// Generate parameters to create a standard animation +function genFx( type, includeWidth ) { + var which, + i = 0, + attrs = { height: type }; + + // If we include width, step value is 1 to do all cssExpand values, + // otherwise step value is 2 to skip over Left and Right + includeWidth = includeWidth ? 1 : 0; + for ( ; i < 4; i += 2 - includeWidth ) { + which = cssExpand[ i ]; + attrs[ "margin" + which ] = attrs[ "padding" + which ] = type; + } + + if ( includeWidth ) { + attrs.opacity = attrs.width = type; + } + + return attrs; +} + +function createTween( value, prop, animation ) { + var tween, + collection = ( Animation.tweeners[ prop ] || [] ).concat( Animation.tweeners[ "*" ] ), + index = 0, + length = collection.length; + for ( ; index < length; index++ ) { + if ( ( tween = collection[ index ].call( animation, prop, value ) ) ) { + + // We're done with this property + return tween; + } + } +} + +function defaultPrefilter( elem, props, opts ) { + var prop, value, toggle, hooks, oldfire, propTween, restoreDisplay, display, + isBox = "width" in props || "height" in props, + anim = this, + orig = {}, + style = elem.style, + hidden = elem.nodeType && isHiddenWithinTree( elem ), + dataShow = dataPriv.get( elem, "fxshow" ); + + // Queue-skipping animations hijack the fx hooks + if ( !opts.queue ) { + hooks = jQuery._queueHooks( elem, "fx" ); + if ( hooks.unqueued == null ) { + hooks.unqueued = 0; + oldfire = hooks.empty.fire; + hooks.empty.fire = function() { + if ( !hooks.unqueued ) { + oldfire(); + } + }; + } + hooks.unqueued++; + + anim.always( function() { + + // Ensure the complete handler is called before this completes + anim.always( function() { + hooks.unqueued--; + if ( !jQuery.queue( elem, "fx" ).length ) { + hooks.empty.fire(); + } + } ); + } ); + } + + // Detect show/hide animations + for ( prop in props ) { + value = props[ prop ]; + if ( rfxtypes.test( value ) ) { + delete props[ prop ]; + toggle = toggle || value === "toggle"; + if ( value === ( hidden ? "hide" : "show" ) ) { + + // Pretend to be hidden if this is a "show" and + // there is still data from a stopped show/hide + if ( value === "show" && dataShow && dataShow[ prop ] !== undefined ) { + hidden = true; + + // Ignore all other no-op show/hide data + } else { + continue; + } + } + orig[ prop ] = dataShow && dataShow[ prop ] || jQuery.style( elem, prop ); + } + } + + // Bail out if this is a no-op like .hide().hide() + propTween = !jQuery.isEmptyObject( props ); + if ( !propTween && jQuery.isEmptyObject( orig ) ) { + return; + } + + // Restrict "overflow" and "display" styles during box animations + if ( isBox && elem.nodeType === 1 ) { + + // Support: IE <=9 - 11, Edge 12 - 15 + // Record all 3 overflow attributes because IE does not infer the shorthand + // from identically-valued overflowX and overflowY and Edge just mirrors + // the overflowX value there. + opts.overflow = [ style.overflow, style.overflowX, style.overflowY ]; + + // Identify a display type, preferring old show/hide data over the CSS cascade + restoreDisplay = dataShow && dataShow.display; + if ( restoreDisplay == null ) { + restoreDisplay = dataPriv.get( elem, "display" ); + } + display = jQuery.css( elem, "display" ); + if ( display === "none" ) { + if ( restoreDisplay ) { + display = restoreDisplay; + } else { + + // Get nonempty value(s) by temporarily forcing visibility + showHide( [ elem ], true ); + restoreDisplay = elem.style.display || restoreDisplay; + display = jQuery.css( elem, "display" ); + showHide( [ elem ] ); + } + } + + // Animate inline elements as inline-block + if ( display === "inline" || display === "inline-block" && restoreDisplay != null ) { + if ( jQuery.css( elem, "float" ) === "none" ) { + + // Restore the original display value at the end of pure show/hide animations + if ( !propTween ) { + anim.done( function() { + style.display = restoreDisplay; + } ); + if ( restoreDisplay == null ) { + display = style.display; + restoreDisplay = display === "none" ? "" : display; + } + } + style.display = "inline-block"; + } + } + } + + if ( opts.overflow ) { + style.overflow = "hidden"; + anim.always( function() { + style.overflow = opts.overflow[ 0 ]; + style.overflowX = opts.overflow[ 1 ]; + style.overflowY = opts.overflow[ 2 ]; + } ); + } + + // Implement show/hide animations + propTween = false; + for ( prop in orig ) { + + // General show/hide setup for this element animation + if ( !propTween ) { + if ( dataShow ) { + if ( "hidden" in dataShow ) { + hidden = dataShow.hidden; + } + } else { + dataShow = dataPriv.access( elem, "fxshow", { display: restoreDisplay } ); + } + + // Store hidden/visible for toggle so `.stop().toggle()` "reverses" + if ( toggle ) { + dataShow.hidden = !hidden; + } + + // Show elements before animating them + if ( hidden ) { + showHide( [ elem ], true ); + } + + /* eslint-disable no-loop-func */ + + anim.done( function() { + + /* eslint-enable no-loop-func */ + + // The final step of a "hide" animation is actually hiding the element + if ( !hidden ) { + showHide( [ elem ] ); + } + dataPriv.remove( elem, "fxshow" ); + for ( prop in orig ) { + jQuery.style( elem, prop, orig[ prop ] ); + } + } ); + } + + // Per-property setup + propTween = createTween( hidden ? dataShow[ prop ] : 0, prop, anim ); + if ( !( prop in dataShow ) ) { + dataShow[ prop ] = propTween.start; + if ( hidden ) { + propTween.end = propTween.start; + propTween.start = 0; + } + } + } +} + +function propFilter( props, specialEasing ) { + var index, name, easing, value, hooks; + + // camelCase, specialEasing and expand cssHook pass + for ( index in props ) { + name = camelCase( index ); + easing = specialEasing[ name ]; + value = props[ index ]; + if ( Array.isArray( value ) ) { + easing = value[ 1 ]; + value = props[ index ] = value[ 0 ]; + } + + if ( index !== name ) { + props[ name ] = value; + delete props[ index ]; + } + + hooks = jQuery.cssHooks[ name ]; + if ( hooks && "expand" in hooks ) { + value = hooks.expand( value ); + delete props[ name ]; + + // Not quite $.extend, this won't overwrite existing keys. + // Reusing 'index' because we have the correct "name" + for ( index in value ) { + if ( !( index in props ) ) { + props[ index ] = value[ index ]; + specialEasing[ index ] = easing; + } + } + } else { + specialEasing[ name ] = easing; + } + } +} + +function Animation( elem, properties, options ) { + var result, + stopped, + index = 0, + length = Animation.prefilters.length, + deferred = jQuery.Deferred().always( function() { + + // Don't match elem in the :animated selector + delete tick.elem; + } ), + tick = function() { + if ( stopped ) { + return false; + } + var currentTime = fxNow || createFxNow(), + remaining = Math.max( 0, animation.startTime + animation.duration - currentTime ), + + // Support: Android 2.3 only + // Archaic crash bug won't allow us to use `1 - ( 0.5 || 0 )` (#12497) + temp = remaining / animation.duration || 0, + percent = 1 - temp, + index = 0, + length = animation.tweens.length; + + for ( ; index < length; index++ ) { + animation.tweens[ index ].run( percent ); + } + + deferred.notifyWith( elem, [ animation, percent, remaining ] ); + + // If there's more to do, yield + if ( percent < 1 && length ) { + return remaining; + } + + // If this was an empty animation, synthesize a final progress notification + if ( !length ) { + deferred.notifyWith( elem, [ animation, 1, 0 ] ); + } + + // Resolve the animation and report its conclusion + deferred.resolveWith( elem, [ animation ] ); + return false; + }, + animation = deferred.promise( { + elem: elem, + props: jQuery.extend( {}, properties ), + opts: jQuery.extend( true, { + specialEasing: {}, + easing: jQuery.easing._default + }, options ), + originalProperties: properties, + originalOptions: options, + startTime: fxNow || createFxNow(), + duration: options.duration, + tweens: [], + createTween: function( prop, end ) { + var tween = jQuery.Tween( elem, animation.opts, prop, end, + animation.opts.specialEasing[ prop ] || animation.opts.easing ); + animation.tweens.push( tween ); + return tween; + }, + stop: function( gotoEnd ) { + var index = 0, + + // If we are going to the end, we want to run all the tweens + // otherwise we skip this part + length = gotoEnd ? animation.tweens.length : 0; + if ( stopped ) { + return this; + } + stopped = true; + for ( ; index < length; index++ ) { + animation.tweens[ index ].run( 1 ); + } + + // Resolve when we played the last frame; otherwise, reject + if ( gotoEnd ) { + deferred.notifyWith( elem, [ animation, 1, 0 ] ); + deferred.resolveWith( elem, [ animation, gotoEnd ] ); + } else { + deferred.rejectWith( elem, [ animation, gotoEnd ] ); + } + return this; + } + } ), + props = animation.props; + + propFilter( props, animation.opts.specialEasing ); + + for ( ; index < length; index++ ) { + result = Animation.prefilters[ index ].call( animation, elem, props, animation.opts ); + if ( result ) { + if ( isFunction( result.stop ) ) { + jQuery._queueHooks( animation.elem, animation.opts.queue ).stop = + result.stop.bind( result ); + } + return result; + } + } + + jQuery.map( props, createTween, animation ); + + if ( isFunction( animation.opts.start ) ) { + animation.opts.start.call( elem, animation ); + } + + // Attach callbacks from options + animation + .progress( animation.opts.progress ) + .done( animation.opts.done, animation.opts.complete ) + .fail( animation.opts.fail ) + .always( animation.opts.always ); + + jQuery.fx.timer( + jQuery.extend( tick, { + elem: elem, + anim: animation, + queue: animation.opts.queue + } ) + ); + + return animation; +} + +jQuery.Animation = jQuery.extend( Animation, { + + tweeners: { + "*": [ function( prop, value ) { + var tween = this.createTween( prop, value ); + adjustCSS( tween.elem, prop, rcssNum.exec( value ), tween ); + return tween; + } ] + }, + + tweener: function( props, callback ) { + if ( isFunction( props ) ) { + callback = props; + props = [ "*" ]; + } else { + props = props.match( rnothtmlwhite ); + } + + var prop, + index = 0, + length = props.length; + + for ( ; index < length; index++ ) { + prop = props[ index ]; + Animation.tweeners[ prop ] = Animation.tweeners[ prop ] || []; + Animation.tweeners[ prop ].unshift( callback ); + } + }, + + prefilters: [ defaultPrefilter ], + + prefilter: function( callback, prepend ) { + if ( prepend ) { + Animation.prefilters.unshift( callback ); + } else { + Animation.prefilters.push( callback ); + } + } +} ); + +jQuery.speed = function( speed, easing, fn ) { + var opt = speed && typeof speed === "object" ? jQuery.extend( {}, speed ) : { + complete: fn || !fn && easing || + isFunction( speed ) && speed, + duration: speed, + easing: fn && easing || easing && !isFunction( easing ) && easing + }; + + // Go to the end state if fx are off + if ( jQuery.fx.off ) { + opt.duration = 0; + + } else { + if ( typeof opt.duration !== "number" ) { + if ( opt.duration in jQuery.fx.speeds ) { + opt.duration = jQuery.fx.speeds[ opt.duration ]; + + } else { + opt.duration = jQuery.fx.speeds._default; + } + } + } + + // Normalize opt.queue - true/undefined/null -> "fx" + if ( opt.queue == null || opt.queue === true ) { + opt.queue = "fx"; + } + + // Queueing + opt.old = opt.complete; + + opt.complete = function() { + if ( isFunction( opt.old ) ) { + opt.old.call( this ); + } + + if ( opt.queue ) { + jQuery.dequeue( this, opt.queue ); + } + }; + + return opt; +}; + +jQuery.fn.extend( { + fadeTo: function( speed, to, easing, callback ) { + + // Show any hidden elements after setting opacity to 0 + return this.filter( isHiddenWithinTree ).css( "opacity", 0 ).show() + + // Animate to the value specified + .end().animate( { opacity: to }, speed, easing, callback ); + }, + animate: function( prop, speed, easing, callback ) { + var empty = jQuery.isEmptyObject( prop ), + optall = jQuery.speed( speed, easing, callback ), + doAnimation = function() { + + // Operate on a copy of prop so per-property easing won't be lost + var anim = Animation( this, jQuery.extend( {}, prop ), optall ); + + // Empty animations, or finishing resolves immediately + if ( empty || dataPriv.get( this, "finish" ) ) { + anim.stop( true ); + } + }; + + doAnimation.finish = doAnimation; + + return empty || optall.queue === false ? + this.each( doAnimation ) : + this.queue( optall.queue, doAnimation ); + }, + stop: function( type, clearQueue, gotoEnd ) { + var stopQueue = function( hooks ) { + var stop = hooks.stop; + delete hooks.stop; + stop( gotoEnd ); + }; + + if ( typeof type !== "string" ) { + gotoEnd = clearQueue; + clearQueue = type; + type = undefined; + } + if ( clearQueue ) { + this.queue( type || "fx", [] ); + } + + return this.each( function() { + var dequeue = true, + index = type != null && type + "queueHooks", + timers = jQuery.timers, + data = dataPriv.get( this ); + + if ( index ) { + if ( data[ index ] && data[ index ].stop ) { + stopQueue( data[ index ] ); + } + } else { + for ( index in data ) { + if ( data[ index ] && data[ index ].stop && rrun.test( index ) ) { + stopQueue( data[ index ] ); + } + } + } + + for ( index = timers.length; index--; ) { + if ( timers[ index ].elem === this && + ( type == null || timers[ index ].queue === type ) ) { + + timers[ index ].anim.stop( gotoEnd ); + dequeue = false; + timers.splice( index, 1 ); + } + } + + // Start the next in the queue if the last step wasn't forced. + // Timers currently will call their complete callbacks, which + // will dequeue but only if they were gotoEnd. + if ( dequeue || !gotoEnd ) { + jQuery.dequeue( this, type ); + } + } ); + }, + finish: function( type ) { + if ( type !== false ) { + type = type || "fx"; + } + return this.each( function() { + var index, + data = dataPriv.get( this ), + queue = data[ type + "queue" ], + hooks = data[ type + "queueHooks" ], + timers = jQuery.timers, + length = queue ? queue.length : 0; + + // Enable finishing flag on private data + data.finish = true; + + // Empty the queue first + jQuery.queue( this, type, [] ); + + if ( hooks && hooks.stop ) { + hooks.stop.call( this, true ); + } + + // Look for any active animations, and finish them + for ( index = timers.length; index--; ) { + if ( timers[ index ].elem === this && timers[ index ].queue === type ) { + timers[ index ].anim.stop( true ); + timers.splice( index, 1 ); + } + } + + // Look for any animations in the old queue and finish them + for ( index = 0; index < length; index++ ) { + if ( queue[ index ] && queue[ index ].finish ) { + queue[ index ].finish.call( this ); + } + } + + // Turn off finishing flag + delete data.finish; + } ); + } +} ); + +jQuery.each( [ "toggle", "show", "hide" ], function( _i, name ) { + var cssFn = jQuery.fn[ name ]; + jQuery.fn[ name ] = function( speed, easing, callback ) { + return speed == null || typeof speed === "boolean" ? + cssFn.apply( this, arguments ) : + this.animate( genFx( name, true ), speed, easing, callback ); + }; +} ); + +// Generate shortcuts for custom animations +jQuery.each( { + slideDown: genFx( "show" ), + slideUp: genFx( "hide" ), + slideToggle: genFx( "toggle" ), + fadeIn: { opacity: "show" }, + fadeOut: { opacity: "hide" }, + fadeToggle: { opacity: "toggle" } +}, function( name, props ) { + jQuery.fn[ name ] = function( speed, easing, callback ) { + return this.animate( props, speed, easing, callback ); + }; +} ); + +jQuery.timers = []; +jQuery.fx.tick = function() { + var timer, + i = 0, + timers = jQuery.timers; + + fxNow = Date.now(); + + for ( ; i < timers.length; i++ ) { + timer = timers[ i ]; + + // Run the timer and safely remove it when done (allowing for external removal) + if ( !timer() && timers[ i ] === timer ) { + timers.splice( i--, 1 ); + } + } + + if ( !timers.length ) { + jQuery.fx.stop(); + } + fxNow = undefined; +}; + +jQuery.fx.timer = function( timer ) { + jQuery.timers.push( timer ); + jQuery.fx.start(); +}; + +jQuery.fx.interval = 13; +jQuery.fx.start = function() { + if ( inProgress ) { + return; + } + + inProgress = true; + schedule(); +}; + +jQuery.fx.stop = function() { + inProgress = null; +}; + +jQuery.fx.speeds = { + slow: 600, + fast: 200, + + // Default speed + _default: 400 +}; + + +// Based off of the plugin by Clint Helfers, with permission. +// https://web.archive.org/web/20100324014747/http://blindsignals.com/index.php/2009/07/jquery-delay/ +jQuery.fn.delay = function( time, type ) { + time = jQuery.fx ? jQuery.fx.speeds[ time ] || time : time; + type = type || "fx"; + + return this.queue( type, function( next, hooks ) { + var timeout = window.setTimeout( next, time ); + hooks.stop = function() { + window.clearTimeout( timeout ); + }; + } ); +}; + + +( function() { + var input = document.createElement( "input" ), + select = document.createElement( "select" ), + opt = select.appendChild( document.createElement( "option" ) ); + + input.type = "checkbox"; + + // Support: Android <=4.3 only + // Default value for a checkbox should be "on" + support.checkOn = input.value !== ""; + + // Support: IE <=11 only + // Must access selectedIndex to make default options select + support.optSelected = opt.selected; + + // Support: IE <=11 only + // An input loses its value after becoming a radio + input = document.createElement( "input" ); + input.value = "t"; + input.type = "radio"; + support.radioValue = input.value === "t"; +} )(); + + +var boolHook, + attrHandle = jQuery.expr.attrHandle; + +jQuery.fn.extend( { + attr: function( name, value ) { + return access( this, jQuery.attr, name, value, arguments.length > 1 ); + }, + + removeAttr: function( name ) { + return this.each( function() { + jQuery.removeAttr( this, name ); + } ); + } +} ); + +jQuery.extend( { + attr: function( elem, name, value ) { + var ret, hooks, + nType = elem.nodeType; + + // Don't get/set attributes on text, comment and attribute nodes + if ( nType === 3 || nType === 8 || nType === 2 ) { + return; + } + + // Fallback to prop when attributes are not supported + if ( typeof elem.getAttribute === "undefined" ) { + return jQuery.prop( elem, name, value ); + } + + // Attribute hooks are determined by the lowercase version + // Grab necessary hook if one is defined + if ( nType !== 1 || !jQuery.isXMLDoc( elem ) ) { + hooks = jQuery.attrHooks[ name.toLowerCase() ] || + ( jQuery.expr.match.bool.test( name ) ? boolHook : undefined ); + } + + if ( value !== undefined ) { + if ( value === null ) { + jQuery.removeAttr( elem, name ); + return; + } + + if ( hooks && "set" in hooks && + ( ret = hooks.set( elem, value, name ) ) !== undefined ) { + return ret; + } + + elem.setAttribute( name, value + "" ); + return value; + } + + if ( hooks && "get" in hooks && ( ret = hooks.get( elem, name ) ) !== null ) { + return ret; + } + + ret = jQuery.find.attr( elem, name ); + + // Non-existent attributes return null, we normalize to undefined + return ret == null ? undefined : ret; + }, + + attrHooks: { + type: { + set: function( elem, value ) { + if ( !support.radioValue && value === "radio" && + nodeName( elem, "input" ) ) { + var val = elem.value; + elem.setAttribute( "type", value ); + if ( val ) { + elem.value = val; + } + return value; + } + } + } + }, + + removeAttr: function( elem, value ) { + var name, + i = 0, + + // Attribute names can contain non-HTML whitespace characters + // https://html.spec.whatwg.org/multipage/syntax.html#attributes-2 + attrNames = value && value.match( rnothtmlwhite ); + + if ( attrNames && elem.nodeType === 1 ) { + while ( ( name = attrNames[ i++ ] ) ) { + elem.removeAttribute( name ); + } + } + } +} ); + +// Hooks for boolean attributes +boolHook = { + set: function( elem, value, name ) { + if ( value === false ) { + + // Remove boolean attributes when set to false + jQuery.removeAttr( elem, name ); + } else { + elem.setAttribute( name, name ); + } + return name; + } +}; + +jQuery.each( jQuery.expr.match.bool.source.match( /\w+/g ), function( _i, name ) { + var getter = attrHandle[ name ] || jQuery.find.attr; + + attrHandle[ name ] = function( elem, name, isXML ) { + var ret, handle, + lowercaseName = name.toLowerCase(); + + if ( !isXML ) { + + // Avoid an infinite loop by temporarily removing this function from the getter + handle = attrHandle[ lowercaseName ]; + attrHandle[ lowercaseName ] = ret; + ret = getter( elem, name, isXML ) != null ? + lowercaseName : + null; + attrHandle[ lowercaseName ] = handle; + } + return ret; + }; +} ); + + + + +var rfocusable = /^(?:input|select|textarea|button)$/i, + rclickable = /^(?:a|area)$/i; + +jQuery.fn.extend( { + prop: function( name, value ) { + return access( this, jQuery.prop, name, value, arguments.length > 1 ); + }, + + removeProp: function( name ) { + return this.each( function() { + delete this[ jQuery.propFix[ name ] || name ]; + } ); + } +} ); + +jQuery.extend( { + prop: function( elem, name, value ) { + var ret, hooks, + nType = elem.nodeType; + + // Don't get/set properties on text, comment and attribute nodes + if ( nType === 3 || nType === 8 || nType === 2 ) { + return; + } + + if ( nType !== 1 || !jQuery.isXMLDoc( elem ) ) { + + // Fix name and attach hooks + name = jQuery.propFix[ name ] || name; + hooks = jQuery.propHooks[ name ]; + } + + if ( value !== undefined ) { + if ( hooks && "set" in hooks && + ( ret = hooks.set( elem, value, name ) ) !== undefined ) { + return ret; + } + + return ( elem[ name ] = value ); + } + + if ( hooks && "get" in hooks && ( ret = hooks.get( elem, name ) ) !== null ) { + return ret; + } + + return elem[ name ]; + }, + + propHooks: { + tabIndex: { + get: function( elem ) { + + // Support: IE <=9 - 11 only + // elem.tabIndex doesn't always return the + // correct value when it hasn't been explicitly set + // https://web.archive.org/web/20141116233347/http://fluidproject.org/blog/2008/01/09/getting-setting-and-removing-tabindex-values-with-javascript/ + // Use proper attribute retrieval(#12072) + var tabindex = jQuery.find.attr( elem, "tabindex" ); + + if ( tabindex ) { + return parseInt( tabindex, 10 ); + } + + if ( + rfocusable.test( elem.nodeName ) || + rclickable.test( elem.nodeName ) && + elem.href + ) { + return 0; + } + + return -1; + } + } + }, + + propFix: { + "for": "htmlFor", + "class": "className" + } +} ); + +// Support: IE <=11 only +// Accessing the selectedIndex property +// forces the browser to respect setting selected +// on the option +// The getter ensures a default option is selected +// when in an optgroup +// eslint rule "no-unused-expressions" is disabled for this code +// since it considers such accessions noop +if ( !support.optSelected ) { + jQuery.propHooks.selected = { + get: function( elem ) { + + /* eslint no-unused-expressions: "off" */ + + var parent = elem.parentNode; + if ( parent && parent.parentNode ) { + parent.parentNode.selectedIndex; + } + return null; + }, + set: function( elem ) { + + /* eslint no-unused-expressions: "off" */ + + var parent = elem.parentNode; + if ( parent ) { + parent.selectedIndex; + + if ( parent.parentNode ) { + parent.parentNode.selectedIndex; + } + } + } + }; +} + +jQuery.each( [ + "tabIndex", + "readOnly", + "maxLength", + "cellSpacing", + "cellPadding", + "rowSpan", + "colSpan", + "useMap", + "frameBorder", + "contentEditable" +], function() { + jQuery.propFix[ this.toLowerCase() ] = this; +} ); + + + + + // Strip and collapse whitespace according to HTML spec + // https://infra.spec.whatwg.org/#strip-and-collapse-ascii-whitespace + function stripAndCollapse( value ) { + var tokens = value.match( rnothtmlwhite ) || []; + return tokens.join( " " ); + } + + +function getClass( elem ) { + return elem.getAttribute && elem.getAttribute( "class" ) || ""; +} + +function classesToArray( value ) { + if ( Array.isArray( value ) ) { + return value; + } + if ( typeof value === "string" ) { + return value.match( rnothtmlwhite ) || []; + } + return []; +} + +jQuery.fn.extend( { + addClass: function( value ) { + var classes, elem, cur, curValue, clazz, j, finalValue, + i = 0; + + if ( isFunction( value ) ) { + return this.each( function( j ) { + jQuery( this ).addClass( value.call( this, j, getClass( this ) ) ); + } ); + } + + classes = classesToArray( value ); + + if ( classes.length ) { + while ( ( elem = this[ i++ ] ) ) { + curValue = getClass( elem ); + cur = elem.nodeType === 1 && ( " " + stripAndCollapse( curValue ) + " " ); + + if ( cur ) { + j = 0; + while ( ( clazz = classes[ j++ ] ) ) { + if ( cur.indexOf( " " + clazz + " " ) < 0 ) { + cur += clazz + " "; + } + } + + // Only assign if different to avoid unneeded rendering. + finalValue = stripAndCollapse( cur ); + if ( curValue !== finalValue ) { + elem.setAttribute( "class", finalValue ); + } + } + } + } + + return this; + }, + + removeClass: function( value ) { + var classes, elem, cur, curValue, clazz, j, finalValue, + i = 0; + + if ( isFunction( value ) ) { + return this.each( function( j ) { + jQuery( this ).removeClass( value.call( this, j, getClass( this ) ) ); + } ); + } + + if ( !arguments.length ) { + return this.attr( "class", "" ); + } + + classes = classesToArray( value ); + + if ( classes.length ) { + while ( ( elem = this[ i++ ] ) ) { + curValue = getClass( elem ); + + // This expression is here for better compressibility (see addClass) + cur = elem.nodeType === 1 && ( " " + stripAndCollapse( curValue ) + " " ); + + if ( cur ) { + j = 0; + while ( ( clazz = classes[ j++ ] ) ) { + + // Remove *all* instances + while ( cur.indexOf( " " + clazz + " " ) > -1 ) { + cur = cur.replace( " " + clazz + " ", " " ); + } + } + + // Only assign if different to avoid unneeded rendering. + finalValue = stripAndCollapse( cur ); + if ( curValue !== finalValue ) { + elem.setAttribute( "class", finalValue ); + } + } + } + } + + return this; + }, + + toggleClass: function( value, stateVal ) { + var type = typeof value, + isValidValue = type === "string" || Array.isArray( value ); + + if ( typeof stateVal === "boolean" && isValidValue ) { + return stateVal ? this.addClass( value ) : this.removeClass( value ); + } + + if ( isFunction( value ) ) { + return this.each( function( i ) { + jQuery( this ).toggleClass( + value.call( this, i, getClass( this ), stateVal ), + stateVal + ); + } ); + } + + return this.each( function() { + var className, i, self, classNames; + + if ( isValidValue ) { + + // Toggle individual class names + i = 0; + self = jQuery( this ); + classNames = classesToArray( value ); + + while ( ( className = classNames[ i++ ] ) ) { + + // Check each className given, space separated list + if ( self.hasClass( className ) ) { + self.removeClass( className ); + } else { + self.addClass( className ); + } + } + + // Toggle whole class name + } else if ( value === undefined || type === "boolean" ) { + className = getClass( this ); + if ( className ) { + + // Store className if set + dataPriv.set( this, "__className__", className ); + } + + // If the element has a class name or if we're passed `false`, + // then remove the whole classname (if there was one, the above saved it). + // Otherwise bring back whatever was previously saved (if anything), + // falling back to the empty string if nothing was stored. + if ( this.setAttribute ) { + this.setAttribute( "class", + className || value === false ? + "" : + dataPriv.get( this, "__className__" ) || "" + ); + } + } + } ); + }, + + hasClass: function( selector ) { + var className, elem, + i = 0; + + className = " " + selector + " "; + while ( ( elem = this[ i++ ] ) ) { + if ( elem.nodeType === 1 && + ( " " + stripAndCollapse( getClass( elem ) ) + " " ).indexOf( className ) > -1 ) { + return true; + } + } + + return false; + } +} ); + + + + +var rreturn = /\r/g; + +jQuery.fn.extend( { + val: function( value ) { + var hooks, ret, valueIsFunction, + elem = this[ 0 ]; + + if ( !arguments.length ) { + if ( elem ) { + hooks = jQuery.valHooks[ elem.type ] || + jQuery.valHooks[ elem.nodeName.toLowerCase() ]; + + if ( hooks && + "get" in hooks && + ( ret = hooks.get( elem, "value" ) ) !== undefined + ) { + return ret; + } + + ret = elem.value; + + // Handle most common string cases + if ( typeof ret === "string" ) { + return ret.replace( rreturn, "" ); + } + + // Handle cases where value is null/undef or number + return ret == null ? "" : ret; + } + + return; + } + + valueIsFunction = isFunction( value ); + + return this.each( function( i ) { + var val; + + if ( this.nodeType !== 1 ) { + return; + } + + if ( valueIsFunction ) { + val = value.call( this, i, jQuery( this ).val() ); + } else { + val = value; + } + + // Treat null/undefined as ""; convert numbers to string + if ( val == null ) { + val = ""; + + } else if ( typeof val === "number" ) { + val += ""; + + } else if ( Array.isArray( val ) ) { + val = jQuery.map( val, function( value ) { + return value == null ? "" : value + ""; + } ); + } + + hooks = jQuery.valHooks[ this.type ] || jQuery.valHooks[ this.nodeName.toLowerCase() ]; + + // If set returns undefined, fall back to normal setting + if ( !hooks || !( "set" in hooks ) || hooks.set( this, val, "value" ) === undefined ) { + this.value = val; + } + } ); + } +} ); + +jQuery.extend( { + valHooks: { + option: { + get: function( elem ) { + + var val = jQuery.find.attr( elem, "value" ); + return val != null ? + val : + + // Support: IE <=10 - 11 only + // option.text throws exceptions (#14686, #14858) + // Strip and collapse whitespace + // https://html.spec.whatwg.org/#strip-and-collapse-whitespace + stripAndCollapse( jQuery.text( elem ) ); + } + }, + select: { + get: function( elem ) { + var value, option, i, + options = elem.options, + index = elem.selectedIndex, + one = elem.type === "select-one", + values = one ? null : [], + max = one ? index + 1 : options.length; + + if ( index < 0 ) { + i = max; + + } else { + i = one ? index : 0; + } + + // Loop through all the selected options + for ( ; i < max; i++ ) { + option = options[ i ]; + + // Support: IE <=9 only + // IE8-9 doesn't update selected after form reset (#2551) + if ( ( option.selected || i === index ) && + + // Don't return options that are disabled or in a disabled optgroup + !option.disabled && + ( !option.parentNode.disabled || + !nodeName( option.parentNode, "optgroup" ) ) ) { + + // Get the specific value for the option + value = jQuery( option ).val(); + + // We don't need an array for one selects + if ( one ) { + return value; + } + + // Multi-Selects return an array + values.push( value ); + } + } + + return values; + }, + + set: function( elem, value ) { + var optionSet, option, + options = elem.options, + values = jQuery.makeArray( value ), + i = options.length; + + while ( i-- ) { + option = options[ i ]; + + /* eslint-disable no-cond-assign */ + + if ( option.selected = + jQuery.inArray( jQuery.valHooks.option.get( option ), values ) > -1 + ) { + optionSet = true; + } + + /* eslint-enable no-cond-assign */ + } + + // Force browsers to behave consistently when non-matching value is set + if ( !optionSet ) { + elem.selectedIndex = -1; + } + return values; + } + } + } +} ); + +// Radios and checkboxes getter/setter +jQuery.each( [ "radio", "checkbox" ], function() { + jQuery.valHooks[ this ] = { + set: function( elem, value ) { + if ( Array.isArray( value ) ) { + return ( elem.checked = jQuery.inArray( jQuery( elem ).val(), value ) > -1 ); + } + } + }; + if ( !support.checkOn ) { + jQuery.valHooks[ this ].get = function( elem ) { + return elem.getAttribute( "value" ) === null ? "on" : elem.value; + }; + } +} ); + + + + +// Return jQuery for attributes-only inclusion + + +support.focusin = "onfocusin" in window; + + +var rfocusMorph = /^(?:focusinfocus|focusoutblur)$/, + stopPropagationCallback = function( e ) { + e.stopPropagation(); + }; + +jQuery.extend( jQuery.event, { + + trigger: function( event, data, elem, onlyHandlers ) { + + var i, cur, tmp, bubbleType, ontype, handle, special, lastElement, + eventPath = [ elem || document ], + type = hasOwn.call( event, "type" ) ? event.type : event, + namespaces = hasOwn.call( event, "namespace" ) ? event.namespace.split( "." ) : []; + + cur = lastElement = tmp = elem = elem || document; + + // Don't do events on text and comment nodes + if ( elem.nodeType === 3 || elem.nodeType === 8 ) { + return; + } + + // focus/blur morphs to focusin/out; ensure we're not firing them right now + if ( rfocusMorph.test( type + jQuery.event.triggered ) ) { + return; + } + + if ( type.indexOf( "." ) > -1 ) { + + // Namespaced trigger; create a regexp to match event type in handle() + namespaces = type.split( "." ); + type = namespaces.shift(); + namespaces.sort(); + } + ontype = type.indexOf( ":" ) < 0 && "on" + type; + + // Caller can pass in a jQuery.Event object, Object, or just an event type string + event = event[ jQuery.expando ] ? + event : + new jQuery.Event( type, typeof event === "object" && event ); + + // Trigger bitmask: & 1 for native handlers; & 2 for jQuery (always true) + event.isTrigger = onlyHandlers ? 2 : 3; + event.namespace = namespaces.join( "." ); + event.rnamespace = event.namespace ? + new RegExp( "(^|\\.)" + namespaces.join( "\\.(?:.*\\.|)" ) + "(\\.|$)" ) : + null; + + // Clean up the event in case it is being reused + event.result = undefined; + if ( !event.target ) { + event.target = elem; + } + + // Clone any incoming data and prepend the event, creating the handler arg list + data = data == null ? + [ event ] : + jQuery.makeArray( data, [ event ] ); + + // Allow special events to draw outside the lines + special = jQuery.event.special[ type ] || {}; + if ( !onlyHandlers && special.trigger && special.trigger.apply( elem, data ) === false ) { + return; + } + + // Determine event propagation path in advance, per W3C events spec (#9951) + // Bubble up to document, then to window; watch for a global ownerDocument var (#9724) + if ( !onlyHandlers && !special.noBubble && !isWindow( elem ) ) { + + bubbleType = special.delegateType || type; + if ( !rfocusMorph.test( bubbleType + type ) ) { + cur = cur.parentNode; + } + for ( ; cur; cur = cur.parentNode ) { + eventPath.push( cur ); + tmp = cur; + } + + // Only add window if we got to document (e.g., not plain obj or detached DOM) + if ( tmp === ( elem.ownerDocument || document ) ) { + eventPath.push( tmp.defaultView || tmp.parentWindow || window ); + } + } + + // Fire handlers on the event path + i = 0; + while ( ( cur = eventPath[ i++ ] ) && !event.isPropagationStopped() ) { + lastElement = cur; + event.type = i > 1 ? + bubbleType : + special.bindType || type; + + // jQuery handler + handle = ( dataPriv.get( cur, "events" ) || Object.create( null ) )[ event.type ] && + dataPriv.get( cur, "handle" ); + if ( handle ) { + handle.apply( cur, data ); + } + + // Native handler + handle = ontype && cur[ ontype ]; + if ( handle && handle.apply && acceptData( cur ) ) { + event.result = handle.apply( cur, data ); + if ( event.result === false ) { + event.preventDefault(); + } + } + } + event.type = type; + + // If nobody prevented the default action, do it now + if ( !onlyHandlers && !event.isDefaultPrevented() ) { + + if ( ( !special._default || + special._default.apply( eventPath.pop(), data ) === false ) && + acceptData( elem ) ) { + + // Call a native DOM method on the target with the same name as the event. + // Don't do default actions on window, that's where global variables be (#6170) + if ( ontype && isFunction( elem[ type ] ) && !isWindow( elem ) ) { + + // Don't re-trigger an onFOO event when we call its FOO() method + tmp = elem[ ontype ]; + + if ( tmp ) { + elem[ ontype ] = null; + } + + // Prevent re-triggering of the same event, since we already bubbled it above + jQuery.event.triggered = type; + + if ( event.isPropagationStopped() ) { + lastElement.addEventListener( type, stopPropagationCallback ); + } + + elem[ type ](); + + if ( event.isPropagationStopped() ) { + lastElement.removeEventListener( type, stopPropagationCallback ); + } + + jQuery.event.triggered = undefined; + + if ( tmp ) { + elem[ ontype ] = tmp; + } + } + } + } + + return event.result; + }, + + // Piggyback on a donor event to simulate a different one + // Used only for `focus(in | out)` events + simulate: function( type, elem, event ) { + var e = jQuery.extend( + new jQuery.Event(), + event, + { + type: type, + isSimulated: true + } + ); + + jQuery.event.trigger( e, null, elem ); + } + +} ); + +jQuery.fn.extend( { + + trigger: function( type, data ) { + return this.each( function() { + jQuery.event.trigger( type, data, this ); + } ); + }, + triggerHandler: function( type, data ) { + var elem = this[ 0 ]; + if ( elem ) { + return jQuery.event.trigger( type, data, elem, true ); + } + } +} ); + + +// Support: Firefox <=44 +// Firefox doesn't have focus(in | out) events +// Related ticket - https://bugzilla.mozilla.org/show_bug.cgi?id=687787 +// +// Support: Chrome <=48 - 49, Safari <=9.0 - 9.1 +// focus(in | out) events fire after focus & blur events, +// which is spec violation - http://www.w3.org/TR/DOM-Level-3-Events/#events-focusevent-event-order +// Related ticket - https://bugs.chromium.org/p/chromium/issues/detail?id=449857 +if ( !support.focusin ) { + jQuery.each( { focus: "focusin", blur: "focusout" }, function( orig, fix ) { + + // Attach a single capturing handler on the document while someone wants focusin/focusout + var handler = function( event ) { + jQuery.event.simulate( fix, event.target, jQuery.event.fix( event ) ); + }; + + jQuery.event.special[ fix ] = { + setup: function() { + + // Handle: regular nodes (via `this.ownerDocument`), window + // (via `this.document`) & document (via `this`). + var doc = this.ownerDocument || this.document || this, + attaches = dataPriv.access( doc, fix ); + + if ( !attaches ) { + doc.addEventListener( orig, handler, true ); + } + dataPriv.access( doc, fix, ( attaches || 0 ) + 1 ); + }, + teardown: function() { + var doc = this.ownerDocument || this.document || this, + attaches = dataPriv.access( doc, fix ) - 1; + + if ( !attaches ) { + doc.removeEventListener( orig, handler, true ); + dataPriv.remove( doc, fix ); + + } else { + dataPriv.access( doc, fix, attaches ); + } + } + }; + } ); +} +var location = window.location; + +var nonce = { guid: Date.now() }; + +var rquery = ( /\?/ ); + + + +// Cross-browser xml parsing +jQuery.parseXML = function( data ) { + var xml, parserErrorElem; + if ( !data || typeof data !== "string" ) { + return null; + } + + // Support: IE 9 - 11 only + // IE throws on parseFromString with invalid input. + try { + xml = ( new window.DOMParser() ).parseFromString( data, "text/xml" ); + } catch ( e ) {} + + parserErrorElem = xml && xml.getElementsByTagName( "parsererror" )[ 0 ]; + if ( !xml || parserErrorElem ) { + jQuery.error( "Invalid XML: " + ( + parserErrorElem ? + jQuery.map( parserErrorElem.childNodes, function( el ) { + return el.textContent; + } ).join( "\n" ) : + data + ) ); + } + return xml; +}; + + +var + rbracket = /\[\]$/, + rCRLF = /\r?\n/g, + rsubmitterTypes = /^(?:submit|button|image|reset|file)$/i, + rsubmittable = /^(?:input|select|textarea|keygen)/i; + +function buildParams( prefix, obj, traditional, add ) { + var name; + + if ( Array.isArray( obj ) ) { + + // Serialize array item. + jQuery.each( obj, function( i, v ) { + if ( traditional || rbracket.test( prefix ) ) { + + // Treat each array item as a scalar. + add( prefix, v ); + + } else { + + // Item is non-scalar (array or object), encode its numeric index. + buildParams( + prefix + "[" + ( typeof v === "object" && v != null ? i : "" ) + "]", + v, + traditional, + add + ); + } + } ); + + } else if ( !traditional && toType( obj ) === "object" ) { + + // Serialize object item. + for ( name in obj ) { + buildParams( prefix + "[" + name + "]", obj[ name ], traditional, add ); + } + + } else { + + // Serialize scalar item. + add( prefix, obj ); + } +} + +// Serialize an array of form elements or a set of +// key/values into a query string +jQuery.param = function( a, traditional ) { + var prefix, + s = [], + add = function( key, valueOrFunction ) { + + // If value is a function, invoke it and use its return value + var value = isFunction( valueOrFunction ) ? + valueOrFunction() : + valueOrFunction; + + s[ s.length ] = encodeURIComponent( key ) + "=" + + encodeURIComponent( value == null ? "" : value ); + }; + + if ( a == null ) { + return ""; + } + + // If an array was passed in, assume that it is an array of form elements. + if ( Array.isArray( a ) || ( a.jquery && !jQuery.isPlainObject( a ) ) ) { + + // Serialize the form elements + jQuery.each( a, function() { + add( this.name, this.value ); + } ); + + } else { + + // If traditional, encode the "old" way (the way 1.3.2 or older + // did it), otherwise encode params recursively. + for ( prefix in a ) { + buildParams( prefix, a[ prefix ], traditional, add ); + } + } + + // Return the resulting serialization + return s.join( "&" ); +}; + +jQuery.fn.extend( { + serialize: function() { + return jQuery.param( this.serializeArray() ); + }, + serializeArray: function() { + return this.map( function() { + + // Can add propHook for "elements" to filter or add form elements + var elements = jQuery.prop( this, "elements" ); + return elements ? jQuery.makeArray( elements ) : this; + } ).filter( function() { + var type = this.type; + + // Use .is( ":disabled" ) so that fieldset[disabled] works + return this.name && !jQuery( this ).is( ":disabled" ) && + rsubmittable.test( this.nodeName ) && !rsubmitterTypes.test( type ) && + ( this.checked || !rcheckableType.test( type ) ); + } ).map( function( _i, elem ) { + var val = jQuery( this ).val(); + + if ( val == null ) { + return null; + } + + if ( Array.isArray( val ) ) { + return jQuery.map( val, function( val ) { + return { name: elem.name, value: val.replace( rCRLF, "\r\n" ) }; + } ); + } + + return { name: elem.name, value: val.replace( rCRLF, "\r\n" ) }; + } ).get(); + } +} ); + + +var + r20 = /%20/g, + rhash = /#.*$/, + rantiCache = /([?&])_=[^&]*/, + rheaders = /^(.*?):[ \t]*([^\r\n]*)$/mg, + + // #7653, #8125, #8152: local protocol detection + rlocalProtocol = /^(?:about|app|app-storage|.+-extension|file|res|widget):$/, + rnoContent = /^(?:GET|HEAD)$/, + rprotocol = /^\/\//, + + /* Prefilters + * 1) They are useful to introduce custom dataTypes (see ajax/jsonp.js for an example) + * 2) These are called: + * - BEFORE asking for a transport + * - AFTER param serialization (s.data is a string if s.processData is true) + * 3) key is the dataType + * 4) the catchall symbol "*" can be used + * 5) execution will start with transport dataType and THEN continue down to "*" if needed + */ + prefilters = {}, + + /* Transports bindings + * 1) key is the dataType + * 2) the catchall symbol "*" can be used + * 3) selection will start with transport dataType and THEN go to "*" if needed + */ + transports = {}, + + // Avoid comment-prolog char sequence (#10098); must appease lint and evade compression + allTypes = "*/".concat( "*" ), + + // Anchor tag for parsing the document origin + originAnchor = document.createElement( "a" ); + +originAnchor.href = location.href; + +// Base "constructor" for jQuery.ajaxPrefilter and jQuery.ajaxTransport +function addToPrefiltersOrTransports( structure ) { + + // dataTypeExpression is optional and defaults to "*" + return function( dataTypeExpression, func ) { + + if ( typeof dataTypeExpression !== "string" ) { + func = dataTypeExpression; + dataTypeExpression = "*"; + } + + var dataType, + i = 0, + dataTypes = dataTypeExpression.toLowerCase().match( rnothtmlwhite ) || []; + + if ( isFunction( func ) ) { + + // For each dataType in the dataTypeExpression + while ( ( dataType = dataTypes[ i++ ] ) ) { + + // Prepend if requested + if ( dataType[ 0 ] === "+" ) { + dataType = dataType.slice( 1 ) || "*"; + ( structure[ dataType ] = structure[ dataType ] || [] ).unshift( func ); + + // Otherwise append + } else { + ( structure[ dataType ] = structure[ dataType ] || [] ).push( func ); + } + } + } + }; +} + +// Base inspection function for prefilters and transports +function inspectPrefiltersOrTransports( structure, options, originalOptions, jqXHR ) { + + var inspected = {}, + seekingTransport = ( structure === transports ); + + function inspect( dataType ) { + var selected; + inspected[ dataType ] = true; + jQuery.each( structure[ dataType ] || [], function( _, prefilterOrFactory ) { + var dataTypeOrTransport = prefilterOrFactory( options, originalOptions, jqXHR ); + if ( typeof dataTypeOrTransport === "string" && + !seekingTransport && !inspected[ dataTypeOrTransport ] ) { + + options.dataTypes.unshift( dataTypeOrTransport ); + inspect( dataTypeOrTransport ); + return false; + } else if ( seekingTransport ) { + return !( selected = dataTypeOrTransport ); + } + } ); + return selected; + } + + return inspect( options.dataTypes[ 0 ] ) || !inspected[ "*" ] && inspect( "*" ); +} + +// A special extend for ajax options +// that takes "flat" options (not to be deep extended) +// Fixes #9887 +function ajaxExtend( target, src ) { + var key, deep, + flatOptions = jQuery.ajaxSettings.flatOptions || {}; + + for ( key in src ) { + if ( src[ key ] !== undefined ) { + ( flatOptions[ key ] ? target : ( deep || ( deep = {} ) ) )[ key ] = src[ key ]; + } + } + if ( deep ) { + jQuery.extend( true, target, deep ); + } + + return target; +} + +/* Handles responses to an ajax request: + * - finds the right dataType (mediates between content-type and expected dataType) + * - returns the corresponding response + */ +function ajaxHandleResponses( s, jqXHR, responses ) { + + var ct, type, finalDataType, firstDataType, + contents = s.contents, + dataTypes = s.dataTypes; + + // Remove auto dataType and get content-type in the process + while ( dataTypes[ 0 ] === "*" ) { + dataTypes.shift(); + if ( ct === undefined ) { + ct = s.mimeType || jqXHR.getResponseHeader( "Content-Type" ); + } + } + + // Check if we're dealing with a known content-type + if ( ct ) { + for ( type in contents ) { + if ( contents[ type ] && contents[ type ].test( ct ) ) { + dataTypes.unshift( type ); + break; + } + } + } + + // Check to see if we have a response for the expected dataType + if ( dataTypes[ 0 ] in responses ) { + finalDataType = dataTypes[ 0 ]; + } else { + + // Try convertible dataTypes + for ( type in responses ) { + if ( !dataTypes[ 0 ] || s.converters[ type + " " + dataTypes[ 0 ] ] ) { + finalDataType = type; + break; + } + if ( !firstDataType ) { + firstDataType = type; + } + } + + // Or just use first one + finalDataType = finalDataType || firstDataType; + } + + // If we found a dataType + // We add the dataType to the list if needed + // and return the corresponding response + if ( finalDataType ) { + if ( finalDataType !== dataTypes[ 0 ] ) { + dataTypes.unshift( finalDataType ); + } + return responses[ finalDataType ]; + } +} + +/* Chain conversions given the request and the original response + * Also sets the responseXXX fields on the jqXHR instance + */ +function ajaxConvert( s, response, jqXHR, isSuccess ) { + var conv2, current, conv, tmp, prev, + converters = {}, + + // Work with a copy of dataTypes in case we need to modify it for conversion + dataTypes = s.dataTypes.slice(); + + // Create converters map with lowercased keys + if ( dataTypes[ 1 ] ) { + for ( conv in s.converters ) { + converters[ conv.toLowerCase() ] = s.converters[ conv ]; + } + } + + current = dataTypes.shift(); + + // Convert to each sequential dataType + while ( current ) { + + if ( s.responseFields[ current ] ) { + jqXHR[ s.responseFields[ current ] ] = response; + } + + // Apply the dataFilter if provided + if ( !prev && isSuccess && s.dataFilter ) { + response = s.dataFilter( response, s.dataType ); + } + + prev = current; + current = dataTypes.shift(); + + if ( current ) { + + // There's only work to do if current dataType is non-auto + if ( current === "*" ) { + + current = prev; + + // Convert response if prev dataType is non-auto and differs from current + } else if ( prev !== "*" && prev !== current ) { + + // Seek a direct converter + conv = converters[ prev + " " + current ] || converters[ "* " + current ]; + + // If none found, seek a pair + if ( !conv ) { + for ( conv2 in converters ) { + + // If conv2 outputs current + tmp = conv2.split( " " ); + if ( tmp[ 1 ] === current ) { + + // If prev can be converted to accepted input + conv = converters[ prev + " " + tmp[ 0 ] ] || + converters[ "* " + tmp[ 0 ] ]; + if ( conv ) { + + // Condense equivalence converters + if ( conv === true ) { + conv = converters[ conv2 ]; + + // Otherwise, insert the intermediate dataType + } else if ( converters[ conv2 ] !== true ) { + current = tmp[ 0 ]; + dataTypes.unshift( tmp[ 1 ] ); + } + break; + } + } + } + } + + // Apply converter (if not an equivalence) + if ( conv !== true ) { + + // Unless errors are allowed to bubble, catch and return them + if ( conv && s.throws ) { + response = conv( response ); + } else { + try { + response = conv( response ); + } catch ( e ) { + return { + state: "parsererror", + error: conv ? e : "No conversion from " + prev + " to " + current + }; + } + } + } + } + } + } + + return { state: "success", data: response }; +} + +jQuery.extend( { + + // Counter for holding the number of active queries + active: 0, + + // Last-Modified header cache for next request + lastModified: {}, + etag: {}, + + ajaxSettings: { + url: location.href, + type: "GET", + isLocal: rlocalProtocol.test( location.protocol ), + global: true, + processData: true, + async: true, + contentType: "application/x-www-form-urlencoded; charset=UTF-8", + + /* + timeout: 0, + data: null, + dataType: null, + username: null, + password: null, + cache: null, + throws: false, + traditional: false, + headers: {}, + */ + + accepts: { + "*": allTypes, + text: "text/plain", + html: "text/html", + xml: "application/xml, text/xml", + json: "application/json, text/javascript" + }, + + contents: { + xml: /\bxml\b/, + html: /\bhtml/, + json: /\bjson\b/ + }, + + responseFields: { + xml: "responseXML", + text: "responseText", + json: "responseJSON" + }, + + // Data converters + // Keys separate source (or catchall "*") and destination types with a single space + converters: { + + // Convert anything to text + "* text": String, + + // Text to html (true = no transformation) + "text html": true, + + // Evaluate text as a json expression + "text json": JSON.parse, + + // Parse text as xml + "text xml": jQuery.parseXML + }, + + // For options that shouldn't be deep extended: + // you can add your own custom options here if + // and when you create one that shouldn't be + // deep extended (see ajaxExtend) + flatOptions: { + url: true, + context: true + } + }, + + // Creates a full fledged settings object into target + // with both ajaxSettings and settings fields. + // If target is omitted, writes into ajaxSettings. + ajaxSetup: function( target, settings ) { + return settings ? + + // Building a settings object + ajaxExtend( ajaxExtend( target, jQuery.ajaxSettings ), settings ) : + + // Extending ajaxSettings + ajaxExtend( jQuery.ajaxSettings, target ); + }, + + ajaxPrefilter: addToPrefiltersOrTransports( prefilters ), + ajaxTransport: addToPrefiltersOrTransports( transports ), + + // Main method + ajax: function( url, options ) { + + // If url is an object, simulate pre-1.5 signature + if ( typeof url === "object" ) { + options = url; + url = undefined; + } + + // Force options to be an object + options = options || {}; + + var transport, + + // URL without anti-cache param + cacheURL, + + // Response headers + responseHeadersString, + responseHeaders, + + // timeout handle + timeoutTimer, + + // Url cleanup var + urlAnchor, + + // Request state (becomes false upon send and true upon completion) + completed, + + // To know if global events are to be dispatched + fireGlobals, + + // Loop variable + i, + + // uncached part of the url + uncached, + + // Create the final options object + s = jQuery.ajaxSetup( {}, options ), + + // Callbacks context + callbackContext = s.context || s, + + // Context for global events is callbackContext if it is a DOM node or jQuery collection + globalEventContext = s.context && + ( callbackContext.nodeType || callbackContext.jquery ) ? + jQuery( callbackContext ) : + jQuery.event, + + // Deferreds + deferred = jQuery.Deferred(), + completeDeferred = jQuery.Callbacks( "once memory" ), + + // Status-dependent callbacks + statusCode = s.statusCode || {}, + + // Headers (they are sent all at once) + requestHeaders = {}, + requestHeadersNames = {}, + + // Default abort message + strAbort = "canceled", + + // Fake xhr + jqXHR = { + readyState: 0, + + // Builds headers hashtable if needed + getResponseHeader: function( key ) { + var match; + if ( completed ) { + if ( !responseHeaders ) { + responseHeaders = {}; + while ( ( match = rheaders.exec( responseHeadersString ) ) ) { + responseHeaders[ match[ 1 ].toLowerCase() + " " ] = + ( responseHeaders[ match[ 1 ].toLowerCase() + " " ] || [] ) + .concat( match[ 2 ] ); + } + } + match = responseHeaders[ key.toLowerCase() + " " ]; + } + return match == null ? null : match.join( ", " ); + }, + + // Raw string + getAllResponseHeaders: function() { + return completed ? responseHeadersString : null; + }, + + // Caches the header + setRequestHeader: function( name, value ) { + if ( completed == null ) { + name = requestHeadersNames[ name.toLowerCase() ] = + requestHeadersNames[ name.toLowerCase() ] || name; + requestHeaders[ name ] = value; + } + return this; + }, + + // Overrides response content-type header + overrideMimeType: function( type ) { + if ( completed == null ) { + s.mimeType = type; + } + return this; + }, + + // Status-dependent callbacks + statusCode: function( map ) { + var code; + if ( map ) { + if ( completed ) { + + // Execute the appropriate callbacks + jqXHR.always( map[ jqXHR.status ] ); + } else { + + // Lazy-add the new callbacks in a way that preserves old ones + for ( code in map ) { + statusCode[ code ] = [ statusCode[ code ], map[ code ] ]; + } + } + } + return this; + }, + + // Cancel the request + abort: function( statusText ) { + var finalText = statusText || strAbort; + if ( transport ) { + transport.abort( finalText ); + } + done( 0, finalText ); + return this; + } + }; + + // Attach deferreds + deferred.promise( jqXHR ); + + // Add protocol if not provided (prefilters might expect it) + // Handle falsy url in the settings object (#10093: consistency with old signature) + // We also use the url parameter if available + s.url = ( ( url || s.url || location.href ) + "" ) + .replace( rprotocol, location.protocol + "//" ); + + // Alias method option to type as per ticket #12004 + s.type = options.method || options.type || s.method || s.type; + + // Extract dataTypes list + s.dataTypes = ( s.dataType || "*" ).toLowerCase().match( rnothtmlwhite ) || [ "" ]; + + // A cross-domain request is in order when the origin doesn't match the current origin. + if ( s.crossDomain == null ) { + urlAnchor = document.createElement( "a" ); + + // Support: IE <=8 - 11, Edge 12 - 15 + // IE throws exception on accessing the href property if url is malformed, + // e.g. http://example.com:80x/ + try { + urlAnchor.href = s.url; + + // Support: IE <=8 - 11 only + // Anchor's host property isn't correctly set when s.url is relative + urlAnchor.href = urlAnchor.href; + s.crossDomain = originAnchor.protocol + "//" + originAnchor.host !== + urlAnchor.protocol + "//" + urlAnchor.host; + } catch ( e ) { + + // If there is an error parsing the URL, assume it is crossDomain, + // it can be rejected by the transport if it is invalid + s.crossDomain = true; + } + } + + // Convert data if not already a string + if ( s.data && s.processData && typeof s.data !== "string" ) { + s.data = jQuery.param( s.data, s.traditional ); + } + + // Apply prefilters + inspectPrefiltersOrTransports( prefilters, s, options, jqXHR ); + + // If request was aborted inside a prefilter, stop there + if ( completed ) { + return jqXHR; + } + + // We can fire global events as of now if asked to + // Don't fire events if jQuery.event is undefined in an AMD-usage scenario (#15118) + fireGlobals = jQuery.event && s.global; + + // Watch for a new set of requests + if ( fireGlobals && jQuery.active++ === 0 ) { + jQuery.event.trigger( "ajaxStart" ); + } + + // Uppercase the type + s.type = s.type.toUpperCase(); + + // Determine if request has content + s.hasContent = !rnoContent.test( s.type ); + + // Save the URL in case we're toying with the If-Modified-Since + // and/or If-None-Match header later on + // Remove hash to simplify url manipulation + cacheURL = s.url.replace( rhash, "" ); + + // More options handling for requests with no content + if ( !s.hasContent ) { + + // Remember the hash so we can put it back + uncached = s.url.slice( cacheURL.length ); + + // If data is available and should be processed, append data to url + if ( s.data && ( s.processData || typeof s.data === "string" ) ) { + cacheURL += ( rquery.test( cacheURL ) ? "&" : "?" ) + s.data; + + // #9682: remove data so that it's not used in an eventual retry + delete s.data; + } + + // Add or update anti-cache param if needed + if ( s.cache === false ) { + cacheURL = cacheURL.replace( rantiCache, "$1" ); + uncached = ( rquery.test( cacheURL ) ? "&" : "?" ) + "_=" + ( nonce.guid++ ) + + uncached; + } + + // Put hash and anti-cache on the URL that will be requested (gh-1732) + s.url = cacheURL + uncached; + + // Change '%20' to '+' if this is encoded form body content (gh-2658) + } else if ( s.data && s.processData && + ( s.contentType || "" ).indexOf( "application/x-www-form-urlencoded" ) === 0 ) { + s.data = s.data.replace( r20, "+" ); + } + + // Set the If-Modified-Since and/or If-None-Match header, if in ifModified mode. + if ( s.ifModified ) { + if ( jQuery.lastModified[ cacheURL ] ) { + jqXHR.setRequestHeader( "If-Modified-Since", jQuery.lastModified[ cacheURL ] ); + } + if ( jQuery.etag[ cacheURL ] ) { + jqXHR.setRequestHeader( "If-None-Match", jQuery.etag[ cacheURL ] ); + } + } + + // Set the correct header, if data is being sent + if ( s.data && s.hasContent && s.contentType !== false || options.contentType ) { + jqXHR.setRequestHeader( "Content-Type", s.contentType ); + } + + // Set the Accepts header for the server, depending on the dataType + jqXHR.setRequestHeader( + "Accept", + s.dataTypes[ 0 ] && s.accepts[ s.dataTypes[ 0 ] ] ? + s.accepts[ s.dataTypes[ 0 ] ] + + ( s.dataTypes[ 0 ] !== "*" ? ", " + allTypes + "; q=0.01" : "" ) : + s.accepts[ "*" ] + ); + + // Check for headers option + for ( i in s.headers ) { + jqXHR.setRequestHeader( i, s.headers[ i ] ); + } + + // Allow custom headers/mimetypes and early abort + if ( s.beforeSend && + ( s.beforeSend.call( callbackContext, jqXHR, s ) === false || completed ) ) { + + // Abort if not done already and return + return jqXHR.abort(); + } + + // Aborting is no longer a cancellation + strAbort = "abort"; + + // Install callbacks on deferreds + completeDeferred.add( s.complete ); + jqXHR.done( s.success ); + jqXHR.fail( s.error ); + + // Get transport + transport = inspectPrefiltersOrTransports( transports, s, options, jqXHR ); + + // If no transport, we auto-abort + if ( !transport ) { + done( -1, "No Transport" ); + } else { + jqXHR.readyState = 1; + + // Send global event + if ( fireGlobals ) { + globalEventContext.trigger( "ajaxSend", [ jqXHR, s ] ); + } + + // If request was aborted inside ajaxSend, stop there + if ( completed ) { + return jqXHR; + } + + // Timeout + if ( s.async && s.timeout > 0 ) { + timeoutTimer = window.setTimeout( function() { + jqXHR.abort( "timeout" ); + }, s.timeout ); + } + + try { + completed = false; + transport.send( requestHeaders, done ); + } catch ( e ) { + + // Rethrow post-completion exceptions + if ( completed ) { + throw e; + } + + // Propagate others as results + done( -1, e ); + } + } + + // Callback for when everything is done + function done( status, nativeStatusText, responses, headers ) { + var isSuccess, success, error, response, modified, + statusText = nativeStatusText; + + // Ignore repeat invocations + if ( completed ) { + return; + } + + completed = true; + + // Clear timeout if it exists + if ( timeoutTimer ) { + window.clearTimeout( timeoutTimer ); + } + + // Dereference transport for early garbage collection + // (no matter how long the jqXHR object will be used) + transport = undefined; + + // Cache response headers + responseHeadersString = headers || ""; + + // Set readyState + jqXHR.readyState = status > 0 ? 4 : 0; + + // Determine if successful + isSuccess = status >= 200 && status < 300 || status === 304; + + // Get response data + if ( responses ) { + response = ajaxHandleResponses( s, jqXHR, responses ); + } + + // Use a noop converter for missing script but not if jsonp + if ( !isSuccess && + jQuery.inArray( "script", s.dataTypes ) > -1 && + jQuery.inArray( "json", s.dataTypes ) < 0 ) { + s.converters[ "text script" ] = function() {}; + } + + // Convert no matter what (that way responseXXX fields are always set) + response = ajaxConvert( s, response, jqXHR, isSuccess ); + + // If successful, handle type chaining + if ( isSuccess ) { + + // Set the If-Modified-Since and/or If-None-Match header, if in ifModified mode. + if ( s.ifModified ) { + modified = jqXHR.getResponseHeader( "Last-Modified" ); + if ( modified ) { + jQuery.lastModified[ cacheURL ] = modified; + } + modified = jqXHR.getResponseHeader( "etag" ); + if ( modified ) { + jQuery.etag[ cacheURL ] = modified; + } + } + + // if no content + if ( status === 204 || s.type === "HEAD" ) { + statusText = "nocontent"; + + // if not modified + } else if ( status === 304 ) { + statusText = "notmodified"; + + // If we have data, let's convert it + } else { + statusText = response.state; + success = response.data; + error = response.error; + isSuccess = !error; + } + } else { + + // Extract error from statusText and normalize for non-aborts + error = statusText; + if ( status || !statusText ) { + statusText = "error"; + if ( status < 0 ) { + status = 0; + } + } + } + + // Set data for the fake xhr object + jqXHR.status = status; + jqXHR.statusText = ( nativeStatusText || statusText ) + ""; + + // Success/Error + if ( isSuccess ) { + deferred.resolveWith( callbackContext, [ success, statusText, jqXHR ] ); + } else { + deferred.rejectWith( callbackContext, [ jqXHR, statusText, error ] ); + } + + // Status-dependent callbacks + jqXHR.statusCode( statusCode ); + statusCode = undefined; + + if ( fireGlobals ) { + globalEventContext.trigger( isSuccess ? "ajaxSuccess" : "ajaxError", + [ jqXHR, s, isSuccess ? success : error ] ); + } + + // Complete + completeDeferred.fireWith( callbackContext, [ jqXHR, statusText ] ); + + if ( fireGlobals ) { + globalEventContext.trigger( "ajaxComplete", [ jqXHR, s ] ); + + // Handle the global AJAX counter + if ( !( --jQuery.active ) ) { + jQuery.event.trigger( "ajaxStop" ); + } + } + } + + return jqXHR; + }, + + getJSON: function( url, data, callback ) { + return jQuery.get( url, data, callback, "json" ); + }, + + getScript: function( url, callback ) { + return jQuery.get( url, undefined, callback, "script" ); + } +} ); + +jQuery.each( [ "get", "post" ], function( _i, method ) { + jQuery[ method ] = function( url, data, callback, type ) { + + // Shift arguments if data argument was omitted + if ( isFunction( data ) ) { + type = type || callback; + callback = data; + data = undefined; + } + + // The url can be an options object (which then must have .url) + return jQuery.ajax( jQuery.extend( { + url: url, + type: method, + dataType: type, + data: data, + success: callback + }, jQuery.isPlainObject( url ) && url ) ); + }; +} ); + +jQuery.ajaxPrefilter( function( s ) { + var i; + for ( i in s.headers ) { + if ( i.toLowerCase() === "content-type" ) { + s.contentType = s.headers[ i ] || ""; + } + } +} ); + + +jQuery._evalUrl = function( url, options, doc ) { + return jQuery.ajax( { + url: url, + + // Make this explicit, since user can override this through ajaxSetup (#11264) + type: "GET", + dataType: "script", + cache: true, + async: false, + global: false, + + // Only evaluate the response if it is successful (gh-4126) + // dataFilter is not invoked for failure responses, so using it instead + // of the default converter is kludgy but it works. + converters: { + "text script": function() {} + }, + dataFilter: function( response ) { + jQuery.globalEval( response, options, doc ); + } + } ); +}; + + +jQuery.fn.extend( { + wrapAll: function( html ) { + var wrap; + + if ( this[ 0 ] ) { + if ( isFunction( html ) ) { + html = html.call( this[ 0 ] ); + } + + // The elements to wrap the target around + wrap = jQuery( html, this[ 0 ].ownerDocument ).eq( 0 ).clone( true ); + + if ( this[ 0 ].parentNode ) { + wrap.insertBefore( this[ 0 ] ); + } + + wrap.map( function() { + var elem = this; + + while ( elem.firstElementChild ) { + elem = elem.firstElementChild; + } + + return elem; + } ).append( this ); + } + + return this; + }, + + wrapInner: function( html ) { + if ( isFunction( html ) ) { + return this.each( function( i ) { + jQuery( this ).wrapInner( html.call( this, i ) ); + } ); + } + + return this.each( function() { + var self = jQuery( this ), + contents = self.contents(); + + if ( contents.length ) { + contents.wrapAll( html ); + + } else { + self.append( html ); + } + } ); + }, + + wrap: function( html ) { + var htmlIsFunction = isFunction( html ); + + return this.each( function( i ) { + jQuery( this ).wrapAll( htmlIsFunction ? html.call( this, i ) : html ); + } ); + }, + + unwrap: function( selector ) { + this.parent( selector ).not( "body" ).each( function() { + jQuery( this ).replaceWith( this.childNodes ); + } ); + return this; + } +} ); + + +jQuery.expr.pseudos.hidden = function( elem ) { + return !jQuery.expr.pseudos.visible( elem ); +}; +jQuery.expr.pseudos.visible = function( elem ) { + return !!( elem.offsetWidth || elem.offsetHeight || elem.getClientRects().length ); +}; + + + + +jQuery.ajaxSettings.xhr = function() { + try { + return new window.XMLHttpRequest(); + } catch ( e ) {} +}; + +var xhrSuccessStatus = { + + // File protocol always yields status code 0, assume 200 + 0: 200, + + // Support: IE <=9 only + // #1450: sometimes IE returns 1223 when it should be 204 + 1223: 204 + }, + xhrSupported = jQuery.ajaxSettings.xhr(); + +support.cors = !!xhrSupported && ( "withCredentials" in xhrSupported ); +support.ajax = xhrSupported = !!xhrSupported; + +jQuery.ajaxTransport( function( options ) { + var callback, errorCallback; + + // Cross domain only allowed if supported through XMLHttpRequest + if ( support.cors || xhrSupported && !options.crossDomain ) { + return { + send: function( headers, complete ) { + var i, + xhr = options.xhr(); + + xhr.open( + options.type, + options.url, + options.async, + options.username, + options.password + ); + + // Apply custom fields if provided + if ( options.xhrFields ) { + for ( i in options.xhrFields ) { + xhr[ i ] = options.xhrFields[ i ]; + } + } + + // Override mime type if needed + if ( options.mimeType && xhr.overrideMimeType ) { + xhr.overrideMimeType( options.mimeType ); + } + + // X-Requested-With header + // For cross-domain requests, seeing as conditions for a preflight are + // akin to a jigsaw puzzle, we simply never set it to be sure. + // (it can always be set on a per-request basis or even using ajaxSetup) + // For same-domain requests, won't change header if already provided. + if ( !options.crossDomain && !headers[ "X-Requested-With" ] ) { + headers[ "X-Requested-With" ] = "XMLHttpRequest"; + } + + // Set headers + for ( i in headers ) { + xhr.setRequestHeader( i, headers[ i ] ); + } + + // Callback + callback = function( type ) { + return function() { + if ( callback ) { + callback = errorCallback = xhr.onload = + xhr.onerror = xhr.onabort = xhr.ontimeout = + xhr.onreadystatechange = null; + + if ( type === "abort" ) { + xhr.abort(); + } else if ( type === "error" ) { + + // Support: IE <=9 only + // On a manual native abort, IE9 throws + // errors on any property access that is not readyState + if ( typeof xhr.status !== "number" ) { + complete( 0, "error" ); + } else { + complete( + + // File: protocol always yields status 0; see #8605, #14207 + xhr.status, + xhr.statusText + ); + } + } else { + complete( + xhrSuccessStatus[ xhr.status ] || xhr.status, + xhr.statusText, + + // Support: IE <=9 only + // IE9 has no XHR2 but throws on binary (trac-11426) + // For XHR2 non-text, let the caller handle it (gh-2498) + ( xhr.responseType || "text" ) !== "text" || + typeof xhr.responseText !== "string" ? + { binary: xhr.response } : + { text: xhr.responseText }, + xhr.getAllResponseHeaders() + ); + } + } + }; + }; + + // Listen to events + xhr.onload = callback(); + errorCallback = xhr.onerror = xhr.ontimeout = callback( "error" ); + + // Support: IE 9 only + // Use onreadystatechange to replace onabort + // to handle uncaught aborts + if ( xhr.onabort !== undefined ) { + xhr.onabort = errorCallback; + } else { + xhr.onreadystatechange = function() { + + // Check readyState before timeout as it changes + if ( xhr.readyState === 4 ) { + + // Allow onerror to be called first, + // but that will not handle a native abort + // Also, save errorCallback to a variable + // as xhr.onerror cannot be accessed + window.setTimeout( function() { + if ( callback ) { + errorCallback(); + } + } ); + } + }; + } + + // Create the abort callback + callback = callback( "abort" ); + + try { + + // Do send the request (this may raise an exception) + xhr.send( options.hasContent && options.data || null ); + } catch ( e ) { + + // #14683: Only rethrow if this hasn't been notified as an error yet + if ( callback ) { + throw e; + } + } + }, + + abort: function() { + if ( callback ) { + callback(); + } + } + }; + } +} ); + + + + +// Prevent auto-execution of scripts when no explicit dataType was provided (See gh-2432) +jQuery.ajaxPrefilter( function( s ) { + if ( s.crossDomain ) { + s.contents.script = false; + } +} ); + +// Install script dataType +jQuery.ajaxSetup( { + accepts: { + script: "text/javascript, application/javascript, " + + "application/ecmascript, application/x-ecmascript" + }, + contents: { + script: /\b(?:java|ecma)script\b/ + }, + converters: { + "text script": function( text ) { + jQuery.globalEval( text ); + return text; + } + } +} ); + +// Handle cache's special case and crossDomain +jQuery.ajaxPrefilter( "script", function( s ) { + if ( s.cache === undefined ) { + s.cache = false; + } + if ( s.crossDomain ) { + s.type = "GET"; + } +} ); + +// Bind script tag hack transport +jQuery.ajaxTransport( "script", function( s ) { + + // This transport only deals with cross domain or forced-by-attrs requests + if ( s.crossDomain || s.scriptAttrs ) { + var script, callback; + return { + send: function( _, complete ) { + script = jQuery( " + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

add_compile_definitions

+
+

New in version 3.12.

+
+

Add preprocessor definitions to the compilation of source files.

+
add_compile_definitions(<definition> ...)
+
+
+

Adds preprocessor definitions to the compiler command line.

+

The preprocessor definitions are added to the COMPILE_DEFINITIONS +directory property for the current CMakeLists file. They are also added to +the COMPILE_DEFINITIONS target property for each target in the +current CMakeLists file.

+

Definitions are specified using the syntax VAR or VAR=value. +Function-style definitions are not supported. CMake will automatically +escape the value correctly for the native build system (note that CMake +language syntax may require escapes to specify some values).

+
+

New in version 3.26: Any leading -D on an item will be removed.

+
+

Arguments to add_compile_definitions may use generator expressions +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_compile_options.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_compile_options.html new file mode 100644 index 0000000000000000000000000000000000000000..1b46e12a83dc221ea0bd16d340edd14ff4aa3569 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_compile_options.html @@ -0,0 +1,220 @@ + + + + + + + + + add_compile_options — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

add_compile_options

+

Add options to the compilation of source files.

+
add_compile_options(<option> ...)
+
+
+

Adds options to the COMPILE_OPTIONS directory property. +These options are used when compiling targets from the current +directory and below.

+
+

Note

+

These options are not used when linking. +See the add_link_options() command for that.

+
+
+

Arguments

+

Arguments to add_compile_options may use generator expressions +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+
+
+

Option De-duplication

+

The final set of options used for a target is constructed by +accumulating options from the current target and the usage requirements of +its dependencies. The set of options is de-duplicated to avoid repetition.

+
+

New in version 3.12: While beneficial for individual options, the de-duplication step can break +up option groups. For example, -option A -option B becomes +-option A B. One may specify a group of options using shell-like +quoting along with a SHELL: prefix. The SHELL: prefix is dropped, +and the rest of the option string is parsed using the +separate_arguments() UNIX_COMMAND mode. For example, +"SHELL:-option A" "SHELL:-option B" becomes -option A -option B.

+
+
+
+

Example

+

Since different compilers support different options, a typical use of +this command is in a compiler-specific conditional clause:

+
if (MSVC)
+    # warning level 4
+    add_compile_options(/W4)
+else()
+    # additional warnings
+    add_compile_options(-Wall -Wextra -Wpedantic)
+endif()
+
+
+

To set per-language options, use the $<COMPILE_LANGUAGE> +or $<COMPILE_LANGUAGE:languages> generator expressions.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_custom_command.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_custom_command.html new file mode 100644 index 0000000000000000000000000000000000000000..f45623a9274d292d23be77fdbdd00bf0ab7b23ca --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_custom_command.html @@ -0,0 +1,671 @@ + + + + + + + + + add_custom_command — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

add_custom_command

+

Add a custom build rule to the generated build system.

+

There are two main signatures for add_custom_command.

+
+

Generating Files

+

The first signature is for adding a custom command to produce an output:

+
add_custom_command(OUTPUT output1 [output2 ...]
+                   COMMAND command1 [ARGS] [args1...]
+                   [COMMAND command2 [ARGS] [args2...] ...]
+                   [MAIN_DEPENDENCY depend]
+                   [DEPENDS [depends...]]
+                   [BYPRODUCTS [files...]]
+                   [IMPLICIT_DEPENDS <lang1> depend1
+                                    [<lang2> depend2] ...]
+                   [WORKING_DIRECTORY dir]
+                   [COMMENT comment]
+                   [DEPFILE depfile]
+                   [JOB_POOL job_pool]
+                   [VERBATIM] [APPEND] [USES_TERMINAL]
+                   [COMMAND_EXPAND_LISTS]
+                   [DEPENDS_EXPLICIT_ONLY])
+
+
+

This defines a command to generate specified OUTPUT file(s). +A target created in the same directory (CMakeLists.txt file) +that specifies any output of the custom command as a source file +is given a rule to generate the file using the command at build time.

+

Do not list the output in more than one independent target that +may build in parallel or the instances of the rule may conflict. +Instead, use the add_custom_target() command to drive the +command and make the other targets depend on that one. See the +Example: Generating Files for Multiple Targets below.

+

The options are:

+
+
APPEND

Append the COMMAND and DEPENDS option values to the custom +command for the first output specified. There must have already +been a previous call to this command with the same output.

+

If the previous call specified the output via a generator expression, +the output specified by the current call must match in at least one +configuration after evaluating generator expressions. In this case, +the appended commands and dependencies apply to all configurations.

+

The COMMENT, MAIN_DEPENDENCY, and WORKING_DIRECTORY +options are currently ignored when APPEND is given, but may be +used in the future.

+
+
BYPRODUCTS
+

New in version 3.2.

+
+

Specify the files the command is expected to produce but whose +modification time may or may not be newer than the dependencies. +If a byproduct name is a relative path it will be interpreted +relative to the build tree directory corresponding to the +current source directory. +Each byproduct file will be marked with the GENERATED +source file property automatically.

+

See policy CMP0058 for the motivation behind this feature.

+

Explicit specification of byproducts is supported by the +Ninja generator to tell the ninja build tool +how to regenerate byproducts when they are missing. It is +also useful when other build rules (e.g. custom commands) +depend on the byproducts. Ninja requires a build rule for any +generated file on which another rule depends even if there are +order-only dependencies to ensure the byproducts will be +available before their dependents build.

+

The Makefile Generators will remove BYPRODUCTS and other +GENERATED files during make clean.

+
+

New in version 3.20: Arguments to BYPRODUCTS may use a restricted set of +generator expressions. +Target-dependent expressions are not +permitted.

+
+
+
COMMAND

Specify the command-line(s) to execute at build time. +If more than one COMMAND is specified they will be executed in order, +but not necessarily composed into a stateful shell or batch script. +(To run a full script, use the configure_file() command or the +file(GENERATE) command to create it, and then specify +a COMMAND to launch it.) +The optional ARGS argument is for backward compatibility and +will be ignored.

+

If COMMAND specifies an executable target name (created by the +add_executable() command), it will automatically be replaced +by the location of the executable created at build time if either of +the following is true:

+
    +
  • The target is not being cross-compiled (i.e. the +CMAKE_CROSSCOMPILING variable is not set to true).

  • +
  • +

    New in version 3.6: The target is being cross-compiled and an emulator is provided (i.e. +its CROSSCOMPILING_EMULATOR target property is set). +In this case, the contents of CROSSCOMPILING_EMULATOR will be +prepended to the command before the location of the target executable.

    +
    +
  • +
+

If neither of the above conditions are met, it is assumed that the +command name is a program to be found on the PATH at build time.

+

Arguments to COMMAND may use +generator expressions. +Use the TARGET_FILE generator expression to refer to the location +of a target later in the command line (i.e. as a command argument rather +than as the command to execute).

+

Whenever one of the following target based generator expressions are used as +a command to execute or is mentioned in a command argument, a target-level +dependency will be added automatically so that the mentioned target will be +built before any target using this custom command +(see policy CMP0112).

+
+
    +
  • TARGET_FILE

  • +
  • TARGET_LINKER_FILE

  • +
  • TARGET_SONAME_FILE

  • +
  • TARGET_PDB_FILE

  • +
+
+

This target-level dependency does NOT add a file-level dependency that would +cause the custom command to re-run whenever the executable is recompiled. +List target names with the DEPENDS option to add such file-level +dependencies.

+
+
COMMENT

Display the given message before the commands are executed at +build time.

+
+

New in version 3.26: Arguments to COMMENT may use +generator expressions.

+
+
+
DEPENDS

Specify files on which the command depends. Each argument is converted +to a dependency as follows:

+
    +
  1. If the argument is the name of a target (created by the +add_custom_target(), add_executable(), or +add_library() command) a target-level dependency is +created to make sure the target is built before any target +using this custom command. Additionally, if the target is an +executable or library, a file-level dependency is created to +cause the custom command to re-run whenever the target is +recompiled.

  2. +
  3. If the argument is an absolute path, a file-level dependency +is created on that path.

  4. +
  5. If the argument is the name of a source file that has been +added to a target or on which a source file property has been set, +a file-level dependency is created on that source file.

  6. +
  7. If the argument is a relative path and it exists in the current +source directory, a file-level dependency is created on that +file in the current source directory.

  8. +
  9. Otherwise, a file-level dependency is created on that path relative +to the current binary directory.

  10. +
+

If any dependency is an OUTPUT of another custom command in the same +directory (CMakeLists.txt file), CMake automatically brings the other +custom command into the target in which this command is built.

+
+

New in version 3.16: A target-level dependency is added if any dependency is listed as +BYPRODUCTS of a target or any of its build events in the same +directory to ensure the byproducts will be available.

+
+

If DEPENDS is not specified, the command will run whenever +the OUTPUT is missing; if the command does not actually +create the OUTPUT, the rule will always run.

+
+

New in version 3.1: Arguments to DEPENDS may use +generator expressions.

+
+
+
COMMAND_EXPAND_LISTS
+

New in version 3.8.

+
+

Lists in COMMAND arguments will be expanded, including those +created with +generator expressions, +allowing COMMAND arguments such as +${CC} "-I$<JOIN:$<TARGET_PROPERTY:foo,INCLUDE_DIRECTORIES>,;-I>" foo.cc +to be properly expanded.

+
+
IMPLICIT_DEPENDS

Request scanning of implicit dependencies of an input file. +The language given specifies the programming language whose +corresponding dependency scanner should be used. +Currently only C and CXX language scanners are supported. +The language has to be specified for every file in the +IMPLICIT_DEPENDS list. Dependencies discovered from the +scanning are added to those of the custom command at build time. +Note that the IMPLICIT_DEPENDS option is currently supported +only for Makefile generators and will be ignored by other generators.

+
+

Note

+

This option cannot be specified at the same time as DEPFILE option.

+
+
+
JOB_POOL
+

New in version 3.15.

+
+

Specify a pool for the Ninja +generator. Incompatible with USES_TERMINAL, which implies +the console pool. +Using a pool that is not defined by JOB_POOLS causes +an error by ninja at build time.

+
+
MAIN_DEPENDENCY

Specify the primary input source file to the command. This is +treated just like any value given to the DEPENDS option +but also suggests to Visual Studio generators where to hang +the custom command. Each source file may have at most one command +specifying it as its main dependency. A compile command (i.e. for a +library or an executable) counts as an implicit main dependency which +gets silently overwritten by a custom command specification.

+
+
OUTPUT

Specify the output files the command is expected to produce. +Each output file will be marked with the GENERATED +source file property automatically. +If the output of the custom command is not actually created +as a file on disk it should be marked with the SYMBOLIC +source file property.

+

If an output file name is a relative path, its absolute path is +determined by interpreting it relative to:

+
    +
  1. the build directory corresponding to the current source directory +(CMAKE_CURRENT_BINARY_DIR), or

  2. +
  3. the current source directory (CMAKE_CURRENT_SOURCE_DIR).

  4. +
+

The path in the build directory is preferred unless the path in the +source tree is mentioned as an absolute source file path elsewhere +in the current directory.

+
+

New in version 3.20: Arguments to OUTPUT may use a restricted set of +generator expressions. +Target-dependent expressions are not +permitted.

+
+
+
USES_TERMINAL
+

New in version 3.2.

+
+

The command will be given direct access to the terminal if possible. +With the Ninja generator, this places the command in +the console pool.

+
+
VERBATIM

All arguments to the commands will be escaped properly for the +build tool so that the invoked command receives each argument +unchanged. Note that one level of escapes is still used by the +CMake language processor before add_custom_command even sees the +arguments. Use of VERBATIM is recommended as it enables +correct behavior. When VERBATIM is not given the behavior +is platform specific because there is no protection of +tool-specific special characters.

+
+
WORKING_DIRECTORY

Execute the command with the given current working directory. +If it is a relative path it will be interpreted relative to the +build tree directory corresponding to the current source directory.

+
+

New in version 3.13: Arguments to WORKING_DIRECTORY may use +generator expressions.

+
+
+
DEPFILE
+

New in version 3.7.

+
+

Specify a depfile which holds dependencies for the custom command. It is +usually emitted by the custom command itself. This keyword may only be used +if the generator supports it, as detailed below.

+

The expected format, compatible with what is generated by gcc with the +option -M, is independent of the generator or platform.

+

The formal syntax, as specified using +BNF notation with +the regular extensions, is the following:

+
+depfile       ::=  rule*
+rule          ::=  targets (':' (separator dependencies?)?)? eol
+targets       ::=  target (separator target)* separator*
+target        ::=  pathname
+dependencies  ::=  dependency (separator dependency)* separator*
+dependency    ::=  pathname
+separator     ::=  (space | line_continue)+
+line_continue ::=  '\' eol
+space         ::=  ' ' | '\t'
+pathname      ::=  character+
+character     ::=  std_character | dollar | hash | whitespace
+std_character ::=  <any character except '$', '#' or ' '>
+dollar        ::=  '$$'
+hash          ::=  '\#'
+whitespace    ::=  '\ '
+eol           ::=  '\r'? '\n'
+
+
+

Note

+

As part of pathname, any slash and backslash is interpreted as +a directory separator.

+
+
+

New in version 3.7: The Ninja generator supports DEPFILE since the keyword +was first added.

+
+
+

New in version 3.17: Added the Ninja Multi-Config generator, which included +support for the DEPFILE keyword.

+
+
+

New in version 3.20: Added support for Makefile Generators.

+
+

Note

+

DEPFILE cannot be specified at the same time as the +IMPLICIT_DEPENDS option for Makefile Generators.

+
+
+
+

New in version 3.21: Added support for Visual Studio Generators with VS 2012 and above, +and for the Xcode generator. Support for +generator expressions was also +added.

+
+

Using DEPFILE with generators other than those listed above is an error.

+

If the DEPFILE argument is relative, it should be relative to +CMAKE_CURRENT_BINARY_DIR, and any relative paths inside the +DEPFILE should also be relative to CMAKE_CURRENT_BINARY_DIR. +See policy CMP0116, which is always NEW for +Makefile Generators, Visual Studio Generators, +and the Xcode generator.

+
+
+

DEPENDS_EXPLICIT_ONLY

+
+
+

New in version 3.27.

+
+

Indicates that the command's DEPENDS argument represents all files +required by the command and implicit dependencies are not required.

+

Without this option, if any target uses the output of the custom command, +CMake will consider that target's dependencies as implicit dependencies for +the custom command in case this custom command requires files implicitly +created by those targets.

+

This option can be enabled on all custom commands by setting +CMAKE_ADD_CUSTOM_COMMAND_DEPENDS_EXPLICIT_ONLY to ON.

+

Only the Ninja Generators actually use this information to remove +unnecessary implicit dependencies.

+

See also the OPTIMIZE_DEPENDENCIES target property, which may +provide another way for reducing the impact of target dependencies in some +scenarios.

+
+
+
+

Examples: Generating Files

+

Custom commands may be used to generate source files. +For example, the code:

+
add_custom_command(
+  OUTPUT out.c
+  COMMAND someTool -i ${CMAKE_CURRENT_SOURCE_DIR}/in.txt
+                   -o out.c
+  DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/in.txt
+  VERBATIM)
+add_library(myLib out.c)
+
+
+

adds a custom command to run someTool to generate out.c and then +compile the generated source as part of a library. The generation rule +will re-run whenever in.txt changes.

+
+

New in version 3.20: One may use generator expressions to specify per-configuration outputs. +For example, the code:

+
add_custom_command(
+  OUTPUT "out-$<CONFIG>.c"
+  COMMAND someTool -i ${CMAKE_CURRENT_SOURCE_DIR}/in.txt
+                   -o "out-$<CONFIG>.c"
+                   -c "$<CONFIG>"
+  DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/in.txt
+  VERBATIM)
+add_library(myLib "out-$<CONFIG>.c")
+
+
+

adds a custom command to run someTool to generate out-<config>.c, +where <config> is the build configuration, and then compile the generated +source as part of a library.

+
+
+

Example: Generating Files for Multiple Targets

+

If multiple independent targets need the same custom command output, +it must be attached to a single custom target on which they all depend. +Consider the following example:

+
add_custom_command(
+  OUTPUT table.csv
+  COMMAND makeTable -i ${CMAKE_CURRENT_SOURCE_DIR}/input.dat
+                    -o table.csv
+  DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/input.dat
+  VERBATIM)
+add_custom_target(generate_table_csv DEPENDS table.csv)
+
+add_custom_command(
+  OUTPUT foo.cxx
+  COMMAND genFromTable -i table.csv -case foo -o foo.cxx
+  DEPENDS table.csv           # file-level dependency
+          generate_table_csv  # target-level dependency
+  VERBATIM)
+add_library(foo foo.cxx)
+
+add_custom_command(
+  OUTPUT bar.cxx
+  COMMAND genFromTable -i table.csv -case bar -o bar.cxx
+  DEPENDS table.csv           # file-level dependency
+          generate_table_csv  # target-level dependency
+  VERBATIM)
+add_library(bar bar.cxx)
+
+
+

Output foo.cxx is needed only by target foo and output bar.cxx +is needed only by target bar, but both targets need table.csv, +transitively. Since foo and bar are independent targets that may +build concurrently, we prevent them from racing to generate table.csv +by placing its custom command in a separate target, generate_table_csv. +The custom commands generating foo.cxx and bar.cxx each specify a +target-level dependency on generate_table_csv, so the targets using them, +foo and bar, will not build until after target generate_table_csv +is built.

+
+
+
+

Build Events

+

The second signature adds a custom command to a target such as a +library or executable. This is useful for performing an operation +before or after building the target. The command becomes part of the +target and will only execute when the target itself is built. If the +target is already built, the command will not execute.

+
add_custom_command(TARGET <target>
+                   PRE_BUILD | PRE_LINK | POST_BUILD
+                   COMMAND command1 [ARGS] [args1...]
+                   [COMMAND command2 [ARGS] [args2...] ...]
+                   [BYPRODUCTS [files...]]
+                   [WORKING_DIRECTORY dir]
+                   [COMMENT comment]
+                   [VERBATIM]
+                   [COMMAND_EXPAND_LISTS])
+
+
+

This defines a new command that will be associated with building the +specified <target>. The <target> must be defined in the current +directory; targets defined in other directories may not be specified.

+

When the command will happen is determined by which +of the following is specified:

+
+
PRE_BUILD

This option has unique behavior for the Visual Studio Generators. +When using one of the Visual Studio generators, the command will run before +any other rules are executed within the target. With all other generators, +this option behaves the same as PRE_LINK instead. Because of this, +it is recommended to avoid using PRE_BUILD except when it is known that +a Visual Studio generator is being used.

+
+
PRE_LINK

Run after sources have been compiled but before linking the binary +or running the librarian or archiver tool of a static library. +This is not defined for targets created by the +add_custom_target() command.

+
+
POST_BUILD

Run after all other rules within the target have been executed.

+
+
+

Projects should always specify one of the above three keywords when using +the TARGET form. For backward compatibility reasons, POST_BUILD is +assumed if no such keyword is given, but projects should explicitly provide +one of the keywords to make clear the behavior they expect.

+
+

Note

+

Because generator expressions can be used in custom commands, +it is possible to define COMMAND lines or whole custom commands +which evaluate to empty strings for certain configurations. +For Visual Studio 11 2012 (and newer) generators these command +lines or custom commands will be omitted for the specific +configuration and no "empty-string-command" will be added.

+

This allows to add individual build events for every configuration.

+
+
+

New in version 3.21: Support for target-dependent generator expressions.

+
+
+
+

Examples: Build Events

+

A POST_BUILD event may be used to post-process a binary after linking. +For example, the code:

+
add_executable(myExe myExe.c)
+add_custom_command(
+  TARGET myExe POST_BUILD
+  COMMAND someHasher -i "$<TARGET_FILE:myExe>"
+                     -o "$<TARGET_FILE:myExe>.hash"
+  VERBATIM)
+
+
+

will run someHasher to produce a .hash file next to the executable +after linking.

+
+

New in version 3.20: One may use generator expressions to specify per-configuration byproducts. +For example, the code:

+
add_library(myPlugin MODULE myPlugin.c)
+add_custom_command(
+  TARGET myPlugin POST_BUILD
+  COMMAND someHasher -i "$<TARGET_FILE:myPlugin>"
+                     --as-code "myPlugin-hash-$<CONFIG>.c"
+  BYPRODUCTS "myPlugin-hash-$<CONFIG>.c"
+  VERBATIM)
+add_executable(myExe myExe.c "myPlugin-hash-$<CONFIG>.c")
+
+
+

will run someHasher after linking myPlugin, e.g. to produce a .c +file containing code to check the hash of myPlugin that the myExe +executable can use to verify it before loading.

+
+
+
+

Ninja Multi-Config

+
+

New in version 3.20: add_custom_command supports the Ninja Multi-Config +generator's cross-config capabilities. See the generator documentation +for more information.

+
+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_custom_target.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_custom_target.html new file mode 100644 index 0000000000000000000000000000000000000000..9ea8c8518cd9ab91f5826306da136db420e71c4a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_custom_target.html @@ -0,0 +1,327 @@ + + + + + + + + + add_custom_target — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

add_custom_target

+

Add a target with no output so it will always be built.

+
add_custom_target(Name [ALL] [command1 [args1...]]
+                  [COMMAND command2 [args2...] ...]
+                  [DEPENDS depend depend depend ... ]
+                  [BYPRODUCTS [files...]]
+                  [WORKING_DIRECTORY dir]
+                  [COMMENT comment]
+                  [JOB_POOL job_pool]
+                  [VERBATIM] [USES_TERMINAL]
+                  [COMMAND_EXPAND_LISTS]
+                  [SOURCES src1 [src2...]])
+
+
+

Adds a target with the given name that executes the given commands. +The target has no output file and is always considered out of date +even if the commands try to create a file with the name of the target. +Use the add_custom_command() command to generate a file with +dependencies. By default nothing depends on the custom target. Use +the add_dependencies() command to add dependencies to or +from other targets.

+

The options are:

+
+
ALL

Indicate that this target should be added to the default build +target so that it will be run every time (the command cannot be +called ALL).

+
+
BYPRODUCTS
+

New in version 3.2.

+
+

Specify the files the command is expected to produce but whose +modification time may or may not be updated on subsequent builds. +If a byproduct name is a relative path it will be interpreted +relative to the build tree directory corresponding to the +current source directory. +Each byproduct file will be marked with the GENERATED +source file property automatically.

+

See policy CMP0058 for the motivation behind this feature.

+

Explicit specification of byproducts is supported by the +Ninja generator to tell the ninja build tool +how to regenerate byproducts when they are missing. It is +also useful when other build rules (e.g. custom commands) +depend on the byproducts. Ninja requires a build rule for any +generated file on which another rule depends even if there are +order-only dependencies to ensure the byproducts will be +available before their dependents build.

+

The Makefile Generators will remove BYPRODUCTS and other +GENERATED files during make clean.

+
+

New in version 3.20: Arguments to BYPRODUCTS may use a restricted set of +generator expressions. +Target-dependent expressions are not +permitted.

+
+
+
COMMAND

Specify the command-line(s) to execute at build time. +If more than one COMMAND is specified they will be executed in order, +but not necessarily composed into a stateful shell or batch script. +(To run a full script, use the configure_file() command or the +file(GENERATE) command to create it, and then specify +a COMMAND to launch it.)

+

If COMMAND specifies an executable target name (created by the +add_executable() command), it will automatically be replaced +by the location of the executable created at build time if either of +the following is true:

+
    +
  • The target is not being cross-compiled (i.e. the +CMAKE_CROSSCOMPILING variable is not set to true).

  • +
  • +

    New in version 3.6: The target is being cross-compiled and an emulator is provided (i.e. +its CROSSCOMPILING_EMULATOR target property is set). +In this case, the contents of CROSSCOMPILING_EMULATOR will be +prepended to the command before the location of the target executable.

    +
    +
  • +
+

If neither of the above conditions are met, it is assumed that the +command name is a program to be found on the PATH at build time.

+

Arguments to COMMAND may use +generator expressions. +Use the TARGET_FILE generator expression to refer to the location +of a target later in the command line (i.e. as a command argument rather +than as the command to execute).

+

Whenever one of the following target based generator expressions are used as +a command to execute or is mentioned in a command argument, a target-level +dependency will be added automatically so that the mentioned target will be +built before this custom target (see policy CMP0112).

+
+
    +
  • TARGET_FILE

  • +
  • TARGET_LINKER_FILE

  • +
  • TARGET_SONAME_FILE

  • +
  • TARGET_PDB_FILE

  • +
+
+

The command and arguments are optional and if not specified an empty +target will be created.

+
+
COMMENT

Display the given message before the commands are executed at +build time.

+
+

New in version 3.26: Arguments to COMMENT may use +generator expressions.

+
+
+
DEPENDS

Reference files and outputs of custom commands created with +add_custom_command() command calls in the same directory +(CMakeLists.txt file). They will be brought up to date when +the target is built.

+
+

Changed in version 3.16: A target-level dependency is added if any dependency is a byproduct +of a target or any of its build events in the same directory to ensure +the byproducts will be available before this target is built.

+
+

Use the add_dependencies() command to add dependencies +on other targets.

+
+
COMMAND_EXPAND_LISTS
+

New in version 3.8.

+
+

Lists in COMMAND arguments will be expanded, including those +created with +generator expressions, +allowing COMMAND arguments such as +${CC} "-I$<JOIN:$<TARGET_PROPERTY:foo,INCLUDE_DIRECTORIES>,;-I>" foo.cc +to be properly expanded.

+
+
JOB_POOL
+

New in version 3.15.

+
+

Specify a pool for the Ninja +generator. Incompatible with USES_TERMINAL, which implies +the console pool. +Using a pool that is not defined by JOB_POOLS causes +an error by ninja at build time.

+
+
SOURCES

Specify additional source files to be included in the custom target. +Specified source files will be added to IDE project files for +convenience in editing even if they have no build rules.

+
+
VERBATIM

All arguments to the commands will be escaped properly for the +build tool so that the invoked command receives each argument +unchanged. Note that one level of escapes is still used by the +CMake language processor before add_custom_target even sees +the arguments. Use of VERBATIM is recommended as it enables +correct behavior. When VERBATIM is not given the behavior +is platform specific because there is no protection of +tool-specific special characters.

+
+
USES_TERMINAL
+

New in version 3.2.

+
+

The command will be given direct access to the terminal if possible. +With the Ninja generator, this places the command in +the console pool.

+
+
WORKING_DIRECTORY

Execute the command with the given current working directory. +If it is a relative path it will be interpreted relative to the +build tree directory corresponding to the current source directory.

+
+

New in version 3.13: Arguments to WORKING_DIRECTORY may use +generator expressions.

+
+
+
+
+

Ninja Multi-Config

+
+

New in version 3.20: add_custom_target supports the Ninja Multi-Config +generator's cross-config capabilities. See the generator documentation +for more information.

+
+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_definitions.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_definitions.html new file mode 100644 index 0000000000000000000000000000000000000000..b565bbf556c79a5436642b1821868843518b0135 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_definitions.html @@ -0,0 +1,182 @@ + + + + + + + + + add_definitions — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

add_definitions

+

Add -D define flags to the compilation of source files.

+
add_definitions(-DFOO -DBAR ...)
+
+
+

Adds definitions to the compiler command line for targets in the current +directory, whether added before or after this command is invoked, and for +the ones in sub-directories added after. This command can be used to add any +flags, but it is intended to add preprocessor definitions.

+
+

Note

+

This command has been superseded by alternatives:

+ +
+

Flags beginning in -D or /D that look like preprocessor definitions are +automatically added to the COMPILE_DEFINITIONS directory +property for the current directory. Definitions with non-trivial values +may be left in the set of flags instead of being converted for reasons of +backwards compatibility. See documentation of the +directory, +target, +source file COMPILE_DEFINITIONS +properties for details on adding preprocessor definitions to specific +scopes and configurations.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_dependencies.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_dependencies.html new file mode 100644 index 0000000000000000000000000000000000000000..65a3ed2d3ddcd3edb268ae58df6a1f5891fa3748 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_dependencies.html @@ -0,0 +1,173 @@ + + + + + + + + + add_dependencies — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

add_dependencies

+

Add a dependency between top-level targets.

+
add_dependencies(<target> [<target-dependency>]...)
+
+
+

Makes a top-level <target> depend on other top-level targets to +ensure that they build before <target> does. A top-level target +is one created by one of the add_executable(), +add_library(), or add_custom_target() commands +(but not targets generated by CMake like install).

+

Dependencies added to an imported target +or an interface library are followed +transitively in its place since the target itself does not build.

+
+

New in version 3.3: Allow adding dependencies to interface libraries.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_executable.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_executable.html new file mode 100644 index 0000000000000000000000000000000000000000..069a7f3f740479d0b96cd2a3795bb12570d7e57b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_executable.html @@ -0,0 +1,259 @@ + + + + + + + + + add_executable — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

add_executable

+ +

Add an executable to the project using the specified source files.

+
+

Normal Executables

+
add_executable(<name> [WIN32] [MACOSX_BUNDLE]
+               [EXCLUDE_FROM_ALL]
+               [source1] [source2 ...])
+
+
+

Adds an executable target called <name> to be built from the source +files listed in the command invocation. The +<name> corresponds to the logical target name and must be globally +unique within a project. The actual file name of the executable built is +constructed based on conventions of the native platform (such as +<name>.exe or just <name>).

+
+

New in version 3.1: Source arguments to add_executable may use "generator expressions" with +the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions.

+
+
+

New in version 3.11: The source files can be omitted if they are added later using +target_sources().

+
+

By default the executable file will be created in the build tree +directory corresponding to the source tree directory in which the +command was invoked. See documentation of the +RUNTIME_OUTPUT_DIRECTORY target property to change this +location. See documentation of the OUTPUT_NAME target property +to change the <name> part of the final file name.

+

If WIN32 is given the property WIN32_EXECUTABLE will be +set on the target created. See documentation of that target property for +details.

+

If MACOSX_BUNDLE is given the corresponding property will be set on +the created target. See documentation of the MACOSX_BUNDLE +target property for details.

+

If EXCLUDE_FROM_ALL is given the corresponding property will be set on +the created target. See documentation of the EXCLUDE_FROM_ALL +target property for details.

+

See the cmake-buildsystem(7) manual for more on defining +buildsystem properties.

+

See also HEADER_FILE_ONLY on what to do if some sources are +pre-processed, and you want to have the original sources reachable from +within IDE.

+
+
+

Imported Executables

+
add_executable(<name> IMPORTED [GLOBAL])
+
+
+

An IMPORTED executable target references an +executable file located outside the project. No rules are generated to +build it, and the IMPORTED target property is True. The +target name has scope in the directory in which it is created and below, but +the GLOBAL option extends visibility. It may be referenced like any +target built within the project. IMPORTED executables are useful +for convenient reference from commands like add_custom_command(). +Details about the imported executable are specified by setting properties +whose names begin in IMPORTED_. The most important such property is +IMPORTED_LOCATION (and its per-configuration version +IMPORTED_LOCATION_<CONFIG>) which specifies the location of +the main executable file on disk. See documentation of the IMPORTED_* +properties for more information.

+
+
+

Alias Executables

+
add_executable(<name> ALIAS <target>)
+
+
+

Creates an Alias Target, such that <name> can +be used to refer to <target> in subsequent commands. The <name> +does not appear in the generated buildsystem as a make target. The +<target> may not be an ALIAS.

+
+

New in version 3.11: An ALIAS can target a GLOBAL Imported Target

+
+
+

New in version 3.18: An ALIAS can target a non-GLOBAL Imported Target. Such alias is +scoped to the directory in which it is created and subdirectories. +The ALIAS_GLOBAL target property can be used to check if the +alias is global or not.

+
+

ALIAS targets can be used as targets to read properties +from, executables for custom commands and custom targets. They can also be +tested for existence with the regular if(TARGET) subcommand. +The <name> may not be used to modify properties of <target>, that +is, it may not be used as the operand of set_property(), +set_target_properties(), target_link_libraries() etc. +An ALIAS target may not be installed or exported.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_library.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_library.html new file mode 100644 index 0000000000000000000000000000000000000000..887f395a3269054112e9937c6118948aa867c315 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_library.html @@ -0,0 +1,401 @@ + + + + + + + + + add_library — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

add_library

+ +

Add a library to the project using the specified source files.

+
+

Normal Libraries

+
add_library(<name> [STATIC | SHARED | MODULE]
+            [EXCLUDE_FROM_ALL]
+            [<source>...])
+
+
+

Adds a library target called <name> to be built from the source files +listed in the command invocation. The <name> +corresponds to the logical target name and must be globally unique within +a project. The actual file name of the library built is constructed based +on conventions of the native platform (such as lib<name>.a or +<name>.lib).

+
+

New in version 3.1: Source arguments to add_library may use "generator expressions" with +the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions.

+
+
+

New in version 3.11: The source files can be omitted if they are added later using +target_sources().

+
+

STATIC, SHARED, or MODULE may be given to specify the type of +library to be created. STATIC libraries are archives of object files +for use when linking other targets. SHARED libraries are linked +dynamically and loaded at runtime. MODULE libraries are plugins that +are not linked into other targets but may be loaded dynamically at runtime +using dlopen-like functionality. If no type is given explicitly the +type is STATIC or SHARED based on whether the current value of the +variable BUILD_SHARED_LIBS is ON. For SHARED and +MODULE libraries the POSITION_INDEPENDENT_CODE target +property is set to ON automatically. +A SHARED library may be marked with the FRAMEWORK +target property to create an macOS Framework.

+
+

New in version 3.8: A STATIC library may be marked with the FRAMEWORK +target property to create a static Framework.

+
+

If a library does not export any symbols, it must not be declared as a +SHARED library. For example, a Windows resource DLL or a managed C++/CLI +DLL that exports no unmanaged symbols would need to be a MODULE library. +This is because CMake expects a SHARED library to always have an +associated import library on Windows.

+

By default the library file will be created in the build tree directory +corresponding to the source tree directory in which the command was +invoked. See documentation of the ARCHIVE_OUTPUT_DIRECTORY, +LIBRARY_OUTPUT_DIRECTORY, and +RUNTIME_OUTPUT_DIRECTORY target properties to change this +location. See documentation of the OUTPUT_NAME target +property to change the <name> part of the final file name.

+

If EXCLUDE_FROM_ALL is given the corresponding property will be set on +the created target. See documentation of the EXCLUDE_FROM_ALL +target property for details.

+

See the cmake-buildsystem(7) manual for more on defining +buildsystem properties.

+

See also HEADER_FILE_ONLY on what to do if some sources are +pre-processed, and you want to have the original sources reachable from +within IDE.

+
+
+

Object Libraries

+
add_library(<name> OBJECT [<source>...])
+
+
+

Creates an Object Library. An object library +compiles source files but does not archive or link their object files into a +library. Instead other targets created by add_library or +add_executable() may reference the objects using an expression of the +form $<TARGET_OBJECTS:objlib> as a source, where +objlib is the object library name. For example:

+
add_library(... $<TARGET_OBJECTS:objlib> ...)
+add_executable(... $<TARGET_OBJECTS:objlib> ...)
+
+
+

will include objlib's object files in a library and an executable +along with those compiled from their own sources. Object libraries +may contain only sources that compile, header files, and other files +that would not affect linking of a normal library (e.g. .txt). +They may contain custom commands generating such sources, but not +PRE_BUILD, PRE_LINK, or POST_BUILD commands. Some native build +systems (such as Xcode) may not like targets that have only object files, so +consider adding at least one real source file to any target that references +$<TARGET_OBJECTS:objlib>.

+
+

New in version 3.12: Object libraries can be linked to with target_link_libraries().

+
+
+
+

Interface Libraries

+
add_library(<name> INTERFACE)
+
+
+

Creates an Interface Library. +An INTERFACE library target does not compile sources and does +not produce a library artifact on disk. However, it may have +properties set on it and it may be installed and exported. +Typically, INTERFACE_* properties are populated on an interface +target using the commands:

+ +

and then it is used as an argument to target_link_libraries() +like any other target.

+

An interface library created with the above signature has no source files +itself and is not included as a target in the generated buildsystem.

+
+

New in version 3.15: An interface library can have PUBLIC_HEADER and +PRIVATE_HEADER properties. The headers specified by those +properties can be installed using the install(TARGETS) command.

+
+
+

New in version 3.19: An interface library target may be created with source files:

+
add_library(<name> INTERFACE [<source>...] [EXCLUDE_FROM_ALL])
+
+
+

Source files may be listed directly in the add_library call or added +later by calls to target_sources() with the PRIVATE or +PUBLIC keywords.

+

If an interface library has source files (i.e. the SOURCES +target property is set), or header sets (i.e. the HEADER_SETS +target property is set), it will appear in the generated buildsystem +as a build target much like a target defined by the +add_custom_target() command. It does not compile any sources, +but does contain build rules for custom commands created by the +add_custom_command() command.

+
+
+

Note

+

In most command signatures where the INTERFACE keyword appears, +the items listed after it only become part of that target's usage +requirements and are not part of the target's own settings. However, +in this signature of add_library, the INTERFACE keyword refers +to the library type only. Sources listed after it in the add_library +call are PRIVATE to the interface library and do not appear in its +INTERFACE_SOURCES target property.

+
+
+
+

Imported Libraries

+
add_library(<name> <type> IMPORTED [GLOBAL])
+
+
+

Creates an IMPORTED library target called <name>. +No rules are generated to build it, and the IMPORTED target +property is True. The target name has scope in the directory in which +it is created and below, but the GLOBAL option extends visibility. +It may be referenced like any target built within the project. +IMPORTED libraries are useful for convenient reference from commands +like target_link_libraries(). Details about the imported library +are specified by setting properties whose names begin in IMPORTED_ and +INTERFACE_.

+

The <type> must be one of:

+
+
STATIC, SHARED, MODULE, UNKNOWN

References a library file located outside the project. The +IMPORTED_LOCATION target property (or its per-configuration +variant IMPORTED_LOCATION_<CONFIG>) specifies the +location of the main library file on disk:

+
    +
  • For a SHARED library on most non-Windows platforms, the main library +file is the .so or .dylib file used by both linkers and dynamic +loaders. If the referenced library file has a SONAME (or on macOS, +has a LC_ID_DYLIB starting in @rpath/), the value of that field +should be set in the IMPORTED_SONAME target property. +If the referenced library file does not have a SONAME, but the +platform supports it, then the IMPORTED_NO_SONAME target +property should be set.

  • +
  • For a SHARED library on Windows, the IMPORTED_IMPLIB +target property (or its per-configuration variant +IMPORTED_IMPLIB_<CONFIG>) specifies the location of the +DLL import library file (.lib or .dll.a) on disk, and the +IMPORTED_LOCATION is the location of the .dll runtime +library (and is optional, but needed by the TARGET_RUNTIME_DLLS +generator expression).

  • +
+

Additional usage requirements may be specified in INTERFACE_* properties.

+

An UNKNOWN library type is typically only used in the implementation of +Find Modules. It allows the path to an imported library (often found +using the find_library() command) to be used without having to know +what type of library it is. This is especially useful on Windows where a +static library and a DLL's import library both have the same file extension.

+
+
OBJECT

References a set of object files located outside the project. +The IMPORTED_OBJECTS target property (or its per-configuration +variant IMPORTED_OBJECTS_<CONFIG>) specifies the locations of +object files on disk. +Additional usage requirements may be specified in INTERFACE_* properties.

+
+
INTERFACE

Does not reference any library or object files on disk, but may +specify usage requirements in INTERFACE_* properties.

+
+
+

See documentation of the IMPORTED_* and INTERFACE_* properties +for more information.

+
+
+

Alias Libraries

+
add_library(<name> ALIAS <target>)
+
+
+

Creates an Alias Target, such that <name> can be +used to refer to <target> in subsequent commands. The <name> does +not appear in the generated buildsystem as a make target. The <target> +may not be an ALIAS.

+
+

New in version 3.11: An ALIAS can target a GLOBAL Imported Target

+
+
+

New in version 3.18: An ALIAS can target a non-GLOBAL Imported Target. Such alias is +scoped to the directory in which it is created and below. +The ALIAS_GLOBAL target property can be used to check if the +alias is global or not.

+
+

ALIAS targets can be used as linkable targets and as targets to +read properties from. They can also be tested for existence with the +regular if(TARGET) subcommand. The <name> may not be used +to modify properties of <target>, that is, it may not be used as the +operand of set_property(), set_target_properties(), +target_link_libraries() etc. An ALIAS target may not be +installed or exported.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_link_options.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_link_options.html new file mode 100644 index 0000000000000000000000000000000000000000..3cb2087b6ddb230ab955e64bfac434c36f10df41 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_link_options.html @@ -0,0 +1,236 @@ + + + + + + + + + add_link_options — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_subdirectory.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_subdirectory.html new file mode 100644 index 0000000000000000000000000000000000000000..6579010b0e834c3a3a7eb83ec271e52692d006d2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_subdirectory.html @@ -0,0 +1,173 @@ + + + + + + + + + add_subdirectory — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

add_subdirectory

+

Add a subdirectory to the build.

+
add_subdirectory(source_dir [binary_dir] [EXCLUDE_FROM_ALL] [SYSTEM])
+
+
+

Adds a subdirectory to the build. The source_dir specifies the +directory in which the source CMakeLists.txt and code files are +located. If it is a relative path, it will be evaluated with respect +to the current directory (the typical usage), but it may also be an +absolute path. The binary_dir specifies the directory in which to +place the output files. If it is a relative path, it will be evaluated +with respect to the current output directory, but it may also be an +absolute path. If binary_dir is not specified, the value of +source_dir, before expanding any relative path, will be used (the +typical usage). The CMakeLists.txt file in the specified source +directory will be processed immediately by CMake before processing in +the current input file continues beyond this command.

+

If the EXCLUDE_FROM_ALL argument is provided then targets in the +subdirectory will not be included in the ALL target of the parent +directory by default, and will be excluded from IDE project files. +Users must explicitly build targets in the subdirectory. This is +meant for use when the subdirectory contains a separate part of the +project that is useful but not necessary, such as a set of examples. +Typically the subdirectory should contain its own project() +command invocation so that a full build system will be generated in the +subdirectory (such as a Visual Studio IDE solution file). Note that +inter-target dependencies supersede this exclusion. If a target built by +the parent project depends on a target in the subdirectory, the dependee +target will be included in the parent project build system to satisfy +the dependency.

+
+

New in version 3.25: If the SYSTEM argument is provided, the SYSTEM directory +property of the subdirectory will be set to true. This property is +used to initialize the SYSTEM property of each non-imported +target created in that subdirectory.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_test.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_test.html new file mode 100644 index 0000000000000000000000000000000000000000..f0d68e17049a30ccf7d55a0c3916a04293f1a951 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/add_test.html @@ -0,0 +1,208 @@ + + + + + + + + + add_test — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

add_test

+

Add a test to the project to be run by ctest(1).

+
add_test(NAME <name> COMMAND <command> [<arg>...]
+         [CONFIGURATIONS <config>...]
+         [WORKING_DIRECTORY <dir>]
+         [COMMAND_EXPAND_LISTS])
+
+
+

Adds a test called <name>. The test name may contain arbitrary +characters, expressed as a Quoted Argument or Bracket Argument +if necessary. See policy CMP0110.

+

CMake only generates tests if the enable_testing() command has been +invoked. The CTest module invokes enable_testing automatically +unless BUILD_TESTING is set to OFF.

+

Tests added with the add_test(NAME) signature support using +generator expressions +in test properties set by set_property(TEST) or +set_tests_properties(). Test properties may only be set in the +directory the test is created in.

+

add_test options are:

+
+
COMMAND

Specify the test command-line. If <command> specifies an executable +target created by add_executable(), it will automatically be +replaced by the location of the executable created at build time.

+

The command may be specified using +generator expressions.

+
+
CONFIGURATIONS

Restrict execution of the test only to the named configurations.

+
+
WORKING_DIRECTORY

Set the test property WORKING_DIRECTORY in which to execute the +test. If not specified, the test will be run in +CMAKE_CURRENT_BINARY_DIR. The working directory may be specified +using generator expressions.

+
+
COMMAND_EXPAND_LISTS
+

New in version 3.16.

+
+

Lists in COMMAND arguments will be expanded, including those created with +generator expressions.

+
+
+

If the test command exits with code 0 the test passes. Non-zero exit code +is a "failed" test. The test property WILL_FAIL inverts this +logic. Note that system-level test failures such as segmentation faults or +heap errors will still fail the test even if WILL_FALL is true. Output +written to stdout or stderr is captured by ctest(1) and only +affects the pass/fail status via the PASS_REGULAR_EXPRESSION, +FAIL_REGULAR_EXPRESSION, or SKIP_REGULAR_EXPRESSION +test properties.

+
+

New in version 3.16: Added SKIP_REGULAR_EXPRESSION property.

+
+

Example usage:

+
add_test(NAME mytest
+         COMMAND testDriver --config $<CONFIG>
+                            --exe $<TARGET_FILE:myexe>)
+
+
+

This creates a test mytest whose command runs a testDriver tool +passing the configuration name and the full path to the executable +file produced by target myexe.

+
+

The command syntax above is recommended over the older, less flexible form:

+
add_test(<name> <command> [<arg>...])
+
+
+

Add a test called <name> with the given command-line.

+

Unlike the above NAME signature, target names are not supported +in the command-line. Furthermore, tests added with this signature do not +support generator expressions +in the command-line or test properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/aux_source_directory.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/aux_source_directory.html new file mode 100644 index 0000000000000000000000000000000000000000..cb5312096ec38a73b5c2ba7e05419b203c3d8f61 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/aux_source_directory.html @@ -0,0 +1,156 @@ + + + + + + + + + aux_source_directory — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

aux_source_directory

+

Find all source files in a directory.

+
aux_source_directory(<dir> <variable>)
+
+
+

Collects the names of all the source files in the specified directory +and stores the list in the <variable> provided. This command is +intended to be used by projects that use explicit template +instantiation. Template instantiation files can be stored in a +Templates subdirectory and collected automatically using this +command to avoid manually listing all instantiations.

+

It is tempting to use this command to avoid writing the list of source +files for a library or executable target. While this seems to work, +there is no way for CMake to generate a build system that knows when a +new source file has been added. Normally the generated build system +knows when it needs to rerun CMake because the CMakeLists.txt file is +modified to add a new source. When the source is just added to the +directory without modifying this file, one would have to manually +rerun CMake to generate a build system incorporating the new file.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/block.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/block.html new file mode 100644 index 0000000000000000000000000000000000000000..8b003fef142b31cfe337992b6c4ca8847c91442f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/block.html @@ -0,0 +1,214 @@ + + + + + + + + + block — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

block

+
+

New in version 3.25.

+
+

Evaluate a group of commands with a dedicated variable and/or policy scope.

+
block([SCOPE_FOR [POLICIES] [VARIABLES] ] [PROPAGATE <var-name>...])
+  <commands>
+endblock()
+
+
+

All commands between block() and the matching endblock() are +recorded without being invoked. Once the endblock() is evaluated, the +recorded list of commands is invoked inside the requested scopes, then the +scopes created by the block() command are removed.

+
+
SCOPE_FOR

Specify which scopes must be created.

+
+
POLICIES

Create a new policy scope. This is equivalent to +cmake_policy(PUSH).

+
+
VARIABLES

Create a new variable scope.

+
+
+

If SCOPE_FOR is not specified, this is equivalent to:

+
block(SCOPE_FOR VARIABLES POLICIES)
+
+
+
+
PROPAGATE

When a variable scope is created by the block() command, this +option sets or unsets the specified variables in the parent scope. This is +equivalent to set(PARENT_SCOPE) or unset(PARENT_SCOPE) +commands.

+
set(var1 "INIT1")
+set(var2 "INIT2")
+
+block(PROPAGATE var1 var2)
+  set(var1 "VALUE1")
+  unset(var2)
+endblock()
+
+# Now var1 holds VALUE1, and var2 is unset
+
+
+

This option is only allowed when a variable scope is created. An error will +be raised in the other cases.

+
+
+

When the block() is inside a foreach() or while() +command, the break() and continue() commands can be used +inside the block.

+
while(TRUE)
+  block()
+     ...
+     # the break() command will terminate the while() command
+     break()
+  endblock()
+endwhile()
+
+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/break.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/break.html new file mode 100644 index 0000000000000000000000000000000000000000..19caa7638ccbc3959e1775f1f5928ea7f1904575 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/break.html @@ -0,0 +1,144 @@ + + + + + + + + + break — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

break

+

Break from an enclosing foreach or while loop.

+
break()
+
+
+

Breaks from an enclosing foreach() or while() loop.

+

See also the continue() command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/build_command.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/build_command.html new file mode 100644 index 0000000000000000000000000000000000000000..1feddf39ec2d866850d510deca33be4cc2b4b109 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/build_command.html @@ -0,0 +1,181 @@ + + + + + + + + + build_command — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

build_command

+

Get a command line to build the current project. +This is mainly intended for internal use by the CTest module.

+
build_command(<variable>
+              [CONFIGURATION <config>]
+              [PARALLEL_LEVEL <parallel>]
+              [TARGET <target>]
+              [PROJECT_NAME <projname>] # legacy, causes warning
+             )
+
+
+

Sets the given <variable> to a command-line string of the form:

+
<cmake> --build . [--config <config>] [--parallel <parallel>] [--target <target>...] [-- -i]
+
+
+

where <cmake> is the location of the cmake(1) command-line +tool, and <config>, <parallel> and <target> are the values +provided to the CONFIGURATION, PARALLEL_LEVEL and TARGET +options, if any. The trailing -- -i option is added for +Makefile Generators if policy CMP0061 is not set to +NEW.

+

When invoked, this cmake --build command line will launch the +underlying build system tool.

+
+

New in version 3.21: The PARALLEL_LEVEL argument can be used to set the +--parallel flag.

+
+
build_command(<cachevariable> <makecommand>)
+
+
+

This second signature is deprecated, but still available for backwards +compatibility. Use the first signature instead.

+

It sets the given <cachevariable> to a command-line string as +above but without the --target option. +The <makecommand> is ignored but should be the full path to +devenv, nmake, make or one of the end user build tools +for legacy invocations.

+
+

Note

+

In CMake versions prior to 3.0 this command returned a command +line that directly invokes the native build tool for the current +generator. Their implementation of the PROJECT_NAME option +had no useful effects, so CMake now warns on use of the option.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/build_name.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/build_name.html new file mode 100644 index 0000000000000000000000000000000000000000..174efd7d9a198eea70abd6d97d33aca7f8e3871e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/build_name.html @@ -0,0 +1,147 @@ + + + + + + + + + build_name — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

build_name

+

Disallowed since version 3.0. See CMake Policy CMP0036.

+

Use ${CMAKE_SYSTEM} and ${CMAKE_CXX_COMPILER} instead.

+
build_name(variable)
+
+
+

Sets the specified variable to a string representing the platform and +compiler settings. These values are now available through the +CMAKE_SYSTEM and +CMAKE_CXX_COMPILER variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_file_api.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_file_api.html new file mode 100644 index 0000000000000000000000000000000000000000..9b752e40aea30b4602596f152b193c3a2afb1f6f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_file_api.html @@ -0,0 +1,217 @@ + + + + + + + + + cmake_file_api — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

cmake_file_api

+
+

New in version 3.27.

+
+

Enables interacting with the CMake file API.

+
+
+cmake_file_api(QUERY ...)
+

The QUERY subcommand adds a file API query for the current CMake +invocation.

+
cmake_file_api(
+  QUERY
+  API_VERSION <version>
+  [CODEMODEL <versions>...]
+  [CACHE <versions>...]
+  [CMAKEFILES <versions>...]
+  [TOOLCHAINS <versions>...]
+)
+
+
+

The API_VERSION must always be given. Currently, the only supported +value for <version> is 1. See API v1 for details of the +reply content and location.

+

Each of the optional keywords CODEMODEL, CACHE, CMAKEFILES and +TOOLCHAINS correspond to one of the object kinds that can be requested +by the project. The configureLog object kind cannot be set with this +command, since it must be set before CMake starts reading the top level +CMakeLists.txt file.

+

For each of the optional keywords, the <versions> list must contain one +or more version values of the form major or major.minor, where +major and minor are integers. Projects should list the versions they +accept in their preferred order, as only the first supported value from the +list will be selected. The command will ignore versions with a major +version higher than any major version it supports for that object kind. +It will raise an error if it encounters an invalid version number, or if none +of the requested versions is supported.

+

For each type of object kind requested, a query equivalent to a shared, +stateless query will be added internally. No query file will be created in +the file system. The reply will be written to the file system at +generation time.

+

It is not an error to add a query for the same thing more than once, whether +from query files or from multiple calls to cmake_file_api(QUERY). +The final set of queries will be a merged combination of all queries +specified on disk and queries submitted by the project.

+
+ +
+

Example

+

A project may want to use replies from the file API at build time to implement +some form of verification task. Instead of relying on something outside of +CMake to create a query file, the project can use cmake_file_api(QUERY) +to request the required information for the current run. It can then create +a custom command to run at build time, knowing that the requested information +should always be available.

+
cmake_file_api(
+  QUERY
+  API_VERSION 1
+  CODEMODEL 2.3
+  TOOLCHAINS 1
+)
+
+add_custom_target(verify_project
+  COMMAND ${CMAKE_COMMAND}
+    -D BUILD_DIR=${CMAKE_BINARY_DIR}
+    -D CONFIG=$<CONFIG>
+    -P ${CMAKE_CURRENT_SOURCE_DIR}/verify_project.cmake
+)
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_host_system_information.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_host_system_information.html new file mode 100644 index 0000000000000000000000000000000000000000..c3be3e454632e0a213a4a6dcb678906a51ca63bf --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_host_system_information.html @@ -0,0 +1,519 @@ + + + + + + + + + cmake_host_system_information — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

cmake_host_system_information

+

Query various host system information.

+
+

Synopsis

+
Query host system specific information
+  cmake_host_system_information(RESULT <variable> QUERY <key> ...)
+
+Query Windows registry
+  cmake_host_system_information(RESULT <variable> QUERY WINDOWS_REGISTRY <key> ...)
+
+
+

Query host system specific information

+
cmake_host_system_information(RESULT <variable> QUERY <key> ...)
+
+
+

Queries system information of the host system on which cmake runs. +One or more <key> can be provided to select the information to be +queried. The list of queried values is stored in <variable>.

+

<key> can be one of the following values:

+
+
NUMBER_OF_LOGICAL_CORES

Number of logical cores

+
+
NUMBER_OF_PHYSICAL_CORES

Number of physical cores

+
+
HOSTNAME

Hostname

+
+
FQDN

Fully qualified domain name

+
+
TOTAL_VIRTUAL_MEMORY

Total virtual memory in MiB [1]

+
+
AVAILABLE_VIRTUAL_MEMORY

Available virtual memory in MiB [1]

+
+
TOTAL_PHYSICAL_MEMORY

Total physical memory in MiB [1]

+
+
AVAILABLE_PHYSICAL_MEMORY

Available physical memory in MiB [1]

+
+
IS_64BIT
+

New in version 3.10.

+
+

One if processor is 64Bit

+
+
HAS_FPU
+

New in version 3.10.

+
+

One if processor has floating point unit

+
+
HAS_MMX
+

New in version 3.10.

+
+

One if processor supports MMX instructions

+
+
HAS_MMX_PLUS
+

New in version 3.10.

+
+

One if processor supports Ext. MMX instructions

+
+
HAS_SSE
+

New in version 3.10.

+
+

One if processor supports SSE instructions

+
+
HAS_SSE2
+

New in version 3.10.

+
+

One if processor supports SSE2 instructions

+
+
HAS_SSE_FP
+

New in version 3.10.

+
+

One if processor supports SSE FP instructions

+
+
HAS_SSE_MMX
+

New in version 3.10.

+
+

One if processor supports SSE MMX instructions

+
+
HAS_AMD_3DNOW
+

New in version 3.10.

+
+

One if processor supports 3DNow instructions

+
+
HAS_AMD_3DNOW_PLUS
+

New in version 3.10.

+
+

One if processor supports 3DNow+ instructions

+
+
HAS_IA64
+

New in version 3.10.

+
+

One if IA64 processor emulating x86

+
+
HAS_SERIAL_NUMBER
+

New in version 3.10.

+
+

One if processor has serial number

+
+
PROCESSOR_SERIAL_NUMBER
+

New in version 3.10.

+
+

Processor serial number

+
+
PROCESSOR_NAME
+

New in version 3.10.

+
+

Human readable processor name

+
+
PROCESSOR_DESCRIPTION
+

New in version 3.10.

+
+

Human readable full processor description

+
+
OS_NAME
+

New in version 3.10.

+
+

See CMAKE_HOST_SYSTEM_NAME

+
+
OS_RELEASE
+

New in version 3.10.

+
+

The OS sub-type e.g. on Windows Professional

+
+
OS_VERSION
+

New in version 3.10.

+
+

The OS build ID

+
+
OS_PLATFORM
+

New in version 3.10.

+
+

See CMAKE_HOST_SYSTEM_PROCESSOR

+
+
DISTRIB_INFO
+

New in version 3.22.

+
+

Read /etc/os-release file and define the given <variable> +into a list of read variables

+
+
DISTRIB_<name>
+

New in version 3.22.

+
+

Get the <name> variable (see man 5 os-release) if it exists in the +/etc/os-release file

+

Example:

+
cmake_host_system_information(RESULT PRETTY_NAME QUERY DISTRIB_PRETTY_NAME)
+message(STATUS "${PRETTY_NAME}")
+
+cmake_host_system_information(RESULT DISTRO QUERY DISTRIB_INFO)
+
+foreach(VAR IN LISTS DISTRO)
+  message(STATUS "${VAR}=`${${VAR}}`")
+endforeach()
+
+
+

Output:

+
-- Ubuntu 20.04.2 LTS
+-- DISTRO_BUG_REPORT_URL=`https://bugs.launchpad.net/ubuntu/`
+-- DISTRO_HOME_URL=`https://www.ubuntu.com/`
+-- DISTRO_ID=`ubuntu`
+-- DISTRO_ID_LIKE=`debian`
+-- DISTRO_NAME=`Ubuntu`
+-- DISTRO_PRETTY_NAME=`Ubuntu 20.04.2 LTS`
+-- DISTRO_PRIVACY_POLICY_URL=`https://www.ubuntu.com/legal/terms-and-policies/privacy-policy`
+-- DISTRO_SUPPORT_URL=`https://help.ubuntu.com/`
+-- DISTRO_UBUNTU_CODENAME=`focal`
+-- DISTRO_VERSION=`20.04.2 LTS (Focal Fossa)`
+-- DISTRO_VERSION_CODENAME=`focal`
+-- DISTRO_VERSION_ID=`20.04`
+
+
+
+
+

If /etc/os-release file is not found, the command tries to gather OS +identification via fallback scripts. The fallback script can use various +distribution-specific files to collect OS identification data and map it +into man 5 os-release variables.

+
+

Fallback Interface Variables

+
+
+CMAKE_GET_OS_RELEASE_FALLBACK_SCRIPTS
+

In addition to the scripts shipped with CMake, a user may append full +paths to his script(s) to the this list. The script filename has the +following format: NNN-<name>.cmake, where NNN is three digits +used to apply collected scripts in a specific order.

+
+ +
+
+CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_<varname>
+

Variables collected by the user provided fallback script +ought to be assigned to CMake variables using this naming +convention. Example, the ID variable from the manual becomes +CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_ID.

+
+ +
+
+CMAKE_GET_OS_RELEASE_FALLBACK_RESULT
+

The fallback script ought to store names of all assigned +CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_<varname> variables in this list.

+
+ +

Example:

+
# Try to detect some old distribution
+# See also
+# - http://linuxmafia.com/faq/Admin/release-files.html
+#
+if(NOT EXISTS "${CMAKE_SYSROOT}/etc/foobar-release")
+  return()
+endif()
+# Get the first string only
+file(
+    STRINGS "${CMAKE_SYSROOT}/etc/foobar-release" CMAKE_GET_OS_RELEASE_FALLBACK_CONTENT
+    LIMIT_COUNT 1
+  )
+#
+# Example:
+#
+#   Foobar distribution release 1.2.3 (server)
+#
+if(CMAKE_GET_OS_RELEASE_FALLBACK_CONTENT MATCHES "Foobar distribution release ([0-9\.]+) .*")
+  set(CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_NAME Foobar)
+  set(CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_PRETTY_NAME "${CMAKE_GET_OS_RELEASE_FALLBACK_CONTENT}")
+  set(CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_ID foobar)
+  set(CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_VERSION ${CMAKE_MATCH_1})
+  set(CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_VERSION_ID ${CMAKE_MATCH_1})
+  list(
+      APPEND CMAKE_GET_OS_RELEASE_FALLBACK_RESULT
+      CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_NAME
+      CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_PRETTY_NAME
+      CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_ID
+      CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_VERSION
+      CMAKE_GET_OS_RELEASE_FALLBACK_RESULT_VERSION_ID
+    )
+endif()
+unset(CMAKE_GET_OS_RELEASE_FALLBACK_CONTENT)
+
+
+

Footnotes

+ +
+
+
+

Query Windows registry

+
+

New in version 3.24.

+
+
cmake_host_system_information(RESULT <variable>
+                              QUERY WINDOWS_REGISTRY <key> [VALUE_NAMES|SUBKEYS|VALUE <name>]
+                              [VIEW (64|32|64_32|32_64|HOST|TARGET|BOTH)]
+                              [SEPARATOR <separator>]
+                              [ERROR_VARIABLE <result>])
+
+
+

Performs query operations on local computer registry subkey. Returns a list of +subkeys or value names that are located under the specified subkey in the +registry or the data of the specified value name. The result of the queried +entity is stored in <variable>.

+
+

Note

+

Querying registry for any other platforms than Windows, including +CYGWIN, will always returns an empty string and sets an error message in +the variable specified with sub-option ERROR_VARIABLE.

+
+

<key> specify the full path of a subkey on the local computer. The +<key> must include a valid root key. Valid root keys for the local computer +are:

+
    +
  • HKLM or HKEY_LOCAL_MACHINE

  • +
  • HKCU or HKEY_CURRENT_USER

  • +
  • HKCR or HKEY_CLASSES_ROOT

  • +
  • HKU or HKEY_USERS

  • +
  • HKCC or HKEY_CURRENT_CONFIG

  • +
+

And, optionally, the path to a subkey under the specified root key. The path +separator can be the slash or the backslash. <key> is not case sensitive. +For example:

+
cmake_host_system_information(RESULT result QUERY WINDOWS_REGISTRY "HKLM")
+cmake_host_system_information(RESULT result QUERY WINDOWS_REGISTRY "HKLM/SOFTWARE/Kitware")
+cmake_host_system_information(RESULT result QUERY WINDOWS_REGISTRY "HKCU\\SOFTWARE\\Kitware")
+
+
+
+
VALUE_NAMES

Request the list of value names defined under <key>. If a default value +is defined, it will be identified with the special name (default).

+
+
SUBKEYS

Request the list of subkeys defined under <key>.

+
+
VALUE <name>

Request the data stored in value named <name>. If VALUE is not +specified or argument is the special name (default), the content of the +default value, if any, will be returned.

+
# query default value for HKLM/SOFTWARE/Kitware key
+cmake_host_system_information(RESULT result
+                              QUERY WINDOWS_REGISTRY "HKLM/SOFTWARE/Kitware")
+
+# query default value for HKLM/SOFTWARE/Kitware key using special value name
+cmake_host_system_information(RESULT result
+                              QUERY WINDOWS_REGISTRY "HKLM/SOFTWARE/Kitware"
+                              VALUE "(default)")
+
+
+

Supported types are:

+
    +
  • REG_SZ.

  • +
  • REG_EXPAND_SZ. The returned data is expanded.

  • +
  • REG_MULTI_SZ. The returned is expressed as a CMake list. See also +SEPARATOR sub-option.

  • +
  • REG_DWORD.

  • +
  • REG_QWORD.

  • +
+

For all other types, an empty string is returned.

+
+
VIEW

Specify which registry views must be queried. When not specified, BOTH +view is used.

+
+
64

Query the 64bit registry. On 32bit Windows, returns always an empty +string.

+
+
32

Query the 32bit registry.

+
+
64_32

For VALUE sub-option or default value, query the registry using view +64, and if the request failed, query the registry using view 32. +For VALUE_NAMES and SUBKEYS sub-options, query both views (64 +and 32) and merge the results (sorted and duplicates removed).

+
+
32_64

For VALUE sub-option or default value, query the registry using view +32, and if the request failed, query the registry using view 64. +For VALUE_NAMES and SUBKEYS sub-options, query both views (32 +and 64) and merge the results (sorted and duplicates removed).

+
+
HOST

Query the registry matching the architecture of the host: 64 on 64bit +Windows and 32 on 32bit Windows.

+
+
TARGET

Query the registry matching the architecture specified by +CMAKE_SIZEOF_VOID_P variable. If not defined, fallback to +HOST view.

+
+
BOTH

Query both views (32 and 64). The order depends of the following +rules: If CMAKE_SIZEOF_VOID_P variable is defined. Use the +following view depending of the content of this variable:

+
    +
  • 8: 64_32

  • +
  • 4: 32_64

  • +
+

If CMAKE_SIZEOF_VOID_P variable is not defined, rely on +architecture of the host:

+
    +
  • 64bit: 64_32

  • +
  • 32bit: 32

  • +
+
+
+
+
SEPARATOR

Specify the separator character for REG_MULTI_SZ type. When not +specified, the character \0 is used.

+
+
ERROR_VARIABLE <result>

Returns any error raised during query operation. In case of success, the +variable holds an empty string.

+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_language.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_language.html new file mode 100644 index 0000000000000000000000000000000000000000..a14ebbb64c908703da8188966c3f72f02f74f39c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_language.html @@ -0,0 +1,627 @@ + + + + + + + + + cmake_language — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

cmake_language

+
+

New in version 3.18.

+
+

Call meta-operations on CMake commands.

+
+

Synopsis

+
cmake_language(CALL <command> [<arg>...])
+cmake_language(EVAL CODE <code>...)
+cmake_language(DEFER <options>... CALL <command> [<arg>...])
+cmake_language(SET_DEPENDENCY_PROVIDER <command> SUPPORTED_METHODS <methods>...)
+cmake_language(GET_MESSAGE_LOG_LEVEL <out-var>)
+
+
+

Introduction

+

This command will call meta-operations on built-in CMake commands or +those created via the macro() or function() commands.

+

cmake_language does not introduce a new variable or policy scope.

+
+
+

Calling Commands

+
+
+cmake_language(CALL <command> [<arg>...])
+

Calls the named <command> with the given arguments (if any). +For example, the code:

+
set(message_command "message")
+cmake_language(CALL ${message_command} STATUS "Hello World!")
+
+
+

is equivalent to

+
message(STATUS "Hello World!")
+
+
+
+

Note

+

To ensure consistency of the code, the following commands are not allowed:

+
    +
  • if / elseif / else / endif

  • +
  • block / endblock

  • +
  • while / endwhile

  • +
  • foreach / endforeach

  • +
  • function / endfunction

  • +
  • macro / endmacro

  • +
+
+
+ +
+
+

Evaluating Code

+
+
+cmake_language(EVAL CODE <code>...)
+

Evaluates the <code>... as CMake code.

+

For example, the code:

+
set(A TRUE)
+set(B TRUE)
+set(C TRUE)
+set(condition "(A AND B) OR C")
+
+cmake_language(EVAL CODE "
+  if (${condition})
+    message(STATUS TRUE)
+  else()
+    message(STATUS FALSE)
+  endif()"
+)
+
+
+

is equivalent to

+
set(A TRUE)
+set(B TRUE)
+set(C TRUE)
+set(condition "(A AND B) OR C")
+
+file(WRITE ${CMAKE_CURRENT_BINARY_DIR}/eval.cmake "
+  if (${condition})
+    message(STATUS TRUE)
+  else()
+    message(STATUS FALSE)
+  endif()"
+)
+
+include(${CMAKE_CURRENT_BINARY_DIR}/eval.cmake)
+
+
+
+ +
+
+

Deferring Calls

+
+

New in version 3.19.

+
+
+
+cmake_language(DEFER <options>... CALL <command> [<arg>...])
+

Schedules a call to the named <command> with the given arguments (if any) +to occur at a later time. By default, deferred calls are executed as if +written at the end of the current directory's CMakeLists.txt file, +except that they run even after a return() call. Variable +references in arguments are evaluated at the time the deferred call is +executed.

+

The options are:

+
+
DIRECTORY <dir>

Schedule the call for the end of the given directory instead of the +current directory. The <dir> may reference either a source +directory or its corresponding binary directory. Relative paths are +treated as relative to the current source directory.

+

The given directory must be known to CMake, being either the top-level +directory or one added by add_subdirectory(). Furthermore, +the given directory must not yet be finished processing. This means +it can be the current directory or one of its ancestors.

+
+
ID <id>

Specify an identification for the deferred call. +The <id> may not be empty and may not begin with a capital letter A-Z. +The <id> may begin with an underscore (_) only if it was generated +automatically by an earlier call that used ID_VAR to get the id.

+
+
ID_VAR <var>

Specify a variable in which to store the identification for the +deferred call. If ID <id> is not given, a new identification +will be generated and the generated id will start with an underscore (_).

+
+
+

The currently scheduled list of deferred calls may be retrieved:

+
cmake_language(DEFER [DIRECTORY <dir>] GET_CALL_IDS <var>)
+
+
+

This will store in <var> a semicolon-separated list of deferred call ids. The ids are for the directory scope in which +the calls have been deferred to (i.e. where they will be executed), which can +be different to the scope in which they were created. The DIRECTORY +option can be used to specify the scope for which to retrieve the call ids. +If that option is not given, the call ids for the current directory scope +will be returned.

+

Details of a specific call may be retrieved from its id:

+
cmake_language(DEFER [DIRECTORY <dir>] GET_CALL <id> <var>)
+
+
+

This will store in <var> a semicolon-separated list in which the first element is the name of the command to be +called, and the remaining elements are its unevaluated arguments (any +contained ; characters are included literally and cannot be distinguished +from multiple arguments). If multiple calls are scheduled with the same id, +this retrieves the first one. If no call is scheduled with the given id in +the specified DIRECTORY scope (or the current directory scope if no +DIRECTORY option is given), this stores an empty string in the variable.

+

Deferred calls may be canceled by their id:

+
cmake_language(DEFER [DIRECTORY <dir>] CANCEL_CALL <id>...)
+
+
+

This cancels all deferred calls matching any of the given ids in the specified +DIRECTORY scope (or the current directory scope if no DIRECTORY option +is given). Unknown ids are silently ignored.

+
+ +
+

Deferred Call Examples

+

For example, the code:

+
cmake_language(DEFER CALL message "${deferred_message}")
+cmake_language(DEFER ID_VAR id CALL message "Canceled Message")
+cmake_language(DEFER CANCEL_CALL ${id})
+message("Immediate Message")
+set(deferred_message "Deferred Message")
+
+
+

prints:

+
Immediate Message
+Deferred Message
+
+
+

The Cancelled Message is never printed because its command is +canceled. The deferred_message variable reference is not evaluated +until the call site, so it can be set after the deferred call is scheduled.

+

In order to evaluate variable references immediately when scheduling a +deferred call, wrap it using cmake_language(EVAL). However, note that +arguments will be re-evaluated in the deferred call, though that can be +avoided by using bracket arguments. For example:

+
set(deferred_message "Deferred Message 1")
+set(re_evaluated [[${deferred_message}]])
+cmake_language(EVAL CODE "
+  cmake_language(DEFER CALL message [[${deferred_message}]])
+  cmake_language(DEFER CALL message \"${re_evaluated}\")
+")
+message("Immediate Message")
+set(deferred_message "Deferred Message 2")
+
+
+

also prints:

+
Immediate Message
+Deferred Message 1
+Deferred Message 2
+
+
+
+
+
+

Dependency Providers

+
+

New in version 3.24.

+
+
+

Note

+

A high-level introduction to this feature can be found in the +Using Dependencies Guide.

+
+
+
+cmake_language(SET_DEPENDENCY_PROVIDER <command> SUPPORTED_METHODS <methods>...)
+

When a call is made to find_package() or +FetchContent_MakeAvailable(), the call may be forwarded to a +dependency provider which then has the opportunity to fulfill the request. +If the request is for one of the <methods> specified when the provider +was set, CMake calls the provider's <command> with a set of +method-specific arguments. If the provider does not fulfill the request, +or if the provider doesn't support the request's method, or no provider +is set, the built-in find_package() or +FetchContent_MakeAvailable() implementation is used to fulfill +the request in the usual way.

+

One or more of the following values can be specified for the <methods> +when setting the provider:

+
+
FIND_PACKAGE

The provider command accepts find_package() requests.

+
+
FETCHCONTENT_MAKEAVAILABLE_SERIAL

The provider command accepts FetchContent_MakeAvailable() +requests. It expects each dependency to be fed to the provider command +one at a time, not the whole list in one go.

+
+
+

Only one provider can be set at any point in time. If a provider is already +set when cmake_language(SET_DEPENDENCY_PROVIDER) is called, the new +provider replaces the previously set one. The specified <command> must +already exist when cmake_language(SET_DEPENDENCY_PROVIDER) is called. +As a special case, providing an empty string for the <command> and no +<methods> will discard any previously set provider.

+

The dependency provider can only be set while processing one of the files +specified by the CMAKE_PROJECT_TOP_LEVEL_INCLUDES variable. +Thus, dependency providers can only be set as part of the first call to +project(). Calling cmake_language(SET_DEPENDENCY_PROVIDER) +outside of that context will result in an error.

+
+

Note

+

The choice of dependency provider should always be under the user's control. +As a convenience, a project may choose to provide a file that users can +list in their CMAKE_PROJECT_TOP_LEVEL_INCLUDES variable, but +the use of such a file should always be the user's choice.

+
+
+ +
+

Provider commands

+

Providers define a single <command> to accept requests. The name of +the command should be specific to that provider, not something overly +generic that another provider might also use. This enables users to compose +different providers in their own custom provider. The recommended form is +xxx_provide_dependency(), where xxx is the provider-specific part +(e.g. vcpkg_provide_dependency(), conan_provide_dependency(), +ourcompany_provide_dependency(), and so on).

+
xxx_provide_dependency(<method> [<method-specific-args>...])
+
+
+

Because some methods expect certain variables to be set in the calling scope, +the provider command should typically be implemented as a macro rather than a +function. This ensures it does not introduce a new variable scope.

+

The arguments CMake passes to the dependency provider depend on the type of +request. The first argument is always the method, and it will only ever +be one of the <methods> that was specified when setting the provider.

+
+
FIND_PACKAGE

The <method-specific-args> will be everything passed to the +find_package() call that requested the dependency. The first of +these <method-specific-args> will therefore always be the name of the +dependency. Dependency names are case-sensitive for this method because +find_package() treats them case-sensitively too.

+

If the provider command fulfills the request, it must set the same variable +that find_package() expects to be set. For a dependency named +depName, the provider must set depName_FOUND to true if it fulfilled +the request. If the provider returns without setting this variable, CMake +will assume the request was not fulfilled and will fall back to the +built-in implementation.

+

If the provider needs to call the built-in find_package() +implementation as part of its processing, it can do so by including the +BYPASS_PROVIDER keyword as one of the arguments.

+
+
FETCHCONTENT_MAKEAVAILABE_SERIAL

The <method-specific-args> will be everything passed to the +FetchContent_Declare() call that corresponds to the requested +dependency, with the following exceptions:

+
    +
  • If SOURCE_DIR or BINARY_DIR were not part of the original +declared arguments, they will be added with their default values.

  • +
  • If FETCHCONTENT_TRY_FIND_PACKAGE_MODE is set to NEVER, +any FIND_PACKAGE_ARGS will be omitted.

  • +
  • The OVERRIDE_FIND_PACKAGE keyword is always omitted.

  • +
+

The first of the <method-specific-args> will always be the name of the +dependency. Dependency names are case-insensitive for this method because +FetchContent also treats them case-insensitively.

+

If the provider fulfills the request, it should call +FetchContent_SetPopulated(), passing the name of the dependency as +the first argument. The SOURCE_DIR and BINARY_DIR arguments to that +command should only be given if the provider makes the dependency's source +and build directories available in exactly the same way as the built-in +FetchContent_MakeAvailable() command.

+

If the provider returns without calling FetchContent_SetPopulated() +for the named dependency, CMake will assume the request was not fulfilled +and will fall back to the built-in implementation.

+

Note that empty arguments may be significant for this method (e.g. an empty +string following a GIT_SUBMODULES keyword). Therefore, if forwarding +these arguments on to another command, extra care must be taken to avoid such +arguments being silently dropped.

+

If FETCHCONTENT_SOURCE_DIR_<uppercaseDepName> is set, then the +dependency provider will never see requests for the <depName> dependency +for this method. When the user sets such a variable, they are explicitly +overriding where to get that dependency from and are taking on the +responsibility that their overriding version meets any requirements for that +dependency and is compatible with whatever else in the project uses it. +Depending on the value of FETCHCONTENT_TRY_FIND_PACKAGE_MODE +and whether the OVERRIDE_FIND_PACKAGE option was given to +FetchContent_Declare(), having +FETCHCONTENT_SOURCE_DIR_<uppercaseDepName> set may also prevent the +dependency provider from seeing requests for a find_package(depName) +call too.

+
+
+
+
+

Provider Examples

+

This first example only intercepts find_package() calls. The +provider command runs an external tool which copies the relevant artifacts +into a provider-specific directory, if that tool knows about the dependency. +It then relies on the built-in implementation to then find those artifacts. +FetchContent_MakeAvailable() calls would not go through the provider.

+
+
mycomp_provider.cmake
+
# Always ensure we have the policy settings this provider expects
+cmake_minimum_required(VERSION 3.24)
+
+set(MYCOMP_PROVIDER_INSTALL_DIR ${CMAKE_BINARY_DIR}/mycomp_packages
+  CACHE PATH "The directory this provider installs packages to"
+)
+# Tell the built-in implementation to look in our area first, unless
+# the find_package() call uses NO_..._PATH options to exclude it
+list(APPEND CMAKE_MODULE_PATH ${MYCOMP_PROVIDER_INSTALL_DIR}/cmake)
+list(APPEND CMAKE_PREFIX_PATH ${MYCOMP_PROVIDER_INSTALL_DIR})
+
+macro(mycomp_provide_dependency method package_name)
+  execute_process(
+    COMMAND some_tool ${package_name} --installdir ${MYCOMP_PROVIDER_INSTALL_DIR}
+    COMMAND_ERROR_IS_FATAL ANY
+  )
+endmacro()
+
+cmake_language(
+  SET_DEPENDENCY_PROVIDER mycomp_provide_dependency
+  SUPPORTED_METHODS FIND_PACKAGE
+)
+
+
+
+

The user would then typically use the above file like so:

+
cmake -DCMAKE_PROJECT_TOP_LEVEL_INCLUDES=/path/to/mycomp_provider.cmake ...
+
+
+

The next example demonstrates a provider that accepts both methods, but +only handles one specific dependency. It enforces providing Google Test +using FetchContent, but leaves all other dependencies to be +fulfilled by CMake's built-in implementation. It accepts a few different +names, which demonstrates one way of working around projects that hard-code +an unusual or undesirable way of adding this particular dependency to the +build. The example also demonstrates how to use the list() command +to preserve variables that may be overwritten by a call to +FetchContent_MakeAvailable().

+
+
mycomp_provider.cmake
+
cmake_minimum_required(VERSION 3.24)
+
+# Because we declare this very early, it will take precedence over any
+# details the project might declare later for the same thing
+include(FetchContent)
+FetchContent_Declare(
+  googletest
+  GIT_REPOSITORY https://github.com/google/googletest.git
+  GIT_TAG        e2239ee6043f73722e7aa812a459f54a28552929 # release-1.11.0
+)
+
+# Both FIND_PACKAGE and FETCHCONTENT_MAKEAVAILABLE_SERIAL methods provide
+# the package or dependency name as the first method-specific argument.
+macro(mycomp_provide_dependency method dep_name)
+  if("${dep_name}" MATCHES "^(gtest|googletest)$")
+    # Save our current command arguments in case we are called recursively
+    list(APPEND mycomp_provider_args ${method} ${dep_name})
+
+    # This will forward to the built-in FetchContent implementation,
+    # which detects a recursive call for the same thing and avoids calling
+    # the provider again if dep_name is the same as the current call.
+    FetchContent_MakeAvailable(googletest)
+
+    # Restore our command arguments
+    list(POP_BACK mycomp_provider_args dep_name method)
+
+    # Tell the caller we fulfilled the request
+    if("${method}" STREQUAL "FIND_PACKAGE")
+      # We need to set this if we got here from a find_package() call
+      # since we used a different method to fulfill the request.
+      # This example assumes projects only use the gtest targets,
+      # not any of the variables the FindGTest module may define.
+      set(${dep_name}_FOUND TRUE)
+    elseif(NOT "${dep_name}" STREQUAL "googletest")
+      # We used the same method, but were given a different name to the
+      # one we populated with. Tell the caller about the name it used.
+      FetchContent_SetPopulated(${dep_name}
+        SOURCE_DIR "${googletest_SOURCE_DIR}"
+        BINARY_DIR "${googletest_BINARY_DIR}"
+      )
+    endif()
+  endif()
+endmacro()
+
+cmake_language(
+  SET_DEPENDENCY_PROVIDER mycomp_provide_dependency
+  SUPPORTED_METHODS
+    FIND_PACKAGE
+    FETCHCONTENT_MAKEAVAILABLE_SERIAL
+)
+
+
+
+

The final example demonstrates how to modify arguments to a +find_package() call. It forces all such calls to have the +QUIET keyword. It uses the BYPASS_PROVIDER keyword to prevent +calling the provider command recursively for the same dependency.

+
+
mycomp_provider.cmake
+
cmake_minimum_required(VERSION 3.24)
+
+macro(mycomp_provide_dependency method)
+  find_package(${ARGN} BYPASS_PROVIDER QUIET)
+endmacro()
+
+cmake_language(
+  SET_DEPENDENCY_PROVIDER mycomp_provide_dependency
+  SUPPORTED_METHODS FIND_PACKAGE
+)
+
+
+
+
+
+
+

Getting current message log level

+
+

New in version 3.25.

+
+
+
+cmake_language(GET_MESSAGE_LOG_LEVEL <output_variable>)
+

Writes the current message() logging level +into the given <output_variable>.

+

See message() for the possible logging levels.

+

The current message logging level can be set either using the +--log-level +command line option of the cmake(1) program or using +the CMAKE_MESSAGE_LOG_LEVEL variable.

+

If both the command line option and the variable are set, the command line +option takes precedence. If neither are set, the default logging level +is returned.

+
+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_minimum_required.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_minimum_required.html new file mode 100644 index 0000000000000000000000000000000000000000..b7a8758d05301526e0345abdaf5767019f29eac0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_minimum_required.html @@ -0,0 +1,233 @@ + + + + + + + + + cmake_minimum_required — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

cmake_minimum_required

+

Require a minimum version of cmake.

+
cmake_minimum_required(VERSION <min>[...<policy_max>] [FATAL_ERROR])
+
+
+
+

New in version 3.12: The optional <policy_max> version.

+
+

Sets the minimum required version of cmake for a project. +Also updates the policy settings as explained below.

+

<min> and the optional <policy_max> are each CMake versions of the +form major.minor[.patch[.tweak]], and the ... is literal.

+

If the running version of CMake is lower than the <min> required +version it will stop processing the project and report an error. +The optional <policy_max> version, if specified, must be at least the +<min> version and affects policy settings as described in Policy Settings. +If the running version of CMake is older than 3.12, the extra ... +dots will be seen as version component separators, resulting in the +...<max> part being ignored and preserving the pre-3.12 behavior +of basing policies on <min>.

+

This command will set the value of the +CMAKE_MINIMUM_REQUIRED_VERSION variable to <min>.

+

The FATAL_ERROR option is accepted but ignored by CMake 2.6 and +higher. It should be specified so CMake versions 2.4 and lower fail +with an error instead of just a warning.

+
+

Note

+

Call the cmake_minimum_required() command at the beginning of +the top-level CMakeLists.txt file even before calling the +project() command. It is important to establish version +and policy settings before invoking other commands whose behavior +they may affect. See also policy CMP0000.

+

Calling cmake_minimum_required() inside a function() +limits some effects to the function scope when invoked. For example, +the CMAKE_MINIMUM_REQUIRED_VERSION variable won't be set +in the calling scope. Functions do not introduce their own policy +scope though, so policy settings of the caller will be affected +(see below). Due to this mix of things that do and do not affect the +calling scope, calling cmake_minimum_required() inside a function +is generally discouraged.

+
+
+

Policy Settings

+

The cmake_minimum_required(VERSION) command implicitly invokes the +cmake_policy(VERSION) command to specify that the current +project code is written for the given range of CMake versions. +All policies known to the running version of CMake and introduced +in the <min> (or <max>, if specified) version or earlier will +be set to use NEW behavior. All policies introduced in later +versions will be unset. This effectively requests behavior preferred +as of a given CMake version and tells newer CMake versions to warn +about their new policies.

+

When a <min> version higher than 2.4 is specified the command +implicitly invokes

+
cmake_policy(VERSION <min>[...<max>])
+
+
+

which sets CMake policies based on the range of versions specified. +When a <min> version 2.4 or lower is given the command implicitly +invokes

+
cmake_policy(VERSION 2.4[...<max>])
+
+
+

which enables compatibility features for CMake 2.4 and lower.

+
+

Changed in version 3.27: Compatibility with versions of CMake older than 3.5 is deprecated. +Calls to cmake_minimum_required(VERSION) or +cmake_policy(VERSION) that do not specify at least +3.5 as their policy version (optionally via ...<max>) +will produce a deprecation warning in CMake 3.27 and above.

+
+
+

Changed in version 3.19: Compatibility with versions of CMake older than 2.8.12 is deprecated. +Calls to cmake_minimum_required(VERSION) or +cmake_policy(VERSION) that do not specify at least +2.8.12 as their policy version (optionally via ...<max>) +will produce a deprecation warning in CMake 3.19 and above.

+
+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_parse_arguments.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_parse_arguments.html new file mode 100644 index 0000000000000000000000000000000000000000..bd18b98b6eddeccb504f64eec6b440afbe76d0fc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_parse_arguments.html @@ -0,0 +1,253 @@ + + + + + + + + + cmake_parse_arguments — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

cmake_parse_arguments

+

Parse function or macro arguments.

+
cmake_parse_arguments(<prefix> <options> <one_value_keywords>
+                      <multi_value_keywords> <args>...)
+
+cmake_parse_arguments(PARSE_ARGV <N> <prefix> <options>
+                      <one_value_keywords> <multi_value_keywords>)
+
+
+
+

New in version 3.5: This command is implemented natively. Previously, it has been defined in the +module CMakeParseArguments.

+
+

This command is for use in macros or functions. +It processes the arguments given to that macro or function, +and defines a set of variables which hold the values of the +respective options.

+

The first signature reads processes arguments passed in the <args>.... +This may be used in either a macro() or a function().

+
+

New in version 3.7: The PARSE_ARGV signature is only for use in a function() +body. In this case the arguments that are parsed come from the +ARGV# variables of the calling function. The parsing starts with +the <N>-th argument, where <N> is an unsigned integer. +This allows for the values to have special characters like ; in them.

+
+

The <options> argument contains all options for the respective macro, +i.e. keywords which can be used when calling the macro without any value +following, like e.g. the OPTIONAL keyword of the install() +command.

+

The <one_value_keywords> argument contains all keywords for this macro +which are followed by one value, like e.g. DESTINATION keyword of the +install() command.

+

The <multi_value_keywords> argument contains all keywords for this +macro which can be followed by more than one value, like e.g. the +TARGETS or FILES keywords of the install() command.

+
+

Changed in version 3.5: All keywords shall be unique. I.e. every keyword shall only be specified +once in either <options>, <one_value_keywords> or +<multi_value_keywords>. A warning will be emitted if uniqueness is +violated.

+
+

When done, cmake_parse_arguments will consider for each of the +keywords listed in <options>, <one_value_keywords> and +<multi_value_keywords> a variable composed of the given <prefix> +followed by "_" and the name of the respective keyword. These +variables will then hold the respective value from the argument list +or be undefined if the associated option could not be found. +For the <options> keywords, these will always be defined, +to TRUE or FALSE, whether the option is in the argument list or not.

+

All remaining arguments are collected in a variable +<prefix>_UNPARSED_ARGUMENTS that will be undefined if all arguments +were recognized. This can be checked afterwards to see +whether your macro was called with unrecognized parameters.

+
+

New in version 3.15: <one_value_keywords> and <multi_value_keywords> that were given no +values at all are collected in a variable +<prefix>_KEYWORDS_MISSING_VALUES that will be undefined if all keywords +received values. This can be checked to see if there were keywords without +any values given.

+
+

Consider the following example macro, my_install(), which takes similar +arguments to the real install() command:

+
macro(my_install)
+    set(options OPTIONAL FAST)
+    set(oneValueArgs DESTINATION RENAME)
+    set(multiValueArgs TARGETS CONFIGURATIONS)
+    cmake_parse_arguments(MY_INSTALL "${options}" "${oneValueArgs}"
+                          "${multiValueArgs}" ${ARGN} )
+
+    # ...
+
+
+

Assume my_install() has been called like this:

+
my_install(TARGETS foo bar DESTINATION bin OPTIONAL blub CONFIGURATIONS)
+
+
+

After the cmake_parse_arguments call the macro will have set or undefined +the following variables:

+
MY_INSTALL_OPTIONAL = TRUE
+MY_INSTALL_FAST = FALSE # was not used in call to my_install
+MY_INSTALL_DESTINATION = "bin"
+MY_INSTALL_RENAME <UNDEFINED> # was not used
+MY_INSTALL_TARGETS = "foo;bar"
+MY_INSTALL_CONFIGURATIONS <UNDEFINED> # was not used
+MY_INSTALL_UNPARSED_ARGUMENTS = "blub" # nothing expected after "OPTIONAL"
+MY_INSTALL_KEYWORDS_MISSING_VALUES = "CONFIGURATIONS"
+         # No value for "CONFIGURATIONS" given
+
+
+

You can then continue and process these variables.

+

Keywords terminate lists of values, e.g. if directly after a +one_value_keyword another recognized keyword follows, this is +interpreted as the beginning of the new option. E.g. +my_install(TARGETS foo DESTINATION OPTIONAL) would result in +MY_INSTALL_DESTINATION set to "OPTIONAL", but as OPTIONAL +is a keyword itself MY_INSTALL_DESTINATION will be empty (but added +to MY_INSTALL_KEYWORDS_MISSING_VALUES) and MY_INSTALL_OPTIONAL will +therefore be set to TRUE.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_path.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_path.html new file mode 100644 index 0000000000000000000000000000000000000000..dc7846aa26df0c4d5a0ebe64827f724822dbe217 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_path.html @@ -0,0 +1,788 @@ + + + + + + + + + cmake_path — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

cmake_path

+
+

New in version 3.20.

+
+

This command is for the manipulation of paths. Only syntactic aspects of +paths are handled, there is no interaction of any kind with any underlying +file system. The path may represent a non-existing path or even one that +is not allowed to exist on the current file system or platform. +For operations that do interact with the filesystem, see the file() +command.

+
+

Note

+

The cmake_path command handles paths in the format of the build system +(i.e. the host platform), not the target system. When cross-compiling, +if the path contains elements that are not representable on the host +platform (e.g. a drive letter when the host is not Windows), the results +will be unpredictable.

+
+
+

Synopsis

+
Conventions
+
+Path Structure And Terminology
+
+Normalization
+
+Decomposition
+  cmake_path(GET <path-var> ROOT_NAME <out-var>)
+  cmake_path(GET <path-var> ROOT_DIRECTORY <out-var>)
+  cmake_path(GET <path-var> ROOT_PATH <out-var>)
+  cmake_path(GET <path-var> FILENAME <out-var>)
+  cmake_path(GET <path-var> EXTENSION [LAST_ONLY] <out-var>)
+  cmake_path(GET <path-var> STEM [LAST_ONLY] <out-var>)
+  cmake_path(GET <path-var> RELATIVE_PART <out-var>)
+  cmake_path(GET <path-var> PARENT_PATH <out-var>)
+
+Query
+  cmake_path(HAS_ROOT_NAME <path-var> <out-var>)
+  cmake_path(HAS_ROOT_DIRECTORY <path-var> <out-var>)
+  cmake_path(HAS_ROOT_PATH <path-var> <out-var>)
+  cmake_path(HAS_FILENAME <path-var> <out-var>)
+  cmake_path(HAS_EXTENSION <path-var> <out-var>)
+  cmake_path(HAS_STEM <path-var> <out-var>)
+  cmake_path(HAS_RELATIVE_PART <path-var> <out-var>)
+  cmake_path(HAS_PARENT_PATH <path-var> <out-var>)
+  cmake_path(IS_ABSOLUTE <path-var> <out-var>)
+  cmake_path(IS_RELATIVE <path-var> <out-var>)
+  cmake_path(IS_PREFIX <path-var> <input> [NORMALIZE] <out-var>)
+  cmake_path(COMPARE <input1> <OP> <input2> <out-var>)
+
+Modification
+  cmake_path(SET <path-var> [NORMALIZE] <input>)
+  cmake_path(APPEND <path-var> [<input>...] [OUTPUT_VARIABLE <out-var>])
+  cmake_path(APPEND_STRING <path-var> [<input>...] [OUTPUT_VARIABLE <out-var>])
+  cmake_path(REMOVE_FILENAME <path-var> [OUTPUT_VARIABLE <out-var>])
+  cmake_path(REPLACE_FILENAME <path-var> <input> [OUTPUT_VARIABLE <out-var>])
+  cmake_path(REMOVE_EXTENSION <path-var> [LAST_ONLY] [OUTPUT_VARIABLE <out-var>])
+  cmake_path(REPLACE_EXTENSION <path-var> [LAST_ONLY] <input> [OUTPUT_VARIABLE <out-var>])
+
+Generation
+  cmake_path(NORMAL_PATH <path-var> [OUTPUT_VARIABLE <out-var>])
+  cmake_path(RELATIVE_PATH <path-var> [BASE_DIRECTORY <input>] [OUTPUT_VARIABLE <out-var>])
+  cmake_path(ABSOLUTE_PATH <path-var> [BASE_DIRECTORY <input>] [NORMALIZE] [OUTPUT_VARIABLE <out-var>])
+
+Native Conversion
+  cmake_path(NATIVE_PATH <path-var> [NORMALIZE] <out-var>)
+  cmake_path(CONVERT <input> TO_CMAKE_PATH_LIST <out-var> [NORMALIZE])
+  cmake_path(CONVERT <input> TO_NATIVE_PATH_LIST <out-var> [NORMALIZE])
+
+Hashing
+  cmake_path(HASH <path-var> <out-var>)
+
+
+

Conventions

+

The following conventions are used in this command's documentation:

+
+
<path-var>

Always the name of a variable. For commands that expect a <path-var> +as input, the variable must exist and it is expected to hold a single path.

+
+
<input>

A string literal which may contain a path, path fragment, or multiple paths +with a special separator depending on the command. See the description of +each command to see how this is interpreted.

+
+
<input>...

Zero or more string literal arguments.

+
+
<out-var>

The name of a variable into which the result of a command will be written.

+
+
+
+
+

Path Structure And Terminology

+

A path has the following structure (all components are optional, with some +constraints):

+
root-name root-directory-separator (item-name directory-separator)* filename
+
+
+
+
root-name

Identifies the root on a filesystem with multiple roots (such as "C:" +or "//myserver"). It is optional.

+
+
root-directory-separator

A directory separator that, if present, indicates that this path is +absolute. If it is missing and the first element other than the +root-name is an item-name, then the path is relative.

+
+
item-name

A sequence of characters that aren't directory separators. This name may +identify a file, a hard link, a symbolic link, or a directory. Two special +cases are recognized:

+
+
    +
  • The item name consisting of a single dot character . is a +directory name that refers to the current directory.

  • +
  • The item name consisting of two dot characters .. is a +directory name that refers to the parent directory.

  • +
+
+

The (...)* pattern shown above is to indicate that there can be zero +or more item names, with multiple items separated by a +directory-separator. The ()* characters are not part of the path.

+
+
directory-separator

The only recognized directory separator is a forward slash character /. +If this character is repeated, it is treated as a single directory +separator. In other words, /usr///////lib is the same as /usr/lib.

+
+
+
+
filename

A path has a filename if it does not end with a directory-separator. +The filename is effectively the last item-name of the path, so it +can also be a hard link, symbolic link or a directory.

+

A filename can have an extension. By default, the extension is +defined as the sub-string beginning at the left-most period (including +the period) and until the end of the filename. In commands that +accept a LAST_ONLY keyword, LAST_ONLY changes the interpretation +to the sub-string beginning at the right-most period.

+

The following exceptions apply to the above interpretation:

+
+
    +
  • If the first character in the filename is a period, that period is +ignored (i.e. a filename like ".profile" is treated as having +no extension).

  • +
  • If the filename is either . or .., it has no extension.

  • +
+
+

The stem is the part of the filename before the extension.

+
+
+

Some commands refer to a root-path. This is the concatenation of +root-name and root-directory-separator, either or both of which can +be empty. A relative-part refers to the full path with any root-path +removed.

+
+
+

Creating A Path Variable

+

While a path can be created with care using an ordinary set() +command, it is recommended to use cmake_path(SET) +instead, as it automatically converts the path to the required form where +required. The cmake_path(APPEND) subcommand may +be another suitable alternative where a path needs to be constructed by +joining fragments. The following example compares the three methods for +constructing the same path:

+
set(path1 "${CMAKE_CURRENT_SOURCE_DIR}/data")
+
+cmake_path(SET path2 "${CMAKE_CURRENT_SOURCE_DIR}/data")
+
+cmake_path(APPEND path3 "${CMAKE_CURRENT_SOURCE_DIR}" "data")
+
+
+

Modification and Generation sub-commands can either store the result +in-place, or in a separate variable named after an OUTPUT_VARIABLE +keyword. All other sub-commands store the result in a mandatory <out-var> +variable.

+
+
+

Normalization

+

Some sub-commands support normalizing a path. The algorithm used to +normalize a path is as follows:

+
    +
  1. If the path is empty, stop (the normalized form of an empty path is +also an empty path).

  2. +
  3. Replace each directory-separator, which may consist of multiple +separators, with a single / (/a///b  --> /a/b).

  4. +
  5. Remove each solitary period (.) and any immediately following +directory-separator (/a/./b/. --> /a/b).

  6. +
  7. Remove each item-name (other than ..) that is immediately +followed by a directory-separator and a .., along with any +immediately following directory-separator (/a/b/../c --> a/c).

  8. +
  9. If there is a root-directory, remove any .. and any +directory-separators immediately following them. The parent of the +root directory is treated as still the root directory (/../a --> /a).

  10. +
  11. If the last item-name is .., remove any trailing +directory-separator (../ --> ..).

  12. +
  13. If the path is empty by this stage, add a dot (normal form of ./ +is .).

  14. +
+
+
+

Decomposition

+

The following forms of the GET subcommand each retrieve a different +component or group of components from a path. See +Path Structure And Terminology for the meaning of each path component.

+
cmake_path(GET <path-var> ROOT_NAME <out-var>)
+cmake_path(GET <path-var> ROOT_DIRECTORY <out-var>)
+cmake_path(GET <path-var> ROOT_PATH <out-var>)
+cmake_path(GET <path-var> FILENAME <out-var>)
+cmake_path(GET <path-var> EXTENSION [LAST_ONLY] <out-var>)
+cmake_path(GET <path-var> STEM [LAST_ONLY] <out-var>)
+cmake_path(GET <path-var> RELATIVE_PART <out-var>)
+cmake_path(GET <path-var> PARENT_PATH <out-var>)
+
+
+

If a requested component is not present in the path, an empty string will be +stored in <out-var>. For example, only Windows systems have the concept +of a root-name, so when the host machine is non-Windows, the ROOT_NAME +subcommand will always return an empty string.

+

For PARENT_PATH, if the HAS_RELATIVE_PART subcommand returns false, +the result is a copy of <path-var>. Note that this implies that a root +directory is considered to have a parent, with that parent being itself. +Where HAS_RELATIVE_PART returns true, the result will essentially be +<path-var> with one less element.

+
+

Root examples

+
set(path "c:/a")
+
+cmake_path(GET path ROOT_NAME rootName)
+cmake_path(GET path ROOT_DIRECTORY rootDir)
+cmake_path(GET path ROOT_PATH rootPath)
+
+message("Root name is \"${rootName}\"")
+message("Root directory is \"${rootDir}\"")
+message("Root path is \"${rootPath}\"")
+
+
+
Root name is "c:"
+Root directory is "/"
+Root path is "c:/"
+
+
+
+
+

Filename examples

+
set(path "/a/b")
+cmake_path(GET path FILENAME filename)
+message("First filename is \"${filename}\"")
+
+# Trailing slash means filename is empty
+set(path "/a/b/")
+cmake_path(GET path FILENAME filename)
+message("Second filename is \"${filename}\"")
+
+
+
First filename is "b"
+Second filename is ""
+
+
+
+
+

Extension and stem examples

+
set(path "name.ext1.ext2")
+
+cmake_path(GET path EXTENSION fullExt)
+cmake_path(GET path STEM fullStem)
+message("Full extension is \"${fullExt}\"")
+message("Full stem is \"${fullStem}\"")
+
+# Effect of LAST_ONLY
+cmake_path(GET path EXTENSION LAST_ONLY lastExt)
+cmake_path(GET path STEM LAST_ONLY lastStem)
+message("Last extension is \"${lastExt}\"")
+message("Last stem is \"${lastStem}\"")
+
+# Special cases
+set(dotPath "/a/.")
+set(dotDotPath "/a/..")
+set(someMorePath "/a/.some.more")
+cmake_path(GET dotPath EXTENSION dotExt)
+cmake_path(GET dotPath STEM dotStem)
+cmake_path(GET dotDotPath EXTENSION dotDotExt)
+cmake_path(GET dotDotPath STEM dotDotStem)
+cmake_path(GET dotMorePath EXTENSION someMoreExt)
+cmake_path(GET dotMorePath STEM someMoreStem)
+message("Dot extension is \"${dotExt}\"")
+message("Dot stem is \"${dotStem}\"")
+message("Dot-dot extension is \"${dotDotExt}\"")
+message("Dot-dot stem is \"${dotDotStem}\"")
+message(".some.more extension is \"${someMoreExt}\"")
+message(".some.more stem is \"${someMoreStem}\"")
+
+
+
Full extension is ".ext1.ext2"
+Full stem is "name"
+Last extension is ".ext2"
+Last stem is "name.ext1"
+Dot extension is ""
+Dot stem is "."
+Dot-dot extension is ""
+Dot-dot stem is ".."
+.some.more extension is ".more"
+.some.more stem is ".some"
+
+
+
+
+

Relative part examples

+
set(path "c:/a/b")
+cmake_path(GET path RELATIVE_PART result)
+message("Relative part is \"${result}\"")
+
+set(path "c/d")
+cmake_path(GET path RELATIVE_PART result)
+message("Relative part is \"${result}\"")
+
+set(path "/")
+cmake_path(GET path RELATIVE_PART result)
+message("Relative part is \"${result}\"")
+
+
+
Relative part is "a/b"
+Relative part is "c/d"
+Relative part is ""
+
+
+
+
+

Path traversal examples

+
set(path "c:/a/b")
+cmake_path(GET path PARENT_PATH result)
+message("Parent path is \"${result}\"")
+
+set(path "c:/")
+cmake_path(GET path PARENT_PATH result)
+message("Parent path is \"${result}\"")
+
+
+
Parent path is "c:/a"
+Parent path is "c:/"
+
+
+
+
+
+

Query

+

Each of the GET subcommands has a corresponding HAS_... +subcommand which can be used to discover whether a particular path +component is present. See Path Structure And Terminology for the +meaning of each path component.

+
cmake_path(HAS_ROOT_NAME <path-var> <out-var>)
+cmake_path(HAS_ROOT_DIRECTORY <path-var> <out-var>)
+cmake_path(HAS_ROOT_PATH <path-var> <out-var>)
+cmake_path(HAS_FILENAME <path-var> <out-var>)
+cmake_path(HAS_EXTENSION <path-var> <out-var>)
+cmake_path(HAS_STEM <path-var> <out-var>)
+cmake_path(HAS_RELATIVE_PART <path-var> <out-var>)
+cmake_path(HAS_PARENT_PATH <path-var> <out-var>)
+
+
+

Each of the above follows the predictable pattern of setting <out-var> +to true if the path has the associated component, or false otherwise. +Note the following special cases:

+
    +
  • For HAS_ROOT_PATH, a true result will only be returned if at least one +of root-name or root-directory is non-empty.

  • +
  • For HAS_PARENT_PATH, the root directory is also considered to have a +parent, which will be itself. The result is true except if the path +consists of just a filename.

  • +
+
cmake_path(IS_ABSOLUTE <path-var> <out-var>)
+
+
+

Sets <out-var> to true if <path-var> is absolute. An absolute path +is a path that unambiguously identifies the location of a file without +reference to an additional starting location. On Windows, this means the +path must have both a root-name and a root-directory-separator to be +considered absolute. On other platforms, just a root-directory-separator +is sufficient. Note that this means on Windows, IS_ABSOLUTE can be +false while HAS_ROOT_DIRECTORY can be true.

+
cmake_path(IS_RELATIVE <path-var> <out-var>)
+
+
+

This will store the opposite of IS_ABSOLUTE in <out-var>.

+
cmake_path(IS_PREFIX <path-var> <input> [NORMALIZE] <out-var>)
+
+
+

Checks if <path-var> is the prefix of <input>.

+

When the NORMALIZE option is specified, <path-var> and <input> +are normalized before the check.

+
set(path "/a/b/c")
+cmake_path(IS_PREFIX path "/a/b/c/d" result) # result = true
+cmake_path(IS_PREFIX path "/a/b" result)     # result = false
+cmake_path(IS_PREFIX path "/x/y/z" result)   # result = false
+
+set(path "/a/b")
+cmake_path(IS_PREFIX path "/a/c/../b" NORMALIZE result)   # result = true
+
+
+
cmake_path(COMPARE <input1> EQUAL <input2> <out-var>)
+cmake_path(COMPARE <input1> NOT_EQUAL <input2> <out-var>)
+
+
+

Compares the lexical representations of two paths provided as string literals. +No normalization is performed on either path, except multiple consecutive +directory separators are effectively collapsed into a single separator. +Equality is determined according to the following pseudo-code logic:

+
if(NOT <input1>.root_name() STREQUAL <input2>.root_name())
+  return FALSE
+
+if(<input1>.has_root_directory() XOR <input2>.has_root_directory())
+  return FALSE
+
+Return FALSE if a relative portion of <input1> is not lexicographically
+equal to the relative portion of <input2>. This comparison is performed path
+component-wise. If all of the components compare equal, then return TRUE.
+
+
+
+

Note

+

Unlike most other cmake_path() subcommands, the COMPARE subcommand +takes literal strings as input, not the names of variables.

+
+
+
+

Modification

+
cmake_path(SET <path-var> [NORMALIZE] <input>)
+
+
+

Assign the <input> path to <path-var>. If <input> is a native +path, it is converted into a cmake-style path with forward-slashes +(/). On Windows, the long filename marker is taken into account.

+

When the NORMALIZE option is specified, the path is normalized after the conversion.

+

For example:

+
set(native_path "c:\\a\\b/..\\c")
+cmake_path(SET path "${native_path}")
+message("CMake path is \"${path}\"")
+
+cmake_path(SET path NORMALIZE "${native_path}")
+message("Normalized CMake path is \"${path}\"")
+
+
+

Output:

+
CMake path is "c:/a/b/../c"
+Normalized CMake path is "c:/a/c"
+
+
+
cmake_path(APPEND <path-var> [<input>...] [OUTPUT_VARIABLE <out-var>])
+
+
+

Append all the <input> arguments to the <path-var> using / as +the directory-separator. Depending on the <input>, the previous +contents of <path-var> may be discarded. For each <input> argument, +the following algorithm (pseudo-code) applies:

+
# <path> is the contents of <path-var>
+
+if(<input>.is_absolute() OR
+   (<input>.has_root_name() AND
+    NOT <input>.root_name() STREQUAL <path>.root_name()))
+  replace <path> with <input>
+  return()
+endif()
+
+if(<input>.has_root_directory())
+  remove any root-directory and the entire relative path from <path>
+elseif(<path>.has_filename() OR
+       (NOT <path-var>.has_root_directory() OR <path>.is_absolute()))
+  append directory-separator to <path>
+endif()
+
+append <input> omitting any root-name to <path>
+
+
+
cmake_path(APPEND_STRING <path-var> [<input>...] [OUTPUT_VARIABLE <out-var>])
+
+
+

Append all the <input> arguments to the <path-var> without adding any +directory-separator.

+
cmake_path(REMOVE_FILENAME <path-var> [OUTPUT_VARIABLE <out-var>])
+
+
+

Removes the filename component (as returned by +GET ... FILENAME) from <path-var>. After removal, +any trailing directory-separator is left alone, if present.

+

If OUTPUT_VARIABLE is not given, then after this function returns, +HAS_FILENAME returns false for <path-var>.

+

For example:

+
set(path "/a/b")
+cmake_path(REMOVE_FILENAME path)
+message("First path is \"${path}\"")
+
+# filename is now already empty, the following removes nothing
+cmake_path(REMOVE_FILENAME path)
+message("Second path is \"${result}\"")
+
+
+

Output:

+
First path is "/a/"
+Second path is "/a/"
+
+
+
cmake_path(REPLACE_FILENAME <path-var> <input> [OUTPUT_VARIABLE <out-var>])
+
+
+

Replaces the filename component from <path-var> +with <input>. If <path-var> has no filename component (i.e. +HAS_FILENAME returns false), the path is unchanged. The operation is +equivalent to the following:

+
cmake_path(HAS_FILENAME path has_filename)
+if(has_filename)
+  cmake_path(REMOVE_FILENAME path)
+  cmake_path(APPEND path input);
+endif()
+
+
+
cmake_path(REMOVE_EXTENSION <path-var> [LAST_ONLY]
+                                       [OUTPUT_VARIABLE <out-var>])
+
+
+

Removes the extension, if any, from <path-var>.

+
cmake_path(REPLACE_EXTENSION <path-var> [LAST_ONLY] <input>
+                             [OUTPUT_VARIABLE <out-var>])
+
+
+

Replaces the extension with <input>. Its effect +is equivalent to the following:

+
cmake_path(REMOVE_EXTENSION path)
+if(NOT "input" MATCHES "^\\.")
+  cmake_path(APPEND_STRING path ".")
+endif()
+cmake_path(APPEND_STRING path "input")
+
+
+
+
+

Generation

+
cmake_path(NORMAL_PATH <path-var> [OUTPUT_VARIABLE <out-var>])
+
+
+

Normalize <path-var> according the steps described in Normalization.

+
cmake_path(RELATIVE_PATH <path-var> [BASE_DIRECTORY <input>]
+                                    [OUTPUT_VARIABLE <out-var>])
+
+
+

Modifies <path-var> to make it relative to the BASE_DIRECTORY argument. +If BASE_DIRECTORY is not specified, the default base directory will be +CMAKE_CURRENT_SOURCE_DIR.

+

For reference, the algorithm used to compute the relative path is the same +as that used by C++ +std::filesystem::path::lexically_relative.

+
cmake_path(ABSOLUTE_PATH <path-var> [BASE_DIRECTORY <input>] [NORMALIZE]
+                                    [OUTPUT_VARIABLE <out-var>])
+
+
+

If <path-var> is a relative path (IS_RELATIVE is true), it is evaluated +relative to the given base directory specified by BASE_DIRECTORY option. +If BASE_DIRECTORY is not specified, the default base directory will be +CMAKE_CURRENT_SOURCE_DIR.

+

When the NORMALIZE option is specified, the path is normalized after the path computation.

+

Because cmake_path() does not access the filesystem, symbolic links are +not resolved and any leading tilde is not expanded. To compute a real path +with symbolic links resolved and leading tildes expanded, use the +file(REAL_PATH) command instead.

+
+
+

Native Conversion

+

For commands in this section, native refers to the host platform, not the +target platform when cross-compiling.

+
cmake_path(NATIVE_PATH <path-var> [NORMALIZE] <out-var>)
+
+
+

Converts a cmake-style <path-var> into a native path with +platform-specific slashes (\ on Windows hosts and / elsewhere).

+

When the NORMALIZE option is specified, the path is normalized before the conversion.

+
cmake_path(CONVERT <input> TO_CMAKE_PATH_LIST <out-var> [NORMALIZE])
+
+
+

Converts a native <input> path into a cmake-style path with forward +slashes (/). On Windows hosts, the long filename marker is taken into +account. The input can be a single path or a system search path like +$ENV{PATH}. A search path will be converted to a cmake-style list +separated by ; characters (on non-Windows platforms, this essentially +means : separators are replaced with ;). The result of the +conversion is stored in the <out-var> variable.

+

When the NORMALIZE option is specified, the path is normalized before the conversion.

+
+

Note

+

Unlike most other cmake_path() subcommands, the CONVERT subcommand +takes a literal string as input, not the name of a variable.

+
+
cmake_path(CONVERT <input> TO_NATIVE_PATH_LIST <out-var> [NORMALIZE])
+
+
+

Converts a cmake-style <input> path into a native path with +platform-specific slashes (\ on Windows hosts and / elsewhere). +The input can be a single path or a cmake-style list. A list will be +converted into a native search path (;-separated on Windows, +:-separated on other platforms). The result of the conversion is +stored in the <out-var> variable.

+

When the NORMALIZE option is specified, the path is normalized before the conversion.

+
+

Note

+

Unlike most other cmake_path() subcommands, the CONVERT subcommand +takes a literal string as input, not the name of a variable.

+
+

For example:

+
set(paths "/a/b/c" "/x/y/z")
+cmake_path(CONVERT "${paths}" TO_NATIVE_PATH_LIST native_paths)
+message("Native path list is \"${native_paths}\"")
+
+
+

Output on Windows:

+
Native path list is "\a\b\c;\x\y\z"
+
+
+

Output on all other platforms:

+
Native path list is "/a/b/c:/x/y/z"
+
+
+
+
+

Hashing

+
cmake_path(HASH <path-var> <out-var>)
+
+
+

Compute a hash value of <path-var> such that for two paths p1 and +p2 that compare equal (COMPARE ... EQUAL), the hash +value of p1 is equal to the hash value of p2. The path is always +normalized before the hash is computed.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_policy.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_policy.html new file mode 100644 index 0000000000000000000000000000000000000000..f748e15479a5b9ae930b39ccd17324e95347e7fe --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/cmake_policy.html @@ -0,0 +1,310 @@ + + + + + + + + + cmake_policy — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

cmake_policy

+

Manage CMake Policy settings. See the cmake-policies(7) +manual for defined policies.

+

As CMake evolves it is sometimes necessary to change existing behavior +in order to fix bugs or improve implementations of existing features. +The CMake Policy mechanism is designed to help keep existing projects +building as new versions of CMake introduce changes in behavior. Each +new policy (behavioral change) is given an identifier of the form +CMP<NNNN> where <NNNN> is an integer index. Documentation +associated with each policy describes the OLD and NEW behavior +and the reason the policy was introduced. Projects may set each policy +to select the desired behavior. When CMake needs to know which behavior +to use it checks for a setting specified by the project. If no +setting is available the OLD behavior is assumed and a warning is +produced requesting that the policy be set.

+
+

Setting Policies by CMake Version

+

The cmake_policy command is used to set policies to OLD or NEW +behavior. While setting policies individually is supported, we +encourage projects to set policies based on CMake versions:

+
cmake_policy(VERSION <min>[...<max>])
+
+
+
+

New in version 3.12: The optional <max> version.

+
+

<min> and the optional <max> are each CMake versions of the form +major.minor[.patch[.tweak]], and the ... is literal. The <min> +version must be at least 2.4 and at most the running version of CMake. +The <max> version, if specified, must be at least the <min> version +but may exceed the running version of CMake. If the running version of +CMake is older than 3.12, the extra ... dots will be seen as version +component separators, resulting in the ...<max> part being ignored and +preserving the pre-3.12 behavior of basing policies on <min>.

+

This specifies that the current CMake code is written for the given +range of CMake versions. All policies known to the running version of CMake +and introduced in the <min> (or <max>, if specified) version +or earlier will be set to use NEW behavior. All policies +introduced in later versions will be unset (unless the +CMAKE_POLICY_DEFAULT_CMP<NNNN> variable sets a default). +This effectively requests behavior preferred as of a given CMake +version and tells newer CMake versions to warn about their new policies.

+

Note that the cmake_minimum_required(VERSION) +command implicitly calls cmake_policy(VERSION) too.

+
+

Changed in version 3.27: Compatibility with versions of CMake older than 3.5 is deprecated. +Calls to cmake_minimum_required(VERSION) or +cmake_policy(VERSION) that do not specify at least +3.5 as their policy version (optionally via ...<max>) +will produce a deprecation warning in CMake 3.27 and above.

+
+
+

Changed in version 3.19: Compatibility with versions of CMake older than 2.8.12 is deprecated. +Calls to cmake_minimum_required(VERSION) or +cmake_policy(VERSION) that do not specify at least +2.8.12 as their policy version (optionally via ...<max>) +will produce a deprecation warning in CMake 3.19 and above.

+
+
+
+

Setting Policies Explicitly

+
cmake_policy(SET CMP<NNNN> NEW)
+cmake_policy(SET CMP<NNNN> OLD)
+
+
+

Tell CMake to use the OLD or NEW behavior for a given policy. +Projects depending on the old behavior of a given policy may silence a +policy warning by setting the policy state to OLD. Alternatively +one may fix the project to work with the new behavior and set the +policy state to NEW.

+
+

Note

+

The OLD behavior of a policy is +deprecated by definition +and may be removed in a future version of CMake.

+
+
+
+

Checking Policy Settings

+
cmake_policy(GET CMP<NNNN> <variable>)
+
+
+

Check whether a given policy is set to OLD or NEW behavior. +The output <variable> value will be OLD or NEW if the +policy is set, and empty otherwise.

+
+
+

CMake Policy Stack

+

CMake keeps policy settings on a stack, so changes made by the +cmake_policy command affect only the top of the stack. A new entry on +the policy stack is managed automatically for each subdirectory to +protect its parents and siblings. CMake also manages a new entry for +scripts loaded by include() and find_package() commands +except when invoked with the NO_POLICY_SCOPE option +(see also policy CMP0011). +The cmake_policy command provides an interface to manage custom +entries on the policy stack:

+
cmake_policy(PUSH)
+cmake_policy(POP)
+
+
+

Each PUSH must have a matching POP to erase any changes. +This is useful to make temporary changes to policy settings. +Calls to the cmake_minimum_required(VERSION), +cmake_policy(VERSION), or cmake_policy(SET) commands +influence only the current top of the policy stack.

+
+

New in version 3.25: The block() and endblock() commands offer a more flexible +and more secure way to manage the policy stack. The pop action is done +automatically when the endblock() command is executed, so it avoid +to call the cmake_policy(POP) command before each +return() command.

+
# stack management with cmake_policy()
+function(my_func)
+  cmake_policy(PUSH)
+  cmake_policy(SET ...)
+  if (<cond1>)
+    ...
+    cmake_policy(POP)
+    return()
+  elseif(<cond2>)
+    ...
+    cmake_policy(POP)
+    return()
+  endif()
+  ...
+  cmake_policy(POP)
+endfunction()
+
+# stack management with block()/endblock()
+function(my_func)
+  block(SCOPE_FOR POLICIES)
+    cmake_policy(SET ...)
+    if (<cond1>)
+      ...
+      return()
+    elseif(<cond2>)
+      ...
+      return()
+    endif()
+    ...
+  endblock()
+endfunction()
+
+
+
+

Commands created by the function() and macro() +commands record policy settings when they are created and +use the pre-record policies when they are invoked. If the function or +macro implementation sets policies, the changes automatically +propagate up through callers until they reach the closest nested +policy stack entry.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/configure_file.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/configure_file.html new file mode 100644 index 0000000000000000000000000000000000000000..161b38af565c5560d0bc4aeb461b59c8f5d45f44 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/configure_file.html @@ -0,0 +1,301 @@ + + + + + + + + + configure_file — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

configure_file

+

Copy a file to another location and modify its contents.

+
configure_file(<input> <output>
+               [NO_SOURCE_PERMISSIONS | USE_SOURCE_PERMISSIONS |
+                FILE_PERMISSIONS <permissions>...]
+               [COPYONLY] [ESCAPE_QUOTES] [@ONLY]
+               [NEWLINE_STYLE [UNIX|DOS|WIN32|LF|CRLF] ])
+
+
+

Copies an <input> file to an <output> file and substitutes +variable values referenced as @VAR@, ${VAR}, $CACHE{VAR} or +$ENV{VAR} in the input file content. Each variable reference will be +replaced with the current value of the variable, or the empty string if +the variable is not defined. Furthermore, input lines of the form

+
#cmakedefine VAR ...
+
+
+

will be replaced with either

+
#define VAR ...
+
+
+

or

+
/* #undef VAR */
+
+
+

depending on whether VAR is set in CMake to any value not considered +a false constant by the if() command. The "..." content on the +line after the variable name, if any, is processed as above.

+

Unlike lines of the form #cmakedefine VAR ..., in lines of the form +#cmakedefine01 VAR, VAR itself will expand to VAR 0 or VAR 1 +rather than being assigned the value .... Therefore, input lines of the form

+
#cmakedefine01 VAR
+
+
+

will be replaced with either

+
#define VAR 0
+
+
+

or

+
#define VAR 1
+
+
+

Input lines of the form #cmakedefine01 VAR ... will expand +as #cmakedefine01 VAR ... 0 or #cmakedefine01 VAR ... 1, +which may lead to undefined behavior.

+
+

New in version 3.10: The result lines (with the exception of the #undef comments) can be +indented using spaces and/or tabs between the # character +and the cmakedefine or cmakedefine01 words. This whitespace +indentation will be preserved in the output lines:

+
#  cmakedefine VAR
+#  cmakedefine01 VAR
+
+
+

will be replaced, if VAR is defined, with

+
#  define VAR
+#  define VAR 1
+
+
+
+

If the input file is modified the build system will re-run CMake to +re-configure the file and generate the build system again. +The generated file is modified and its timestamp updated on subsequent +cmake runs only if its content is changed.

+

The arguments are:

+
+
<input>

Path to the input file. A relative path is treated with respect to +the value of CMAKE_CURRENT_SOURCE_DIR. The input path +must be a file, not a directory.

+
+
<output>

Path to the output file or directory. A relative path is treated +with respect to the value of CMAKE_CURRENT_BINARY_DIR. +If the path names an existing directory the output file is placed +in that directory with the same file name as the input file. +If the path contains non-existent directories, they are created.

+
+
NO_SOURCE_PERMISSIONS
+

New in version 3.19.

+
+

Do not transfer the permissions of the input file to the output file. +The copied file permissions default to the standard 644 value +(-rw-r--r--).

+
+
USE_SOURCE_PERMISSIONS
+

New in version 3.20.

+
+

Transfer the permissions of the input file to the output file. +This is already the default behavior if none of the three permissions-related +keywords are given (NO_SOURCE_PERMISSIONS, USE_SOURCE_PERMISSIONS +or FILE_PERMISSIONS). The USE_SOURCE_PERMISSIONS keyword mostly +serves as a way of making the intended behavior clearer at the call site.

+
+
FILE_PERMISSIONS <permissions>...
+

New in version 3.20.

+
+

Ignore the input file's permissions and use the specified <permissions> +for the output file instead.

+
+
COPYONLY

Copy the file without replacing any variable references or other +content. This option may not be used with NEWLINE_STYLE.

+
+
ESCAPE_QUOTES

Escape any substituted quotes with backslashes (C-style).

+
+
@ONLY

Restrict variable replacement to references of the form @VAR@. +This is useful for configuring scripts that use ${VAR} syntax.

+
+
NEWLINE_STYLE <style>

Specify the newline style for the output file. Specify +UNIX or LF for \n newlines, or specify +DOS, WIN32, or CRLF for \r\n newlines. +This option may not be used with COPYONLY.

+
+
+
+

Example

+

Consider a source tree containing a foo.h.in file:

+
#cmakedefine FOO_ENABLE
+#cmakedefine FOO_STRING "@FOO_STRING@"
+
+
+

An adjacent CMakeLists.txt may use configure_file to +configure the header:

+
option(FOO_ENABLE "Enable Foo" ON)
+if(FOO_ENABLE)
+  set(FOO_STRING "foo")
+endif()
+configure_file(foo.h.in foo.h @ONLY)
+
+
+

This creates a foo.h in the build directory corresponding to +this source directory. If the FOO_ENABLE option is on, the +configured file will contain:

+
#define FOO_ENABLE
+#define FOO_STRING "foo"
+
+
+

Otherwise it will contain:

+
/* #undef FOO_ENABLE */
+/* #undef FOO_STRING */
+
+
+

One may then use the target_include_directories() command to +specify the output directory as an include directory:

+
target_include_directories(<target> [SYSTEM] <INTERFACE|PUBLIC|PRIVATE> "${CMAKE_CURRENT_BINARY_DIR}")
+
+
+

so that sources may include the header as #include <foo.h>.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/continue.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/continue.html new file mode 100644 index 0000000000000000000000000000000000000000..69a052420048d5b472eb851e10bebade400c5148 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/continue.html @@ -0,0 +1,149 @@ + + + + + + + + + continue — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

continue

+
+

New in version 3.2.

+
+

Continue to the top of enclosing foreach or while loop.

+
continue()
+
+
+

The continue() command allows a cmake script to abort the rest of the +current iteration of a foreach() or while() loop, and start +at the top of the next iteration.

+

See also the break() command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/create_test_sourcelist.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/create_test_sourcelist.html new file mode 100644 index 0000000000000000000000000000000000000000..2b4f5865cdede248be60a419eddd16b0d9a3f58f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/create_test_sourcelist.html @@ -0,0 +1,163 @@ + + + + + + + + + create_test_sourcelist — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

create_test_sourcelist

+

Create a test driver and source list for building test programs.

+
create_test_sourcelist(sourceListName driverName
+                       test1 test2 test3
+                       EXTRA_INCLUDE include.h
+                       FUNCTION function)
+
+
+

A test driver is a program that links together many small tests into a +single executable. This is useful when building static executables +with large libraries to shrink the total required size. The list of +source files needed to build the test driver will be in +sourceListName. driverName is the name of the test driver program. +The rest of the arguments consist of a list of test source files, can +be semicolon separated. Each test source file should have a function +in it that is the same name as the file with no extension (foo.cxx +should have int foo(int, char*[]);) driverName will be able to call +each of the tests by name on the command line. If EXTRA_INCLUDE is +specified, then the next argument is included into the generated file. +If FUNCTION is specified, then the next argument is taken as a +function name that is passed a pointer to ac and av. This can be used +to add extra command line processing to each test. The +CMAKE_TESTDRIVER_BEFORE_TESTMAIN cmake variable can be set to +have code that will be placed directly before calling the test main function. +CMAKE_TESTDRIVER_AFTER_TESTMAIN can be set to have code that +will be placed directly after the call to the test main function.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_build.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_build.html new file mode 100644 index 0000000000000000000000000000000000000000..4d2db1d7d5f4c0695fc24c1ad1440121c4e5106e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_build.html @@ -0,0 +1,217 @@ + + + + + + + + + ctest_build — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_build

+

Perform the CTest Build Step as a Dashboard Client.

+
ctest_build([BUILD <build-dir>] [APPEND]
+            [CONFIGURATION <config>]
+            [PARALLEL_LEVEL <parallel>]
+            [FLAGS <flags>]
+            [PROJECT_NAME <project-name>]
+            [TARGET <target-name>]
+            [NUMBER_ERRORS <num-err-var>]
+            [NUMBER_WARNINGS <num-warn-var>]
+            [RETURN_VALUE <result-var>]
+            [CAPTURE_CMAKE_ERROR <result-var>]
+            )
+
+
+

Build the project and store results in Build.xml +for submission with the ctest_submit() command.

+

The CTEST_BUILD_COMMAND variable may be set to explicitly +specify the build command line. Otherwise the build command line is +computed automatically based on the options given.

+

The options are:

+
+
BUILD <build-dir>

Specify the top-level build directory. If not given, the +CTEST_BINARY_DIRECTORY variable is used.

+
+
APPEND

Mark Build.xml for append to results previously submitted to a +dashboard server since the last ctest_start() call. +Append semantics are defined by the dashboard server in use. +This does not cause results to be appended to a .xml file +produced by a previous call to this command.

+
+
CONFIGURATION <config>

Specify the build configuration (e.g. Debug). If not +specified the CTEST_BUILD_CONFIGURATION variable will be checked. +Otherwise the -C <cfg> option given to the +ctest(1) command will be used, if any.

+
+
PARALLEL_LEVEL <parallel>
+

New in version 3.21.

+
+

Specify the parallel level of the underlying build system. If not +specified, the CMAKE_BUILD_PARALLEL_LEVEL environment +variable will be checked.

+
+
FLAGS <flags>

Pass additional arguments to the underlying build command. +If not specified the CTEST_BUILD_FLAGS variable will be checked. +This can, e.g., be used to trigger a parallel build using the +-j option of make. See the ProcessorCount module +for an example.

+
+
PROJECT_NAME <project-name>

Ignored since CMake 3.0.

+
+

Changed in version 3.14: This value is no longer required.

+
+
+
TARGET <target-name>

Specify the name of a target to build. If not specified the +CTEST_BUILD_TARGET variable will be checked. Otherwise the +default target will be built. This is the "all" target +(called ALL_BUILD in Visual Studio Generators).

+
+
NUMBER_ERRORS <num-err-var>

Store the number of build errors detected in the given variable.

+
+
NUMBER_WARNINGS <num-warn-var>

Store the number of build warnings detected in the given variable.

+
+
RETURN_VALUE <result-var>

Store the return value of the native build tool in the given variable.

+
+
CAPTURE_CMAKE_ERROR <result-var>
+

New in version 3.7.

+
+

Store in the <result-var> variable -1 if there are any errors running +the command and prevent ctest from returning non-zero if an error occurs.

+
+
QUIET
+

New in version 3.3.

+
+

Suppress any CTest-specific non-error output that would have been +printed to the console otherwise. The summary of warnings / errors, +as well as the output from the native build tool is unaffected by +this option.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_configure.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_configure.html new file mode 100644 index 0000000000000000000000000000000000000000..ee7d30d463220cd282c928ebbff3ac0df2fae2cc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_configure.html @@ -0,0 +1,179 @@ + + + + + + + + + ctest_configure — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_configure

+

Perform the CTest Configure Step as a Dashboard Client.

+
ctest_configure([BUILD <build-dir>] [SOURCE <source-dir>] [APPEND]
+                [OPTIONS <options>] [RETURN_VALUE <result-var>] [QUIET]
+                [CAPTURE_CMAKE_ERROR <result-var>])
+
+
+

Configure the project build tree and record results in Configure.xml +for submission with the ctest_submit() command.

+

The options are:

+
+
BUILD <build-dir>

Specify the top-level build directory. If not given, the +CTEST_BINARY_DIRECTORY variable is used.

+
+
SOURCE <source-dir>

Specify the source directory. If not given, the +CTEST_SOURCE_DIRECTORY variable is used.

+
+
APPEND

Mark Configure.xml for append to results previously submitted to a +dashboard server since the last ctest_start() call. +Append semantics are defined by the dashboard server in use. +This does not cause results to be appended to a .xml file +produced by a previous call to this command.

+
+
OPTIONS <options>

Specify command-line arguments to pass to the configuration tool.

+
+
RETURN_VALUE <result-var>

Store in the <result-var> variable the return value of the native +configuration tool.

+
+
CAPTURE_CMAKE_ERROR <result-var>
+

New in version 3.7.

+
+

Store in the <result-var> variable -1 if there are any errors running +the command and prevent ctest from returning non-zero if an error occurs.

+
+
QUIET
+

New in version 3.3.

+
+

Suppress any CTest-specific non-error messages that would have +otherwise been printed to the console. Output from the underlying +configure command is not affected.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_coverage.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_coverage.html new file mode 100644 index 0000000000000000000000000000000000000000..ae24d9fa871bf450198571924f880f6759f61cbe --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_coverage.html @@ -0,0 +1,180 @@ + + + + + + + + + ctest_coverage — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_coverage

+

Perform the CTest Coverage Step as a Dashboard Client.

+
ctest_coverage([BUILD <build-dir>] [APPEND]
+               [LABELS <label>...]
+               [RETURN_VALUE <result-var>]
+               [CAPTURE_CMAKE_ERROR <result-var>]
+               [QUIET]
+               )
+
+
+

Collect coverage tool results and stores them in Coverage.xml +for submission with the ctest_submit() command.

+

The options are:

+
+
BUILD <build-dir>

Specify the top-level build directory. If not given, the +CTEST_BINARY_DIRECTORY variable is used.

+
+
APPEND

Mark Coverage.xml for append to results previously submitted to a +dashboard server since the last ctest_start() call. +Append semantics are defined by the dashboard server in use. +This does not cause results to be appended to a .xml file +produced by a previous call to this command.

+
+
LABELS

Filter the coverage report to include only source files labeled +with at least one of the labels specified.

+
+
RETURN_VALUE <result-var>

Store in the <result-var> variable 0 if coverage tools +ran without error and non-zero otherwise.

+
+
CAPTURE_CMAKE_ERROR <result-var>
+

New in version 3.7.

+
+

Store in the <result-var> variable -1 if there are any errors running +the command and prevent ctest from returning non-zero if an error occurs.

+
+
QUIET
+

New in version 3.3.

+
+

Suppress any CTest-specific non-error output that would have been +printed to the console otherwise. The summary indicating how many +lines of code were covered is unaffected by this option.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_empty_binary_directory.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_empty_binary_directory.html new file mode 100644 index 0000000000000000000000000000000000000000..6057e5af7151f2b42f0b66cd52ea3d268cf3d9c9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_empty_binary_directory.html @@ -0,0 +1,145 @@ + + + + + + + + + ctest_empty_binary_directory — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_empty_binary_directory

+

empties the binary directory

+
ctest_empty_binary_directory(<directory>)
+
+
+

Removes a binary directory. This command will perform some checks +prior to deleting the directory in an attempt to avoid malicious or +accidental directory deletion.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_memcheck.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_memcheck.html new file mode 100644 index 0000000000000000000000000000000000000000..a0ee9dbe95eb433ca08c9b20eff8f1f071daeea1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_memcheck.html @@ -0,0 +1,177 @@ + + + + + + + + + ctest_memcheck — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_memcheck

+

Perform the CTest MemCheck Step as a Dashboard Client.

+
ctest_memcheck([BUILD <build-dir>] [APPEND]
+               [START <start-number>]
+               [END <end-number>]
+               [STRIDE <stride-number>]
+               [EXCLUDE <exclude-regex>]
+               [INCLUDE <include-regex>]
+               [EXCLUDE_LABEL <label-exclude-regex>]
+               [INCLUDE_LABEL <label-include-regex>]
+               [EXCLUDE_FIXTURE <regex>]
+               [EXCLUDE_FIXTURE_SETUP <regex>]
+               [EXCLUDE_FIXTURE_CLEANUP <regex>]
+               [PARALLEL_LEVEL <level>]
+               [RESOURCE_SPEC_FILE <file>]
+               [TEST_LOAD <threshold>]
+               [SCHEDULE_RANDOM <ON|OFF>]
+               [STOP_ON_FAILURE]
+               [STOP_TIME <time-of-day>]
+               [RETURN_VALUE <result-var>]
+               [CAPTURE_CMAKE_ERROR <result-var>]
+               [REPEAT <mode>:<n>]
+               [OUTPUT_JUNIT <file>]
+               [DEFECT_COUNT <defect-count-var>]
+               [QUIET]
+               )
+
+
+

Run tests with a dynamic analysis tool and store results in +MemCheck.xml for submission with the ctest_submit() +command.

+

Most options are the same as those for the ctest_test() command.

+

The options unique to this command are:

+
+
DEFECT_COUNT <defect-count-var>
+

New in version 3.8.

+
+

Store in the <defect-count-var> the number of defects found.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_read_custom_files.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_read_custom_files.html new file mode 100644 index 0000000000000000000000000000000000000000..b5dd83cbe9b919970b25ec419c79072ca6d94034 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_read_custom_files.html @@ -0,0 +1,146 @@ + + + + + + + + + ctest_read_custom_files — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_read_custom_files

+

read CTestCustom files.

+
ctest_read_custom_files(<directory>...)
+
+
+

Read all the CTestCustom.ctest or CTestCustom.cmake files from the +given directory.

+

By default, invoking ctest(1) without a script will read custom +files from the binary directory.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_run_script.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_run_script.html new file mode 100644 index 0000000000000000000000000000000000000000..dad144b7fd1ca6626ef7ccdbf468f855e5b395a6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_run_script.html @@ -0,0 +1,148 @@ + + + + + + + + + ctest_run_script — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_run_script

+

runs a ctest -S script

+
ctest_run_script([NEW_PROCESS] script_file_name script_file_name1
+            script_file_name2 ... [RETURN_VALUE var])
+
+
+

Runs a script or scripts much like if it was run from ctest -S. +If no argument is provided then the current script is run using the current +settings of the variables. If NEW_PROCESS is specified then each +script will be run in a separate process.If RETURN_VALUE is specified +the return value of the last script run will be put into var.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_sleep.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_sleep.html new file mode 100644 index 0000000000000000000000000000000000000000..be0a0e6ba157023bdbf28ca590a9f1a78b8856ed --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_sleep.html @@ -0,0 +1,147 @@ + + + + + + + + + ctest_sleep — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_sleep

+

sleeps for some amount of time

+
ctest_sleep(<seconds>)
+
+
+

Sleep for given number of seconds.

+
ctest_sleep(<time1> <duration> <time2>)
+
+
+

Sleep for t=(time1 + duration - time2) seconds if t > 0.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_start.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_start.html new file mode 100644 index 0000000000000000000000000000000000000000..d540de5dfc1723b1fc32d21bc6ddb7db7f73080c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_start.html @@ -0,0 +1,209 @@ + + + + + + + + + ctest_start — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_start

+

Starts the testing for a given model

+
ctest_start(<model> [<source> [<binary>]] [GROUP <group>] [QUIET])
+
+ctest_start([<model> [<source> [<binary>]]] [GROUP <group>] APPEND [QUIET])
+
+
+

Starts the testing for a given model. The command should be called +after the binary directory is initialized.

+

The parameters are as follows:

+
+
<model>

Set the dashboard model. Must be one of Experimental, Continuous, or +Nightly. This parameter is required unless APPEND is specified.

+
+
<source>

Set the source directory. If not specified, the value of +CTEST_SOURCE_DIRECTORY is used instead.

+
+
<binary>

Set the binary directory. If not specified, the value of +CTEST_BINARY_DIRECTORY is used instead.

+
+
GROUP <group>

If GROUP is used, the submissions will go to the specified group on the +CDash server. If no GROUP is specified, the name of the model is used by +default.

+
+

Changed in version 3.16: This replaces the deprecated option TRACK. Despite the name +change its behavior is unchanged.

+
+
+
APPEND

If APPEND is used, the existing TAG is used rather than creating a new +one based on the current time stamp. If you use APPEND, you can omit the +<model> and GROUP <group> parameters, because they will be read from +the generated TAG file. For example:

+
ctest_start(Experimental GROUP GroupExperimental)
+
+
+

Later, in another ctest -S script:

+
ctest_start(APPEND)
+
+
+

When the second script runs ctest_start(APPEND), it will read the +Experimental model and GroupExperimental group from the TAG file +generated by the first ctest_start() command. Please note that if you +call ctest_start(APPEND) and specify a different model or group than +in the first ctest_start() command, a warning will be issued, and the +new model and group will be used.

+
+
QUIET
+

New in version 3.3.

+
+

If QUIET is used, CTest will suppress any non-error messages that it +otherwise would have printed to the console.

+
+
+

The parameters for ctest_start() can be issued in any order, with the +exception that <model>, <source>, and <binary> have to appear +in that order with respect to each other. The following are all valid and +equivalent:

+
ctest_start(Experimental path/to/source path/to/binary GROUP SomeGroup QUIET APPEND)
+
+ctest_start(GROUP SomeGroup Experimental QUIET path/to/source APPEND path/to/binary)
+
+ctest_start(APPEND QUIET Experimental path/to/source GROUP SomeGroup path/to/binary)
+
+
+

However, for the sake of readability, it is recommended that you order your +parameters in the order listed at the top of this page.

+

If the CTEST_CHECKOUT_COMMAND variable (or the +CTEST_CVS_CHECKOUT variable) is set, its content is treated as +command-line. The command is invoked with the current working directory set +to the parent of the source directory, even if the source directory already +exists. This can be used to create the source tree from a version control +repository.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_submit.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_submit.html new file mode 100644 index 0000000000000000000000000000000000000000..82b7ec0a015f4b1d376bb34020a03396f97efca7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_submit.html @@ -0,0 +1,267 @@ + + + + + + + + + ctest_submit — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_submit

+

Perform the CTest Submit Step as a Dashboard Client.

+
ctest_submit([PARTS <part>...] [FILES <file>...]
+             [SUBMIT_URL <url>]
+             [BUILD_ID <result-var>]
+             [HTTPHEADER <header>]
+             [RETRY_COUNT <count>]
+             [RETRY_DELAY <delay>]
+             [RETURN_VALUE <result-var>]
+             [CAPTURE_CMAKE_ERROR <result-var>]
+             [QUIET]
+             )
+
+
+

Submit results to a dashboard server. +By default all available parts are submitted.

+

The options are:

+
+
PARTS <part>...

Specify a subset of parts to submit. Valid part names are:

+
Start      = nothing
+Update     = ctest_update results, in Update.xml
+Configure  = ctest_configure results, in Configure.xml
+Build      = ctest_build results, in Build.xml
+Test       = ctest_test results, in Test.xml
+Coverage   = ctest_coverage results, in Coverage.xml
+MemCheck   = ctest_memcheck results, in DynamicAnalysis.xml and
+             DynamicAnalysis-Test.xml
+Notes      = Files listed by CTEST_NOTES_FILES, in Notes.xml
+ExtraFiles = Files listed by CTEST_EXTRA_SUBMIT_FILES
+Upload     = Files prepared for upload by ctest_upload(), in Upload.xml
+Submit     = nothing
+Done       = Build is complete, in Done.xml
+
+
+
+
FILES <file>...

Specify an explicit list of specific files to be submitted. +Each individual file must exist at the time of the call.

+
+
SUBMIT_URL <url>
+

New in version 3.14.

+
+

The http or https URL of the dashboard server to send the submission +to. If not given, the CTEST_SUBMIT_URL variable is used.

+
+
BUILD_ID <result-var>
+

New in version 3.15.

+
+

Store in the <result-var> variable the ID assigned to this build by +CDash.

+
+
HTTPHEADER <HTTP-header>
+

New in version 3.9.

+
+

Specify HTTP header to be included in the request to CDash during submission. +For example, CDash can be configured to only accept submissions from +authenticated clients. In this case, you should provide a bearer token in your +header:

+
ctest_submit(HTTPHEADER "Authorization: Bearer <auth-token>")
+
+
+

This suboption can be repeated several times for multiple headers.

+
+
RETRY_COUNT <count>

Specify how many times to retry a timed-out submission.

+
+
RETRY_DELAY <delay>

Specify how long (in seconds) to wait after a timed-out submission +before attempting to re-submit.

+
+
RETURN_VALUE <result-var>

Store in the <result-var> variable 0 for success and +non-zero on failure.

+
+
CAPTURE_CMAKE_ERROR <result-var>
+

New in version 3.13.

+
+

Store in the <result-var> variable -1 if there are any errors running +the command and prevent ctest from returning non-zero if an error occurs.

+
+
QUIET
+

New in version 3.3.

+
+

Suppress all non-error messages that would have otherwise been +printed to the console.

+
+
+
+

Submit to CDash Upload API

+
+

New in version 3.2.

+
+
ctest_submit(CDASH_UPLOAD <file> [CDASH_UPLOAD_TYPE <type>]
+             [SUBMIT_URL <url>]
+             [BUILD_ID <result-var>]
+             [HTTPHEADER <header>]
+             [RETRY_COUNT <count>]
+             [RETRY_DELAY <delay>]
+             [RETURN_VALUE <result-var>]
+             [QUIET])
+
+
+

This second signature is used to upload files to CDash via the CDash +file upload API. The API first sends a request to upload to CDash along +with a content hash of the file. If CDash does not already have the file, +then it is uploaded. Along with the file, a CDash type string is specified +to tell CDash which handler to use to process the data.

+

This signature interprets options in the same way as the first one.

+
+

New in version 3.8: Added the RETRY_COUNT, RETRY_DELAY, QUIET options.

+
+
+

New in version 3.9: Added the HTTPHEADER option.

+
+
+

New in version 3.13: Added the RETURN_VALUE option.

+
+
+

New in version 3.14: Added the SUBMIT_URL option.

+
+
+

New in version 3.15: Added the BUILD_ID option.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_test.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_test.html new file mode 100644 index 0000000000000000000000000000000000000000..7af6ba1f5285256c45fc65e7cdf7477a27905b53 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_test.html @@ -0,0 +1,419 @@ + + + + + + + + + ctest_test — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_test

+

Perform the CTest Test Step as a Dashboard Client.

+
ctest_test([BUILD <build-dir>] [APPEND]
+           [START <start-number>]
+           [END <end-number>]
+           [STRIDE <stride-number>]
+           [EXCLUDE <exclude-regex>]
+           [INCLUDE <include-regex>]
+           [EXCLUDE_LABEL <label-exclude-regex>]
+           [INCLUDE_LABEL <label-include-regex>]
+           [EXCLUDE_FIXTURE <regex>]
+           [EXCLUDE_FIXTURE_SETUP <regex>]
+           [EXCLUDE_FIXTURE_CLEANUP <regex>]
+           [PARALLEL_LEVEL <level>]
+           [RESOURCE_SPEC_FILE <file>]
+           [TEST_LOAD <threshold>]
+           [SCHEDULE_RANDOM <ON|OFF>]
+           [STOP_ON_FAILURE]
+           [STOP_TIME <time-of-day>]
+           [RETURN_VALUE <result-var>]
+           [CAPTURE_CMAKE_ERROR <result-var>]
+           [REPEAT <mode>:<n>]
+           [OUTPUT_JUNIT <file>]
+           [QUIET]
+           )
+
+
+

Run tests in the project build tree and store results in +Test.xml for submission with the ctest_submit() command.

+

The options are:

+
+
BUILD <build-dir>

Specify the top-level build directory. If not given, the +CTEST_BINARY_DIRECTORY variable is used.

+
+
APPEND

Mark Test.xml for append to results previously submitted to a +dashboard server since the last ctest_start() call. +Append semantics are defined by the dashboard server in use. +This does not cause results to be appended to a .xml file +produced by a previous call to this command.

+
+
START <start-number>

Specify the beginning of a range of test numbers.

+
+
END <end-number>

Specify the end of a range of test numbers.

+
+
STRIDE <stride-number>

Specify the stride by which to step across a range of test numbers.

+
+
EXCLUDE <exclude-regex>

Specify a regular expression matching test names to exclude.

+
+
INCLUDE <include-regex>

Specify a regular expression matching test names to include. +Tests not matching this expression are excluded.

+
+
EXCLUDE_LABEL <label-exclude-regex>

Specify a regular expression matching test labels to exclude.

+
+
INCLUDE_LABEL <label-include-regex>

Specify a regular expression matching test labels to include. +Tests not matching this expression are excluded.

+
+
EXCLUDE_FIXTURE <regex>
+

New in version 3.7.

+
+

If a test in the set of tests to be executed requires a particular fixture, +that fixture's setup and cleanup tests would normally be added to the test +set automatically. This option prevents adding setup or cleanup tests for +fixtures matching the <regex>. Note that all other fixture behavior is +retained, including test dependencies and skipping tests that have fixture +setup tests that fail.

+
+
EXCLUDE_FIXTURE_SETUP <regex>
+

New in version 3.7.

+
+

Same as EXCLUDE_FIXTURE except only matching setup tests are excluded.

+
+
EXCLUDE_FIXTURE_CLEANUP <regex>
+

New in version 3.7.

+
+

Same as EXCLUDE_FIXTURE except only matching cleanup tests are excluded.

+
+
PARALLEL_LEVEL <level>

Specify a positive number representing the number of tests to +be run in parallel.

+
+
RESOURCE_SPEC_FILE <file>
+

New in version 3.16.

+
+

Specify a +resource specification file. See +Resource Allocation for more information.

+
+
TEST_LOAD <threshold>
+

New in version 3.4.

+
+

While running tests in parallel, try not to start tests when they +may cause the CPU load to pass above a given threshold. If not +specified the CTEST_TEST_LOAD variable will be checked, +and then the --test-load command-line +argument to ctest(1). See also the TestLoad setting +in the CTest Test Step.

+
+
REPEAT <mode>:<n>
+

New in version 3.17.

+
+

Run tests repeatedly based on the given <mode> up to <n> times. +The modes are:

+
+
UNTIL_FAIL

Require each test to run <n> times without failing in order to pass. +This is useful in finding sporadic failures in test cases.

+
+
UNTIL_PASS

Allow each test to run up to <n> times in order to pass. +Repeats tests if they fail for any reason. +This is useful in tolerating sporadic failures in test cases.

+
+
AFTER_TIMEOUT

Allow each test to run up to <n> times in order to pass. +Repeats tests only if they timeout. +This is useful in tolerating sporadic timeouts in test cases +on busy machines.

+
+
+
+
SCHEDULE_RANDOM <ON|OFF>

Launch tests in a random order. This may be useful for detecting +implicit test dependencies.

+
+
STOP_ON_FAILURE
+

New in version 3.18.

+
+

Stop the execution of the tests once one has failed.

+
+
STOP_TIME <time-of-day>

Specify a time of day at which the tests should all stop running.

+
+
RETURN_VALUE <result-var>

Store in the <result-var> variable 0 if all tests passed. +Store non-zero if anything went wrong.

+
+
CAPTURE_CMAKE_ERROR <result-var>
+

New in version 3.7.

+
+

Store in the <result-var> variable -1 if there are any errors running +the command and prevent ctest from returning non-zero if an error occurs.

+
+
OUTPUT_JUNIT <file>
+

New in version 3.21.

+
+

Write test results to <file> in JUnit XML format. If <file> is a +relative path, it will be placed in the build directory. If <file> +already exists, it will be overwritten. Note that the resulting JUnit XML +file is not uploaded to CDash because it would be redundant with +CTest's Test.xml file.

+
+
QUIET
+

New in version 3.3.

+
+

Suppress any CTest-specific non-error messages that would have otherwise +been printed to the console. Output from the underlying test command is not +affected. Summary info detailing the percentage of passing tests is also +unaffected by the QUIET option.

+
+
+

See also the CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE, +CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE and +CTEST_CUSTOM_TEST_OUTPUT_TRUNCATION variables, along with their +corresponding ctest(1) command line options +--test-output-size-passed, +--test-output-size-failed, and +--test-output-truncation.

+
+

Additional Test Measurements

+

CTest can parse the output of your tests for extra measurements to report +to CDash.

+

When run as a Dashboard Client, CTest will include these custom +measurements in the Test.xml file that gets uploaded to CDash.

+

Check the CDash test measurement documentation +for more information on the types of test measurements that CDash recognizes.

+

The following example demonstrates how to output a variety of custom test +measurements.

+
std::cout <<
+  "<CTestMeasurement type=\"numeric/double\" name=\"score\">28.3</CTestMeasurement>"
+  << std::endl;
+
+std::cout <<
+  "<CTestMeasurement type=\"text/string\" name=\"color\">red</CTestMeasurement>"
+  << std::endl;
+
+std::cout <<
+  "<CTestMeasurement type=\"text/link\" name=\"CMake URL\">https://cmake.org</CTestMeasurement>"
+  << std::endl;
+
+std::cout <<
+  "<CTestMeasurement type=\"text/preformatted\" name=\"Console Output\">" <<
+  "line 1.\n" <<
+  "  \033[31;1m line 2. Bold red, and indented!\033[0;0ml\n" <<
+  "line 3. Not bold or indented...\n" <<
+  "</CTestMeasurement>" << std::endl;
+
+
+
+

Image Measurements

+

The following example demonstrates how to upload test images to CDash.

+
std::cout <<
+  "<CTestMeasurementFile type=\"image/jpg\" name=\"TestImage\">" <<
+  "/dir/to/test_img.jpg</CTestMeasurementFile>" << std::endl;
+
+std::cout <<
+  "<CTestMeasurementFile type=\"image/gif\" name=\"ValidImage\">" <<
+  "/dir/to/valid_img.gif</CTestMeasurementFile>" << std::endl;
+
+std::cout <<
+  "<CTestMeasurementFile type=\"image/png\" name=\"AlgoResult\">" <<
+  "/dir/to/img.png</CTestMeasurementFile>"
+  << std::endl;
+
+
+

Images will be displayed together in an interactive comparison mode on CDash +if they are provided with two or more of the following names.

+
    +
  • TestImage

  • +
  • ValidImage

  • +
  • BaselineImage

  • +
  • DifferenceImage2

  • +
+

By convention, TestImage is the image generated by your test, and +ValidImage (or BaselineImage) is basis of comparison used to determine +if the test passed or failed.

+

If another image name is used it will be displayed by CDash as a static image +separate from the interactive comparison UI.

+
+
+

Attached Files

+
+

New in version 3.21.

+
+

The following example demonstrates how to upload non-image files to CDash.

+
std::cout <<
+  "<CTestMeasurementFile type=\"file\" name=\"TestInputData1\">" <<
+  "/dir/to/data1.csv</CTestMeasurementFile>\n"                   <<
+  "<CTestMeasurementFile type=\"file\" name=\"TestInputData2\">" <<
+  "/dir/to/data2.csv</CTestMeasurementFile>"                     << std::endl;
+
+
+

If the name of the file to upload is known at configure time, you can use the +ATTACHED_FILES or ATTACHED_FILES_ON_FAIL test +properties instead.

+
+
+

Custom Details

+
+

New in version 3.21.

+
+

The following example demonstrates how to specify a custom value for the +Test Details field displayed on CDash.

+
std::cout <<
+  "<CTestDetails>My Custom Details Value</CTestDetails>" << std::endl;
+
+
+
+
+

Additional Labels

+
+

New in version 3.22.

+
+

The following example demonstrates how to add additional labels to a test +at runtime.

+
std::cout <<
+  "<CTestLabel>Custom Label 1</CTestLabel>\n" <<
+  "<CTestLabel>Custom Label 2</CTestLabel>"   << std::endl;
+
+
+

Use the LABELS test property instead for labels that can be +determined at configure time.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_update.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_update.html new file mode 100644 index 0000000000000000000000000000000000000000..d441cf70592ce562cae91fbf8aed5aa975f275d4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_update.html @@ -0,0 +1,174 @@ + + + + + + + + + ctest_update — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_update

+

Perform the CTest Update Step as a Dashboard Client.

+
ctest_update([SOURCE <source-dir>]
+             [RETURN_VALUE <result-var>]
+             [CAPTURE_CMAKE_ERROR <result-var>]
+             [QUIET])
+
+
+

Update the source tree from version control and record results in +Update.xml for submission with the ctest_submit() command.

+

The options are:

+
+
SOURCE <source-dir>

Specify the source directory. If not given, the +CTEST_SOURCE_DIRECTORY variable is used.

+
+
RETURN_VALUE <result-var>

Store in the <result-var> variable the number of files +updated or -1 on error.

+
+
CAPTURE_CMAKE_ERROR <result-var>
+

New in version 3.13.

+
+

Store in the <result-var> variable -1 if there are any errors running +the command and prevent ctest from returning non-zero if an error occurs.

+
+
QUIET
+

New in version 3.3.

+
+

Tell CTest to suppress most non-error messages that it would +have otherwise printed to the console. CTest will still report +the new revision of the repository and any conflicting files +that were found.

+
+
+

The update always follows the version control branch currently checked +out in the source directory. See the CTest Update Step +documentation for information about variables that change the behavior +of ctest_update().

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_upload.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_upload.html new file mode 100644 index 0000000000000000000000000000000000000000..9cb905a3ff2ee35648c5fb6a1aa112a8e636c19a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/ctest_upload.html @@ -0,0 +1,160 @@ + + + + + + + + + ctest_upload — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ctest_upload

+

Upload files to a dashboard server as a Dashboard Client.

+
ctest_upload(FILES <file>... [QUIET] [CAPTURE_CMAKE_ERROR <result-var>])
+
+
+

The options are:

+
+
FILES <file>...

Specify a list of files to be sent along with the build results to the +dashboard server.

+
+
QUIET
+

New in version 3.3.

+
+

Suppress any CTest-specific non-error output that would have been +printed to the console otherwise.

+
+
CAPTURE_CMAKE_ERROR <result-var>
+

New in version 3.7.

+
+

Store in the <result-var> variable -1 if there are any errors running +the command and prevent ctest from returning non-zero if an error occurs.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/define_property.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/define_property.html new file mode 100644 index 0000000000000000000000000000000000000000..eedd255bbd0337a2fc1129437a1e5045ec6ece32 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/define_property.html @@ -0,0 +1,217 @@ + + + + + + + + + define_property — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

define_property

+

Define and document custom properties.

+
define_property(<GLOBAL | DIRECTORY | TARGET | SOURCE |
+                 TEST | VARIABLE | CACHED_VARIABLE>
+                 PROPERTY <name> [INHERITED]
+                 [BRIEF_DOCS <brief-doc> [docs...]]
+                 [FULL_DOCS <full-doc> [docs...]]
+                 [INITIALIZE_FROM_VARIABLE <variable>])
+
+
+

Defines one property in a scope for use with the set_property() and +get_property() commands. It is mainly useful for defining the way +a property is initialized or inherited. Historically, the command also +associated documentation with a property, but that is no longer considered a +primary use case.

+

The first argument determines the kind of scope in which the property should +be used. It must be one of the following:

+
GLOBAL    = associated with the global namespace
+DIRECTORY = associated with one directory
+TARGET    = associated with one target
+SOURCE    = associated with one source file
+TEST      = associated with a test named with add_test
+VARIABLE  = documents a CMake language variable
+CACHED_VARIABLE = documents a CMake cache variable
+
+
+

Note that unlike set_property() and get_property() no +actual scope needs to be given; only the kind of scope is important.

+

The required PROPERTY option is immediately followed by the name of +the property being defined.

+

If the INHERITED option is given, then the get_property() command +will chain up to the next higher scope when the requested property is not set +in the scope given to the command.

+
    +
  • DIRECTORY scope chains to its parent directory's scope, continuing the +walk up parent directories until a directory has the property set or there +are no more parents. If still not found at the top level directory, it +chains to the GLOBAL scope.

  • +
  • TARGET, SOURCE and TEST properties chain to DIRECTORY scope, +including further chaining up the directories, etc. as needed.

  • +
+

Note that this scope chaining behavior only applies to calls to +get_property(), get_directory_property(), +get_target_property(), get_source_file_property() and +get_test_property(). There is no inheriting behavior when setting +properties, so using APPEND or APPEND_STRING with the +set_property() command will not consider inherited values when working +out the contents to append to.

+

The BRIEF_DOCS and FULL_DOCS options are followed by strings to be +associated with the property as its brief and full documentation. +CMake does not use this documentation other than making it available to the +project via corresponding options to the get_property() command.

+
+

Changed in version 3.23: The BRIEF_DOCS and FULL_DOCS options are optional.

+
+
+

New in version 3.23: The INITIALIZE_FROM_VARIABLE option specifies a variable from which the +property should be initialized. It can only be used with target properties. +The <variable> name must end with the property name and must not begin +with CMAKE_ or _CMAKE_. The property name must contain at least one +underscore. It is recommended that the property name have a prefix specific +to the project.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/else.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/else.html new file mode 100644 index 0000000000000000000000000000000000000000..1dda1ab43f5dbdf2141e3776b851c65f710149b4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/else.html @@ -0,0 +1,143 @@ + + + + + + + + + else — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

else

+

Starts the else portion of an if block.

+
else([<condition>])
+
+
+

See the if() command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/elseif.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/elseif.html new file mode 100644 index 0000000000000000000000000000000000000000..474ec96467f6ce8f2cd61aa6a8483aaae953e482 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/elseif.html @@ -0,0 +1,144 @@ + + + + + + + + + elseif — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

elseif

+

Starts an elseif portion of an if block.

+
elseif(<condition>)
+
+
+

See the if() command, especially for the syntax and logic +of the <condition>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/enable_language.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/enable_language.html new file mode 100644 index 0000000000000000000000000000000000000000..7abec3d6f3848658828ffdb713f3853c1784ca62 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/enable_language.html @@ -0,0 +1,178 @@ + + + + + + + + + enable_language — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

enable_language

+

Enable languages (CXX/C/OBJC/OBJCXX/Fortran/etc)

+
enable_language(<lang>... [OPTIONAL])
+
+
+

Enables support for the named languages in CMake. This is the same as +the project() command but does not create any of the extra +variables that are created by the project command.

+

Supported languages are C, CXX (i.e. C++), CSharp (i.e. C#), CUDA, +OBJC (i.e. Objective-C), OBJCXX (i.e. Objective-C++), Fortran, HIP, +ISPC, Swift, ASM, ASM_NASM, ASM_MARMASM, ASM_MASM, and ASM-ATT.

+
+
+

New in version 3.8: Added CSharp and CUDA support.

+
+
+

New in version 3.15: Added Swift support.

+
+
+

New in version 3.16: Added OBJC and OBJCXX support.

+
+
+

New in version 3.18: Added ISPC support.

+
+
+

New in version 3.21: Added HIP support.

+
+
+

New in version 3.26: Added ASM_MARMASM support.

+
+
+

If enabling ASM, list it last so that CMake can check whether +compilers for other languages like C work for assembly too.

+

This command must be called in file scope, not in a function call. +Furthermore, it must be called in the highest directory common to all +targets using the named language directly for compiling sources or +indirectly through link dependencies. It is simplest to enable all +needed languages in the top-level directory of a project.

+

The OPTIONAL keyword is a placeholder for future implementation and +does not currently work. Instead you can use the CheckLanguage +module to verify support before enabling.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/enable_testing.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/enable_testing.html new file mode 100644 index 0000000000000000000000000000000000000000..da0d03346de707cf5e4bf653f034799e0b7c58eb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/enable_testing.html @@ -0,0 +1,150 @@ + + + + + + + + + enable_testing — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

enable_testing

+

Enable testing for current directory and below.

+
enable_testing()
+
+
+

Enables testing for this directory and below.

+

This command should be in the source directory root +because ctest expects to find a test file in the build +directory root.

+

This command is automatically invoked when the CTest +module is included, except if the BUILD_TESTING option is +turned off.

+

See also the add_test() command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endblock.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endblock.html new file mode 100644 index 0000000000000000000000000000000000000000..feee3a149d758505400ea4f3a052fdf5a4aa5b49 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endblock.html @@ -0,0 +1,146 @@ + + + + + + + + + endblock — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

endblock

+
+

New in version 3.25.

+
+

Ends a list of commands in a block() and removes the scopes +created by the block() command.

+
endblock()
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endforeach.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endforeach.html new file mode 100644 index 0000000000000000000000000000000000000000..dbc089fc1c3e772a18004fc036c0345c80b3290f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endforeach.html @@ -0,0 +1,146 @@ + + + + + + + + + endforeach — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

endforeach

+

Ends a list of commands in a foreach block.

+
endforeach([<loop_var>])
+
+
+

See the foreach() command.

+

The optional <loop_var> argument is supported for backward compatibility +only. If used it must be a verbatim repeat of the <loop_var> argument of +the opening foreach clause.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endfunction.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endfunction.html new file mode 100644 index 0000000000000000000000000000000000000000..80b6bf1263e6de4baa993444e1bb0bb9fdadb964 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endfunction.html @@ -0,0 +1,146 @@ + + + + + + + + + endfunction — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

endfunction

+

Ends a list of commands in a function block.

+
endfunction([<name>])
+
+
+

See the function() command.

+

The optional <name> argument is supported for backward compatibility +only. If used it must be a verbatim repeat of the <name> argument +of the opening function command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endif.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endif.html new file mode 100644 index 0000000000000000000000000000000000000000..871804454b6d5c2046400d5737fe6a68d8d34ea6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endif.html @@ -0,0 +1,146 @@ + + + + + + + + + endif — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

endif

+

Ends a list of commands in an if block.

+
endif([<condition>])
+
+
+

See the if() command.

+

The optional <condition> argument is supported for backward compatibility +only. If used it must be a verbatim repeat of the argument of the opening +if clause.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endmacro.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endmacro.html new file mode 100644 index 0000000000000000000000000000000000000000..84beb46b88991ef372e99d37104296967ee47697 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endmacro.html @@ -0,0 +1,146 @@ + + + + + + + + + endmacro — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

endmacro

+

Ends a list of commands in a macro block.

+
endmacro([<name>])
+
+
+

See the macro() command.

+

The optional <name> argument is supported for backward compatibility +only. If used it must be a verbatim repeat of the <name> argument +of the opening macro command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endwhile.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endwhile.html new file mode 100644 index 0000000000000000000000000000000000000000..b0511af5228cc18526643311835ccbe79124e2bb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/endwhile.html @@ -0,0 +1,146 @@ + + + + + + + + + endwhile — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

endwhile

+

Ends a list of commands in a while block.

+
endwhile([<condition>])
+
+
+

See the while() command.

+

The optional <condition> argument is supported for backward compatibility +only. If used it must be a verbatim repeat of the argument of the opening +while clause.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/exec_program.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/exec_program.html new file mode 100644 index 0000000000000000000000000000000000000000..eae22e3e98f5a16bc85f86932d2edc9ba980cb4a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/exec_program.html @@ -0,0 +1,158 @@ + + + + + + + + + exec_program — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

exec_program

+
+

Deprecated since version 3.0: Use the execute_process() command instead.

+
+

Run an executable program during the processing of the CMakeList.txt +file.

+
exec_program(Executable [directory in which to run]
+             [ARGS <arguments to executable>]
+             [OUTPUT_VARIABLE <var>]
+             [RETURN_VALUE <var>])
+
+
+

The executable is run in the optionally specified directory. The +executable can include arguments if it is double quoted, but it is +better to use the optional ARGS argument to specify arguments to the +program. This is because cmake will then be able to escape spaces in +the executable path. An optional argument OUTPUT_VARIABLE specifies a +variable in which to store the output. To capture the return value of +the execution, provide a RETURN_VALUE. If OUTPUT_VARIABLE is +specified, then no output will go to the stdout/stderr of the console +running cmake.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/execute_process.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/execute_process.html new file mode 100644 index 0000000000000000000000000000000000000000..79942dca14c81d15e0a8c07e7ca480c026ef76b1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/execute_process.html @@ -0,0 +1,296 @@ + + + + + + + + + execute_process — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

execute_process

+

Execute one or more child processes.

+
execute_process(COMMAND <cmd1> [<arguments>]
+                [COMMAND <cmd2> [<arguments>]]...
+                [WORKING_DIRECTORY <directory>]
+                [TIMEOUT <seconds>]
+                [RESULT_VARIABLE <variable>]
+                [RESULTS_VARIABLE <variable>]
+                [OUTPUT_VARIABLE <variable>]
+                [ERROR_VARIABLE <variable>]
+                [INPUT_FILE <file>]
+                [OUTPUT_FILE <file>]
+                [ERROR_FILE <file>]
+                [OUTPUT_QUIET]
+                [ERROR_QUIET]
+                [COMMAND_ECHO <where>]
+                [OUTPUT_STRIP_TRAILING_WHITESPACE]
+                [ERROR_STRIP_TRAILING_WHITESPACE]
+                [ENCODING <name>]
+                [ECHO_OUTPUT_VARIABLE]
+                [ECHO_ERROR_VARIABLE]
+                [COMMAND_ERROR_IS_FATAL <ANY|LAST>])
+
+
+

Runs the given sequence of one or more commands.

+

Commands are executed concurrently as a pipeline, with the standard +output of each process piped to the standard input of the next. +A single standard error pipe is used for all processes.

+

execute_process runs commands while CMake is configuring the project, +prior to build system generation. Use the add_custom_target() and +add_custom_command() commands to create custom commands that run +at build time.

+

Options:

+
+
COMMAND

A child process command line.

+

CMake executes the child process using operating system APIs directly:

+
    +
  • On POSIX platforms, the command line is passed to the +child process in an argv[] style array.

  • +
  • On Windows platforms, the command line is encoded as a string such +that child processes using CommandLineToArgvW will decode the +original arguments.

  • +
+

No intermediate shell is used, so shell operators such as > +are treated as normal arguments. +(Use the INPUT_*, OUTPUT_*, and ERROR_* options to +redirect stdin, stdout, and stderr.)

+

For sequential execution of multiple commands use multiple +execute_process calls each with a single COMMAND argument.

+
+
WORKING_DIRECTORY

The named directory will be set as the current working directory of +the child processes.

+
+
TIMEOUT

After the specified number of seconds (fractions allowed), all unfinished +child processes will be terminated, and the RESULT_VARIABLE will be +set to a string mentioning the "timeout".

+
+
RESULT_VARIABLE

The variable will be set to contain the result of last child process. +This will be an integer return code from the last child or a string +describing an error condition.

+
+
RESULTS_VARIABLE <variable>
+

New in version 3.10.

+
+

The variable will be set to contain the result of all processes as a +semicolon-separated list, in order of the +given COMMAND arguments. Each entry will be an integer return code +from the corresponding child or a string describing an error condition.

+
+
INPUT_FILE <file>

<file> is attached to the standard input pipe of the first COMMAND +process.

+
+
OUTPUT_FILE <file>

<file> is attached to the standard output pipe of the last COMMAND +process.

+
+
ERROR_FILE <file>

<file> is attached to the standard error pipe of all COMMAND +processes.

+
+
+
+

New in version 3.3: If the same <file> is named for both OUTPUT_FILE and ERROR_FILE +then it will be used for both standard output and standard error pipes.

+
+
+
OUTPUT_QUIET, ERROR_QUIET

The standard output on OUTPUT_VARIABLE or standard error on +ERROR_VARIABLE are not connected (no variable content). +The *_FILE and ECHO_*_VARIABLE options are not affected.

+
+
OUTPUT_VARIABLE, ERROR_VARIABLE

The variable named will be set with the contents of the standard output +and standard error pipes, respectively. If the same variable is named +for both pipes their output will be merged in the order produced.

+
+
ECHO_OUTPUT_VARIABLE, ECHO_ERROR_VARIABLE
+

New in version 3.18.

+
+

The standard output or standard error will not be exclusively redirected to +the specified variables.

+

The output will be duplicated into the specified variables and also onto +standard output or standard error analogous to the tee Unix command.

+
+
+
+

Note

+

If more than one OUTPUT_* or ERROR_* option is given for the +same pipe the precedence is not specified. +If no OUTPUT_* or ERROR_* options are given the output will +be shared with the corresponding pipes of the CMake process itself.

+
+
+
COMMAND_ECHO <where>
+

New in version 3.15.

+
+

The command being run will be echo'ed to <where> with <where> +being set to one of STDERR, STDOUT or NONE. +See the CMAKE_EXECUTE_PROCESS_COMMAND_ECHO variable for a way +to control the default behavior when this option is not present.

+
+
ENCODING <name>
+

New in version 3.8.

+
+

On Windows, the encoding that is used to decode output from the process. +Ignored on other platforms. +Valid encoding names are:

+
+
NONE

Perform no decoding. This assumes that the process output is encoded +in the same way as CMake's internal encoding (UTF-8). +This is the default.

+
+
AUTO

Use the current active console's codepage or if that isn't +available then use ANSI.

+
+
ANSI

Use the ANSI codepage.

+
+
OEM

Use the original equipment manufacturer (OEM) code page.

+
+
UTF8 or UTF-8

Use the UTF-8 codepage.

+
+

New in version 3.11: Accept UTF-8 spelling for consistency with the +UTF-8 RFC naming convention.

+
+
+
+
+
COMMAND_ERROR_IS_FATAL <ANY|LAST>
+

New in version 3.19.

+
+

The option following COMMAND_ERROR_IS_FATAL determines the behavior when +an error is encountered:

+
+

ANY +If any of the commands in the list of commands fail, the +execute_process() command halts with an error.

+

LAST +If the last command in the list of commands fails, the +execute_process() command halts with an error. Commands earlier in the +list will not cause a fatal error.

+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/export.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/export.html new file mode 100644 index 0000000000000000000000000000000000000000..8e30b97efc568e4158ac8e30f285ebf3d0ecdfb6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/export.html @@ -0,0 +1,280 @@ + + + + + + + + + export — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

export

+

Export targets or packages for outside projects to use them directly +from the current project's build tree, without installation.

+

See the install(EXPORT) command to export targets from an +install tree.

+
+

Synopsis

+
export(TARGETS <target>... [...])
+export(EXPORT <export-name> [...])
+export(PACKAGE <PackageName>)
+
+
+

Exporting Targets

+
export(TARGETS <target>... [NAMESPACE <namespace>]
+       [APPEND] FILE <filename> [EXPORT_LINK_INTERFACE_LIBRARIES]
+       [CXX_MODULES_DIRECTORY <directory>])
+
+
+

Creates a file <filename> that may be included by outside projects to +import targets named by <target>... from the current project's build tree. +This is useful during cross-compiling to build utility executables that can +run on the host platform in one project and then import them into another +project being compiled for the target platform.

+

The file created by this command is specific to the build tree and +should never be installed. See the install(EXPORT) command to +export targets from an install tree.

+

The options are:

+
+
NAMESPACE <namespace>

Prepend the <namespace> string to all target names written to the file.

+
+
APPEND

Append to the file instead of overwriting it. This can be used to +incrementally export multiple targets to the same file.

+
+
EXPORT_LINK_INTERFACE_LIBRARIES

Include the contents of the properties named with the pattern +(IMPORTED_)?LINK_INTERFACE_LIBRARIES(_<CONFIG>)? +in the export, even when policy CMP0022 is NEW. This is useful +to support consumers using CMake versions older than 2.8.12.

+
+
+

CXX_MODULES_DIRECTORY <directory>

+
+
+

Note

+

Experimental. Gated by CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API

+
+

Export C++ module properties to files under the given directory. Each file +will be named according to the target's export name (without any namespace). +These files will automatically be included from the export file.

+
+

This signature requires all targets to be listed explicitly. If a library +target is included in the export, but a target to which it links is not +included, the behavior is unspecified. See the export(EXPORT) signature +to automatically export the same targets from the build tree as +install(EXPORT) would from an install tree.

+
+

Note

+

Object Libraries under Xcode have special handling if +multiple architectures are listed in CMAKE_OSX_ARCHITECTURES. +In this case they will be exported as Interface Libraries with +no object files available to clients. This is sufficient to satisfy +transitive usage requirements of other targets that link to the +object libraries in their implementation.

+
+

This command exports all Build Configurations from the build tree. +See the CMAKE_MAP_IMPORTED_CONFIG_<CONFIG> variable to map +configurations of dependent projects to the exported configurations.

+
+

Exporting Targets to Android.mk

+
export(TARGETS <target>... ANDROID_MK <filename>)
+
+
+
+

New in version 3.7.

+
+

This signature exports cmake built targets to the android ndk build system +by creating an Android.mk file that references the prebuilt targets. The +Android NDK supports the use of prebuilt libraries, both static and shared. +This allows cmake to build the libraries of a project and make them available +to an ndk build system complete with transitive dependencies, include flags +and defines required to use the libraries. The signature takes a list of +targets and puts them in the Android.mk file specified by the +<filename> given. This signature can only be used if policy +CMP0022 is NEW for all targets given. A error will be issued if +that policy is set to OLD for one of the targets.

+
+
+
+

Exporting Targets matching install(EXPORT)

+
export(EXPORT <export-name> [NAMESPACE <namespace>] [FILE <filename>]
+       [CXX_MODULES_DIRECTORY <directory>])
+
+
+

Creates a file <filename> that may be included by outside projects to +import targets from the current project's build tree. This is the same +as the export(TARGETS) signature, except that the targets are not +explicitly listed. Instead, it exports the targets associated with +the installation export <export-name>. Target installations may be +associated with the export <export-name> using the EXPORT option +of the install(TARGETS) command.

+
+
+

Exporting Packages

+
export(PACKAGE <PackageName>)
+
+
+

Store the current build directory in the CMake user package registry +for package <PackageName>. The find_package() command may consider the +directory while searching for package <PackageName>. This helps dependent +projects find and use a package from the current project's build tree +without help from the user. Note that the entry in the package +registry that this command creates works only in conjunction with a +package configuration file (<PackageName>Config.cmake) that works with the +build tree. In some cases, for example for packaging and for system +wide installations, it is not desirable to write the user package +registry.

+
+

Changed in version 3.1: If the CMAKE_EXPORT_NO_PACKAGE_REGISTRY variable +is enabled, the export(PACKAGE) command will do nothing.

+
+
+

Changed in version 3.15: By default the export(PACKAGE) command does nothing (see policy +CMP0090) because populating the user package registry has effects +outside the source and build trees. Set the +CMAKE_EXPORT_PACKAGE_REGISTRY variable to add build directories +to the CMake user package registry.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/export_library_dependencies.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/export_library_dependencies.html new file mode 100644 index 0000000000000000000000000000000000000000..192ddaa34e50b89df9d30656f5c3f06c5d49516c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/export_library_dependencies.html @@ -0,0 +1,158 @@ + + + + + + + + + export_library_dependencies — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

export_library_dependencies

+

Disallowed since version 3.0. See CMake Policy CMP0033.

+

Use install(EXPORT) or export() command.

+

This command generates an old-style library dependencies file. +Projects requiring CMake 2.6 or later should not use the command. Use +instead the install(EXPORT) command to help export targets from an +installation tree and the export() command to export targets from a +build tree.

+

The old-style library dependencies file does not take into account +per-configuration names of libraries or the +LINK_INTERFACE_LIBRARIES target property.

+
export_library_dependencies(<file> [APPEND])
+
+
+

Create a file named <file> that can be included into a CMake listfile +with the INCLUDE command. The file will contain a number of SET +commands that will set all the variables needed for library dependency +information. This should be the last command in the top level +CMakeLists.txt file of the project. If the APPEND option is +specified, the SET commands will be appended to the given file instead +of replacing it.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/file.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/file.html new file mode 100644 index 0000000000000000000000000000000000000000..da8626ddcb6dab2cd5fa359cb409b12e64b382e1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/file.html @@ -0,0 +1,1355 @@ + + + + + + + + + file — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

file

+

File manipulation command.

+

This command is dedicated to file and path manipulation requiring access to the +filesystem.

+

For other path manipulation, handling only syntactic aspects, have a look at +cmake_path() command.

+
+

Note

+

The sub-commands RELATIVE_PATH, TO_CMAKE_PATH and TO_NATIVE_PATH has +been superseded, respectively, by sub-commands +RELATIVE_PATH, +CONVERT ... TO_CMAKE_PATH_LIST and +CONVERT ... TO_NATIVE_PATH_LIST of +cmake_path() command.

+
+
+

Synopsis

+
Reading
+  file(READ <filename> <out-var> [...])
+  file(STRINGS <filename> <out-var> [...])
+  file(<HASH> <filename> <out-var>)
+  file(TIMESTAMP <filename> <out-var> [...])
+  file(GET_RUNTIME_DEPENDENCIES [...])
+
+Writing
+  file({WRITE | APPEND} <filename> <content>...)
+  file({TOUCH | TOUCH_NOCREATE} [<file>...])
+  file(GENERATE OUTPUT <output-file> [...])
+  file(CONFIGURE OUTPUT <output-file> CONTENT <content> [...])
+
+Filesystem
+  file({GLOB | GLOB_RECURSE} <out-var> [...] [<globbing-expr>...])
+  file(MAKE_DIRECTORY [<dir>...])
+  file({REMOVE | REMOVE_RECURSE } [<files>...])
+  file(RENAME <oldname> <newname> [...])
+  file(COPY_FILE <oldname> <newname> [...])
+  file({COPY | INSTALL} <file>... DESTINATION <dir> [...])
+  file(SIZE <filename> <out-var>)
+  file(READ_SYMLINK <linkname> <out-var>)
+  file(CREATE_LINK <original> <linkname> [...])
+  file(CHMOD <files>... <directories>... PERMISSIONS <permissions>... [...])
+  file(CHMOD_RECURSE <files>... <directories>... PERMISSIONS <permissions>... [...])
+
+Path Conversion
+  file(REAL_PATH <path> <out-var> [BASE_DIRECTORY <dir>] [EXPAND_TILDE])
+  file(RELATIVE_PATH <out-var> <directory> <file>)
+  file({TO_CMAKE_PATH | TO_NATIVE_PATH} <path> <out-var>)
+
+Transfer
+  file(DOWNLOAD <url> [<file>] [...])
+  file(UPLOAD <file> <url> [...])
+
+Locking
+  file(LOCK <path> [...])
+
+Archiving
+  file(ARCHIVE_CREATE OUTPUT <archive> PATHS <paths>... [...])
+  file(ARCHIVE_EXTRACT INPUT <archive> [...])
+
+
+

Reading

+
+
+file(READ <filename> <variable> [OFFSET <offset>] [LIMIT <max-in>] [HEX])
+

Read content from a file called <filename> and store it in a +<variable>. Optionally start from the given <offset> and +read at most <max-in> bytes. The HEX option causes data to +be converted to a hexadecimal representation (useful for binary data). +If the HEX option is specified, letters in the output +(a through f) are in lowercase.

+
+ +
+
+file(STRINGS <filename> <variable> [<options>...])
+

Parse a list of ASCII strings from <filename> and store it in +<variable>. Binary data in the file are ignored. Carriage return +(\r, CR) characters are ignored. The options are:

+
+
+
LENGTH_MAXIMUM <max-len>

Consider only strings of at most a given length.

+
+
LENGTH_MINIMUM <min-len>

Consider only strings of at least a given length.

+
+
LIMIT_COUNT <max-num>

Limit the number of distinct strings to be extracted.

+
+
LIMIT_INPUT <max-in>

Limit the number of input bytes to read from the file.

+
+
LIMIT_OUTPUT <max-out>

Limit the number of total bytes to store in the <variable>.

+
+
NEWLINE_CONSUME

Treat newline characters (\n, LF) as part of string content +instead of terminating at them.

+
+
NO_HEX_CONVERSION

Intel Hex and Motorola S-record files are automatically converted to +binary while reading unless this option is given.

+
+
REGEX <regex>

Consider only strings that match the given regular expression, +as described under string(REGEX).

+
+
ENCODING <encoding-type>
+

New in version 3.1.

+
+

Consider strings of a given encoding. Currently supported encodings are: +UTF-8, UTF-16LE, UTF-16BE, UTF-32LE, UTF-32BE. +If the ENCODING option is not provided and the file +has a Byte Order Mark, the ENCODING option will be defaulted +to respect the Byte Order Mark.

+
+
+
+
+

New in version 3.2: Added the UTF-16LE, UTF-16BE, UTF-32LE, UTF-32BE encodings.

+
+

For example, the code

+
file(STRINGS myfile.txt myfile)
+
+
+

stores a list in the variable myfile in which each item is a line +from the input file.

+
+ +
+
+file(<HASH> <filename> <variable>)
+

Compute a cryptographic hash of the content of <filename> and +store it in a <variable>. The supported <HASH> algorithm names +are those listed by the string(<HASH>) command.

+
+ +
+
+file(TIMESTAMP <filename> <variable> [<format>] [UTC])
+

Compute a string representation of the modification time of <filename> +and store it in <variable>. Should the command be unable to obtain a +timestamp variable will be set to the empty string ("").

+

See the string(TIMESTAMP) command for documentation of +the <format> and UTC options.

+
+ +
+
+file(GET_RUNTIME_DEPENDENCIES [...])
+
+

New in version 3.16.

+
+

Recursively get the list of libraries depended on by the given files:

+
file(GET_RUNTIME_DEPENDENCIES
+  [RESOLVED_DEPENDENCIES_VAR <deps_var>]
+  [UNRESOLVED_DEPENDENCIES_VAR <unresolved_deps_var>]
+  [CONFLICTING_DEPENDENCIES_PREFIX <conflicting_deps_prefix>]
+  [EXECUTABLES [<executable_files>...]]
+  [LIBRARIES [<library_files>...]]
+  [MODULES [<module_files>...]]
+  [DIRECTORIES [<directories>...]]
+  [BUNDLE_EXECUTABLE <bundle_executable_file>]
+  [PRE_INCLUDE_REGEXES [<regexes>...]]
+  [PRE_EXCLUDE_REGEXES [<regexes>...]]
+  [POST_INCLUDE_REGEXES [<regexes>...]]
+  [POST_EXCLUDE_REGEXES [<regexes>...]]
+  [POST_INCLUDE_FILES [<files>...]]
+  [POST_EXCLUDE_FILES [<files>...]]
+  )
+
+
+

Please note that this sub-command is not intended to be used in project mode. +It is intended for use at install time, either from code generated by the +install(RUNTIME_DEPENDENCY_SET) command, or from code provided by +the project via install(CODE) or install(SCRIPT). +For example:

+
install(CODE [[
+  file(GET_RUNTIME_DEPENDENCIES
+    # ...
+    )
+  ]])
+
+
+

The arguments are as follows:

+
+
+
RESOLVED_DEPENDENCIES_VAR <deps_var>

Name of the variable in which to store the list of resolved dependencies.

+
+
UNRESOLVED_DEPENDENCIES_VAR <unresolved_deps_var>

Name of the variable in which to store the list of unresolved +dependencies. If this variable is not specified, and there are any +unresolved dependencies, an error is issued.

+
+
CONFLICTING_DEPENDENCIES_PREFIX <conflicting_deps_prefix>

Variable prefix in which to store conflicting dependency information. +Dependencies are conflicting if two files with the same name are found in +two different directories. The list of filenames that conflict are stored +in <conflicting_deps_prefix>_FILENAMES. For each filename, the list +of paths that were found for that filename are stored in +<conflicting_deps_prefix>_<filename>.

+
+
EXECUTABLES <executable_files>

List of executable files to read for dependencies. These are executables +that are typically created with add_executable(), but they do +not have to be created by CMake. On Apple platforms, the paths to these +files determine the value of @executable_path when recursively +resolving the libraries. Specifying any kind of library (STATIC, +MODULE, or SHARED) here will result in undefined behavior.

+
+
LIBRARIES <library_files>

List of library files to read for dependencies. These are libraries that +are typically created with add_library(SHARED), but they do +not have to be created by CMake. Specifying STATIC libraries, +MODULE libraries, or executables here will result in undefined +behavior.

+
+
MODULES <module_files>

List of loadable module files to read for dependencies. These are modules +that are typically created with add_library(MODULE), but they +do not have to be created by CMake. They are typically used by calling +dlopen() at runtime rather than linked at link time with ld -l. +Specifying STATIC libraries, SHARED libraries, or executables +here will result in undefined behavior.

+
+
DIRECTORIES <directories>

List of additional directories to search for dependencies. On Linux +platforms, these directories are searched if the dependency is not found +in any of the other usual paths. If it is found in such a directory, a +warning is issued, because it means that the file is incomplete (it does +not list all of the directories that contain its dependencies). +On Windows platforms, these directories are searched if the dependency +is not found in any of the other search paths, but no warning is issued, +because searching other paths is a normal part of Windows dependency +resolution. On Apple platforms, this argument has no effect.

+
+
BUNDLE_EXECUTABLE <bundle_executable_file>

Executable to treat as the "bundle executable" when resolving libraries. +On Apple platforms, this argument determines the value of +@executable_path when recursively resolving libraries for +LIBRARIES and MODULES files. It has no effect on EXECUTABLES +files. On other platforms, it has no effect. This is typically (but not +always) one of the executables in the EXECUTABLES argument which +designates the "main" executable of the package.

+
+
+
+

The following arguments specify filters for including or excluding libraries +to be resolved. See below for a full description of how they work.

+
+
+
PRE_INCLUDE_REGEXES <regexes>

List of pre-include regexes through which to filter the names of +not-yet-resolved dependencies.

+
+
PRE_EXCLUDE_REGEXES <regexes>

List of pre-exclude regexes through which to filter the names of +not-yet-resolved dependencies.

+
+
POST_INCLUDE_REGEXES <regexes>

List of post-include regexes through which to filter the names of +resolved dependencies.

+
+
POST_EXCLUDE_REGEXES <regexes>

List of post-exclude regexes through which to filter the names of +resolved dependencies.

+
+
POST_INCLUDE_FILES <files>
+

New in version 3.21.

+
+

List of post-include filenames through which to filter the names of +resolved dependencies. Symlinks are resolved when attempting to match +these filenames.

+
+
POST_EXCLUDE_FILES <files>
+

New in version 3.21.

+
+

List of post-exclude filenames through which to filter the names of +resolved dependencies. Symlinks are resolved when attempting to match +these filenames.

+
+
+
+

These arguments can be used to exclude unwanted system libraries when +resolving the dependencies, or to include libraries from a specific +directory. The filtering works as follows:

+
    +
  1. If the not-yet-resolved dependency matches any of the +PRE_INCLUDE_REGEXES, steps 2 and 3 are skipped, and the dependency +resolution proceeds to step 4.

  2. +
  3. If the not-yet-resolved dependency matches any of the +PRE_EXCLUDE_REGEXES, dependency resolution stops for that dependency.

  4. +
  5. Otherwise, dependency resolution proceeds.

  6. +
  7. file(GET_RUNTIME_DEPENDENCIES) searches for the dependency according +to the linking rules of the platform (see below).

  8. +
  9. If the dependency is found, and its full path matches one of the +POST_INCLUDE_REGEXES or POST_INCLUDE_FILES, the full path is added +to the resolved dependencies, and file(GET_RUNTIME_DEPENDENCIES) +recursively resolves that library's own dependencies. Otherwise, resolution +proceeds to step 6.

  10. +
  11. If the dependency is found, but its full path matches one of the +POST_EXCLUDE_REGEXES or POST_EXCLUDE_FILES, it is not added to the +resolved dependencies, and dependency resolution stops for that dependency.

  12. +
  13. If the dependency is found, and its full path does not match either +POST_INCLUDE_REGEXES, POST_INCLUDE_FILES, POST_EXCLUDE_REGEXES, +or POST_EXCLUDE_FILES, the full path is added to the resolved +dependencies, and file(GET_RUNTIME_DEPENDENCIES) recursively resolves +that library's own dependencies.

  14. +
+

Different platforms have different rules for how dependencies are resolved. +These specifics are described here.

+

On Linux platforms, library resolution works as follows:

+
    +
  1. If the depending file does not have any RUNPATH entries, and the +library exists in one of the depending file's RPATH entries, or its +parents', in that order, the dependency is resolved to that file.

  2. +
  3. Otherwise, if the depending file has any RUNPATH entries, and the +library exists in one of those entries, the dependency is resolved to that +file.

  4. +
  5. Otherwise, if the library exists in one of the directories listed by +ldconfig, the dependency is resolved to that file.

  6. +
  7. Otherwise, if the library exists in one of the DIRECTORIES entries, +the dependency is resolved to that file. In this case, a warning is +issued, because finding a file in one of the DIRECTORIES means that +the depending file is not complete (it does not list all the directories +from which it pulls dependencies).

  8. +
  9. Otherwise, the dependency is unresolved.

  10. +
+

On Windows platforms, library resolution works as follows:

+
    +
  1. DLL dependency names are converted to lowercase for matching filters. +Windows DLL names are case-insensitive, and some linkers mangle the +case of the DLL dependency names. However, this makes it more difficult +for PRE_INCLUDE_REGEXES, PRE_EXCLUDE_REGEXES, +POST_INCLUDE_REGEXES, and POST_EXCLUDE_REGEXES to properly +filter DLL names - every regex would have to check for both uppercase +and lowercase letters. For example:

    +
    file(GET_RUNTIME_DEPENDENCIES
    +  # ...
    +  PRE_INCLUDE_REGEXES "^[Mm][Yy][Ll][Ii][Bb][Rr][Aa][Rr][Yy]\\.[Dd][Ll][Ll]$"
    +  )
    +
    +
    +

    Converting the DLL name to lowercase allows the regexes to only match +lowercase names, thus simplifying the regex. For example:

    +
    file(GET_RUNTIME_DEPENDENCIES
    +  # ...
    +  PRE_INCLUDE_REGEXES "^mylibrary\\.dll$"
    +  )
    +
    +
    +

    This regex will match mylibrary.dll regardless of how it is cased, +either on disk or in the depending file. (For example, it will match +mylibrary.dll, MyLibrary.dll, and MYLIBRARY.DLL.)

    +
    +

    Changed in version 3.27: The conversion to lowercase only applies while matching filters. +Results reported after filtering case-preserve each DLL name as it is +found on disk, if resolved, and otherwise as it is referenced by the +dependent binary.

    +

    Prior to CMake 3.27, the results were reported with lowercase DLL +file names, but the directory portion retained its casing.

    +
    +
  2. +
  3. (Not yet implemented) If the depending file is a Windows Store app, +and the dependency is listed as a dependency in the application's package +manifest, the dependency is resolved to that file.

  4. +
  5. Otherwise, if the library exists in the same directory as the depending +file, the dependency is resolved to that file.

  6. +
  7. Otherwise, if the library exists in either the operating system's +system32 directory or the Windows directory, in that order, the +dependency is resolved to that file.

  8. +
  9. Otherwise, if the library exists in one of the directories specified by +DIRECTORIES, in the order they are listed, the dependency is resolved +to that file. In this case, a warning is not issued, because searching +other directories is a normal part of Windows library resolution.

  10. +
  11. Otherwise, the dependency is unresolved.

  12. +
+

On Apple platforms, library resolution works as follows:

+
    +
  1. If the dependency starts with @executable_path/, and an +EXECUTABLES argument is in the process of being resolved, and +replacing @executable_path/ with the directory of the executable +yields an existing file, the dependency is resolved to that file.

  2. +
  3. Otherwise, if the dependency starts with @executable_path/, and there +is a BUNDLE_EXECUTABLE argument, and replacing @executable_path/ +with the directory of the bundle executable yields an existing file, the +dependency is resolved to that file.

  4. +
  5. Otherwise, if the dependency starts with @loader_path/, and replacing +@loader_path/ with the directory of the depending file yields an +existing file, the dependency is resolved to that file.

  6. +
  7. Otherwise, if the dependency starts with @rpath/, and replacing +@rpath/ with one of the RPATH entries of the depending file +yields an existing file, the dependency is resolved to that file. +Note that RPATH entries that start with @executable_path/ or +@loader_path/ also have these items replaced with the appropriate +path.

  8. +
  9. Otherwise, if the dependency is an absolute file that exists, +the dependency is resolved to that file.

  10. +
  11. Otherwise, the dependency is unresolved.

  12. +
+

This function accepts several variables that determine which tool is used for +dependency resolution:

+
+
+CMAKE_GET_RUNTIME_DEPENDENCIES_PLATFORM
+

Determines which operating system and executable format the files are built +for. This could be one of several values:

+
    +
  • linux+elf

  • +
  • windows+pe

  • +
  • macos+macho

  • +
+

If this variable is not specified, it is determined automatically by system +introspection.

+
+ +
+
+CMAKE_GET_RUNTIME_DEPENDENCIES_TOOL
+

Determines the tool to use for dependency resolution. It could be one of +several values, depending on the value of +CMAKE_GET_RUNTIME_DEPENDENCIES_PLATFORM:

+ + + + + + + + + + + + + + + + + +

CMAKE_GET_RUNTIME_DEPENDENCIES_PLATFORM

CMAKE_GET_RUNTIME_DEPENDENCIES_TOOL

linux+elf

objdump

windows+pe

objdump or dumpbin

macos+macho

otool

+

If this variable is not specified, it is determined automatically by system +introspection.

+
+ +
+
+CMAKE_GET_RUNTIME_DEPENDENCIES_COMMAND
+

Determines the path to the tool to use for dependency resolution. This is +the actual path to objdump, dumpbin, or otool.

+

If this variable is not specified, it is determined by the value of +CMAKE_OBJDUMP if set, else by system introspection.

+
+

New in version 3.18: Use CMAKE_OBJDUMP if set.

+
+
+ +
+ +
+
+

Writing

+
+
+file(WRITE <filename> <content>...)
+
+file(APPEND <filename> <content>...)
+

Write <content> into a file called <filename>. If the file does +not exist, it will be created. If the file already exists, WRITE +mode will overwrite it and APPEND mode will append to the end. +Any directories in the path specified by <filename> that do not +exist will be created.

+

If the file is a build input, use the configure_file() command +to update the file only when its content changes.

+
+ +
+
+file(TOUCH [<files>...])
+
+file(TOUCH_NOCREATE [<files>...])
+
+

New in version 3.12.

+
+

Create a file with no content if it does not yet exist. If the file already +exists, its access and/or modification will be updated to the time when the +function call is executed.

+

Use TOUCH_NOCREATE to touch a file if it exists but not create it. +If a file does not exist it will be silently ignored.

+

With TOUCH and TOUCH_NOCREATE, the contents of an existing file +will not be modified.

+
+ +
+
+file(GENERATE [...])
+

Generate an output file for each build configuration supported by the current +CMake Generator. Evaluate +generator expressions +from the input content to produce the output content.

+
file(GENERATE OUTPUT <output-file>
+     <INPUT <input-file>|CONTENT <content>>
+     [CONDITION <expression>] [TARGET <target>]
+     [NO_SOURCE_PERMISSIONS | USE_SOURCE_PERMISSIONS |
+      FILE_PERMISSIONS <permissions>...]
+     [NEWLINE_STYLE [UNIX|DOS|WIN32|LF|CRLF] ])
+
+
+

The options are:

+
+
+
CONDITION <condition>

Generate the output file for a particular configuration only if +the condition is true. The condition must be either 0 or 1 +after evaluating generator expressions.

+
+
CONTENT <content>

Use the content given explicitly as input.

+
+
INPUT <input-file>

Use the content from a given file as input.

+
+

Changed in version 3.10: A relative path is treated with respect to the value of +CMAKE_CURRENT_SOURCE_DIR. See policy CMP0070.

+
+
+
OUTPUT <output-file>

Specify the output file name to generate. Use generator expressions +such as $<CONFIG> to specify a configuration-specific +output file name. Multiple configurations may generate the same output +file only if the generated content is identical. Otherwise, the +<output-file> must evaluate to an unique name for each configuration.

+
+

Changed in version 3.10: A relative path (after evaluating generator expressions) is treated +with respect to the value of CMAKE_CURRENT_BINARY_DIR. +See policy CMP0070.

+
+
+
TARGET <target>
+

New in version 3.19.

+
+

Specify which target to use when evaluating generator expressions that +require a target for evaluation (e.g. +$<COMPILE_FEATURES:...>, +$<TARGET_PROPERTY:prop>).

+
+
NO_SOURCE_PERMISSIONS
+

New in version 3.20.

+
+

The generated file permissions default to the standard 644 value +(-rw-r--r--).

+
+
USE_SOURCE_PERMISSIONS
+

New in version 3.20.

+
+

Transfer the file permissions of the INPUT file to the generated +file. This is already the default behavior if none of the three +permissions-related keywords are given (NO_SOURCE_PERMISSIONS, +USE_SOURCE_PERMISSIONS or FILE_PERMISSIONS). The +USE_SOURCE_PERMISSIONS keyword mostly serves as a way of making +the intended behavior clearer at the call site. It is an error to +specify this option without INPUT.

+
+
FILE_PERMISSIONS <permissions>...
+

New in version 3.20.

+
+

Use the specified permissions for the generated file.

+
+
NEWLINE_STYLE <style>
+

New in version 3.20.

+
+

Specify the newline style for the generated file. Specify +UNIX or LF for \n newlines, or specify +DOS, WIN32, or CRLF for \r\n newlines.

+
+
+
+

Exactly one CONTENT or INPUT option must be given. A specific +OUTPUT file may be named by at most one invocation of file(GENERATE). +Generated files are modified and their timestamp updated on subsequent cmake +runs only if their content is changed.

+

Note also that file(GENERATE) does not create the output file until the +generation phase. The output file will not yet have been written when the +file(GENERATE) command returns, it is written only after processing all +of a project's CMakeLists.txt files.

+
+ +
+
+file(CONFIGURE OUTPUT <output-file> CONTENT <content> [ESCAPE_QUOTES] [@ONLY] [NEWLINE_STYLE [UNIX|DOS|WIN32|LF|CRLF] ])
+
+

New in version 3.18.

+
+

Generate an output file using the input given by CONTENT and substitute +variable values referenced as @VAR@ or ${VAR} contained therein. The +substitution rules behave the same as the configure_file() command. +In order to match configure_file()'s behavior, generator expressions +are not supported for both OUTPUT and CONTENT.

+

The arguments are:

+
+
+
OUTPUT <output-file>

Specify the output file name to generate. A relative path is treated with +respect to the value of CMAKE_CURRENT_BINARY_DIR. +<output-file> does not support generator expressions.

+
+
CONTENT <content>

Use the content given explicitly as input. +<content> does not support generator expressions.

+
+
ESCAPE_QUOTES

Escape any substituted quotes with backslashes (C-style).

+
+
@ONLY

Restrict variable replacement to references of the form @VAR@. +This is useful for configuring scripts that use ${VAR} syntax.

+
+
NEWLINE_STYLE <style>

Specify the newline style for the output file. Specify +UNIX or LF for \n newlines, or specify +DOS, WIN32, or CRLF for \r\n newlines.

+
+
+
+
+ +
+
+

Filesystem

+
+
+file(GLOB <variable> [LIST_DIRECTORIES true|false] [RELATIVE <path>] [CONFIGURE_DEPENDS] [<globbing-expressions>...])
+
+file(GLOB_RECURSE <variable> [FOLLOW_SYMLINKS] [LIST_DIRECTORIES true|false] [RELATIVE <path>] [CONFIGURE_DEPENDS] [<globbing-expressions>...])
+

Generate a list of files that match the <globbing-expressions> and +store it into the <variable>. Globbing expressions are similar to +regular expressions, but much simpler. If RELATIVE flag is +specified, the results will be returned as relative paths to the given +path.

+
+

Changed in version 3.6: The results will be ordered lexicographically.

+
+

On Windows and macOS, globbing is case-insensitive even if the underlying +filesystem is case-sensitive (both filenames and globbing expressions are +converted to lowercase before matching). On other platforms, globbing is +case-sensitive.

+
+

New in version 3.3: By default GLOB lists directories. Directories are omitted in the +result if LIST_DIRECTORIES is set to false.

+
+
+

New in version 3.12: If the CONFIGURE_DEPENDS flag is specified, CMake will add logic +to the main build system check target to rerun the flagged GLOB +commands at build time. If any of the outputs change, CMake will regenerate +the build system.

+
+
+

Note

+

We do not recommend using GLOB to collect a list of source files from +your source tree. If no CMakeLists.txt file changes when a source is +added or removed then the generated build system cannot know when to +ask CMake to regenerate. +The CONFIGURE_DEPENDS flag may not work reliably on all generators, or +if a new generator is added in the future that cannot support it, projects +using it will be stuck. Even if CONFIGURE_DEPENDS works reliably, there +is still a cost to perform the check on every rebuild.

+
+

Examples of globbing expressions include:

+ + + + + + + + + + + + +

*.cxx

match all files with extension cxx

*.vt?

match all files with extension vta, ..., vtz

f[3-5].txt

match files f3.txt, f4.txt, f5.txt

+

The GLOB_RECURSE mode will traverse all the subdirectories of the +matched directory and match the files. Subdirectories that are symlinks +are only traversed if FOLLOW_SYMLINKS is given or policy +CMP0009 is not set to NEW.

+
+

New in version 3.3: By default GLOB_RECURSE omits directories from result list. Setting +LIST_DIRECTORIES to true adds directories to result list. +If FOLLOW_SYMLINKS is given or policy CMP0009 is not set to +NEW then LIST_DIRECTORIES treats symlinks as directories.

+
+

Examples of recursive globbing include:

+ + + + + + +

/dir/*.py

match all python files in /dir and subdirectories

+
+ +
+
+file(MAKE_DIRECTORY [<directories>...])
+

Create the given directories and their parents as needed.

+
+ +
+
+file(REMOVE [<files>...])
+
+file(REMOVE_RECURSE [<files>...])
+

Remove the given files. The REMOVE_RECURSE mode will remove the given +files and directories, including non-empty directories. No error is emitted +if a given file does not exist. Relative input paths are evaluated with +respect to the current source directory.

+
+

Changed in version 3.15: Empty input paths are ignored with a warning. Previous versions of CMake +interpreted empty strings as a relative path with respect to the current +directory and removed its contents.

+
+
+ +
+
+file(RENAME <oldname> <newname> [RESULT <result>] [NO_REPLACE])
+

Move a file or directory within a filesystem from <oldname> to +<newname>, replacing the destination atomically.

+

The options are:

+
+
+
RESULT <result>
+

New in version 3.21.

+
+

Set <result> variable to 0 on success or an error message +otherwise. If RESULT is not specified and the operation fails, +an error is emitted.

+
+
NO_REPLACE
+

New in version 3.21.

+
+

If the <newname> path already exists, do not replace it. +If RESULT <result> is used, the result variable will be +set to NO_REPLACE. Otherwise, an error is emitted.

+
+
+
+
+ +
+
+file(COPY_FILE <oldname> <newname> [RESULT <result>] [ONLY_IF_DIFFERENT] [INPUT_MAY_BE_RECENT])
+
+

New in version 3.21.

+
+

Copy a file from <oldname> to <newname>. Directories are not +supported. Symlinks are ignored and <oldfile>'s content is read and +written to <newname> as a new file.

+

The options are:

+
+
+
RESULT <result>

Set <result> variable to 0 on success or an error message +otherwise. If RESULT is not specified and the operation fails, +an error is emitted.

+
+
ONLY_IF_DIFFERENT

If the <newname> path already exists, do not replace it if the file's +contents are already the same as <oldname> (this avoids updating +<newname>'s timestamp).

+
+
INPUT_MAY_BE_RECENT
+

New in version 3.26.

+
+

Tell CMake that the input file may have been recently created. This is +meaningful only on Windows, where files may be inaccessible for a short +time after they are created. With this option, if permission is denied, +CMake will retry reading the input a few times.

+
+
+
+

This sub-command has some similarities to configure_file() +with the COPYONLY option. An important difference is that +configure_file() creates a dependency on the source file, +so CMake will be re-run if it changes. The file(COPY_FILE) +sub-command does not create such a dependency.

+

See also the file(COPY) sub-command just below which provides +further file-copying capabilities.

+
+ +
+
+file(COPY [...])
+
+file(INSTALL [...])
+

The COPY signature copies files, directories, and symlinks to a +destination folder. Relative input paths are evaluated with respect +to the current source directory, and a relative destination is +evaluated with respect to the current build directory. Copying +preserves input file timestamps, and optimizes out a file if it exists +at the destination with the same timestamp. Copying preserves input +permissions unless explicit permissions or NO_SOURCE_PERMISSIONS +are given (default is USE_SOURCE_PERMISSIONS).

+
file(<COPY|INSTALL> <files>... DESTINATION <dir>
+     [NO_SOURCE_PERMISSIONS | USE_SOURCE_PERMISSIONS]
+     [FILE_PERMISSIONS <permissions>...]
+     [DIRECTORY_PERMISSIONS <permissions>...]
+     [FOLLOW_SYMLINK_CHAIN]
+     [FILES_MATCHING]
+     [[PATTERN <pattern> | REGEX <regex>]
+      [EXCLUDE] [PERMISSIONS <permissions>...]] [...])
+
+
+
+

Note

+

For a simple file copying operation, the file(COPY_FILE) +sub-command just above may be easier to use.

+
+
+

New in version 3.15: If FOLLOW_SYMLINK_CHAIN is specified, COPY will recursively resolve +the symlinks at the paths given until a real file is found, and install +a corresponding symlink in the destination for each symlink encountered. +For each symlink that is installed, the resolution is stripped of the +directory, leaving only the filename, meaning that the new symlink points +to a file in the same directory as the symlink. This feature is useful on +some Unix systems, where libraries are installed as a chain of symlinks +with version numbers, with less specific versions pointing to more specific +versions. FOLLOW_SYMLINK_CHAIN will install all of these symlinks and +the library itself into the destination directory. For example, if you have +the following directory structure:

+
+
    +
  • /opt/foo/lib/libfoo.so.1.2.3

  • +
  • /opt/foo/lib/libfoo.so.1.2 -> libfoo.so.1.2.3

  • +
  • /opt/foo/lib/libfoo.so.1 -> libfoo.so.1.2

  • +
  • /opt/foo/lib/libfoo.so -> libfoo.so.1

  • +
+
+

and you do:

+
file(COPY /opt/foo/lib/libfoo.so DESTINATION lib FOLLOW_SYMLINK_CHAIN)
+
+
+

This will install all of the symlinks and libfoo.so.1.2.3 itself into +lib.

+
+

See the install(DIRECTORY) command for documentation of +permissions, FILES_MATCHING, PATTERN, REGEX, and +EXCLUDE options. Copying directories preserves the structure +of their content even if options are used to select a subset of +files.

+

The INSTALL signature differs slightly from COPY: it prints +status messages, and NO_SOURCE_PERMISSIONS is default. Installation +scripts generated by the install() command use this signature +(with some undocumented options for internal use).

+
+

Changed in version 3.22: The environment variable CMAKE_INSTALL_MODE can override the +default copying behavior of file(INSTALL).

+
+
+ +
+
+file(SIZE <filename> <variable>)
+
+

New in version 3.14.

+
+

Determine the file size of the <filename> and put the result in +<variable> variable. Requires that <filename> is a valid path +pointing to a file and is readable.

+
+ +
+ +
+

New in version 3.14.

+
+

Query the symlink <linkname> and stores the path it points to +in the result <variable>. If <linkname> does not exist +or is not a symlink, CMake issues a fatal error.

+

Note that this command returns the raw symlink path and does not resolve +a relative path. The following is an example of how to ensure that an +absolute path is obtained:

+
set(linkname "/path/to/foo.sym")
+file(READ_SYMLINK "${linkname}" result)
+if(NOT IS_ABSOLUTE "${result}")
+  get_filename_component(dir "${linkname}" DIRECTORY)
+  set(result "${dir}/${result}")
+endif()
+
+
+
+ +
+ +
+

New in version 3.14.

+
+

Create a link <linkname> that points to <original>. +It will be a hard link by default, but providing the SYMBOLIC option +results in a symbolic link instead. Hard links require that original +exists and is a file, not a directory. If <linkname> already exists, +it will be overwritten.

+

The <result> variable, if specified, receives the status of the +operation. It is set to 0 upon success or an error message otherwise. +If RESULT is not specified and the operation fails, a fatal error is +emitted.

+

Specifying COPY_ON_ERROR enables copying the file as a fallback if +creating the link fails. It can be useful for handling situations such as +<original> and <linkname> being on different drives or mount points, +which would make them unable to support a hard link.

+
+ +
+
+file(CHMOD <files>... <directories>... [PERMISSIONS <permissions>...] [FILE_PERMISSIONS <permissions>...] [DIRECTORY_PERMISSIONS <permissions>...])
+
+

New in version 3.19.

+
+

Set the permissions for the <files>... and <directories>... +specified. Valid permissions are OWNER_READ, OWNER_WRITE, +OWNER_EXECUTE, GROUP_READ, GROUP_WRITE, GROUP_EXECUTE, +WORLD_READ, WORLD_WRITE, WORLD_EXECUTE, SETUID, SETGID.

+

Valid combination of keywords are:

+
+
+
PERMISSIONS

All items are changed.

+
+
FILE_PERMISSIONS

Only files are changed.

+
+
DIRECTORY_PERMISSIONS

Only directories are changed.

+
+
PERMISSIONS and FILE_PERMISSIONS

FILE_PERMISSIONS overrides PERMISSIONS for files.

+
+
PERMISSIONS and DIRECTORY_PERMISSIONS

DIRECTORY_PERMISSIONS overrides PERMISSIONS for directories.

+
+
FILE_PERMISSIONS and DIRECTORY_PERMISSIONS

Use FILE_PERMISSIONS for files and DIRECTORY_PERMISSIONS for +directories.

+
+
+
+
+ +
+
+file(CHMOD_RECURSE <files>... <directories>... [PERMISSIONS <permissions>...] [FILE_PERMISSIONS <permissions>...] [DIRECTORY_PERMISSIONS <permissions>...])
+
+

New in version 3.19.

+
+

Same as CHMOD, but change the permissions of files and directories +present in the <directories>... recursively.

+
+ +
+
+

Path Conversion

+
+
+file(REAL_PATH <path> <out-var> [BASE_DIRECTORY <dir>] [EXPAND_TILDE])
+
+

New in version 3.19.

+
+

Compute the absolute path to an existing file or directory with symlinks +resolved. The options are:

+
+
+
BASE_DIRECTORY <dir>

If the provided <path> is a relative path, it is evaluated relative +to the given base directory <dir>. If no base directory is provided, +the default base directory will be CMAKE_CURRENT_SOURCE_DIR.

+
+
EXPAND_TILDE
+

New in version 3.21.

+
+

If the <path> is ~ or starts with ~/, the ~ is replaced +by the user's home directory. The path to the home directory is obtained +from environment variables. On Windows, the USERPROFILE environment +variable is used, falling back to the HOME environment variable +if USERPROFILE is not defined. On all other platforms, only HOME +is used.

+
+
+
+
+ +
+
+file(RELATIVE_PATH <variable> <directory> <file>)
+

Compute the relative path from a <directory> to a <file> and +store it in the <variable>.

+
+ +
+
+file(TO_CMAKE_PATH "<path>" <variable>)
+
+file(TO_NATIVE_PATH "<path>" <variable>)
+

The TO_CMAKE_PATH mode converts a native <path> into a cmake-style +path with forward-slashes (/). The input can be a single path or a +system search path like $ENV{PATH}. A search path will be converted +to a cmake-style list separated by ; characters.

+

The TO_NATIVE_PATH mode converts a cmake-style <path> into a native +path with platform-specific slashes (\ on Windows hosts and / +elsewhere).

+

Always use double quotes around the <path> to be sure it is treated +as a single argument to this command.

+
+ +
+
+

Transfer

+
+
+file(DOWNLOAD <url> [<file>] [<options>...])
+
+file(UPLOAD <file> <url> [<options>...])
+

The DOWNLOAD subcommand downloads the given <url> to a local +<file>. The UPLOAD mode uploads a local <file> to a given +<url>.

+
+

New in version 3.19: If <file> is not specified for file(DOWNLOAD), the file is not +saved. This can be useful if you want to know if a file can be downloaded +(for example, to check that it exists) without actually saving it anywhere.

+
+

Options to both DOWNLOAD and UPLOAD are:

+
+
+
INACTIVITY_TIMEOUT <seconds>

Terminate the operation after a period of inactivity.

+
+
LOG <variable>

Store a human-readable log of the operation in a variable.

+
+
SHOW_PROGRESS

Print progress information as status messages until the operation is +complete.

+
+
STATUS <variable>

Store the resulting status of the operation in a variable. +The status is a ; separated list of length 2. +The first element is the numeric return value for the operation, +and the second element is a string value for the error. +A 0 numeric error means no error in the operation.

+
+
TIMEOUT <seconds>

Terminate the operation after a given total time has elapsed.

+
+
USERPWD <username>:<password>
+

New in version 3.7.

+
+

Set username and password for operation.

+
+
HTTPHEADER <HTTP-header>
+

New in version 3.7.

+
+

HTTP header for DOWNLOAD and UPLOAD operations. HTTPHEADER +can be repeated for multiple options:

+
file(DOWNLOAD <url>
+     HTTPHEADER "Authorization: Bearer <auth-token>"
+     HTTPHEADER "UserAgent: Mozilla/5.0")
+
+
+
+
NETRC <level>
+

New in version 3.11.

+
+

Specify whether the .netrc file is to be used for operation. If this +option is not specified, the value of the CMAKE_NETRC +variable will be used instead.

+

Valid levels are:

+
+
+
IGNORED

The .netrc file is ignored. +This is the default.

+
+
OPTIONAL

The .netrc file is optional, and information in the URL is preferred. +The file will be scanned to find which ever information is not +specified in the URL.

+
+
REQUIRED

The .netrc file is required, and information in the URL is ignored.

+
+
+
+
+
NETRC_FILE <file>
+

New in version 3.11.

+
+

Specify an alternative .netrc file to the one in your home directory, +if the NETRC level is OPTIONAL or REQUIRED. If this option +is not specified, the value of the CMAKE_NETRC_FILE variable +will be used instead.

+
+
TLS_VERIFY <ON|OFF>

Specify whether to verify the server certificate for https:// URLs. +The default is to not verify. If this option is not specified, the +value of the CMAKE_TLS_VERIFY variable will be used instead.

+
+

New in version 3.18: Added support to file(UPLOAD).

+
+
+
TLS_CAINFO <file>

Specify a custom Certificate Authority file for https:// URLs. +If this option is not specified, the value of the +CMAKE_TLS_CAINFO variable will be used instead.

+
+

New in version 3.18: Added support to file(UPLOAD).

+
+
+
+
+

For https:// URLs CMake must be built with OpenSSL support. TLS/SSL +certificates are not checked by default. Set TLS_VERIFY to ON to +check certificates.

+

Additional options to DOWNLOAD are:

+
+
+
EXPECTED_HASH <algorithm>=<value>

Verify that the downloaded content hash matches the expected value, where +<algorithm> is one of the algorithms supported by <HASH>. +If the file already exists and matches the hash, the download is skipped. +If the file already exists and does not match the hash, the file is +downloaded again. If after download the file does not match the hash, the +operation fails with an error. It is an error to specify this option if +DOWNLOAD is not given a <file>.

+
+
EXPECTED_MD5 <value>

Historical short-hand for EXPECTED_HASH MD5=<value>. It is an error +to specify this if DOWNLOAD is not given a <file>.

+
+
RANGE_START <value>
+

New in version 3.24.

+
+

Offset of the start of the range in file in bytes. Could be omitted to +download up to the specified RANGE_END.

+
+
RANGE_END <value>
+

New in version 3.24.

+
+

Offset of the end of the range in file in bytes. Could be omitted to +download everything from the specified RANGE_START to the end of +file.

+
+
+
+
+ +
+
+

Locking

+
+
+file(LOCK <path> [DIRECTORY] [RELEASE] [GUARD <FUNCTION|FILE|PROCESS>] [RESULT_VARIABLE <variable>] [TIMEOUT <seconds>])
+
+

New in version 3.2.

+
+

Lock a file specified by <path> if no DIRECTORY option present and +file <path>/cmake.lock otherwise. The file will be locked for the scope +defined by the GUARD option (default value is PROCESS). The +RELEASE option can be used to unlock the file explicitly. If the +TIMEOUT option is not specified, CMake will wait until the lock succeeds +or until a fatal error occurs. If TIMEOUT is set to 0, locking will +be tried once and the result will be reported immediately. If TIMEOUT +is not 0, CMake will try to lock the file for the period specified by +the TIMEOUT <seconds> value. Any errors will be interpreted as fatal if +there is no RESULT_VARIABLE option. Otherwise, the result will be stored +in <variable> and will be 0 on success or an error message on +failure.

+

Note that lock is advisory; there is no guarantee that other processes will +respect this lock, i.e. lock synchronize two or more CMake instances sharing +some modifiable resources. Similar logic applies to the DIRECTORY option; +locking a parent directory doesn't prevent other LOCK commands from +locking any child directory or file.

+

Trying to lock the same file twice is not allowed. Any intermediate +directories and the file itself will be created if they not exist. The +GUARD and TIMEOUT options are ignored on the RELEASE operation.

+
+ +
+
+

Archiving

+
+
+file(ARCHIVE_CREATE OUTPUT <archive> PATHS <paths>... [FORMAT <format>] [COMPRESSION <compression> [COMPRESSION_LEVEL <compression-level>]] [MTIME <mtime>] [VERBOSE])
+
+

New in version 3.18.

+
+

Creates the specified <archive> file with the files and directories +listed in <paths>. Note that <paths> must list actual files or +directories; wildcards are not supported.

+

Use the FORMAT option to specify the archive format. Supported values +for <format> are 7zip, gnutar, pax, paxr, raw and +zip. If FORMAT is not given, the default format is paxr.

+

Some archive formats allow the type of compression to be specified. +The 7zip and zip archive formats already imply a specific type of +compression. The other formats use no compression by default, but can be +directed to do so with the COMPRESSION option. Valid values for +<compression> are None, BZip2, GZip, XZ, and Zstd.

+
+

New in version 3.19: The compression level can be specified with the COMPRESSION_LEVEL +option. The <compression-level> should be between 0-9, with the +default being 0. The COMPRESSION option must be present when +COMPRESSION_LEVEL is given.

+
+
+

New in version 3.26: The <compression-level> of the Zstd algorithm can be set +between 0-19.

+
+
+

Note

+

With FORMAT set to raw, only one file will be compressed with the +compression type specified by COMPRESSION.

+
+

The VERBOSE option enables verbose output for the archive operation.

+

To specify the modification time recorded in tarball entries, use +the MTIME option.

+
+ +
+
+file(ARCHIVE_EXTRACT INPUT <archive> [DESTINATION <dir>] [PATTERNS <patterns>...] [LIST_ONLY] [VERBOSE] [TOUCH])
+
+

New in version 3.18.

+
+

Extracts or lists the content of the specified <archive>.

+

The directory where the content of the archive will be extracted to can +be specified using the DESTINATION option. If the directory does not +exist, it will be created. If DESTINATION is not given, the current +binary directory will be used.

+

If required, you may select which files and directories to list or extract +from the archive using the specified <patterns>. Wildcards are +supported. If the PATTERNS option is not given, the entire archive will +be listed or extracted.

+

LIST_ONLY will list the files in the archive rather than extract them.

+
+

New in version 3.24: The TOUCH option gives extracted files a current local +timestamp instead of extracting file timestamps from the archive.

+
+

With VERBOSE, the command will produce verbose output.

+
+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_file.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_file.html new file mode 100644 index 0000000000000000000000000000000000000000..0474dee7fdc1c9783c31272101fa5d69b5c525af --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_file.html @@ -0,0 +1,433 @@ + + + + + + + + + find_file — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

find_file

+

A short-hand signature is:

+
find_file (<VAR> name1 [path1 path2 ...])
+

The general signature is:

+
find_file (
+          <VAR>
+          name | NAMES name1 [name2 ...]
+          [HINTS [path | ENV var]... ]
+          [PATHS [path | ENV var]... ]
+          [REGISTRY_VIEW (64|32|64_32|32_64|HOST|TARGET|BOTH)]
+          [PATH_SUFFIXES suffix1 [suffix2 ...]]
+          [VALIDATOR function]
+          [DOC "cache documentation string"]
+          [NO_CACHE]
+          [REQUIRED]
+          [NO_DEFAULT_PATH]
+          [NO_PACKAGE_ROOT_PATH]
+          [NO_CMAKE_PATH]
+          [NO_CMAKE_ENVIRONMENT_PATH]
+          [NO_SYSTEM_ENVIRONMENT_PATH]
+          [NO_CMAKE_SYSTEM_PATH]
+          [NO_CMAKE_INSTALL_PREFIX]
+          [CMAKE_FIND_ROOT_PATH_BOTH |
+           ONLY_CMAKE_FIND_ROOT_PATH |
+           NO_CMAKE_FIND_ROOT_PATH]
+         )
+

This command is used to find a full path to named file. +A cache entry, or a normal variable if NO_CACHE is specified, +named by <VAR> is created to store the result of this command. +If the full path to a file is found the result is stored in the variable +and the search will not be repeated unless the variable is cleared. +If nothing is found, the result will be <VAR>-NOTFOUND.

+

Options include:

+
+
NAMES

Specify one or more possible names for the full path to a file.

+

When using this to specify names with and without a version +suffix, we recommend specifying the unversioned name first +so that locally-built packages can be found before those +provided by distributions.

+
+
HINTS, PATHS

Specify directories to search in addition to the default locations. +The ENV var sub-option reads paths from a system environment +variable.

+
+

Changed in version 3.24: On Windows platform, it is possible to include registry queries as part +of the directories, using a dedicated syntax. +Such specifications will be ignored on all other platforms.

+
+
+
REGISTRY_VIEW
+

New in version 3.24.

+
+

Specify which registry views must be queried. This option is only meaningful +on Windows platforms and will be ignored on other ones. When not +specified, the TARGET view is used when the +CMP0134 policy is NEW. Refer to CMP0134 for the +default view when the policy is OLD.

+
+
64

Query the 64-bit registry. On 32-bit Windows, it always returns the string +/REGISTRY-NOTFOUND.

+
+
32

Query the 32-bit registry.

+
+
64_32

Query both views (64 and 32) and generate a path for each.

+
+
32_64

Query both views (32 and 64) and generate a path for each.

+
+
HOST

Query the registry matching the architecture of the host: 64 on 64-bit +Windows and 32 on 32-bit Windows.

+
+
TARGET

Query the registry matching the architecture specified by the +CMAKE_SIZEOF_VOID_P variable. If not defined, fall back to +HOST view.

+
+
BOTH

Query both views (32 and 64). The order depends on the following +rules: If the CMAKE_SIZEOF_VOID_P variable is defined, use the +following view depending on the content of this variable:

+
    +
  • 8: 64_32

  • +
  • 4: 32_64

  • +
+

If the CMAKE_SIZEOF_VOID_P variable is not defined, rely on the +architecture of the host:

+
    +
  • 64-bit: 64_32

  • +
  • 32-bit: 32

  • +
+
+
+
+
PATH_SUFFIXES

Specify additional subdirectories to check below each directory +location otherwise considered.

+
+
VALIDATOR
+

New in version 3.25.

+
+

Specify a function() to be called for each candidate item found +(a macro() cannot be provided, that will result in an error). +Two arguments will be passed to the validator function: the name of a +result variable, and the absolute path to the candidate item. The item +will be accepted and the search will end unless the function sets the +value in the result variable to false in the calling scope. The result +variable will hold a true value when the validator function is entered.

+
function(my_check validator_result_var item)
+  if(NOT item MATCHES ...)
+    set(${validator_result_var} FALSE PARENT_SCOPE)
+  endif()
+endfunction()
+
+find_file (result NAMES ... VALIDATOR my_check)
+

Note that if a cached result is used, the search is skipped and any +VALIDATOR is ignored. The cached result is not required to pass the +validation function.

+
+
DOC

Specify the documentation string for the <VAR> cache entry.

+
+
NO_CACHE
+

New in version 3.21.

+
+

The result of the search will be stored in a normal variable rather than +a cache entry.

+
+

Note

+

If the variable is already set before the call (as a normal or cache +variable) then the search will not occur.

+
+
+

Warning

+

This option should be used with caution because it can greatly increase +the cost of repeated configure steps.

+
+
+
REQUIRED
+

New in version 3.18.

+
+

Stop processing with an error message if nothing is found, otherwise +the search will be attempted again the next time find_file is invoked +with the same variable.

+
+
+

If NO_DEFAULT_PATH is specified, then no additional paths are +added to the search. +If NO_DEFAULT_PATH is not specified, the search process is as follows:

+
    +
  1. If called from within a find module or any other script loaded by a call to +find_package(<PackageName>), search prefixes unique to the +current package being found. See policy CMP0074.

    +
    +

    New in version 3.12.

    +
    +

    Specifically, search paths specified by the following variables, in order:

    +
      +
    1. <PackageName>_ROOT CMake variable, +where <PackageName> is the case-preserved package name.

    2. +
    3. <PACKAGENAME>_ROOT CMake variable, +where <PACKAGENAME> is the upper-cased package name. +See policy CMP0144.

      +
      +

      New in version 3.27.

      +
      +
    4. +
    5. <PackageName>_ROOT environment variable, +where <PackageName> is the case-preserved package name.

    6. +
    7. <PACKAGENAME>_ROOT environment variable, +where <PACKAGENAME> is the upper-cased package name. +See policy CMP0144.

      +
      +

      New in version 3.27.

      +
      +
    8. +
    +

    The package root variables are maintained as a stack, so if called from +nested find modules or config packages, root paths from the parent's find +module or config package will be searched after paths from the current +module or package. In other words, the search order would be +<CurrentPackage>_ROOT, ENV{<CurrentPackage>_ROOT}, +<ParentPackage>_ROOT, ENV{<ParentPackage>_ROOT}, etc. +This can be skipped if NO_PACKAGE_ROOT_PATH is passed or by setting +the CMAKE_FIND_USE_PACKAGE_ROOT_PATH to FALSE.

    + +
  2. +
  3. Search paths specified in cmake-specific cache variables. +These are intended to be used on the command line with a -DVAR=value. +The values are interpreted as semicolon-separated lists. +This can be skipped if NO_CMAKE_PATH is passed or by setting the +CMAKE_FIND_USE_CMAKE_PATH to FALSE.

    + +
  4. +
  5. Search paths specified in cmake-specific environment variables. +These are intended to be set in the user's shell configuration, +and therefore use the host's native path separator +(; on Windows and : on UNIX). +This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed or +by setting the CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH to FALSE.

    + +
  6. +
  7. Search the paths specified by the HINTS option. +These should be paths computed by system introspection, such as a +hint provided by the location of another item already found. +Hard-coded guesses should be specified with the PATHS option.

  8. +
  9. Search the standard system environment variables. +This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is passed or by +setting the CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH to FALSE.

    +
      +
    • The directories in INCLUDE +and PATH.

    • +
    • On Windows hosts: +<prefix>/include/<arch> if CMAKE_LIBRARY_ARCHITECTURE +is set, and <prefix>/include for each <prefix>/[s]bin in PATH, and +<entry>/include for other entries in PATH.

    • +
    +
  10. +
  11. Search cmake variables defined in the Platform files +for the current system. The searching of CMAKE_INSTALL_PREFIX and +CMAKE_STAGING_PREFIX can be +skipped if NO_CMAKE_INSTALL_PREFIX is passed or by setting the +CMAKE_FIND_USE_INSTALL_PREFIX to FALSE. All these locations +can be skipped if NO_CMAKE_SYSTEM_PATH is passed or by setting the +CMAKE_FIND_USE_CMAKE_SYSTEM_PATH to FALSE.

    + +

    The platform paths that these variables contain are locations that +typically include installed software. An example being /usr/local for +UNIX based platforms.

    +
  12. +
  13. Search the paths specified by the PATHS option +or in the short-hand version of the command. +These are typically hard-coded guesses.

  14. +
+

The CMAKE_IGNORE_PATH, CMAKE_IGNORE_PREFIX_PATH, +CMAKE_SYSTEM_IGNORE_PATH and +CMAKE_SYSTEM_IGNORE_PREFIX_PATH variables can also cause some +of the above locations to be ignored.

+
+

New in version 3.16: Added CMAKE_FIND_USE_<CATEGORY>_PATH variables to globally disable +various search locations.

+
+

On macOS the CMAKE_FIND_FRAMEWORK and +CMAKE_FIND_APPBUNDLE variables determine the order of +preference between Apple-style and unix-style package components.

+

The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more +directories to be prepended to all other search directories. This +effectively "re-roots" the entire search under given locations. +Paths which are descendants of the CMAKE_STAGING_PREFIX are excluded +from this re-rooting, because that variable is always a path on the host system. +By default the CMAKE_FIND_ROOT_PATH is empty.

+

The CMAKE_SYSROOT variable can also be used to specify exactly one +directory to use as a prefix. Setting CMAKE_SYSROOT also has other +effects. See the documentation for that variable for more.

+

These variables are especially useful when cross-compiling to +point to the root directory of the target environment and CMake will +search there too. By default at first the directories listed in +CMAKE_FIND_ROOT_PATH are searched, then the CMAKE_SYSROOT +directory is searched, and then the non-rooted directories will be +searched. The default behavior can be adjusted by setting +CMAKE_FIND_ROOT_PATH_MODE_INCLUDE. This behavior can be manually +overridden on a per-call basis using options:

+
+
CMAKE_FIND_ROOT_PATH_BOTH

Search in the order described above.

+
+
NO_CMAKE_FIND_ROOT_PATH

Do not use the CMAKE_FIND_ROOT_PATH variable.

+
+
ONLY_CMAKE_FIND_ROOT_PATH

Search only the re-rooted directories and directories below +CMAKE_STAGING_PREFIX.

+
+
+

The default search order is designed to be most-specific to +least-specific for common use cases. +Projects may override the order by simply calling the command +multiple times and using the NO_* options:

+
find_file (<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)
+find_file (<VAR> NAMES name)
+

Once one of the calls succeeds the result variable will be set +and stored in the cache so that no call will search again.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_library.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_library.html new file mode 100644 index 0000000000000000000000000000000000000000..dd1173255e2bca8a2c8d21005b66881211c93028 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_library.html @@ -0,0 +1,471 @@ + + + + + + + + + find_library — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

find_library

+

A short-hand signature is:

+
find_library (<VAR> name1 [path1 path2 ...])
+

The general signature is:

+
find_library (
+          <VAR>
+          name | NAMES name1 [name2 ...] [NAMES_PER_DIR]
+          [HINTS [path | ENV var]... ]
+          [PATHS [path | ENV var]... ]
+          [REGISTRY_VIEW (64|32|64_32|32_64|HOST|TARGET|BOTH)]
+          [PATH_SUFFIXES suffix1 [suffix2 ...]]
+          [VALIDATOR function]
+          [DOC "cache documentation string"]
+          [NO_CACHE]
+          [REQUIRED]
+          [NO_DEFAULT_PATH]
+          [NO_PACKAGE_ROOT_PATH]
+          [NO_CMAKE_PATH]
+          [NO_CMAKE_ENVIRONMENT_PATH]
+          [NO_SYSTEM_ENVIRONMENT_PATH]
+          [NO_CMAKE_SYSTEM_PATH]
+          [NO_CMAKE_INSTALL_PREFIX]
+          [CMAKE_FIND_ROOT_PATH_BOTH |
+           ONLY_CMAKE_FIND_ROOT_PATH |
+           NO_CMAKE_FIND_ROOT_PATH]
+         )
+

This command is used to find a library. +A cache entry, or a normal variable if NO_CACHE is specified, +named by <VAR> is created to store the result of this command. +If the library is found the result is stored in the variable +and the search will not be repeated unless the variable is cleared. +If nothing is found, the result will be <VAR>-NOTFOUND.

+

Options include:

+
+
NAMES

Specify one or more possible names for the library.

+

When using this to specify names with and without a version +suffix, we recommend specifying the unversioned name first +so that locally-built packages can be found before those +provided by distributions.

+
+
HINTS, PATHS

Specify directories to search in addition to the default locations. +The ENV var sub-option reads paths from a system environment +variable.

+
+

Changed in version 3.24: On Windows platform, it is possible to include registry queries as part +of the directories, using a dedicated syntax. +Such specifications will be ignored on all other platforms.

+
+
+
REGISTRY_VIEW
+

New in version 3.24.

+
+

Specify which registry views must be queried. This option is only meaningful +on Windows platforms and will be ignored on other ones. When not +specified, the TARGET view is used when the +CMP0134 policy is NEW. Refer to CMP0134 for the +default view when the policy is OLD.

+
+
64

Query the 64-bit registry. On 32-bit Windows, it always returns the string +/REGISTRY-NOTFOUND.

+
+
32

Query the 32-bit registry.

+
+
64_32

Query both views (64 and 32) and generate a path for each.

+
+
32_64

Query both views (32 and 64) and generate a path for each.

+
+
HOST

Query the registry matching the architecture of the host: 64 on 64-bit +Windows and 32 on 32-bit Windows.

+
+
TARGET

Query the registry matching the architecture specified by the +CMAKE_SIZEOF_VOID_P variable. If not defined, fall back to +HOST view.

+
+
BOTH

Query both views (32 and 64). The order depends on the following +rules: If the CMAKE_SIZEOF_VOID_P variable is defined, use the +following view depending on the content of this variable:

+
    +
  • 8: 64_32

  • +
  • 4: 32_64

  • +
+

If the CMAKE_SIZEOF_VOID_P variable is not defined, rely on the +architecture of the host:

+
    +
  • 64-bit: 64_32

  • +
  • 32-bit: 32

  • +
+
+
+
+
PATH_SUFFIXES

Specify additional subdirectories to check below each directory +location otherwise considered.

+
+
VALIDATOR
+

New in version 3.25.

+
+

Specify a function() to be called for each candidate item found +(a macro() cannot be provided, that will result in an error). +Two arguments will be passed to the validator function: the name of a +result variable, and the absolute path to the candidate item. The item +will be accepted and the search will end unless the function sets the +value in the result variable to false in the calling scope. The result +variable will hold a true value when the validator function is entered.

+
function(my_check validator_result_var item)
+  if(NOT item MATCHES ...)
+    set(${validator_result_var} FALSE PARENT_SCOPE)
+  endif()
+endfunction()
+
+find_library (result NAMES ... VALIDATOR my_check)
+

Note that if a cached result is used, the search is skipped and any +VALIDATOR is ignored. The cached result is not required to pass the +validation function.

+
+
DOC

Specify the documentation string for the <VAR> cache entry.

+
+
NO_CACHE
+

New in version 3.21.

+
+

The result of the search will be stored in a normal variable rather than +a cache entry.

+
+

Note

+

If the variable is already set before the call (as a normal or cache +variable) then the search will not occur.

+
+
+

Warning

+

This option should be used with caution because it can greatly increase +the cost of repeated configure steps.

+
+
+
REQUIRED
+

New in version 3.18.

+
+

Stop processing with an error message if nothing is found, otherwise +the search will be attempted again the next time find_library is invoked +with the same variable.

+
+
+

If NO_DEFAULT_PATH is specified, then no additional paths are +added to the search. +If NO_DEFAULT_PATH is not specified, the search process is as follows:

+
    +
  1. If called from within a find module or any other script loaded by a call to +find_package(<PackageName>), search prefixes unique to the +current package being found. See policy CMP0074.

    +
    +

    New in version 3.12.

    +
    +

    Specifically, search paths specified by the following variables, in order:

    +
      +
    1. <PackageName>_ROOT CMake variable, +where <PackageName> is the case-preserved package name.

    2. +
    3. <PACKAGENAME>_ROOT CMake variable, +where <PACKAGENAME> is the upper-cased package name. +See policy CMP0144.

      +
      +

      New in version 3.27.

      +
      +
    4. +
    5. <PackageName>_ROOT environment variable, +where <PackageName> is the case-preserved package name.

    6. +
    7. <PACKAGENAME>_ROOT environment variable, +where <PACKAGENAME> is the upper-cased package name. +See policy CMP0144.

      +
      +

      New in version 3.27.

      +
      +
    8. +
    +

    The package root variables are maintained as a stack, so if called from +nested find modules or config packages, root paths from the parent's find +module or config package will be searched after paths from the current +module or package. In other words, the search order would be +<CurrentPackage>_ROOT, ENV{<CurrentPackage>_ROOT}, +<ParentPackage>_ROOT, ENV{<ParentPackage>_ROOT}, etc. +This can be skipped if NO_PACKAGE_ROOT_PATH is passed or by setting +the CMAKE_FIND_USE_PACKAGE_ROOT_PATH to FALSE.

    + +
  2. +
  3. Search paths specified in cmake-specific cache variables. +These are intended to be used on the command line with a -DVAR=value. +The values are interpreted as semicolon-separated lists. +This can be skipped if NO_CMAKE_PATH is passed or by setting the +CMAKE_FIND_USE_CMAKE_PATH to FALSE.

    + +
  4. +
  5. Search paths specified in cmake-specific environment variables. +These are intended to be set in the user's shell configuration, +and therefore use the host's native path separator +(; on Windows and : on UNIX). +This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed or +by setting the CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH to FALSE.

    + +
  6. +
  7. Search the paths specified by the HINTS option. +These should be paths computed by system introspection, such as a +hint provided by the location of another item already found. +Hard-coded guesses should be specified with the PATHS option.

  8. +
  9. Search the standard system environment variables. +This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is passed or by +setting the CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH to FALSE.

    +
      +
    • The directories in LIB +and PATH.

    • +
    • On Windows hosts: +<prefix>/lib/<arch> if CMAKE_LIBRARY_ARCHITECTURE +is set, and <prefix>/lib for each <prefix>/[s]bin in PATH, and +<entry>/lib for other entries in PATH.

    • +
    +
  10. +
  11. Search cmake variables defined in the Platform files +for the current system. The searching of CMAKE_INSTALL_PREFIX and +CMAKE_STAGING_PREFIX can be +skipped if NO_CMAKE_INSTALL_PREFIX is passed or by setting the +CMAKE_FIND_USE_INSTALL_PREFIX to FALSE. All these locations +can be skipped if NO_CMAKE_SYSTEM_PATH is passed or by setting the +CMAKE_FIND_USE_CMAKE_SYSTEM_PATH to FALSE.

    + +

    The platform paths that these variables contain are locations that +typically include installed software. An example being /usr/local for +UNIX based platforms.

    +
  12. +
  13. Search the paths specified by the PATHS option +or in the short-hand version of the command. +These are typically hard-coded guesses.

  14. +
+

The CMAKE_IGNORE_PATH, CMAKE_IGNORE_PREFIX_PATH, +CMAKE_SYSTEM_IGNORE_PATH and +CMAKE_SYSTEM_IGNORE_PREFIX_PATH variables can also cause some +of the above locations to be ignored.

+
+

New in version 3.16: Added CMAKE_FIND_USE_<CATEGORY>_PATH variables to globally disable +various search locations.

+
+

On macOS the CMAKE_FIND_FRAMEWORK and +CMAKE_FIND_APPBUNDLE variables determine the order of +preference between Apple-style and unix-style package components.

+

The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more +directories to be prepended to all other search directories. This +effectively "re-roots" the entire search under given locations. +Paths which are descendants of the CMAKE_STAGING_PREFIX are excluded +from this re-rooting, because that variable is always a path on the host system. +By default the CMAKE_FIND_ROOT_PATH is empty.

+

The CMAKE_SYSROOT variable can also be used to specify exactly one +directory to use as a prefix. Setting CMAKE_SYSROOT also has other +effects. See the documentation for that variable for more.

+

These variables are especially useful when cross-compiling to +point to the root directory of the target environment and CMake will +search there too. By default at first the directories listed in +CMAKE_FIND_ROOT_PATH are searched, then the CMAKE_SYSROOT +directory is searched, and then the non-rooted directories will be +searched. The default behavior can be adjusted by setting +CMAKE_FIND_ROOT_PATH_MODE_LIBRARY. This behavior can be manually +overridden on a per-call basis using options:

+
+
CMAKE_FIND_ROOT_PATH_BOTH

Search in the order described above.

+
+
NO_CMAKE_FIND_ROOT_PATH

Do not use the CMAKE_FIND_ROOT_PATH variable.

+
+
ONLY_CMAKE_FIND_ROOT_PATH

Search only the re-rooted directories and directories below +CMAKE_STAGING_PREFIX.

+
+
+

The default search order is designed to be most-specific to +least-specific for common use cases. +Projects may override the order by simply calling the command +multiple times and using the NO_* options:

+
find_library (<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)
+find_library (<VAR> NAMES name)
+

Once one of the calls succeeds the result variable will be set +and stored in the cache so that no call will search again.

+

When more than one value is given to the NAMES option this command by +default will consider one name at a time and search every directory +for it. The NAMES_PER_DIR option tells this command to consider one +directory at a time and search for all names in it.

+

Each library name given to the NAMES option is first considered +as a library file name and then considered with platform-specific +prefixes (e.g. lib) and suffixes (e.g. .so). Therefore one +may specify library file names such as libfoo.a directly. +This can be used to locate static libraries on UNIX-like systems.

+

If the library found is a framework, then <VAR> will be set to the full +path to the framework <fullPath>/A.framework. When a full path to a +framework is used as a library, CMake will use a -framework A, and a +-F<fullPath> to link the framework to the target.

+

If the CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX variable is set all +search paths will be tested as normal, with the suffix appended, and with +all matches of lib/ replaced with +lib${CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX}/. This variable overrides +the FIND_LIBRARY_USE_LIB32_PATHS, +FIND_LIBRARY_USE_LIBX32_PATHS, +and FIND_LIBRARY_USE_LIB64_PATHS global properties.

+

If the FIND_LIBRARY_USE_LIB32_PATHS global property is set +all search paths will be tested as normal, with 32/ appended, and +with all matches of lib/ replaced with lib32/. This property is +automatically set for the platforms that are known to need it if at +least one of the languages supported by the project() command +is enabled.

+

If the FIND_LIBRARY_USE_LIBX32_PATHS global property is set +all search paths will be tested as normal, with x32/ appended, and +with all matches of lib/ replaced with libx32/. This property is +automatically set for the platforms that are known to need it if at +least one of the languages supported by the project() command +is enabled.

+

If the FIND_LIBRARY_USE_LIB64_PATHS global property is set +all search paths will be tested as normal, with 64/ appended, and +with all matches of lib/ replaced with lib64/. This property is +automatically set for the platforms that are known to need it if at +least one of the languages supported by the project() command +is enabled.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_package.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_package.html new file mode 100644 index 0000000000000000000000000000000000000000..dfa70ec821da5e2f1361125cb5bc840d4bc4ddf9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_package.html @@ -0,0 +1,951 @@ + + + + + + + + + find_package — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

find_package

+ +
+

Note

+

The Using Dependencies Guide provides a high-level +introduction to this general topic. It provides a broader overview of +where the find_package() command fits into the bigger picture, +including its relationship to the FetchContent module. +The guide is recommended pre-reading before moving on to the details below.

+
+

Find a package (usually provided by something external to the project), +and load its package-specific details. Calls to this command can also +be intercepted by dependency providers.

+
+

Search Modes

+

The command has a few modes by which it searches for packages:

+
+
Module mode

In this mode, CMake searches for a file called Find<PackageName>.cmake, +looking first in the locations listed in the CMAKE_MODULE_PATH, +then among the Find Modules provided by the CMake installation. +If the file is found, it is read and processed by CMake. It is responsible +for finding the package, checking the version, and producing any needed +messages. Some Find modules provide limited or no support for versioning; +check the Find module's documentation.

+

The Find<PackageName>.cmake file is not typically provided by the +package itself. Rather, it is normally provided by something external to +the package, such as the operating system, CMake itself, or even the project +from which the find_package() command was called. Being externally +provided, Find Modules tend to be heuristic in nature and are +susceptible to becoming out-of-date. They typically search for certain +libraries, files and other package artifacts.

+

Module mode is only supported by the +basic command signature.

+
+
Config mode

In this mode, CMake searches for a file called +<lowercasePackageName>-config.cmake or <PackageName>Config.cmake. +It will also look for <lowercasePackageName>-config-version.cmake or +<PackageName>ConfigVersion.cmake if version details were specified +(see Config Mode Version Selection for an explanation of how these separate +version files are used).

+

In config mode, the command can be given a list of names to search for +as package names. The locations where CMake searches for the config and +version files is considerably more complicated than for Module mode +(see Config Mode Search Procedure).

+

The config and version files are typically installed as part of the +package, so they tend to be more reliable than Find modules. They usually +contain direct knowledge of the package contents, so no searching or +heuristics are needed within the config or version files themselves.

+

Config mode is supported by both the basic and +full command signatures.

+
+
FetchContent redirection mode
+

New in version 3.24: A call to find_package() can be redirected internally to a package +provided by the FetchContent module. To the caller, the behavior +will appear similar to Config mode, except that the search logic is +by-passed and the component information is not used. See +FetchContent_Declare() and FetchContent_MakeAvailable() +for further details.

+
+
+
+

When not redirected to a package provided by FetchContent, the +command arguments determine whether Module or Config mode is used. When the +basic signature is used, the command searches in Module mode first. +If the package is not found, the search falls back to Config mode. +A user may set the CMAKE_FIND_PACKAGE_PREFER_CONFIG variable +to true to reverse the priority and direct CMake to search using Config mode +first before falling back to Module mode. The basic signature can also be +forced to use only Module mode with a MODULE keyword. If the +full signature is used, the command only searches in Config mode.

+

Where possible, user code should generally look for packages using the +basic signature, since that allows the package to be found with any mode. +Project maintainers wishing to provide a config package should understand +the bigger picture, as explained in Full Signature and all subsequent +sections on this page.

+
+
+

Basic Signature

+
find_package(<PackageName> [version] [EXACT] [QUIET] [MODULE]
+             [REQUIRED] [[COMPONENTS] [components...]]
+             [OPTIONAL_COMPONENTS components...]
+             [REGISTRY_VIEW  (64|32|64_32|32_64|HOST|TARGET|BOTH)]
+             [GLOBAL]
+             [NO_POLICY_SCOPE]
+             [BYPASS_PROVIDER])
+
+
+

The basic signature is supported by both Module and Config modes. +The MODULE keyword implies that only Module mode can be used to find +the package, with no fallback to Config mode.

+

Regardless of the mode used, a <PackageName>_FOUND variable will be +set to indicate whether the package was found. When the package is found, +package-specific information may be provided through other variables and +Imported Targets documented by the package itself. The +QUIET option disables informational messages, including those indicating +that the package cannot be found if it is not REQUIRED. The REQUIRED +option stops processing with an error message if the package cannot be found.

+

A package-specific list of required components may be listed after the +COMPONENTS keyword. If any of these components are not able to be +satisfied, the package overall is considered to be not found. If the +REQUIRED option is also present, this is treated as a fatal error, +otherwise execution still continues. As a form of shorthand, if the +REQUIRED option is present, the COMPONENTS keyword can be omitted +and the required components can be listed directly after REQUIRED.

+

Additional optional components may be listed after +OPTIONAL_COMPONENTS. If these cannot be satisfied, the package overall +can still be considered found, as long as all required components are +satisfied.

+

The set of available components and their meaning are defined by the +target package. Formally, it is up to the target package how to +interpret the component information given to it, but it should follow +the expectations stated above. For calls where no components are specified, +there is no single expected behavior and target packages should clearly +define what occurs in such cases. Common arrangements include assuming it +should find all components, no components or some well-defined subset of the +available components.

+
+

New in version 3.24: The REGISTRY_VIEW keyword specifies which registry views should be +queried. This keyword is only meaningful on Windows platforms and will +be ignored on all others. Formally, it is up to the target package how to +interpret the registry view information given to it.

+
+
+

New in version 3.24: Specifying the GLOBAL keyword will promote all imported targets to +a global scope in the importing project. Alternatively, this functionality +can be enabled by setting the CMAKE_FIND_PACKAGE_TARGETS_GLOBAL +variable.

+
+

The [version] argument requests a version with which the package found +should be compatible. There are two possible forms in which it may be +specified:

+
+
    +
  • A single version with the format major[.minor[.patch[.tweak]]], where +each component is a numeric value.

  • +
  • A version range with the format versionMin...[<]versionMax where +versionMin and versionMax have the same format and constraints +on components being integers as the single version. By default, both end +points are included. By specifying <, the upper end point will be +excluded. Version ranges are only supported with CMake 3.19 or later.

  • +
+
+

The EXACT option requests that the version be matched exactly. This option +is incompatible with the specification of a version range.

+

If no [version] and/or component list is given to a recursive invocation +inside a find-module, the corresponding arguments are forwarded +automatically from the outer call (including the EXACT flag for +[version]). Version support is currently provided only on a +package-by-package basis (see the Version Selection section below). +When a version range is specified but the package is only designed to expect +a single version, the package will ignore the upper end point of the range and +only take the single version at the lower end of the range into account.

+

See the cmake_policy() command documentation for discussion +of the NO_POLICY_SCOPE option.

+
+

New in version 3.24: The BYPASS_PROVIDER keyword is only allowed when find_package() is +being called by a dependency provider. +It can be used by providers to call the built-in find_package() +implementation directly and prevent that call from being re-routed back to +itself. Future versions of CMake may detect attempts to use this keyword +from places other than a dependency provider and halt with a fatal error.

+
+
+
+

Full Signature

+
find_package(<PackageName> [version] [EXACT] [QUIET]
+             [REQUIRED] [[COMPONENTS] [components...]]
+             [OPTIONAL_COMPONENTS components...]
+             [CONFIG|NO_MODULE]
+             [GLOBAL]
+             [NO_POLICY_SCOPE]
+             [BYPASS_PROVIDER]
+             [NAMES name1 [name2 ...]]
+             [CONFIGS config1 [config2 ...]]
+             [HINTS path1 [path2 ... ]]
+             [PATHS path1 [path2 ... ]]
+             [REGISTRY_VIEW  (64|32|64_32|32_64|HOST|TARGET|BOTH)]
+             [PATH_SUFFIXES suffix1 [suffix2 ...]]
+             [NO_DEFAULT_PATH]
+             [NO_PACKAGE_ROOT_PATH]
+             [NO_CMAKE_PATH]
+             [NO_CMAKE_ENVIRONMENT_PATH]
+             [NO_SYSTEM_ENVIRONMENT_PATH]
+             [NO_CMAKE_PACKAGE_REGISTRY]
+             [NO_CMAKE_BUILDS_PATH] # Deprecated; does nothing.
+             [NO_CMAKE_SYSTEM_PATH]
+             [NO_CMAKE_INSTALL_PREFIX]
+             [NO_CMAKE_SYSTEM_PACKAGE_REGISTRY]
+             [CMAKE_FIND_ROOT_PATH_BOTH |
+              ONLY_CMAKE_FIND_ROOT_PATH |
+              NO_CMAKE_FIND_ROOT_PATH])
+
+
+

The CONFIG option, the synonymous NO_MODULE option, or the use +of options not specified in the basic signature all enforce pure Config +mode. In pure Config mode, the command skips Module mode search and +proceeds at once with Config mode search.

+

Config mode search attempts to locate a configuration file provided by the +package to be found. A cache entry called <PackageName>_DIR is created to +hold the directory containing the file. By default, the command searches for +a package with the name <PackageName>. If the NAMES option is given, +the names following it are used instead of <PackageName>. The names are +also considered when determining whether to redirect the call to a package +provided by FetchContent.

+

The command searches for a file called <PackageName>Config.cmake or +<lowercasePackageName>-config.cmake for each name specified. +A replacement set of possible configuration file names may be given +using the CONFIGS option. The Config Mode Search Procedure is specified below. +Once found, any version constraint is checked, +and if satisfied, the configuration file is read and processed by CMake. +Since the file is provided by the package it already knows the +location of package contents. The full path to the configuration file +is stored in the cmake variable <PackageName>_CONFIG.

+

All configuration files which have been considered by CMake while +searching for the package with an appropriate version are stored in the +<PackageName>_CONSIDERED_CONFIGS variable, and the associated versions +in the <PackageName>_CONSIDERED_VERSIONS variable.

+

If the package configuration file cannot be found CMake will generate +an error describing the problem unless the QUIET argument is +specified. If REQUIRED is specified and the package is not found a +fatal error is generated and the configure step stops executing. If +<PackageName>_DIR has been set to a directory not containing a +configuration file CMake will ignore it and search from scratch.

+

Package maintainers providing CMake package configuration files are +encouraged to name and install them such that the Config Mode Search Procedure +outlined below will find them without requiring use of additional options.

+
+
+

Config Mode Search Procedure

+
+

Note

+

When Config mode is used, this search procedure is applied regardless of +whether the full or basic +signature was given.

+
+
+

New in version 3.24: All calls to find_package() (even in Module mode) first look for a config +package file in the CMAKE_FIND_PACKAGE_REDIRECTS_DIR directory. +The FetchContent module, or even the project itself, may write files +to that location to redirect find_package() calls to content already +provided by the project. If no config package file is found in that location, +the search proceeds with the logic described below.

+
+

CMake constructs a set of possible installation prefixes for the +package. Under each prefix several directories are searched for a +configuration file. The tables below show the directories searched. +Each entry is meant for installation trees following Windows (W), UNIX +(U), or Apple (A) conventions:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Entry

Convention

<prefix>/

W

<prefix>/(cmake|CMake)/

W

<prefix>/<name>*/

W

<prefix>/<name>*/(cmake|CMake)/

W

<prefix>/<name>*/(cmake|CMake)/<name>*/ [1]

W

<prefix>/(lib/<arch>|lib*|share)/cmake/<name>*/

U

<prefix>/(lib/<arch>|lib*|share)/<name>*/

U

<prefix>/(lib/<arch>|lib*|share)/<name>*/(cmake|CMake)/

U

<prefix>/<name>*/(lib/<arch>|lib*|share)/cmake/<name>*/

W/U

<prefix>/<name>*/(lib/<arch>|lib*|share)/<name>*/

W/U

<prefix>/<name>*/(lib/<arch>|lib*|share)/<name>*/(cmake|CMake)/

W/U

+ +

On systems supporting macOS FRAMEWORK and BUNDLE, the +following directories are searched for Frameworks or Application Bundles +containing a configuration file:

+ + + + + + + + + + + + + + + + + + + + + + + + + + +

Entry

Convention

<prefix>/<name>.framework/Resources/

A

<prefix>/<name>.framework/Resources/CMake/

A

<prefix>/<name>.framework/Versions/*/Resources/

A

<prefix>/<name>.framework/Versions/*/Resources/CMake/

A

<prefix>/<name>.app/Contents/Resources/

A

<prefix>/<name>.app/Contents/Resources/CMake/

A

+

In all cases the <name> is treated as case-insensitive and corresponds +to any of the names specified (<PackageName> or names given by NAMES).

+

Paths with lib/<arch> are enabled if the +CMAKE_LIBRARY_ARCHITECTURE variable is set. lib* includes one +or more of the values lib64, lib32, libx32 or lib (searched in +that order).

+ +
+

Changed in version 3.24: On Windows platform, it is possible to include registry queries as part +of the directories specified through HINTS and PATHS keywords, using +a dedicated syntax. Such specifications +will be ignored on all other platforms.

+
+
+

New in version 3.24: REGISTRY_VIEW can be specified to manage Windows registry queries +specified as part of PATHS and HINTS.

+
+

Specify which registry views must be queried. This option is only meaningful +on Windows platforms and will be ignored on other ones. When not +specified, the TARGET view is used when the +CMP0134 policy is NEW. Refer to CMP0134 for the +default view when the policy is OLD.

+
+
64

Query the 64-bit registry. On 32-bit Windows, it always returns the string +/REGISTRY-NOTFOUND.

+
+
32

Query the 32-bit registry.

+
+
64_32

Query both views (64 and 32) and generate a path for each.

+
+
32_64

Query both views (32 and 64) and generate a path for each.

+
+
HOST

Query the registry matching the architecture of the host: 64 on 64-bit +Windows and 32 on 32-bit Windows.

+
+
TARGET

Query the registry matching the architecture specified by the +CMAKE_SIZEOF_VOID_P variable. If not defined, fall back to +HOST view.

+
+
BOTH

Query both views (32 and 64). The order depends on the following +rules: If the CMAKE_SIZEOF_VOID_P variable is defined, use the +following view depending on the content of this variable:

+
    +
  • 8: 64_32

  • +
  • 4: 32_64

  • +
+

If the CMAKE_SIZEOF_VOID_P variable is not defined, rely on the +architecture of the host:

+
    +
  • 64-bit: 64_32

  • +
  • 32-bit: 32

  • +
+
+
+

If PATH_SUFFIXES is specified, the suffixes are appended to each +(W) or (U) directory entry one-by-one.

+

This set of directories is intended to work in cooperation with +projects that provide configuration files in their installation trees. +Directories above marked with (W) are intended for installations on +Windows where the prefix may point at the top of an application's +installation directory. Those marked with (U) are intended for +installations on UNIX platforms where the prefix is shared by multiple +packages. This is merely a convention, so all (W) and (U) directories +are still searched on all platforms. Directories marked with (A) are +intended for installations on Apple platforms. The +CMAKE_FIND_FRAMEWORK and CMAKE_FIND_APPBUNDLE +variables determine the order of preference.

+

The set of installation prefixes is constructed using the following +steps. If NO_DEFAULT_PATH is specified all NO_* options are +enabled.

+
    +
  1. Search prefixes unique to the current <PackageName> being found. +See policy CMP0074.

    +
    +

    New in version 3.12.

    +
    +

    Specifically, search prefixes specified by the following variables, +in order:

    +
      +
    1. <PackageName>_ROOT CMake variable, +where <PackageName> is the case-preserved package name.

    2. +
    3. <PACKAGENAME>_ROOT CMake variable, +where <PACKAGENAME> is the upper-cased package name. +See policy CMP0144.

      +
      +

      New in version 3.27.

      +
      +
    4. +
    5. <PackageName>_ROOT environment variable, +where <PackageName> is the case-preserved package name.

    6. +
    7. <PACKAGENAME>_ROOT environment variable, +where <PACKAGENAME> is the upper-cased package name. +See policy CMP0144.

      +
      +

      New in version 3.27.

      +
      +
    8. +
    +

    The package root variables are maintained as a stack so if +called from within a find module, root paths from the parent's find +module will also be searched after paths for the current package. +This can be skipped if NO_PACKAGE_ROOT_PATH is passed or by setting +the CMAKE_FIND_USE_PACKAGE_ROOT_PATH to FALSE.

    +
  2. +
  3. Search paths specified in cmake-specific cache variables. These +are intended to be used on the command line with a -DVAR=VALUE. +The values are interpreted as semicolon-separated lists. +This can be skipped if NO_CMAKE_PATH is passed or by setting the +CMAKE_FIND_USE_CMAKE_PATH to FALSE:

    + +
  4. +
  5. Search paths specified in cmake-specific environment variables. +These are intended to be set in the user's shell configuration, +and therefore use the host's native path separator +(; on Windows and : on UNIX). +This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed or by setting +the CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH to FALSE:

    + +
  6. +
  7. Search paths specified by the HINTS option. These should be paths +computed by system introspection, such as a hint provided by the +location of another item already found. Hard-coded guesses should +be specified with the PATHS option.

  8. +
  9. Search the standard system environment variables. This can be +skipped if NO_SYSTEM_ENVIRONMENT_PATH is passed or by setting the +CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH to FALSE. Path entries +ending in /bin or /sbin are automatically converted to their +parent directories:

    +
      +
    • PATH

    • +
    +
  10. +
  11. Search paths stored in the CMake User Package Registry. +This can be skipped if NO_CMAKE_PACKAGE_REGISTRY is passed or by +setting the variable CMAKE_FIND_USE_PACKAGE_REGISTRY +to FALSE or the deprecated variable +CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY to TRUE.

    +

    See the cmake-packages(7) manual for details on the user +package registry.

    +
  12. +
  13. Search cmake variables defined in the Platform files for the +current system. The searching of CMAKE_INSTALL_PREFIX and +CMAKE_STAGING_PREFIX can be +skipped if NO_CMAKE_INSTALL_PREFIX is passed or by setting the +CMAKE_FIND_USE_INSTALL_PREFIX to FALSE. All these locations +can be skipped if NO_CMAKE_SYSTEM_PATH is passed or by setting the +CMAKE_FIND_USE_CMAKE_SYSTEM_PATH to FALSE:

    + +

    The platform paths that these variables contain are locations that +typically include installed software. An example being /usr/local for +UNIX based platforms.

    +
  14. +
  15. Search paths stored in the CMake System Package Registry. +This can be skipped if NO_CMAKE_SYSTEM_PACKAGE_REGISTRY is passed +or by setting the CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY +variable to FALSE or the deprecated variable +CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY to TRUE.

    +

    See the cmake-packages(7) manual for details on the system +package registry.

    +
  16. +
  17. Search paths specified by the PATHS option. These are typically +hard-coded guesses.

  18. +
+

The CMAKE_IGNORE_PATH, CMAKE_IGNORE_PREFIX_PATH, +CMAKE_SYSTEM_IGNORE_PATH and +CMAKE_SYSTEM_IGNORE_PREFIX_PATH variables can also cause some +of the above locations to be ignored.

+
+

New in version 3.16: Added the CMAKE_FIND_USE_<CATEGORY> variables to globally disable +various search locations.

+
+

The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more +directories to be prepended to all other search directories. This +effectively "re-roots" the entire search under given locations. +Paths which are descendants of the CMAKE_STAGING_PREFIX are excluded +from this re-rooting, because that variable is always a path on the host system. +By default the CMAKE_FIND_ROOT_PATH is empty.

+

The CMAKE_SYSROOT variable can also be used to specify exactly one +directory to use as a prefix. Setting CMAKE_SYSROOT also has other +effects. See the documentation for that variable for more.

+

These variables are especially useful when cross-compiling to +point to the root directory of the target environment and CMake will +search there too. By default at first the directories listed in +CMAKE_FIND_ROOT_PATH are searched, then the CMAKE_SYSROOT +directory is searched, and then the non-rooted directories will be +searched. The default behavior can be adjusted by setting +CMAKE_FIND_ROOT_PATH_MODE_PACKAGE. This behavior can be manually +overridden on a per-call basis using options:

+
+
CMAKE_FIND_ROOT_PATH_BOTH

Search in the order described above.

+
+
NO_CMAKE_FIND_ROOT_PATH

Do not use the CMAKE_FIND_ROOT_PATH variable.

+
+
ONLY_CMAKE_FIND_ROOT_PATH

Search only the re-rooted directories and directories below +CMAKE_STAGING_PREFIX.

+
+
+

The default search order is designed to be most-specific to +least-specific for common use cases. +Projects may override the order by simply calling the command +multiple times and using the NO_* options:

+
find_package (<PackageName> PATHS paths... NO_DEFAULT_PATH)
+find_package (<PackageName>)
+

Once one of the calls succeeds the result variable will be set +and stored in the cache so that no call will search again.

+

By default the value stored in the result variable will be the path at +which the file is found. The CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS +variable may be set to TRUE before calling find_package in order +to resolve symbolic links and store the real path to the file.

+

Every non-REQUIRED find_package call can be disabled or made REQUIRED:

+ +

Setting both variables to TRUE simultaneously is an error.

+
+
+

Config Mode Version Selection

+
+

Note

+

When Config mode is used, this version selection process is applied +regardless of whether the full or +basic signature was given.

+
+

When the [version] argument is given, Config mode will only find a +version of the package that claims compatibility with the requested +version (see format specification). If the +EXACT option is given, only a version of the package claiming an exact match +of the requested version may be found. CMake does not establish any +convention for the meaning of version numbers. Package version +numbers are checked by "version" files provided by the packages themselves +or by FetchContent. For a candidate package configuration file +<config-file>.cmake the corresponding version file is located next +to it and named either <config-file>-version.cmake or +<config-file>Version.cmake. If no such version file is available +then the configuration file is assumed to not be compatible with any +requested version. A basic version file containing generic version +matching code can be created using the +CMakePackageConfigHelpers module. When a version file +is found it is loaded to check the requested version number. The +version file is loaded in a nested scope in which the following +variables have been defined:

+
+
PACKAGE_FIND_NAME

The <PackageName>

+
+
PACKAGE_FIND_VERSION

Full requested version string

+
+
PACKAGE_FIND_VERSION_MAJOR

Major version if requested, else 0

+
+
PACKAGE_FIND_VERSION_MINOR

Minor version if requested, else 0

+
+
PACKAGE_FIND_VERSION_PATCH

Patch version if requested, else 0

+
+
PACKAGE_FIND_VERSION_TWEAK

Tweak version if requested, else 0

+
+
PACKAGE_FIND_VERSION_COUNT

Number of version components, 0 to 4

+
+
+

When a version range is specified, the above version variables will hold +values based on the lower end of the version range. This is to preserve +compatibility with packages that have not been implemented to expect version +ranges. In addition, the version range will be described by the following +variables:

+
+
PACKAGE_FIND_VERSION_RANGE

Full requested version range string

+
+
PACKAGE_FIND_VERSION_RANGE_MIN

This specifies whether the lower end point of the version range should be +included or excluded. Currently, the only supported value for this variable +is INCLUDE.

+
+
PACKAGE_FIND_VERSION_RANGE_MAX

This specifies whether the upper end point of the version range should be +included or excluded. The supported values for this variable are +INCLUDE and EXCLUDE.

+
+
PACKAGE_FIND_VERSION_MIN

Full requested version string of the lower end point of the range

+
+
PACKAGE_FIND_VERSION_MIN_MAJOR

Major version of the lower end point if requested, else 0

+
+
PACKAGE_FIND_VERSION_MIN_MINOR

Minor version of the lower end point if requested, else 0

+
+
PACKAGE_FIND_VERSION_MIN_PATCH

Patch version of the lower end point if requested, else 0

+
+
PACKAGE_FIND_VERSION_MIN_TWEAK

Tweak version of the lower end point if requested, else 0

+
+
PACKAGE_FIND_VERSION_MIN_COUNT

Number of version components of the lower end point, 0 to 4

+
+
PACKAGE_FIND_VERSION_MAX

Full requested version string of the upper end point of the range

+
+
PACKAGE_FIND_VERSION_MAX_MAJOR

Major version of the upper end point if requested, else 0

+
+
PACKAGE_FIND_VERSION_MAX_MINOR

Minor version of the upper end point if requested, else 0

+
+
PACKAGE_FIND_VERSION_MAX_PATCH

Patch version of the upper end point if requested, else 0

+
+
PACKAGE_FIND_VERSION_MAX_TWEAK

Tweak version of the upper end point if requested, else 0

+
+
PACKAGE_FIND_VERSION_MAX_COUNT

Number of version components of the upper end point, 0 to 4

+
+
+

Regardless of whether a single version or a version range is specified, the +variable PACKAGE_FIND_VERSION_COMPLETE will be defined and will hold +the full requested version string as specified.

+

The version file checks whether it satisfies the requested version and +sets these variables:

+
+
PACKAGE_VERSION

Full provided version string

+
+
PACKAGE_VERSION_EXACT

True if version is exact match

+
+
PACKAGE_VERSION_COMPATIBLE

True if version is compatible

+
+
PACKAGE_VERSION_UNSUITABLE

True if unsuitable as any version

+
+
+

These variables are checked by the find_package command to determine +whether the configuration file provides an acceptable version. They +are not available after the find_package call returns. If the version +is acceptable the following variables are set:

+
+
<PackageName>_VERSION

Full provided version string

+
+
<PackageName>_VERSION_MAJOR

Major version if provided, else 0

+
+
<PackageName>_VERSION_MINOR

Minor version if provided, else 0

+
+
<PackageName>_VERSION_PATCH

Patch version if provided, else 0

+
+
<PackageName>_VERSION_TWEAK

Tweak version if provided, else 0

+
+
<PackageName>_VERSION_COUNT

Number of version components, 0 to 4

+
+
+

and the corresponding package configuration file is loaded. +When multiple package configuration files are available whose version files +claim compatibility with the version requested it is unspecified which +one is chosen: unless the variable CMAKE_FIND_PACKAGE_SORT_ORDER +is set no attempt is made to choose a highest or closest version number.

+

To control the order in which find_package checks for compatibility use +the two variables CMAKE_FIND_PACKAGE_SORT_ORDER and +CMAKE_FIND_PACKAGE_SORT_DIRECTION. +For instance in order to select the highest version one can set

+
SET(CMAKE_FIND_PACKAGE_SORT_ORDER NATURAL)
+SET(CMAKE_FIND_PACKAGE_SORT_DIRECTION DEC)
+
+
+

before calling find_package.

+
+
+

Package File Interface Variables

+

When loading a find module or package configuration file find_package +defines variables to provide information about the call arguments (and +restores their original state before returning):

+
+
CMAKE_FIND_PACKAGE_NAME

The <PackageName> which is searched for

+
+
<PackageName>_FIND_REQUIRED

True if REQUIRED option was given

+
+
<PackageName>_FIND_QUIETLY

True if QUIET option was given

+
+
<PackageName>_FIND_REGISTRY_VIEW

The requested view if REGISTRY_VIEW option was given

+
+
<PackageName>_FIND_VERSION

Full requested version string

+
+
<PackageName>_FIND_VERSION_MAJOR

Major version if requested, else 0

+
+
<PackageName>_FIND_VERSION_MINOR

Minor version if requested, else 0

+
+
<PackageName>_FIND_VERSION_PATCH

Patch version if requested, else 0

+
+
<PackageName>_FIND_VERSION_TWEAK

Tweak version if requested, else 0

+
+
<PackageName>_FIND_VERSION_COUNT

Number of version components, 0 to 4

+
+
<PackageName>_FIND_VERSION_EXACT

True if EXACT option was given

+
+
<PackageName>_FIND_COMPONENTS

List of specified components (required and optional)

+
+
<PackageName>_FIND_REQUIRED_<c>

True if component <c> is required, +false if component <c> is optional

+
+
+

When a version range is specified, the above version variables will hold +values based on the lower end of the version range. This is to preserve +compatibility with packages that have not been implemented to expect version +ranges. In addition, the version range will be described by the following +variables:

+
+
<PackageName>_FIND_VERSION_RANGE

Full requested version range string

+
+
<PackageName>_FIND_VERSION_RANGE_MIN

This specifies whether the lower end point of the version range is +included or excluded. Currently, INCLUDE is the only supported value.

+
+
<PackageName>_FIND_VERSION_RANGE_MAX

This specifies whether the upper end point of the version range is +included or excluded. The possible values for this variable are +INCLUDE or EXCLUDE.

+
+
<PackageName>_FIND_VERSION_MIN

Full requested version string of the lower end point of the range

+
+
<PackageName>_FIND_VERSION_MIN_MAJOR

Major version of the lower end point if requested, else 0

+
+
<PackageName>_FIND_VERSION_MIN_MINOR

Minor version of the lower end point if requested, else 0

+
+
<PackageName>_FIND_VERSION_MIN_PATCH

Patch version of the lower end point if requested, else 0

+
+
<PackageName>_FIND_VERSION_MIN_TWEAK

Tweak version of the lower end point if requested, else 0

+
+
<PackageName>_FIND_VERSION_MIN_COUNT

Number of version components of the lower end point, 0 to 4

+
+
<PackageName>_FIND_VERSION_MAX

Full requested version string of the upper end point of the range

+
+
<PackageName>_FIND_VERSION_MAX_MAJOR

Major version of the upper end point if requested, else 0

+
+
<PackageName>_FIND_VERSION_MAX_MINOR

Minor version of the upper end point if requested, else 0

+
+
<PackageName>_FIND_VERSION_MAX_PATCH

Patch version of the upper end point if requested, else 0

+
+
<PackageName>_FIND_VERSION_MAX_TWEAK

Tweak version of the upper end point if requested, else 0

+
+
<PackageName>_FIND_VERSION_MAX_COUNT

Number of version components of the upper end point, 0 to 4

+
+
+

Regardless of whether a single version or a version range is specified, the +variable <PackageName>_FIND_VERSION_COMPLETE will be defined and will hold +the full requested version string as specified.

+

In Module mode the loaded find module is responsible to honor the +request detailed by these variables; see the find module for details. +In Config mode find_package handles REQUIRED, QUIET, and +[version] options automatically but leaves it to the package +configuration file to handle components in a way that makes sense +for the package. The package configuration file may set +<PackageName>_FOUND to false to tell find_package that component +requirements are not satisfied.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_path.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_path.html new file mode 100644 index 0000000000000000000000000000000000000000..8ee5d8106c69f8bf7de8c5ae55a7492f7005e0f5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_path.html @@ -0,0 +1,437 @@ + + + + + + + + + find_path — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

find_path

+

A short-hand signature is:

+
find_path (<VAR> name1 [path1 path2 ...])
+

The general signature is:

+
find_path (
+          <VAR>
+          name | NAMES name1 [name2 ...]
+          [HINTS [path | ENV var]... ]
+          [PATHS [path | ENV var]... ]
+          [REGISTRY_VIEW (64|32|64_32|32_64|HOST|TARGET|BOTH)]
+          [PATH_SUFFIXES suffix1 [suffix2 ...]]
+          [VALIDATOR function]
+          [DOC "cache documentation string"]
+          [NO_CACHE]
+          [REQUIRED]
+          [NO_DEFAULT_PATH]
+          [NO_PACKAGE_ROOT_PATH]
+          [NO_CMAKE_PATH]
+          [NO_CMAKE_ENVIRONMENT_PATH]
+          [NO_SYSTEM_ENVIRONMENT_PATH]
+          [NO_CMAKE_SYSTEM_PATH]
+          [NO_CMAKE_INSTALL_PREFIX]
+          [CMAKE_FIND_ROOT_PATH_BOTH |
+           ONLY_CMAKE_FIND_ROOT_PATH |
+           NO_CMAKE_FIND_ROOT_PATH]
+         )
+

This command is used to find a directory containing the named file. +A cache entry, or a normal variable if NO_CACHE is specified, +named by <VAR> is created to store the result of this command. +If the file in a directory is found the result is stored in the variable +and the search will not be repeated unless the variable is cleared. +If nothing is found, the result will be <VAR>-NOTFOUND.

+

Options include:

+
+
NAMES

Specify one or more possible names for the file in a directory.

+

When using this to specify names with and without a version +suffix, we recommend specifying the unversioned name first +so that locally-built packages can be found before those +provided by distributions.

+
+
HINTS, PATHS

Specify directories to search in addition to the default locations. +The ENV var sub-option reads paths from a system environment +variable.

+
+

Changed in version 3.24: On Windows platform, it is possible to include registry queries as part +of the directories, using a dedicated syntax. +Such specifications will be ignored on all other platforms.

+
+
+
REGISTRY_VIEW
+

New in version 3.24.

+
+

Specify which registry views must be queried. This option is only meaningful +on Windows platforms and will be ignored on other ones. When not +specified, the TARGET view is used when the +CMP0134 policy is NEW. Refer to CMP0134 for the +default view when the policy is OLD.

+
+
64

Query the 64-bit registry. On 32-bit Windows, it always returns the string +/REGISTRY-NOTFOUND.

+
+
32

Query the 32-bit registry.

+
+
64_32

Query both views (64 and 32) and generate a path for each.

+
+
32_64

Query both views (32 and 64) and generate a path for each.

+
+
HOST

Query the registry matching the architecture of the host: 64 on 64-bit +Windows and 32 on 32-bit Windows.

+
+
TARGET

Query the registry matching the architecture specified by the +CMAKE_SIZEOF_VOID_P variable. If not defined, fall back to +HOST view.

+
+
BOTH

Query both views (32 and 64). The order depends on the following +rules: If the CMAKE_SIZEOF_VOID_P variable is defined, use the +following view depending on the content of this variable:

+
    +
  • 8: 64_32

  • +
  • 4: 32_64

  • +
+

If the CMAKE_SIZEOF_VOID_P variable is not defined, rely on the +architecture of the host:

+
    +
  • 64-bit: 64_32

  • +
  • 32-bit: 32

  • +
+
+
+
+
PATH_SUFFIXES

Specify additional subdirectories to check below each directory +location otherwise considered.

+
+
VALIDATOR
+

New in version 3.25.

+
+

Specify a function() to be called for each candidate item found +(a macro() cannot be provided, that will result in an error). +Two arguments will be passed to the validator function: the name of a +result variable, and the absolute path to the candidate item. The item +will be accepted and the search will end unless the function sets the +value in the result variable to false in the calling scope. The result +variable will hold a true value when the validator function is entered.

+
function(my_check validator_result_var item)
+  if(NOT item MATCHES ...)
+    set(${validator_result_var} FALSE PARENT_SCOPE)
+  endif()
+endfunction()
+
+find_path (result NAMES ... VALIDATOR my_check)
+

Note that if a cached result is used, the search is skipped and any +VALIDATOR is ignored. The cached result is not required to pass the +validation function.

+
+
DOC

Specify the documentation string for the <VAR> cache entry.

+
+
NO_CACHE
+

New in version 3.21.

+
+

The result of the search will be stored in a normal variable rather than +a cache entry.

+
+

Note

+

If the variable is already set before the call (as a normal or cache +variable) then the search will not occur.

+
+
+

Warning

+

This option should be used with caution because it can greatly increase +the cost of repeated configure steps.

+
+
+
REQUIRED
+

New in version 3.18.

+
+

Stop processing with an error message if nothing is found, otherwise +the search will be attempted again the next time find_path is invoked +with the same variable.

+
+
+

If NO_DEFAULT_PATH is specified, then no additional paths are +added to the search. +If NO_DEFAULT_PATH is not specified, the search process is as follows:

+
    +
  1. If called from within a find module or any other script loaded by a call to +find_package(<PackageName>), search prefixes unique to the +current package being found. See policy CMP0074.

    +
    +

    New in version 3.12.

    +
    +

    Specifically, search paths specified by the following variables, in order:

    +
      +
    1. <PackageName>_ROOT CMake variable, +where <PackageName> is the case-preserved package name.

    2. +
    3. <PACKAGENAME>_ROOT CMake variable, +where <PACKAGENAME> is the upper-cased package name. +See policy CMP0144.

      +
      +

      New in version 3.27.

      +
      +
    4. +
    5. <PackageName>_ROOT environment variable, +where <PackageName> is the case-preserved package name.

    6. +
    7. <PACKAGENAME>_ROOT environment variable, +where <PACKAGENAME> is the upper-cased package name. +See policy CMP0144.

      +
      +

      New in version 3.27.

      +
      +
    8. +
    +

    The package root variables are maintained as a stack, so if called from +nested find modules or config packages, root paths from the parent's find +module or config package will be searched after paths from the current +module or package. In other words, the search order would be +<CurrentPackage>_ROOT, ENV{<CurrentPackage>_ROOT}, +<ParentPackage>_ROOT, ENV{<ParentPackage>_ROOT}, etc. +This can be skipped if NO_PACKAGE_ROOT_PATH is passed or by setting +the CMAKE_FIND_USE_PACKAGE_ROOT_PATH to FALSE.

    + +
  2. +
  3. Search paths specified in cmake-specific cache variables. +These are intended to be used on the command line with a -DVAR=value. +The values are interpreted as semicolon-separated lists. +This can be skipped if NO_CMAKE_PATH is passed or by setting the +CMAKE_FIND_USE_CMAKE_PATH to FALSE.

    + +
  4. +
  5. Search paths specified in cmake-specific environment variables. +These are intended to be set in the user's shell configuration, +and therefore use the host's native path separator +(; on Windows and : on UNIX). +This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed or +by setting the CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH to FALSE.

    + +
  6. +
  7. Search the paths specified by the HINTS option. +These should be paths computed by system introspection, such as a +hint provided by the location of another item already found. +Hard-coded guesses should be specified with the PATHS option.

  8. +
  9. Search the standard system environment variables. +This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is passed or by +setting the CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH to FALSE.

    +
      +
    • The directories in INCLUDE +and PATH.

    • +
    • On Windows hosts: +<prefix>/include/<arch> if CMAKE_LIBRARY_ARCHITECTURE +is set, and <prefix>/include for each <prefix>/[s]bin in PATH, and +<entry>/include for other entries in PATH.

    • +
    +
  10. +
  11. Search cmake variables defined in the Platform files +for the current system. The searching of CMAKE_INSTALL_PREFIX and +CMAKE_STAGING_PREFIX can be +skipped if NO_CMAKE_INSTALL_PREFIX is passed or by setting the +CMAKE_FIND_USE_INSTALL_PREFIX to FALSE. All these locations +can be skipped if NO_CMAKE_SYSTEM_PATH is passed or by setting the +CMAKE_FIND_USE_CMAKE_SYSTEM_PATH to FALSE.

    + +

    The platform paths that these variables contain are locations that +typically include installed software. An example being /usr/local for +UNIX based platforms.

    +
  12. +
  13. Search the paths specified by the PATHS option +or in the short-hand version of the command. +These are typically hard-coded guesses.

  14. +
+

The CMAKE_IGNORE_PATH, CMAKE_IGNORE_PREFIX_PATH, +CMAKE_SYSTEM_IGNORE_PATH and +CMAKE_SYSTEM_IGNORE_PREFIX_PATH variables can also cause some +of the above locations to be ignored.

+
+

New in version 3.16: Added CMAKE_FIND_USE_<CATEGORY>_PATH variables to globally disable +various search locations.

+
+

On macOS the CMAKE_FIND_FRAMEWORK and +CMAKE_FIND_APPBUNDLE variables determine the order of +preference between Apple-style and unix-style package components.

+

The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more +directories to be prepended to all other search directories. This +effectively "re-roots" the entire search under given locations. +Paths which are descendants of the CMAKE_STAGING_PREFIX are excluded +from this re-rooting, because that variable is always a path on the host system. +By default the CMAKE_FIND_ROOT_PATH is empty.

+

The CMAKE_SYSROOT variable can also be used to specify exactly one +directory to use as a prefix. Setting CMAKE_SYSROOT also has other +effects. See the documentation for that variable for more.

+

These variables are especially useful when cross-compiling to +point to the root directory of the target environment and CMake will +search there too. By default at first the directories listed in +CMAKE_FIND_ROOT_PATH are searched, then the CMAKE_SYSROOT +directory is searched, and then the non-rooted directories will be +searched. The default behavior can be adjusted by setting +CMAKE_FIND_ROOT_PATH_MODE_INCLUDE. This behavior can be manually +overridden on a per-call basis using options:

+
+
CMAKE_FIND_ROOT_PATH_BOTH

Search in the order described above.

+
+
NO_CMAKE_FIND_ROOT_PATH

Do not use the CMAKE_FIND_ROOT_PATH variable.

+
+
ONLY_CMAKE_FIND_ROOT_PATH

Search only the re-rooted directories and directories below +CMAKE_STAGING_PREFIX.

+
+
+

The default search order is designed to be most-specific to +least-specific for common use cases. +Projects may override the order by simply calling the command +multiple times and using the NO_* options:

+
find_path (<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)
+find_path (<VAR> NAMES name)
+

Once one of the calls succeeds the result variable will be set +and stored in the cache so that no call will search again.

+

When searching for frameworks, if the file is specified as A/b.h, then +the framework search will look for A.framework/Headers/b.h. If that +is found the path will be set to the path to the framework. CMake +will convert this to the correct -F option to include the file.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_program.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_program.html new file mode 100644 index 0000000000000000000000000000000000000000..a1b3caf253ecdd1ff38a02f372c161c067582756 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/find_program.html @@ -0,0 +1,429 @@ + + + + + + + + + find_program — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

find_program

+

A short-hand signature is:

+
find_program (<VAR> name1 [path1 path2 ...])
+

The general signature is:

+
find_program (
+          <VAR>
+          name | NAMES name1 [name2 ...] [NAMES_PER_DIR]
+          [HINTS [path | ENV var]... ]
+          [PATHS [path | ENV var]... ]
+          [REGISTRY_VIEW (64|32|64_32|32_64|HOST|TARGET|BOTH)]
+          [PATH_SUFFIXES suffix1 [suffix2 ...]]
+          [VALIDATOR function]
+          [DOC "cache documentation string"]
+          [NO_CACHE]
+          [REQUIRED]
+          [NO_DEFAULT_PATH]
+          [NO_PACKAGE_ROOT_PATH]
+          [NO_CMAKE_PATH]
+          [NO_CMAKE_ENVIRONMENT_PATH]
+          [NO_SYSTEM_ENVIRONMENT_PATH]
+          [NO_CMAKE_SYSTEM_PATH]
+          [NO_CMAKE_INSTALL_PREFIX]
+          [CMAKE_FIND_ROOT_PATH_BOTH |
+           ONLY_CMAKE_FIND_ROOT_PATH |
+           NO_CMAKE_FIND_ROOT_PATH]
+         )
+

This command is used to find a program. +A cache entry, or a normal variable if NO_CACHE is specified, +named by <VAR> is created to store the result of this command. +If the program is found the result is stored in the variable +and the search will not be repeated unless the variable is cleared. +If nothing is found, the result will be <VAR>-NOTFOUND.

+

Options include:

+
+
NAMES

Specify one or more possible names for the program.

+

When using this to specify names with and without a version +suffix, we recommend specifying the unversioned name first +so that locally-built packages can be found before those +provided by distributions.

+
+
HINTS, PATHS

Specify directories to search in addition to the default locations. +The ENV var sub-option reads paths from a system environment +variable.

+
+

Changed in version 3.24: On Windows platform, it is possible to include registry queries as part +of the directories, using a dedicated syntax. +Such specifications will be ignored on all other platforms.

+
+
+
REGISTRY_VIEW
+

New in version 3.24.

+
+

Specify which registry views must be queried. This option is only meaningful +on Windows platforms and will be ignored on other ones. When not +specified, the BOTH view is used when the +CMP0134 policy is NEW. Refer to CMP0134 for the +default view when the policy is OLD.

+
+
64

Query the 64-bit registry. On 32-bit Windows, it always returns the string +/REGISTRY-NOTFOUND.

+
+
32

Query the 32-bit registry.

+
+
64_32

Query both views (64 and 32) and generate a path for each.

+
+
32_64

Query both views (32 and 64) and generate a path for each.

+
+
HOST

Query the registry matching the architecture of the host: 64 on 64-bit +Windows and 32 on 32-bit Windows.

+
+
TARGET

Query the registry matching the architecture specified by the +CMAKE_SIZEOF_VOID_P variable. If not defined, fall back to +HOST view.

+
+
BOTH

Query both views (32 and 64). The order depends on the following +rules: If the CMAKE_SIZEOF_VOID_P variable is defined, use the +following view depending on the content of this variable:

+
    +
  • 8: 64_32

  • +
  • 4: 32_64

  • +
+

If the CMAKE_SIZEOF_VOID_P variable is not defined, rely on the +architecture of the host:

+
    +
  • 64-bit: 64_32

  • +
  • 32-bit: 32

  • +
+
+
+
+
PATH_SUFFIXES

Specify additional subdirectories to check below each directory +location otherwise considered.

+
+
VALIDATOR
+

New in version 3.25.

+
+

Specify a function() to be called for each candidate item found +(a macro() cannot be provided, that will result in an error). +Two arguments will be passed to the validator function: the name of a +result variable, and the absolute path to the candidate item. The item +will be accepted and the search will end unless the function sets the +value in the result variable to false in the calling scope. The result +variable will hold a true value when the validator function is entered.

+
function(my_check validator_result_var item)
+  if(NOT item MATCHES ...)
+    set(${validator_result_var} FALSE PARENT_SCOPE)
+  endif()
+endfunction()
+
+find_program (result NAMES ... VALIDATOR my_check)
+

Note that if a cached result is used, the search is skipped and any +VALIDATOR is ignored. The cached result is not required to pass the +validation function.

+
+
DOC

Specify the documentation string for the <VAR> cache entry.

+
+
NO_CACHE
+

New in version 3.21.

+
+

The result of the search will be stored in a normal variable rather than +a cache entry.

+
+

Note

+

If the variable is already set before the call (as a normal or cache +variable) then the search will not occur.

+
+
+

Warning

+

This option should be used with caution because it can greatly increase +the cost of repeated configure steps.

+
+
+
REQUIRED
+

New in version 3.18.

+
+

Stop processing with an error message if nothing is found, otherwise +the search will be attempted again the next time find_program is invoked +with the same variable.

+
+
+

If NO_DEFAULT_PATH is specified, then no additional paths are +added to the search. +If NO_DEFAULT_PATH is not specified, the search process is as follows:

+
    +
  1. If called from within a find module or any other script loaded by a call to +find_package(<PackageName>), search prefixes unique to the +current package being found. See policy CMP0074.

    +
    +

    New in version 3.12.

    +
    +

    Specifically, search paths specified by the following variables, in order:

    +
      +
    1. <PackageName>_ROOT CMake variable, +where <PackageName> is the case-preserved package name.

    2. +
    3. <PACKAGENAME>_ROOT CMake variable, +where <PACKAGENAME> is the upper-cased package name. +See policy CMP0144.

      +
      +

      New in version 3.27.

      +
      +
    4. +
    5. <PackageName>_ROOT environment variable, +where <PackageName> is the case-preserved package name.

    6. +
    7. <PACKAGENAME>_ROOT environment variable, +where <PACKAGENAME> is the upper-cased package name. +See policy CMP0144.

      +
      +

      New in version 3.27.

      +
      +
    8. +
    +

    The package root variables are maintained as a stack, so if called from +nested find modules or config packages, root paths from the parent's find +module or config package will be searched after paths from the current +module or package. In other words, the search order would be +<CurrentPackage>_ROOT, ENV{<CurrentPackage>_ROOT}, +<ParentPackage>_ROOT, ENV{<ParentPackage>_ROOT}, etc. +This can be skipped if NO_PACKAGE_ROOT_PATH is passed or by setting +the CMAKE_FIND_USE_PACKAGE_ROOT_PATH to FALSE.

    + +
  2. +
  3. Search paths specified in cmake-specific cache variables. +These are intended to be used on the command line with a -DVAR=value. +The values are interpreted as semicolon-separated lists. +This can be skipped if NO_CMAKE_PATH is passed or by setting the +CMAKE_FIND_USE_CMAKE_PATH to FALSE.

    + +
  4. +
  5. Search paths specified in cmake-specific environment variables. +These are intended to be set in the user's shell configuration, +and therefore use the host's native path separator +(; on Windows and : on UNIX). +This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed or +by setting the CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH to FALSE.

    + +
  6. +
  7. Search the paths specified by the HINTS option. +These should be paths computed by system introspection, such as a +hint provided by the location of another item already found. +Hard-coded guesses should be specified with the PATHS option.

  8. +
  9. Search the standard system environment variables. +This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is passed or by +setting the CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH to FALSE.

    +
      +
    • The directories in PATH itself.

    • +
    • On Windows hosts no extra search paths are included

    • +
    +
  10. +
  11. Search cmake variables defined in the Platform files +for the current system. The searching of CMAKE_INSTALL_PREFIX and +CMAKE_STAGING_PREFIX can be +skipped if NO_CMAKE_INSTALL_PREFIX is passed or by setting the +CMAKE_FIND_USE_INSTALL_PREFIX to FALSE. All these locations +can be skipped if NO_CMAKE_SYSTEM_PATH is passed or by setting the +CMAKE_FIND_USE_CMAKE_SYSTEM_PATH to FALSE.

    + +

    The platform paths that these variables contain are locations that +typically include installed software. An example being /usr/local for +UNIX based platforms.

    +
  12. +
  13. Search the paths specified by the PATHS option +or in the short-hand version of the command. +These are typically hard-coded guesses.

  14. +
+

The CMAKE_IGNORE_PATH, CMAKE_IGNORE_PREFIX_PATH, +CMAKE_SYSTEM_IGNORE_PATH and +CMAKE_SYSTEM_IGNORE_PREFIX_PATH variables can also cause some +of the above locations to be ignored.

+
+

New in version 3.16: Added CMAKE_FIND_USE_<CATEGORY>_PATH variables to globally disable +various search locations.

+
+

On macOS the CMAKE_FIND_FRAMEWORK and +CMAKE_FIND_APPBUNDLE variables determine the order of +preference between Apple-style and unix-style package components.

+

The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more +directories to be prepended to all other search directories. This +effectively "re-roots" the entire search under given locations. +Paths which are descendants of the CMAKE_STAGING_PREFIX are excluded +from this re-rooting, because that variable is always a path on the host system. +By default the CMAKE_FIND_ROOT_PATH is empty.

+

The CMAKE_SYSROOT variable can also be used to specify exactly one +directory to use as a prefix. Setting CMAKE_SYSROOT also has other +effects. See the documentation for that variable for more.

+

These variables are especially useful when cross-compiling to +point to the root directory of the target environment and CMake will +search there too. By default at first the directories listed in +CMAKE_FIND_ROOT_PATH are searched, then the CMAKE_SYSROOT +directory is searched, and then the non-rooted directories will be +searched. The default behavior can be adjusted by setting +CMAKE_FIND_ROOT_PATH_MODE_PROGRAM. This behavior can be manually +overridden on a per-call basis using options:

+
+
CMAKE_FIND_ROOT_PATH_BOTH

Search in the order described above.

+
+
NO_CMAKE_FIND_ROOT_PATH

Do not use the CMAKE_FIND_ROOT_PATH variable.

+
+
ONLY_CMAKE_FIND_ROOT_PATH

Search only the re-rooted directories and directories below +CMAKE_STAGING_PREFIX.

+
+
+

The default search order is designed to be most-specific to +least-specific for common use cases. +Projects may override the order by simply calling the command +multiple times and using the NO_* options:

+
find_program (<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)
+find_program (<VAR> NAMES name)
+

Once one of the calls succeeds the result variable will be set +and stored in the cache so that no call will search again.

+

When more than one value is given to the NAMES option this command by +default will consider one name at a time and search every directory +for it. The NAMES_PER_DIR option tells this command to consider one +directory at a time and search for all names in it.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/fltk_wrap_ui.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/fltk_wrap_ui.html new file mode 100644 index 0000000000000000000000000000000000000000..687119dc62849cac9bc93bf0504981a657114642 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/fltk_wrap_ui.html @@ -0,0 +1,147 @@ + + + + + + + + + fltk_wrap_ui — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

fltk_wrap_ui

+

Create FLTK user interfaces Wrappers.

+
fltk_wrap_ui(resultingLibraryName source1
+             source2 ... sourceN )
+
+
+

Produce .h and .cxx files for all the .fl and .fld files listed. The +resulting .h and .cxx files will be added to a variable named +resultingLibraryName_FLTK_UI_SRCS which should be added to your +library.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/foreach.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/foreach.html new file mode 100644 index 0000000000000000000000000000000000000000..55b4c6dc1b478afbba727b9f40d1af188b13a183 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/foreach.html @@ -0,0 +1,269 @@ + + + + + + + + + foreach — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

foreach

+

Evaluate a group of commands for each value in a list.

+
foreach(<loop_var> <items>)
+  <commands>
+endforeach()
+
+
+

where <items> is a list of items that are separated by +semicolon or whitespace. +All commands between foreach and the matching endforeach are recorded +without being invoked. Once the endforeach is evaluated, the recorded +list of commands is invoked once for each item in <items>. +At the beginning of each iteration the variable <loop_var> will be set +to the value of the current item.

+

The scope of <loop_var> is restricted to the loop scope. See policy +CMP0124 for details.

+

The commands break() and continue() provide means to +escape from the normal control flow.

+

Per legacy, the endforeach() command admits +an optional <loop_var> argument. +If used, it must be a verbatim +repeat of the argument of the opening +foreach command.

+
foreach(<loop_var> RANGE <stop>)
+
+
+

In this variant, foreach iterates over the numbers +0, 1, ... up to (and including) the nonnegative integer <stop>.

+
foreach(<loop_var> RANGE <start> <stop> [<step>])
+
+
+

In this variant, foreach iterates over the numbers from +<start> up to at most <stop> in steps of <step>. +If <step> is not specified, then the step size is 1. +The three arguments <start> <stop> <step> must +all be nonnegative integers, and <stop> must not be +smaller than <start>; otherwise you enter the danger zone +of undocumented behavior that may change in future releases.

+
foreach(<loop_var> IN [LISTS [<lists>]] [ITEMS [<items>]])
+
+
+

In this variant, <lists> is a whitespace or semicolon +separated list of list-valued variables. The foreach +command iterates over each item in each given list. +The <items> following the ITEMS keyword are processed +as in the first variant of the foreach command. +The forms LISTS A and ITEMS ${A} are +equivalent.

+

The following example shows how the LISTS option is +processed:

+
set(A 0;1)
+set(B 2 3)
+set(C "4 5")
+set(D 6;7 8)
+set(E "")
+foreach(X IN LISTS A B C D E)
+    message(STATUS "X=${X}")
+endforeach()
+
+
+

yields:

+
-- X=0
+-- X=1
+-- X=2
+-- X=3
+-- X=4 5
+-- X=6
+-- X=7
+-- X=8
+
+
+
foreach(<loop_var>... IN ZIP_LISTS <lists>)
+
+
+
+

New in version 3.17.

+
+

In this variant, <lists> is a whitespace or semicolon +separated list of list-valued variables. The foreach +command iterates over each list simultaneously setting the +iteration variables as follows:

+
    +
  • if the only loop_var given, then it sets a series of +loop_var_N variables to the current item from the +corresponding list;

  • +
  • if multiple variable names passed, their count should match +the lists variables count;

  • +
  • if any of the lists are shorter, the corresponding iteration +variable is not defined for the current iteration.

  • +
+
list(APPEND English one two three four)
+list(APPEND Bahasa satu dua tiga)
+
+foreach(num IN ZIP_LISTS English Bahasa)
+    message(STATUS "num_0=${num_0}, num_1=${num_1}")
+endforeach()
+
+foreach(en ba IN ZIP_LISTS English Bahasa)
+    message(STATUS "en=${en}, ba=${ba}")
+endforeach()
+
+
+

yields:

+
-- num_0=one, num_1=satu
+-- num_0=two, num_1=dua
+-- num_0=three, num_1=tiga
+-- num_0=four, num_1=
+-- en=one, ba=satu
+-- en=two, ba=dua
+-- en=three, ba=tiga
+-- en=four, ba=
+
+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/function.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/function.html new file mode 100644 index 0000000000000000000000000000000000000000..7df92929d5a52801cb42dd666a04d57199a5fdff --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/function.html @@ -0,0 +1,216 @@ + + + + + + + + + function — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

function

+

Start recording a function for later invocation as a command.

+
function(<name> [<arg1> ...])
+  <commands>
+endfunction()
+
+
+

Defines a function named <name> that takes arguments named +<arg1>, ... The <commands> in the function definition +are recorded; they are not executed until the function is invoked.

+

Per legacy, the endfunction() command admits an optional +<name> argument. If used, it must be a verbatim repeat of the +argument of the opening function command.

+

A function opens a new scope: see set(var PARENT_SCOPE) for +details.

+

See the cmake_policy() command documentation for the behavior +of policies inside functions.

+

See the macro() command documentation for differences +between CMake functions and macros.

+
+

Invocation

+

The function invocation is case-insensitive. A function defined as

+
function(foo)
+  <commands>
+endfunction()
+
+
+

can be invoked through any of

+
foo()
+Foo()
+FOO()
+cmake_language(CALL foo)
+
+
+

and so on. However, it is strongly recommended to stay with the +case chosen in the function definition. Typically functions use +all-lowercase names.

+
+

New in version 3.18: The cmake_language(CALL ...) command can also be used to +invoke the function.

+
+
+
+

Arguments

+

When the function is invoked, the recorded <commands> are first +modified by replacing formal parameters (${arg1}, ...) with the +arguments passed, and then invoked as normal commands.

+

In addition to referencing the formal parameters you can reference the +ARGC variable which will be set to the number of arguments passed +into the function as well as ARGV0, ARGV1, ARGV2, ... which +will have the actual values of the arguments passed in. This facilitates +creating functions with optional arguments.

+

Furthermore, ARGV holds the list of all arguments given to the +function and ARGN holds the list of arguments past the last expected +argument. Referencing to ARGV# arguments beyond ARGC have +undefined behavior. Checking that ARGC is greater than # is +the only way to ensure that ARGV# was passed to the function as an +extra argument.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_cmake_property.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_cmake_property.html new file mode 100644 index 0000000000000000000000000000000000000000..dee58863d333c722e600472f0221c53673e63035 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_cmake_property.html @@ -0,0 +1,166 @@ + + + + + + + + + get_cmake_property — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

get_cmake_property

+

Get a global property of the CMake instance.

+
get_cmake_property(<var> <property>)
+
+
+

Gets a global property from the CMake instance. The value of +the <property> is stored in the variable <var>. +If the property is not found, <var> will be set to NOTFOUND. +See the cmake-properties(7) manual for available properties.

+

In addition to global properties, this command (for historical reasons) +also supports the VARIABLES and MACROS directory +properties. It also supports a special COMPONENTS global property that +lists the components given to the install() command.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_directory_property.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_directory_property.html new file mode 100644 index 0000000000000000000000000000000000000000..89e0c6e0d1ecae3ba67e497be5410db8a1af9ce7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_directory_property.html @@ -0,0 +1,180 @@ + + + + + + + + + get_directory_property — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

get_directory_property

+

Get a property of DIRECTORY scope.

+
get_directory_property(<variable> [DIRECTORY <dir>] <prop-name>)
+
+
+

Stores a property of directory scope in the named <variable>.

+

The DIRECTORY argument specifies another directory from which +to retrieve the property value instead of the current directory. +Relative paths are treated as relative to the +current source directory. CMake must already know about the directory, +either by having added it through a call to add_subdirectory() +or being the top level directory.

+
+

New in version 3.19: <dir> may reference a binary directory.

+
+

If the property is not defined for the nominated directory scope, +an empty string is returned. In the case of INHERITED properties, +if the property is not found for the nominated directory scope, +the search will chain to a parent scope as described for the +define_property() command.

+
get_directory_property(<variable> [DIRECTORY <dir>]
+                       DEFINITION <var-name>)
+
+
+

Get a variable definition from a directory. This form is useful to +get a variable definition from another directory.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_filename_component.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_filename_component.html new file mode 100644 index 0000000000000000000000000000000000000000..fafd97931c08a5294017a239a943bd8d02bcab0f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_filename_component.html @@ -0,0 +1,212 @@ + + + + + + + + + get_filename_component — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

get_filename_component

+

Get a specific component of a full filename.

+
+

Changed in version 3.20: This command has been superseded by the cmake_path() command, except +for REALPATH, which is now offered by file(REAL_PATH), and +PROGRAM, now available in separate_arguments(PROGRAM).

+
+
+

Changed in version 3.24: The undocumented feature offering the capability to query the Windows +registry is superseded by +cmake_host_system_information(QUERY WINDOWS_REGISTRY) +command.

+
+
get_filename_component(<var> <FileName> <mode> [CACHE])
+
+
+

Sets <var> to a component of <FileName>, where <mode> is one of:

+
DIRECTORY = Directory without file name
+NAME      = File name without directory
+EXT       = File name longest extension (.b.c from d/a.b.c)
+NAME_WE   = File name with neither the directory nor the longest extension
+LAST_EXT  = File name last extension (.c from d/a.b.c)
+NAME_WLE  = File name with neither the directory nor the last extension
+PATH      = Legacy alias for DIRECTORY (use for CMake <= 2.8.11)
+
+
+
+

New in version 3.14: Added the LAST_EXT and NAME_WLE modes.

+
+

Paths are returned with forward slashes and have no trailing slashes. +If the optional CACHE argument is specified, the result variable is +added to the cache.

+
get_filename_component(<var> <FileName> <mode> [BASE_DIR <dir>] [CACHE])
+
+
+
+

New in version 3.4.

+
+

Sets <var> to the absolute path of <FileName>, where <mode> is one +of:

+
ABSOLUTE  = Full path to file
+REALPATH  = Full path to existing file with symlinks resolved
+
+
+

If the provided <FileName> is a relative path, it is evaluated relative +to the given base directory <dir>. If no base directory is +provided, the default base directory will be +CMAKE_CURRENT_SOURCE_DIR.

+

Paths are returned with forward slashes and have no trailing slashes. If the +optional CACHE argument is specified, the result variable is added to the +cache.

+
get_filename_component(<var> <FileName> PROGRAM [PROGRAM_ARGS <arg_var>] [CACHE])
+
+
+

The program in <FileName> will be found in the system search path or +left as a full path. If PROGRAM_ARGS is present with PROGRAM, then +any command-line arguments present in the <FileName> string are split +from the program name and stored in <arg_var>. This is used to +separate a program name from its arguments in a command line string.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_property.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_property.html new file mode 100644 index 0000000000000000000000000000000000000000..478056fce41cb81798c7a75003f30a0092d1a43f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_property.html @@ -0,0 +1,241 @@ + + + + + + + + + get_property — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

get_property

+

Get a property.

+
get_property(<variable>
+             <GLOBAL             |
+              DIRECTORY [<dir>]  |
+              TARGET    <target> |
+              SOURCE    <source>
+                        [DIRECTORY <dir> | TARGET_DIRECTORY <target>] |
+              INSTALL   <file>   |
+              TEST      <test>   |
+              CACHE     <entry>  |
+              VARIABLE           >
+             PROPERTY <name>
+             [SET | DEFINED | BRIEF_DOCS | FULL_DOCS])
+
+
+

Gets one property from one object in a scope.

+

The first argument specifies the variable in which to store the result. +The second argument determines the scope from which to get the property. +It must be one of the following:

+
+
GLOBAL

Scope is unique and does not accept a name.

+
+
DIRECTORY

Scope defaults to the current directory but another +directory (already processed by CMake) may be named by the +full or relative path <dir>. +Relative paths are treated as relative to the current source directory. +See also the get_directory_property() command.

+
+

New in version 3.19: <dir> may reference a binary directory.

+
+
+
TARGET

Scope must name one existing target. +See also the get_target_property() command.

+
+
SOURCE

Scope must name one source file. By default, the source file's property +will be read from the current source directory's scope.

+
+

New in version 3.18: Directory scope can be overridden with one of the following sub-options:

+
+
DIRECTORY <dir>

The source file property will be read from the <dir> directory's +scope. CMake must already know about +the directory, either by having added it through a call +to add_subdirectory() or <dir> being the top level directory. +Relative paths are treated as relative to the current source directory.

+
+

New in version 3.19: <dir> may reference a binary directory.

+
+
+
TARGET_DIRECTORY <target>

The source file property will be read from the directory scope in which +<target> was created (<target> must therefore already exist).

+
+
+
+

See also the get_source_file_property() command.

+
+
INSTALL
+

New in version 3.1.

+
+

Scope must name one installed file path.

+
+
TEST

Scope must name one existing test. +See also the get_test_property() command.

+
+
CACHE

Scope must name one cache entry.

+
+
VARIABLE

Scope is unique and does not accept a name.

+
+
+

The required PROPERTY option is immediately followed by the name of +the property to get. If the property is not set an empty value is +returned, although some properties support inheriting from a parent scope +if defined to behave that way (see define_property()).

+

If the SET option is given the variable is set to a boolean +value indicating whether the property has been set. If the DEFINED +option is given the variable is set to a boolean value indicating +whether the property has been defined such as with the +define_property() command.

+

If BRIEF_DOCS or FULL_DOCS is given then the variable is set to a +string containing documentation for the requested property. If +documentation is requested for a property that has not been defined +NOTFOUND is returned.

+
+

Note

+

The GENERATED source file property may be globally visible. +See its documentation for details.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_source_file_property.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_source_file_property.html new file mode 100644 index 0000000000000000000000000000000000000000..b0250afdc8a9456f89d5614c54b69dee34996cca --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_source_file_property.html @@ -0,0 +1,194 @@ + + + + + + + + + get_source_file_property — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

get_source_file_property

+

Get a property for a source file.

+
get_source_file_property(<variable> <file>
+                         [DIRECTORY <dir> | TARGET_DIRECTORY <target>]
+                         <property>)
+
+
+

Gets a property from a source file. The value of the property is +stored in the specified <variable>. If the source property is not found, +the behavior depends on whether it has been defined to be an INHERITED +property or not (see define_property()). Non-inherited properties +will set variable to NOTFOUND, whereas inherited properties will search +the relevant parent scope as described for the define_property() +command and if still unable to find the property, variable will be set to +an empty string.

+

By default, the source file's property will be read from the current source +directory's scope.

+
+

New in version 3.18: Directory scope can be overridden with one of the following sub-options:

+
+
DIRECTORY <dir>

The source file property will be read from the <dir> directory's +scope. CMake must already know about that source directory, either by +having added it through a call to add_subdirectory() or <dir> +being the top level source directory. Relative paths are treated as +relative to the current source directory.

+
+
TARGET_DIRECTORY <target>

The source file property will be read from the directory scope in which +<target> was created (<target> must therefore already exist).

+
+
+
+

Use set_source_files_properties() to set property values. Source +file properties usually control how the file is built. One property that is +always there is LOCATION.

+
+

Note

+

The GENERATED source file property may be globally visible. +See its documentation for details.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_target_property.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_target_property.html new file mode 100644 index 0000000000000000000000000000000000000000..5dd237fea57b37303570f74bd92658d0df2f131d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_target_property.html @@ -0,0 +1,174 @@ + + + + + + + + + get_target_property — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

get_target_property

+

Get a property from a target.

+
get_target_property(<VAR> target property)
+
+
+

Get a property from a target. The value of the property is stored in +the variable <VAR>. If the target property is not found, the behavior +depends on whether it has been defined to be an INHERITED property +or not (see define_property()). Non-inherited properties will +set <VAR> to <VAR>-NOTFOUND, whereas inherited properties will search +the relevant parent scope as described for the define_property() +command and if still unable to find the property, <VAR> will be set to +an empty string.

+

Use set_target_properties() to set target property values. +Properties are usually used to control how a target is built, but some +query the target instead. This command can get properties for any +target so far created. The targets do not need to be in the current +CMakeLists.txt file.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_test_property.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_test_property.html new file mode 100644 index 0000000000000000000000000000000000000000..a64bf8fa7bdb1cc6dd7e6da337d7c023dd266341 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/get_test_property.html @@ -0,0 +1,169 @@ + + + + + + + + + get_test_property — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

get_test_property

+

Get a property of the test.

+
get_test_property(test property VAR)
+
+
+

Get a property from the test. The value of the property is stored in +the variable VAR. If the test property is not found, the behavior +depends on whether it has been defined to be an INHERITED property +or not (see define_property()). Non-inherited properties will +set VAR to "NOTFOUND", whereas inherited properties will search the +relevant parent scope as described for the define_property() +command and if still unable to find the property, VAR will be set to +an empty string.

+

For a list of standard properties you can type +cmake --help-property-list.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/if.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/if.html new file mode 100644 index 0000000000000000000000000000000000000000..fc3fd39a90f799d39c4c89adddd33f80222c960b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/if.html @@ -0,0 +1,647 @@ + + + + + + + + + if — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

if

+

Conditionally execute a group of commands.

+
+

Synopsis

+
if(<condition>)
+  <commands>
+elseif(<condition>) # optional block, can be repeated
+  <commands>
+else()              # optional block
+  <commands>
+endif()
+
+
+

Evaluates the condition argument of the if clause according to the +Condition syntax described below. If the result is true, then the +commands in the if block are executed. +Otherwise, optional elseif blocks are processed in the same way. +Finally, if no condition is true, commands in the optional else +block are executed.

+

Per legacy, the else() and endif() commands admit +an optional <condition> argument. +If used, it must be a verbatim +repeat of the argument of the opening +if command.

+
+
+

Condition Syntax

+

The following syntax applies to the condition argument of +the if, elseif and while() clauses.

+

Compound conditions are evaluated in the following order of precedence:

+
    +
  1. Parentheses.

  2. +
  3. Unary tests such as EXISTS, COMMAND, and DEFINED.

  4. +
  5. Binary tests such as EQUAL, LESS, LESS_EQUAL, GREATER, +GREATER_EQUAL, STREQUAL, STRLESS, STRLESS_EQUAL, +STRGREATER, STRGREATER_EQUAL, VERSION_EQUAL, VERSION_LESS, +VERSION_LESS_EQUAL, VERSION_GREATER, VERSION_GREATER_EQUAL, +PATH_EQUAL, and MATCHES.

  6. +
  7. Unary logical operator NOT.

  8. +
  9. Binary logical operators AND and OR, from left to right, +without any short-circuit.

  10. +
+
+

Basic Expressions

+
+
+if(<constant>)
+

True if the constant is 1, ON, YES, TRUE, Y, +or a non-zero number (including floating point numbers). +False if the constant is 0, OFF, +NO, FALSE, N, IGNORE, NOTFOUND, the empty string, +or ends in the suffix -NOTFOUND. Named boolean constants are +case-insensitive. If the argument is not one of these specific +constants, it is treated as a variable or string (see Variable Expansion +further below) and one of the following two forms applies.

+
+ +
+
+if(<variable>)
+

True if given a variable that is defined to a value that is not a false +constant. False otherwise, including if the variable is undefined. +Note that macro arguments are not variables. +Environment Variables also +cannot be tested this way, e.g. if(ENV{some_var}) will always evaluate +to false.

+
+ +
+
+if(<string>)
+

A quoted string always evaluates to false unless:

+
    +
  • The string's value is one of the true constants, or

  • +
  • Policy CMP0054 is not set to NEW and the string's value +happens to be a variable name that is affected by CMP0054's +behavior.

  • +
+
+ +
+
+

Logic Operators

+
+
+if(NOT <condition>)
+

True if the condition is not true.

+
+ +
+
+if(<cond1> AND <cond2>)
+

True if both conditions would be considered true individually.

+
+ +
+
+if(<cond1> OR <cond2>)
+

True if either condition would be considered true individually.

+
+ +
+
+if((condition) AND (condition OR (condition)))
+

The conditions inside the parenthesis are evaluated first and then +the remaining condition is evaluated as in the other examples. +Where there are nested parenthesis the innermost are evaluated as part +of evaluating the condition that contains them.

+
+ +
+
+

Existence Checks

+
+
+if(COMMAND <command-name>)
+

True if the given name is a command, macro or function that can be +invoked.

+
+ +
+
+if(POLICY <policy-id>)
+

True if the given name is an existing policy (of the form CMP<NNNN>).

+
+ +
+
+if(TARGET <target-name>)
+

True if the given name is an existing logical target name created +by a call to the add_executable(), add_library(), +or add_custom_target() command that has already been invoked +(in any directory).

+
+ +
+
+if(TEST <test-name>)
+
+

New in version 3.3.

+
+

True if the given name is an existing test name created by the +add_test() command.

+
+ +
+
+if(DEFINED <name>|CACHE{<name>}|ENV{<name>})
+
+

True if a variable, cache variable or environment variable +with given <name> is defined. The value of the variable +does not matter. Note the following caveats:

+
    +
  • Macro arguments are not variables.

  • +
  • It is not possible to test directly whether a <name> is a non-cache +variable. The expression if(DEFINED someName) will evaluate to true +if either a cache or non-cache variable someName exists. In +comparison, the expression if(DEFINED CACHE{someName}) will only +evaluate to true if a cache variable someName exists. Both expressions +need to be tested if you need to know whether a non-cache variable exists: +if(DEFINED someName AND NOT DEFINED CACHE{someName}).

  • +
+
+
+

New in version 3.14: Added support for CACHE{<name>} variables.

+
+
+ +
+
+if(<variable|string> IN_LIST <variable>)
+
+

New in version 3.3.

+
+

True if the given element is contained in the named list variable.

+
+ +
+
+

File Operations

+
+
+if(EXISTS <path-to-file-or-directory>)
+

True if the named file or directory exists and is readable. Behavior +is well-defined only for explicit full paths (a leading ~/ is not +expanded as a home directory and is considered a relative path). +Resolves symbolic links, i.e. if the named file or directory is a +symbolic link, returns true if the target of the symbolic link exists.

+

False if the given path is an empty string.

+
+ +
+
+if(<file1> IS_NEWER_THAN <file2>)
+

True if file1 is newer than file2 or if one of the two files doesn't +exist. Behavior is well-defined only for full paths. If the file +time stamps are exactly the same, an IS_NEWER_THAN comparison returns +true, so that any dependent build operations will occur in the event +of a tie. This includes the case of passing the same file name for +both file1 and file2.

+
+ +
+
+if(IS_DIRECTORY <path>)
+

True if path is a directory. Behavior is well-defined only +for full paths.

+

False if the given path is an empty string.

+
+ +
+ +

True if the given path is a symbolic link. Behavior is well-defined +only for full paths.

+
+ +
+
+if(IS_ABSOLUTE <path>)
+

True if the given path is an absolute path. Note the following special +cases:

+
    +
  • An empty path evaluates to false.

  • +
  • On Windows hosts, any path that begins with a drive letter and colon +(e.g. C:), a forward slash or a backslash will evaluate to true. +This means a path like C:no\base\dir will evaluate to true, even +though the non-drive part of the path is relative.

  • +
  • On non-Windows hosts, any path that begins with a tilde (~) +evaluates to true.

  • +
+
+ +
+
+

Comparisons

+
+
+if(<variable|string> MATCHES <regex>)
+

True if the given string or variable's value matches the given regular +expression. See Regex Specification for regex format.

+
+

New in version 3.9: () groups are captured in CMAKE_MATCH_<n> variables.

+
+
+ +
+
+if(<variable|string> LESS <variable|string>)
+

True if the given string or variable's value is a valid number and less +than that on the right.

+
+ +
+
+if(<variable|string> GREATER <variable|string>)
+

True if the given string or variable's value is a valid number and greater +than that on the right.

+
+ +
+
+if(<variable|string> EQUAL <variable|string>)
+

True if the given string or variable's value is a valid number and equal +to that on the right.

+
+ +
+
+if(<variable|string> LESS_EQUAL <variable|string>)
+
+

New in version 3.7.

+
+

True if the given string or variable's value is a valid number and less +than or equal to that on the right.

+
+ +
+
+if(<variable|string> GREATER_EQUAL <variable|string>)
+
+

New in version 3.7.

+
+

True if the given string or variable's value is a valid number and greater +than or equal to that on the right.

+
+ +
+
+if(<variable|string> STRLESS <variable|string>)
+

True if the given string or variable's value is lexicographically less +than the string or variable on the right.

+
+ +
+
+if(<variable|string> STRGREATER <variable|string>)
+

True if the given string or variable's value is lexicographically greater +than the string or variable on the right.

+
+ +
+
+if(<variable|string> STREQUAL <variable|string>)
+

True if the given string or variable's value is lexicographically equal +to the string or variable on the right.

+
+ +
+
+if(<variable|string> STRLESS_EQUAL <variable|string>)
+
+

New in version 3.7.

+
+

True if the given string or variable's value is lexicographically less +than or equal to the string or variable on the right.

+
+ +
+
+if(<variable|string> STRGREATER_EQUAL <variable|string>)
+
+

New in version 3.7.

+
+

True if the given string or variable's value is lexicographically greater +than or equal to the string or variable on the right.

+
+ +
+
+

Version Comparisons

+
+
+if(<variable|string> VERSION_LESS <variable|string>)
+

Component-wise integer version number comparison (version format is +major[.minor[.patch[.tweak]]], omitted components are treated as zero). +Any non-integer version component or non-integer trailing part of a version +component effectively truncates the string at that point.

+
+ +
+
+if(<variable|string> VERSION_GREATER <variable|string>)
+

Component-wise integer version number comparison (version format is +major[.minor[.patch[.tweak]]], omitted components are treated as zero). +Any non-integer version component or non-integer trailing part of a version +component effectively truncates the string at that point.

+
+ +
+
+if(<variable|string> VERSION_EQUAL <variable|string>)
+

Component-wise integer version number comparison (version format is +major[.minor[.patch[.tweak]]], omitted components are treated as zero). +Any non-integer version component or non-integer trailing part of a version +component effectively truncates the string at that point.

+
+ +
+
+if(<variable|string> VERSION_LESS_EQUAL <variable|string>)
+
+

New in version 3.7.

+
+

Component-wise integer version number comparison (version format is +major[.minor[.patch[.tweak]]], omitted components are treated as zero). +Any non-integer version component or non-integer trailing part of a version +component effectively truncates the string at that point.

+
+ +
+
+if(<variable|string> VERSION_GREATER_EQUAL <variable|string>)
+
+

New in version 3.7.

+
+

Component-wise integer version number comparison (version format is +major[.minor[.patch[.tweak]]], omitted components are treated as zero). +Any non-integer version component or non-integer trailing part of a version +component effectively truncates the string at that point.

+
+ +
+
+

Path Comparisons

+
+
+if(<variable|string> PATH_EQUAL <variable|string>)
+
+

New in version 3.24.

+
+

Compares the two paths component-by-component. Only if every component of +both paths match will the two paths compare equal. Multiple path separators +are effectively collapsed into a single separator, but note that backslashes +are not converted to forward slashes. No other +path normalization is performed.

+

Component-wise comparison is superior to string-based comparison due to the +handling of multiple path separators. In the following example, the +expression evaluates to true using PATH_EQUAL, but false with +STREQUAL:

+
# comparison is TRUE
+if ("/a//b/c" PATH_EQUAL "/a/b/c")
+   ...
+endif()
+
+# comparison is FALSE
+if ("/a//b/c" STREQUAL "/a/b/c")
+   ...
+endif()
+
+
+

See cmake_path(COMPARE) for more details.

+
+ +
+
+
+

Variable Expansion

+

The if command was written very early in CMake's history, predating +the ${} variable evaluation syntax, and for convenience evaluates +variables named by its arguments as shown in the above signatures. +Note that normal variable evaluation with ${} applies before the if +command even receives the arguments. Therefore code like

+
set(var1 OFF)
+set(var2 "var1")
+if(${var2})
+
+
+

appears to the if command as

+
if(var1)
+
+
+

and is evaluated according to the if(<variable>) case documented +above. The result is OFF which is false. However, if we remove the +${} from the example then the command sees

+
if(var2)
+
+
+

which is true because var2 is defined to var1 which is not a false +constant.

+

Automatic evaluation applies in the other cases whenever the +above-documented condition syntax accepts <variable|string>:

+
    +
  • The left hand argument to MATCHES is first checked to see if it is +a defined variable. If so, the variable's value is used, otherwise the +original value is used.

  • +
  • If the left hand argument to MATCHES is missing it returns false +without error

  • +
  • Both left and right hand arguments to LESS, GREATER, EQUAL, +LESS_EQUAL, and GREATER_EQUAL, are independently tested to see if +they are defined variables. If so, their defined values are used otherwise +the original value is used.

  • +
  • Both left and right hand arguments to STRLESS, STRGREATER, +STREQUAL, STRLESS_EQUAL, and STRGREATER_EQUAL are independently +tested to see if they are defined variables. If so, their defined values are +used otherwise the original value is used.

  • +
  • Both left and right hand arguments to VERSION_LESS, +VERSION_GREATER, VERSION_EQUAL, VERSION_LESS_EQUAL, and +VERSION_GREATER_EQUAL are independently tested to see if they are defined +variables. If so, their defined values are used otherwise the original value +is used.

  • +
  • The right hand argument to NOT is tested to see if it is a boolean +constant. If so, the value is used, otherwise it is assumed to be a +variable and it is dereferenced.

  • +
  • The left and right hand arguments to AND and OR are independently +tested to see if they are boolean constants. If so, they are used as +such, otherwise they are assumed to be variables and are dereferenced.

  • +
+
+

Changed in version 3.1: To prevent ambiguity, potential variable or keyword names can be +specified in a Quoted Argument or a Bracket Argument. +A quoted or bracketed variable or keyword will be interpreted as a +string and not dereferenced or interpreted. +See policy CMP0054.

+
+

There is no automatic evaluation for environment or cache +Variable References. Their values must be referenced as +$ENV{<name>} or $CACHE{<name>} wherever the above-documented +condition syntax accepts <variable|string>.

+
+
+

See also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include.html new file mode 100644 index 0000000000000000000000000000000000000000..322232f78453134b9613f63a97e102cb40c34529 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include.html @@ -0,0 +1,156 @@ + + + + + + + + + include — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

include

+

Load and run CMake code from a file or module.

+
include(<file|module> [OPTIONAL] [RESULT_VARIABLE <var>]
+                      [NO_POLICY_SCOPE])
+
+
+

Loads and runs CMake code from the file given. Variable reads and +writes access the scope of the caller (dynamic scoping). If OPTIONAL +is present, then no error is raised if the file does not exist. If +RESULT_VARIABLE is given the variable <var> will be set to the +full filename which has been included or NOTFOUND if it failed.

+

If a module is specified instead of a file, the file with name +<modulename>.cmake is searched first in CMAKE_MODULE_PATH, +then in the CMake module directory. There is one exception to this: if +the file which calls include() is located itself in the CMake builtin +module directory, then first the CMake builtin module directory is searched and +CMAKE_MODULE_PATH afterwards. See also policy CMP0017.

+

See the cmake_policy() command documentation for discussion of the +NO_POLICY_SCOPE option.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_directories.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_directories.html new file mode 100644 index 0000000000000000000000000000000000000000..0c7ac3c5d11ef7064a0d5b7a9020370c2f1ab43b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_directories.html @@ -0,0 +1,186 @@ + + + + + + + + + include_directories — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

include_directories

+

Add include directories to the build.

+
include_directories([AFTER|BEFORE] [SYSTEM] dir1 [dir2 ...])
+
+
+

Add the given directories to those the compiler uses to search for +include files. Relative paths are interpreted as relative to the +current source directory.

+

The include directories are added to the INCLUDE_DIRECTORIES +directory property for the current CMakeLists file. They are also +added to the INCLUDE_DIRECTORIES target property for each +target in the current CMakeLists file. The target property values +are the ones used by the generators.

+

By default the directories specified are appended onto the current list of +directories. This default behavior can be changed by setting +CMAKE_INCLUDE_DIRECTORIES_BEFORE to ON. By using +AFTER or BEFORE explicitly, you can select between appending and +prepending, independent of the default.

+

If the SYSTEM option is given, the compiler will be told the +directories are meant as system include directories on some platforms. +Signaling this setting might achieve effects such as the compiler +skipping warnings, or these fixed-install system files not being +considered in dependency calculations - see compiler docs.

+

Arguments to include_directories may use generator expressions +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+
+

Note

+

Prefer the target_include_directories() command to add include +directories to individual targets and optionally propagate/export them +to dependents.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_external_msproject.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_external_msproject.html new file mode 100644 index 0000000000000000000000000000000000000000..09ccdc88e97d2d495ae87c1e043f9999f539cb84 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_external_msproject.html @@ -0,0 +1,159 @@ + + + + + + + + + include_external_msproject — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

include_external_msproject

+

Include an external Microsoft project file in a workspace.

+
include_external_msproject(projectname location
+                           [TYPE projectTypeGUID]
+                           [GUID projectGUID]
+                           [PLATFORM platformName]
+                           dep1 dep2 ...)
+
+
+

Includes an external Microsoft project in the generated workspace +file. Currently does nothing on UNIX. This will create a target +named [projectname]. This can be used in the add_dependencies() +command to make things depend on the external project.

+

TYPE, GUID and PLATFORM are optional parameters that allow one to +specify the type of project, id (GUID) of the project and the name of +the target platform. This is useful for projects requiring values +other than the default (e.g. WIX projects).

+
+

New in version 3.9: If the imported project has different configuration names than the +current project, set the MAP_IMPORTED_CONFIG_<CONFIG> +target property to specify the mapping.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_guard.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_guard.html new file mode 100644 index 0000000000000000000000000000000000000000..1d6fb19841ce8633884d7c37253eadb6b221eacb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_guard.html @@ -0,0 +1,178 @@ + + + + + + + + + include_guard — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

include_guard

+
+

New in version 3.10.

+
+

Provides an include guard for the file currently being processed by CMake.

+
include_guard([DIRECTORY|GLOBAL])
+
+
+

Sets up an include guard for the current CMake file (see the +CMAKE_CURRENT_LIST_FILE variable documentation).

+

CMake will end its processing of the current file at the location of the +include_guard command if the current file has already been +processed for the applicable scope (see below). This provides functionality +similar to the include guards commonly used in source headers or to the +#pragma once directive. If the current file has been processed previously +for the applicable scope, the effect is as though return() had been +called. Do not call this command from inside a function being defined within +the current file.

+

An optional argument specifying the scope of the guard may be provided. +Possible values for the option are:

+
+
DIRECTORY

The include guard applies within the current directory and below. The file +will only be included once within this directory scope, but may be included +again by other files outside of this directory (i.e. a parent directory or +another directory not pulled in by add_subdirectory() or +include() from the current file or its children).

+
+
GLOBAL

The include guard applies globally to the whole build. The current file +will only be included once regardless of the scope.

+
+
+

If no arguments given, include_guard has the same scope as a variable, +meaning that the include guard effect is isolated by the most recent +function scope or current directory if no inner function scopes exist. +In this case the command behavior is the same as:

+
if(__CURRENT_FILE_VAR__)
+  return()
+endif()
+set(__CURRENT_FILE_VAR__ TRUE)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_regular_expression.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_regular_expression.html new file mode 100644 index 0000000000000000000000000000000000000000..29542d43327d41f81a7237054a643db9f394c0ef --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/include_regular_expression.html @@ -0,0 +1,150 @@ + + + + + + + + + include_regular_expression — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

include_regular_expression

+

Set the regular expression used for dependency checking.

+
include_regular_expression(regex_match [regex_complain])
+
+
+

Sets the regular expressions used in dependency checking. Only files +matching regex_match will be traced as dependencies. Only files +matching regex_complain will generate warnings if they cannot be found +(standard header paths are not searched). The defaults are:

+
regex_match    = "^.*$" (match everything)
+regex_complain = "^$" (match empty string only)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install.html new file mode 100644 index 0000000000000000000000000000000000000000..a2a77cd8dc2b48b1423ee06b2a0e1a6dea938e8d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install.html @@ -0,0 +1,1169 @@ + + + + + + + + + install — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

install

+

Specify rules to run at install time.

+
+

Synopsis

+
install(TARGETS <target>... [...])
+install(IMPORTED_RUNTIME_ARTIFACTS <target>... [...])
+install({FILES | PROGRAMS} <file>... [...])
+install(DIRECTORY <dir>... [...])
+install(SCRIPT <file> [...])
+install(CODE <code> [...])
+install(EXPORT <export-name> [...])
+install(RUNTIME_DEPENDENCY_SET <set-name> [...])
+
+
+

Introduction

+

This command generates installation rules for a project. Install rules +specified by calls to the install() command within a source directory +are executed in order during installation.

+
+

Changed in version 3.14: Install rules in subdirectories +added by calls to the add_subdirectory() command are interleaved +with those in the parent directory to run in the order declared (see +policy CMP0082).

+
+
+

Changed in version 3.22: The environment variable CMAKE_INSTALL_MODE can override the +default copying behavior of install().

+
+

There are multiple signatures for this command. Some of them define +installation options for files and targets. Options common to +multiple signatures are covered here but they are valid only for +signatures that specify them. The common options are:

+
+
DESTINATION

Specify the directory on disk to which a file will be installed. +Arguments can be relative or absolute paths.

+

If a relative path is given it is interpreted relative to the value +of the CMAKE_INSTALL_PREFIX variable. +The prefix can be relocated at install time using the DESTDIR +mechanism explained in the CMAKE_INSTALL_PREFIX variable +documentation.

+

If an absolute path (with a leading slash or drive letter) is given +it is used verbatim.

+

As absolute paths are not supported by cpack installer +generators, it is preferable to use relative paths throughout. +In particular, there is no need to make paths absolute by prepending +CMAKE_INSTALL_PREFIX; this prefix is used by default if +the DESTINATION is a relative path.

+
+
PERMISSIONS

Specify permissions for installed files. Valid permissions are +OWNER_READ, OWNER_WRITE, OWNER_EXECUTE, GROUP_READ, +GROUP_WRITE, GROUP_EXECUTE, WORLD_READ, WORLD_WRITE, +WORLD_EXECUTE, SETUID, and SETGID. Permissions that do +not make sense on certain platforms are ignored on those platforms.

+
+
CONFIGURATIONS

Specify a list of build configurations for which the install rule +applies (Debug, Release, etc.). Note that the values specified for +this option only apply to options listed AFTER the CONFIGURATIONS +option. For example, to set separate install paths for the Debug and +Release configurations, do the following:

+
install(TARGETS target
+        CONFIGURATIONS Debug
+        RUNTIME DESTINATION Debug/bin)
+install(TARGETS target
+        CONFIGURATIONS Release
+        RUNTIME DESTINATION Release/bin)
+
+
+

Note that CONFIGURATIONS appears BEFORE RUNTIME DESTINATION.

+
+
COMPONENT

Specify an installation component name with which the install rule +is associated, such as Runtime or Development. During +component-specific installation only install rules associated with +the given component name will be executed. During a full installation +all components are installed unless marked with EXCLUDE_FROM_ALL. +If COMPONENT is not provided a default component "Unspecified" is +created. The default component name may be controlled with the +CMAKE_INSTALL_DEFAULT_COMPONENT_NAME variable.

+
+
EXCLUDE_FROM_ALL
+

New in version 3.6.

+
+

Specify that the file is excluded from a full installation and only +installed as part of a component-specific installation

+
+
RENAME

Specify a name for an installed file that may be different from the +original file. Renaming is allowed only when a single file is +installed by the command.

+
+
OPTIONAL

Specify that it is not an error if the file to be installed does +not exist.

+
+
+
+

New in version 3.1: Command signatures that install files may print messages during +installation. Use the CMAKE_INSTALL_MESSAGE variable +to control which messages are printed.

+
+
+

New in version 3.11: Many of the install() variants implicitly create the directories +containing the installed files. If +CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS is set, these +directories will be created with the permissions specified. Otherwise, +they will be created according to the uname rules on Unix-like platforms. +Windows platforms are unaffected.

+
+
+
+

Installing Targets

+
install(TARGETS targets... [EXPORT <export-name>]
+        [RUNTIME_DEPENDENCIES args...|RUNTIME_DEPENDENCY_SET <set-name>]
+        [[ARCHIVE|LIBRARY|RUNTIME|OBJECTS|FRAMEWORK|BUNDLE|
+          PRIVATE_HEADER|PUBLIC_HEADER|RESOURCE|FILE_SET <set-name>|CXX_MODULES_BMI]
+         [DESTINATION <dir>]
+         [PERMISSIONS permissions...]
+         [CONFIGURATIONS [Debug|Release|...]]
+         [COMPONENT <component>]
+         [NAMELINK_COMPONENT <component>]
+         [OPTIONAL] [EXCLUDE_FROM_ALL]
+         [NAMELINK_ONLY|NAMELINK_SKIP]
+        ] [...]
+        [INCLUDES DESTINATION [<dir> ...]]
+        )
+
+
+

The TARGETS form specifies rules for installing targets from a +project. There are several kinds of target Output Artifacts +that may be installed:

+
+
ARCHIVE

Target artifacts of this kind include:

+
    +
  • Static libraries +(except on macOS when marked as FRAMEWORK, see below);

  • +
  • DLL import libraries +(on all Windows-based systems including Cygwin; they have extension +.lib, in contrast to the .dll libraries that go to RUNTIME);

  • +
  • On AIX, the linker import file created for executables with +ENABLE_EXPORTS enabled.

  • +
  • On macOS, the linker import file created for shared libraries with +ENABLE_EXPORTS enabled (except when marked as FRAMEWORK, +see below).

  • +
+
+
LIBRARY

Target artifacts of this kind include:

+
    +
  • Shared libraries, except

    +
      +
    • DLLs (these go to RUNTIME, see below),

    • +
    • on macOS when marked as FRAMEWORK (see below).

    • +
    +
  • +
+
+
RUNTIME

Target artifacts of this kind include:

+
    +
  • Executables +(except on macOS when marked as MACOSX_BUNDLE, see BUNDLE below);

  • +
  • DLLs (on all Windows-based systems including Cygwin; note that the +accompanying import libraries are of kind ARCHIVE).

  • +
+
+
OBJECTS
+

New in version 3.9.

+
+

Object files associated with object libraries.

+
+
FRAMEWORK

Both static and shared libraries marked with the FRAMEWORK +property are treated as FRAMEWORK targets on macOS.

+
+
BUNDLE

Executables marked with the MACOSX_BUNDLE property are treated as +BUNDLE targets on macOS.

+
+
PUBLIC_HEADER

Any PUBLIC_HEADER files associated with a library are installed in +the destination specified by the PUBLIC_HEADER argument on non-Apple +platforms. Rules defined by this argument are ignored for FRAMEWORK +libraries on Apple platforms because the associated files are installed +into the appropriate locations inside the framework folder. See +PUBLIC_HEADER for details.

+
+
PRIVATE_HEADER

Similar to PUBLIC_HEADER, but for PRIVATE_HEADER files. See +PRIVATE_HEADER for details.

+
+
RESOURCE

Similar to PUBLIC_HEADER and PRIVATE_HEADER, but for +RESOURCE files. See RESOURCE for details.

+
+
FILE_SET <set>
+

New in version 3.23.

+
+

File sets are defined by the target_sources(FILE_SET) command. +If the file set <set> exists and is PUBLIC or INTERFACE, any +files in the set are installed under the destination (see below). +The directory structure relative to the file set's base directories is +preserved. For example, a file added to the file set as +/blah/include/myproj/here.h with a base directory /blah/include +would be installed to myproj/here.h below the destination.

+
+
+

CXX_MODULES_BMI

+
+
+

Note

+

Experimental. Gated by CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API

+
+

Any module files from C++ modules from PUBLIC sources in a file set of +type CXX_MODULES will be installed to the given DESTINATION. All +modules are placed directly in the destination as no directory structure is +derived from the names of the modules. An empty DESTINATION may be used +to suppress installing these files (for use in generic code).

+
+

For each of these arguments given, the arguments following them only apply +to the target or file type specified in the argument. If none is given, the +installation properties apply to all target types.

+

For regular executables, static libraries and shared libraries, the +DESTINATION argument is not required. For these target types, when +DESTINATION is omitted, a default destination will be taken from the +appropriate variable from GNUInstallDirs, or set to a built-in +default value if that variable is not defined. The same is true for file +sets, and the public and private headers associated with the installed +targets through the PUBLIC_HEADER and PRIVATE_HEADER +target properties. A destination must always be provided for module libraries, +Apple bundles and frameworks. A destination can be omitted for interface and +object libraries, but they are handled differently (see the discussion of this +topic toward the end of this section).

+

For shared libraries on DLL platforms, if neither RUNTIME nor ARCHIVE +destinations are specified, both the RUNTIME and ARCHIVE components are +installed to their default destinations. If either a RUNTIME or ARCHIVE +destination is specified, the component is installed to that destination, and +the other component is not installed. If both RUNTIME and ARCHIVE +destinations are specified, then both components are installed to their +respective destinations.

+

The following table shows the target types with their associated variables and +built-in defaults that apply when no destination is given:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Target Type

GNUInstallDirs Variable

Built-In Default

RUNTIME

${CMAKE_INSTALL_BINDIR}

bin

LIBRARY

${CMAKE_INSTALL_LIBDIR}

lib

ARCHIVE

${CMAKE_INSTALL_LIBDIR}

lib

PRIVATE_HEADER

${CMAKE_INSTALL_INCLUDEDIR}

include

PUBLIC_HEADER

${CMAKE_INSTALL_INCLUDEDIR}

include

FILE_SET (type HEADERS)

${CMAKE_INSTALL_INCLUDEDIR}

include

+

Projects wishing to follow the common practice of installing headers into a +project-specific subdirectory may prefer using file sets with appropriate +paths and base directories. Otherwise, they must provide a DESTINATION +instead of being able to rely on the above (see next example below).

+

To make packages compliant with distribution filesystem layout policies, if +projects must specify a DESTINATION, it is recommended that they use a +path that begins with the appropriate GNUInstallDirs variable. +This allows package maintainers to control the install destination by setting +the appropriate cache variables. The following example shows a static library +being installed to the default destination provided by +GNUInstallDirs, but with its headers installed to a project-specific +subdirectory without using file sets:

+
add_library(mylib STATIC ...)
+set_target_properties(mylib PROPERTIES PUBLIC_HEADER mylib.h)
+include(GNUInstallDirs)
+install(TARGETS mylib
+        PUBLIC_HEADER
+          DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/myproj
+)
+
+
+

In addition to the common options listed above, each target can accept +the following additional arguments:

+
+
NAMELINK_COMPONENT
+

New in version 3.12.

+
+

On some platforms a versioned shared library has a symbolic link such +as:

+
lib<name>.so -> lib<name>.so.1
+
+
+

where lib<name>.so.1 is the soname of the library and lib<name>.so +is a "namelink" allowing linkers to find the library when given +-l<name>. The NAMELINK_COMPONENT option is similar to the +COMPONENT option, but it changes the installation component of a shared +library namelink if one is generated. If not specified, this defaults to the +value of COMPONENT. It is an error to use this parameter outside of a +LIBRARY block.

+
+

Changed in version 3.27: This parameter is also usable for an ARCHIVE block to manage +the linker import file created, on macOS, for shared libraries with +ENABLE_EXPORTS enabled.

+
+

Consider the following example:

+
install(TARGETS mylib
+        LIBRARY
+          COMPONENT Libraries
+          NAMELINK_COMPONENT Development
+        PUBLIC_HEADER
+          COMPONENT Development
+       )
+
+
+

In this scenario, if you choose to install only the Development +component, both the headers and namelink will be installed without the +library. (If you don't also install the Libraries component, the +namelink will be a dangling symlink, and projects that link to the library +will have build errors.) If you install only the Libraries component, +only the library will be installed, without the headers and namelink.

+

This option is typically used for package managers that have separate +runtime and development packages. For example, on Debian systems, the +library is expected to be in the runtime package, and the headers and +namelink are expected to be in the development package.

+

See the VERSION and SOVERSION target properties for +details on creating versioned shared libraries.

+
+
NAMELINK_ONLY

This option causes the installation of only the namelink when a library +target is installed. On platforms where versioned shared libraries do not +have namelinks or when a library is not versioned, the NAMELINK_ONLY +option installs nothing. It is an error to use this parameter outside of a +LIBRARY block.

+
+

Changed in version 3.27: This parameter is also usable for an ARCHIVE block to manage +the linker import file created, on macOS, for shared libraries with +ENABLE_EXPORTS enabled.

+
+

When NAMELINK_ONLY is given, either NAMELINK_COMPONENT or +COMPONENT may be used to specify the installation component of the +namelink, but COMPONENT should generally be preferred.

+
+
NAMELINK_SKIP

Similar to NAMELINK_ONLY, but it has the opposite effect: it causes the +installation of library files other than the namelink when a library target +is installed. When neither NAMELINK_ONLY or NAMELINK_SKIP are given, +both portions are installed. On platforms where versioned shared libraries +do not have symlinks or when a library is not versioned, NAMELINK_SKIP +installs the library. It is an error to use this parameter outside of a +LIBRARY block.

+
+

Changed in version 3.27: This parameter is also usable for an ARCHIVE block to manage +the linker import file created, on macOS, for shared libraries with +ENABLE_EXPORTS enabled.

+
+

If NAMELINK_SKIP is specified, NAMELINK_COMPONENT has no effect. It +is not recommended to use NAMELINK_SKIP in conjunction with +NAMELINK_COMPONENT.

+
+
+

The install(TARGETS) command can also accept the following options at the +top level:

+
+
EXPORT

This option associates the installed target files with an export called +<export-name>. It must appear before any target options. To actually +install the export file itself, call install(EXPORT), documented below. +See documentation of the EXPORT_NAME target property to change +the name of the exported target.

+

If EXPORT is used and the targets include PUBLIC or INTERFACE +file sets, all of them must be specified with FILE_SET arguments. All +PUBLIC or INTERFACE file sets associated with a target are included +in the export.

+
+
INCLUDES DESTINATION

This option specifies a list of directories which will be added to the +INTERFACE_INCLUDE_DIRECTORIES target property of the +<targets> when exported by the install(EXPORT) command. If a +relative path is specified, it is treated as relative to the +$<INSTALL_PREFIX>.

+
+
RUNTIME_DEPENDENCY_SET
+

New in version 3.21.

+
+

This option causes all runtime dependencies of installed executable, shared +library, and module targets to be added to the specified runtime dependency +set. This set can then be installed with an +install(RUNTIME_DEPENDENCY_SET) command.

+

This keyword and the RUNTIME_DEPENDENCIES keyword are mutually +exclusive.

+
+
RUNTIME_DEPENDENCIES
+

New in version 3.21.

+
+

This option causes all runtime dependencies of installed executable, shared +library, and module targets to be installed along with the targets +themselves. The RUNTIME, LIBRARY, FRAMEWORK, and generic +arguments are used to determine the properties (DESTINATION, +COMPONENT, etc.) of the installation of these dependencies.

+

RUNTIME_DEPENDENCIES is semantically equivalent to the following pair +of calls:

+
install(TARGETS ... RUNTIME_DEPENDENCY_SET <set-name>)
+install(RUNTIME_DEPENDENCY_SET <set-name> args...)
+
+
+

where <set-name> will be a randomly generated set name. +The args... may include any of the following keywords supported by +the install(RUNTIME_DEPENDENCY_SET) command:

+
    +
  • DIRECTORIES

  • +
  • PRE_INCLUDE_REGEXES

  • +
  • PRE_EXCLUDE_REGEXES

  • +
  • POST_INCLUDE_REGEXES

  • +
  • POST_EXCLUDE_REGEXES

  • +
  • POST_INCLUDE_FILES

  • +
  • POST_EXCLUDE_FILES

  • +
+

The RUNTIME_DEPENDENCIES and RUNTIME_DEPENDENCY_SET keywords are +mutually exclusive.

+
+
+

One or more groups of properties may be specified in a single call to +the TARGETS form of this command. A target may be installed more than +once to different locations. Consider hypothetical targets myExe, +mySharedLib, and myStaticLib. The code:

+
install(TARGETS myExe mySharedLib myStaticLib
+        RUNTIME DESTINATION bin
+        LIBRARY DESTINATION lib
+        ARCHIVE DESTINATION lib/static)
+install(TARGETS mySharedLib DESTINATION /some/full/path)
+
+
+

will install myExe to <prefix>/bin and myStaticLib to +<prefix>/lib/static. On non-DLL platforms mySharedLib will be +installed to <prefix>/lib and /some/full/path. On DLL platforms +the mySharedLib DLL will be installed to <prefix>/bin and +/some/full/path and its import library will be installed to +<prefix>/lib/static and /some/full/path.

+

Interface Libraries may be listed among the targets to install. +They install no artifacts but will be included in an associated EXPORT. +If Object Libraries are listed but given no destination for their +object files, they will be exported as Interface Libraries. +This is sufficient to satisfy transitive usage requirements of other +targets that link to the object libraries in their implementation.

+

Installing a target with the EXCLUDE_FROM_ALL target property +set to TRUE has undefined behavior.

+
+

New in version 3.3: An install destination given as a DESTINATION argument may +use "generator expressions" with the syntax $<...>. See the +cmake-generator-expressions(7) manual for available expressions.

+
+
+

New in version 3.13: install(TARGETS) can install targets that were created in +other directories. When using such cross-directory install rules, running +make install (or similar) from a subdirectory will not guarantee that +targets from other directories are up-to-date. You can use +target_link_libraries() or add_dependencies() +to ensure that such out-of-directory targets are built before the +subdirectory-specific install rules are run.

+
+
+
+

Installing Imported Runtime Artifacts

+
+

New in version 3.21.

+
+
install(IMPORTED_RUNTIME_ARTIFACTS targets...
+        [RUNTIME_DEPENDENCY_SET <set-name>]
+        [[LIBRARY|RUNTIME|FRAMEWORK|BUNDLE]
+         [DESTINATION <dir>]
+         [PERMISSIONS permissions...]
+         [CONFIGURATIONS [Debug|Release|...]]
+         [COMPONENT <component>]
+         [OPTIONAL] [EXCLUDE_FROM_ALL]
+        ] [...]
+        )
+
+
+

The IMPORTED_RUNTIME_ARTIFACTS form specifies rules for installing the +runtime artifacts of imported targets. Projects may do this if they want to +bundle outside executables or modules inside their installation. The +LIBRARY, RUNTIME, FRAMEWORK, and BUNDLE arguments have the +same semantics that they do in the TARGETS mode. Only the runtime artifacts +of imported targets are installed (except in the case of FRAMEWORK +libraries, MACOSX_BUNDLE executables, and BUNDLE +CFBundles.) For example, headers and import libraries associated with DLLs are +not installed. In the case of FRAMEWORK libraries, +MACOSX_BUNDLE executables, and BUNDLE CFBundles, the +entire directory is installed.

+

The RUNTIME_DEPENDENCY_SET option causes the runtime artifacts of the +imported executable, shared library, and module library targets to be +added to the <set-name> runtime dependency set. This set can then be +installed with an install(RUNTIME_DEPENDENCY_SET) command.

+
+
+

Installing Files

+
+

Note

+

If installing header files, consider using file sets defined by +target_sources(FILE_SET) instead. File sets associate +headers with a target and they install as part of the target.

+
+
install(<FILES|PROGRAMS> files...
+        TYPE <type> | DESTINATION <dir>
+        [PERMISSIONS permissions...]
+        [CONFIGURATIONS [Debug|Release|...]]
+        [COMPONENT <component>]
+        [RENAME <name>] [OPTIONAL] [EXCLUDE_FROM_ALL])
+
+
+

The FILES form specifies rules for installing files for a project. +File names given as relative paths are interpreted with respect to the +current source directory. Files installed by this form are by default +given permissions OWNER_WRITE, OWNER_READ, GROUP_READ, and +WORLD_READ if no PERMISSIONS argument is given.

+

The PROGRAMS form is identical to the FILES form except that the +default permissions for the installed file also include OWNER_EXECUTE, +GROUP_EXECUTE, and WORLD_EXECUTE. This form is intended to install +programs that are not targets, such as shell scripts. Use the TARGETS +form to install targets built within the project.

+

The list of files... given to FILES or PROGRAMS may use +"generator expressions" with the syntax $<...>. See the +cmake-generator-expressions(7) manual for available expressions. +However, if any item begins in a generator expression it must evaluate +to a full path.

+

Either a TYPE or a DESTINATION must be provided, but not both. +A TYPE argument specifies the generic file type of the files being +installed. A destination will then be set automatically by taking the +corresponding variable from GNUInstallDirs, or by using a +built-in default if that variable is not defined. See the table below for +the supported file types and their corresponding variables and built-in +defaults. Projects can provide a DESTINATION argument instead of a +file type if they wish to explicitly define the install destination.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

TYPE Argument

GNUInstallDirs Variable

Built-In Default

BIN

${CMAKE_INSTALL_BINDIR}

bin

SBIN

${CMAKE_INSTALL_SBINDIR}

sbin

LIB

${CMAKE_INSTALL_LIBDIR}

lib

INCLUDE

${CMAKE_INSTALL_INCLUDEDIR}

include

SYSCONF

${CMAKE_INSTALL_SYSCONFDIR}

etc

SHAREDSTATE

${CMAKE_INSTALL_SHARESTATEDIR}

com

LOCALSTATE

${CMAKE_INSTALL_LOCALSTATEDIR}

var

RUNSTATE

${CMAKE_INSTALL_RUNSTATEDIR}

<LOCALSTATE dir>/run

DATA

${CMAKE_INSTALL_DATADIR}

<DATAROOT dir>

INFO

${CMAKE_INSTALL_INFODIR}

<DATAROOT dir>/info

LOCALE

${CMAKE_INSTALL_LOCALEDIR}

<DATAROOT dir>/locale

MAN

${CMAKE_INSTALL_MANDIR}

<DATAROOT dir>/man

DOC

${CMAKE_INSTALL_DOCDIR}

<DATAROOT dir>/doc

+

Projects wishing to follow the common practice of installing headers into a +project-specific subdirectory will need to provide a destination rather than +rely on the above. Using file sets for headers instead of install(FILES) +would be even better (see target_sources(FILE_SET)).

+

Note that some of the types' built-in defaults use the DATAROOT directory as +a prefix. The DATAROOT prefix is calculated similarly to the types, with +CMAKE_INSTALL_DATAROOTDIR as the variable and share as the built-in +default. You cannot use DATAROOT as a TYPE parameter; please use +DATA instead.

+

To make packages compliant with distribution filesystem layout policies, if +projects must specify a DESTINATION, it is recommended that they use a +path that begins with the appropriate GNUInstallDirs variable. +This allows package maintainers to control the install destination by setting +the appropriate cache variables. The following example shows how to follow +this advice while installing an image to a project-specific documentation +subdirectory:

+
include(GNUInstallDirs)
+install(FILES logo.png
+        DESTINATION ${CMAKE_INSTALL_DOCDIR}/myproj
+)
+
+
+
+

New in version 3.4: An install destination given as a DESTINATION argument may +use "generator expressions" with the syntax $<...>. See the +cmake-generator-expressions(7) manual for available expressions.

+
+
+

New in version 3.20: An install rename given as a RENAME argument may +use "generator expressions" with the syntax $<...>. See the +cmake-generator-expressions(7) manual for available expressions.

+
+
+
+

Installing Directories

+
+

Note

+

To install a directory sub-tree of headers, consider using file sets +defined by target_sources(FILE_SET) instead. File sets not only +preserve directory structure, they also associate headers with a target +and install as part of the target.

+
+
install(DIRECTORY dirs...
+        TYPE <type> | DESTINATION <dir>
+        [FILE_PERMISSIONS permissions...]
+        [DIRECTORY_PERMISSIONS permissions...]
+        [USE_SOURCE_PERMISSIONS] [OPTIONAL] [MESSAGE_NEVER]
+        [CONFIGURATIONS [Debug|Release|...]]
+        [COMPONENT <component>] [EXCLUDE_FROM_ALL]
+        [FILES_MATCHING]
+        [[PATTERN <pattern> | REGEX <regex>]
+         [EXCLUDE] [PERMISSIONS permissions...]] [...])
+
+
+

The DIRECTORY form installs contents of one or more directories to a +given destination. The directory structure is copied verbatim to the +destination. The last component of each directory name is appended to +the destination directory but a trailing slash may be used to avoid +this because it leaves the last component empty. Directory names +given as relative paths are interpreted with respect to the current +source directory. If no input directory names are given the +destination directory will be created but nothing will be installed +into it. The FILE_PERMISSIONS and DIRECTORY_PERMISSIONS options +specify permissions given to files and directories in the destination. +If USE_SOURCE_PERMISSIONS is specified and FILE_PERMISSIONS is not, +file permissions will be copied from the source directory structure. +If no permissions are specified files will be given the default +permissions specified in the FILES form of the command, and the +directories will be given the default permissions specified in the +PROGRAMS form of the command.

+
+

New in version 3.1: The MESSAGE_NEVER option disables file installation status output.

+
+

Installation of directories may be controlled with fine granularity +using the PATTERN or REGEX options. These "match" options specify a +globbing pattern or regular expression to match directories or files +encountered within input directories. They may be used to apply +certain options (see below) to a subset of the files and directories +encountered. The full path to each input file or directory (with +forward slashes) is matched against the expression. A PATTERN will +match only complete file names: the portion of the full path matching +the pattern must occur at the end of the file name and be preceded by +a slash. A REGEX will match any portion of the full path but it may +use / and $ to simulate the PATTERN behavior. By default all +files and directories are installed whether or not they are matched. +The FILES_MATCHING option may be given before the first match option +to disable installation of files (but not directories) not matched by +any expression. For example, the code

+
install(DIRECTORY src/ DESTINATION doc/myproj
+        FILES_MATCHING PATTERN "*.png")
+
+
+

will extract and install images from a source tree.

+

Some options may follow a PATTERN or REGEX expression as described +under string(REGEX) and are applied +only to files or directories matching them. The EXCLUDE option will +skip the matched file or directory. The PERMISSIONS option overrides +the permissions setting for the matched file or directory. For +example the code

+
install(DIRECTORY icons scripts/ DESTINATION share/myproj
+        PATTERN "CVS" EXCLUDE
+        PATTERN "scripts/*"
+        PERMISSIONS OWNER_EXECUTE OWNER_WRITE OWNER_READ
+                    GROUP_EXECUTE GROUP_READ)
+
+
+

will install the icons directory to share/myproj/icons and the +scripts directory to share/myproj. The icons will get default +file permissions, the scripts will be given specific permissions, and any +CVS directories will be excluded.

+

Either a TYPE or a DESTINATION must be provided, but not both. +A TYPE argument specifies the generic file type of the files within the +listed directories being installed. A destination will then be set +automatically by taking the corresponding variable from +GNUInstallDirs, or by using a built-in default if that variable +is not defined. See the table below for the supported file types and their +corresponding variables and built-in defaults. Projects can provide a +DESTINATION argument instead of a file type if they wish to explicitly +define the install destination.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

TYPE Argument

GNUInstallDirs Variable

Built-In Default

BIN

${CMAKE_INSTALL_BINDIR}

bin

SBIN

${CMAKE_INSTALL_SBINDIR}

sbin

LIB

${CMAKE_INSTALL_LIBDIR}

lib

INCLUDE

${CMAKE_INSTALL_INCLUDEDIR}

include

SYSCONF

${CMAKE_INSTALL_SYSCONFDIR}

etc

SHAREDSTATE

${CMAKE_INSTALL_SHARESTATEDIR}

com

LOCALSTATE

${CMAKE_INSTALL_LOCALSTATEDIR}

var

RUNSTATE

${CMAKE_INSTALL_RUNSTATEDIR}

<LOCALSTATE dir>/run

DATA

${CMAKE_INSTALL_DATADIR}

<DATAROOT dir>

INFO

${CMAKE_INSTALL_INFODIR}

<DATAROOT dir>/info

LOCALE

${CMAKE_INSTALL_LOCALEDIR}

<DATAROOT dir>/locale

MAN

${CMAKE_INSTALL_MANDIR}

<DATAROOT dir>/man

DOC

${CMAKE_INSTALL_DOCDIR}

<DATAROOT dir>/doc

+

Note that some of the types' built-in defaults use the DATAROOT directory as +a prefix. The DATAROOT prefix is calculated similarly to the types, with +CMAKE_INSTALL_DATAROOTDIR as the variable and share as the built-in +default. You cannot use DATAROOT as a TYPE parameter; please use +DATA instead.

+

To make packages compliant with distribution filesystem layout policies, if +projects must specify a DESTINATION, it is recommended that they use a +path that begins with the appropriate GNUInstallDirs variable. +This allows package maintainers to control the install destination by setting +the appropriate cache variables.

+
+

New in version 3.4: An install destination given as a DESTINATION argument may +use "generator expressions" with the syntax $<...>. See the +cmake-generator-expressions(7) manual for available expressions.

+
+
+

New in version 3.5: The list of dirs... given to DIRECTORY may use +"generator expressions" too.

+
+
+
+

Custom Installation Logic

+
install([[SCRIPT <file>] [CODE <code>]]
+        [ALL_COMPONENTS | COMPONENT <component>]
+        [EXCLUDE_FROM_ALL] [...])
+
+
+

The SCRIPT form will invoke the given CMake script files during +installation. If the script file name is a relative path it will be +interpreted with respect to the current source directory. The CODE +form will invoke the given CMake code during installation. Code is +specified as a single argument inside a double-quoted string. For +example, the code

+
install(CODE "MESSAGE(\"Sample install message.\")")
+
+
+

will print a message during installation.

+
+

New in version 3.21: When the ALL_COMPONENTS option is given, the custom installation +script code will be executed for every component of a component-specific +installation. This option is mutually exclusive with the COMPONENT +option.

+
+
+

New in version 3.14: <file> or <code> may use "generator expressions" with the syntax +$<...> (in the case of <file>, this refers to their use in the file +name, not the file's contents). See the +cmake-generator-expressions(7) manual for available expressions.

+
+
+
+

Installing Exports

+
install(EXPORT <export-name> DESTINATION <dir>
+        [NAMESPACE <namespace>] [FILE <name>.cmake]
+        [PERMISSIONS permissions...]
+        [CONFIGURATIONS [Debug|Release|...]
+        [CXX_MODULES_DIRECTORY <directory>]
+        [EXPORT_LINK_INTERFACE_LIBRARIES]
+        [COMPONENT <component>]
+        [EXCLUDE_FROM_ALL])
+install(EXPORT_ANDROID_MK <export-name> DESTINATION <dir> [...])
+
+
+

The EXPORT form generates and installs a CMake file containing code to +import targets from the installation tree into another project. +Target installations are associated with the export <export-name> +using the EXPORT option of the install(TARGETS) signature +documented above. The NAMESPACE option will prepend <namespace> to +the target names as they are written to the import file. By default +the generated file will be called <export-name>.cmake but the FILE +option may be used to specify a different name. The value given to +the FILE option must be a file name with the .cmake extension. +If a CONFIGURATIONS option is given then the file will only be installed +when one of the named configurations is installed. Additionally, the +generated import file will reference only the matching target +configurations. See the CMAKE_MAP_IMPORTED_CONFIG_<CONFIG> +variable to map configurations of dependent projects to the installed +configurations. The EXPORT_LINK_INTERFACE_LIBRARIES keyword, if +present, causes the contents of the properties matching +(IMPORTED_)?LINK_INTERFACE_LIBRARIES(_<CONFIG>)? to be exported, when +policy CMP0022 is NEW.

+
+

Note

+

The installed <export-name>.cmake file may come with additional +per-configuration <export-name>-*.cmake files to be loaded by +globbing. Do not use an export name that is the same as the package +name in combination with installing a <package-name>-config.cmake +file or the latter may be incorrectly matched by the glob and loaded.

+
+

When a COMPONENT option is given, the listed <component> implicitly +depends on all components mentioned in the export set. The exported +<name>.cmake file will require each of the exported components to be +present in order for dependent projects to build properly. For example, a +project may define components Runtime and Development, with shared +libraries going into the Runtime component and static libraries and +headers going into the Development component. The export set would also +typically be part of the Development component, but it would export +targets from both the Runtime and Development components. Therefore, +the Runtime component would need to be installed if the Development +component was installed, but not vice versa. If the Development component +was installed without the Runtime component, dependent projects that try +to link against it would have build errors. Package managers, such as APT and +RPM, typically handle this by listing the Runtime component as a dependency +of the Development component in the package metadata, ensuring that the +library is always installed if the headers and CMake export file are present.

+
+

New in version 3.7: In addition to cmake language files, the EXPORT_ANDROID_MK mode may be +used to specify an export to the android ndk build system. This mode +accepts the same options as the normal export mode. The Android +NDK supports the use of prebuilt libraries, both static and shared. This +allows cmake to build the libraries of a project and make them available +to an ndk build system complete with transitive dependencies, include flags +and defines required to use the libraries.

+
+

CXX_MODULES_DIRECTORY

+
+
+

Note

+

Experimental. Gated by CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API

+
+

Specify a subdirectory to store C++ module information for targets in the +export set. This directory will be populated with files which add the +necessary target property information to the relevant targets. Note that +without this information, none of the C++ modules which are part of the +targets in the export set will support being imported in consuming targets.

+
+

The EXPORT form is useful to help outside projects use targets built +and installed by the current project. For example, the code

+
install(TARGETS myexe EXPORT myproj DESTINATION bin)
+install(EXPORT myproj NAMESPACE mp_ DESTINATION lib/myproj)
+install(EXPORT_ANDROID_MK myproj DESTINATION share/ndk-modules)
+
+
+

will install the executable myexe to <prefix>/bin and code to import +it in the file <prefix>/lib/myproj/myproj.cmake and +<prefix>/share/ndk-modules/Android.mk. An outside project +may load this file with the include command and reference the myexe +executable from the installation tree using the imported target name +mp_myexe as if the target were built in its own tree.

+
+

Note

+

This command supersedes the install_targets() command and +the PRE_INSTALL_SCRIPT and POST_INSTALL_SCRIPT +target properties. It also replaces the FILES forms of the +install_files() and install_programs() commands. +The processing order of these install rules relative to +those generated by install_targets(), +install_files(), and install_programs() commands +is not defined.

+
+
+
+

Installing Runtime Dependencies

+
+

New in version 3.21.

+
+
install(RUNTIME_DEPENDENCY_SET <set-name>
+        [[LIBRARY|RUNTIME|FRAMEWORK]
+         [DESTINATION <dir>]
+         [PERMISSIONS permissions...]
+         [CONFIGURATIONS [Debug|Release|...]]
+         [COMPONENT <component>]
+         [NAMELINK_COMPONENT <component>]
+         [OPTIONAL] [EXCLUDE_FROM_ALL]
+        ] [...]
+        [PRE_INCLUDE_REGEXES regexes...]
+        [PRE_EXCLUDE_REGEXES regexes...]
+        [POST_INCLUDE_REGEXES regexes...]
+        [POST_EXCLUDE_REGEXES regexes...]
+        [POST_INCLUDE_FILES files...]
+        [POST_EXCLUDE_FILES files...]
+        [DIRECTORIES directories...]
+        )
+
+
+

Installs a runtime dependency set previously created by one or more +install(TARGETS) or install(IMPORTED_RUNTIME_ARTIFACTS) commands. The +dependencies of targets belonging to a runtime dependency set are installed in +the RUNTIME destination and component on DLL platforms, and in the +LIBRARY destination and component on non-DLL platforms. macOS frameworks +are installed in the FRAMEWORK destination and component. +Targets built within the build tree will never be installed as runtime +dependencies, nor will their own dependencies, unless the targets themselves +are installed with install(TARGETS).

+

The generated install script calls file(GET_RUNTIME_DEPENDENCIES) +on the build-tree files to calculate the runtime dependencies. The build-tree +executable files are passed as the EXECUTABLES argument, the build-tree +shared libraries as the LIBRARIES argument, and the build-tree modules as +the MODULES argument. On macOS, if one of the executables is a +MACOSX_BUNDLE, that executable is passed as the +BUNDLE_EXECUTABLE argument. At most one such bundle executable may be in +the runtime dependency set on macOS. The MACOSX_BUNDLE property +has no effect on other platforms. Note that +file(GET_RUNTIME_DEPENDENCIES) only supports collecting the runtime +dependencies for Windows, Linux and macOS platforms, so +install(RUNTIME_DEPENDENCY_SET) has the same limitation.

+

The following sub-arguments are forwarded through as the corresponding +arguments to file(GET_RUNTIME_DEPENDENCIES) (for those that provide +a non-empty list of directories, regular expressions or files). They all +support generator expressions.

+
    +
  • DIRECTORIES <directories>

  • +
  • PRE_INCLUDE_REGEXES <regexes>

  • +
  • PRE_EXCLUDE_REGEXES <regexes>

  • +
  • POST_INCLUDE_REGEXES <regexes>

  • +
  • POST_EXCLUDE_REGEXES <regexes>

  • +
  • POST_INCLUDE_FILES <files>

  • +
  • POST_EXCLUDE_FILES <files>

  • +
+
+
+

Generated Installation Script

+
+

Note

+

Use of this feature is not recommended. Please consider using the +cmake --install instead.

+
+

The install() command generates a file, cmake_install.cmake, inside +the build directory, which is used internally by the generated install target +and by CPack. You can also invoke this script manually with +cmake -P. This script accepts several variables:

+
+
COMPONENT

Set this variable to install only a single CPack component as opposed to all +of them. For example, if you only want to install the Development +component, run cmake -DCOMPONENT=Development -P cmake_install.cmake.

+
+
BUILD_TYPE

Set this variable to change the build type if you are using a multi-config +generator. For example, to install with the Debug configuration, run +cmake -DBUILD_TYPE=Debug -P cmake_install.cmake.

+
+
DESTDIR

This is an environment variable rather than a CMake variable. It allows you +to change the installation prefix on UNIX systems. See DESTDIR for +details.

+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install_files.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install_files.html new file mode 100644 index 0000000000000000000000000000000000000000..5eb10437cdde78f08197f7c938adfeec9c8c4a8b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install_files.html @@ -0,0 +1,168 @@ + + + + + + + + + install_files — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

install_files

+
+

Deprecated since version 3.0: Use the install(FILES) command instead.

+
+

This command has been superseded by the install() command. It is +provided for compatibility with older CMake code. The FILES form is +directly replaced by the FILES form of the install() +command. The regexp form can be expressed more clearly using the GLOB +form of the file() command.

+
install_files(<dir> extension file file ...)
+
+
+

Create rules to install the listed files with the given extension into +the given directory. Only files existing in the current source tree +or its corresponding location in the binary tree may be listed. If a +file specified already has an extension, that extension will be +removed first. This is useful for providing lists of source files +such as foo.cxx when you want the corresponding foo.h to be installed. +A typical extension is .h.

+
install_files(<dir> regexp)
+
+
+

Any files in the current source directory that match the regular +expression will be installed.

+
install_files(<dir> FILES file file ...)
+
+
+

Any files listed after the FILES keyword will be installed explicitly +from the names given. Full paths are allowed in this form.

+

The directory <dir> is relative to the installation prefix, which is +stored in the variable CMAKE_INSTALL_PREFIX.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install_programs.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install_programs.html new file mode 100644 index 0000000000000000000000000000000000000000..ce92d3c5fadb1eaa18b96c8a13cdf4c5ee1bcbaf --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install_programs.html @@ -0,0 +1,164 @@ + + + + + + + + + install_programs — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

install_programs

+
+

Deprecated since version 3.0: Use the install(PROGRAMS) command instead.

+
+

This command has been superseded by the install() command. It is +provided for compatibility with older CMake code. The FILES form is +directly replaced by the PROGRAMS form of the install() +command. The regexp form can be expressed more clearly using the GLOB +form of the file() command.

+
install_programs(<dir> file1 file2 [file3 ...])
+install_programs(<dir> FILES file1 [file2 ...])
+
+
+

Create rules to install the listed programs into the given directory. +Use the FILES argument to guarantee that the file list version of the +command will be used even when there is only one argument.

+
install_programs(<dir> regexp)
+
+
+

In the second form any program in the current source directory that +matches the regular expression will be installed.

+

This command is intended to install programs that are not built by +cmake, such as shell scripts. See the TARGETS form of the +install() command to create installation rules for targets built +by cmake.

+

The directory <dir> is relative to the installation prefix, which is +stored in the variable CMAKE_INSTALL_PREFIX.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install_targets.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install_targets.html new file mode 100644 index 0000000000000000000000000000000000000000..0dd8b2b732b9b89c0a1606e93c78951a6bd9a49e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/install_targets.html @@ -0,0 +1,151 @@ + + + + + + + + + install_targets — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

install_targets

+
+

Deprecated since version 3.0: Use the install(TARGETS) command instead.

+
+

This command has been superseded by the install() command. It is +provided for compatibility with older CMake code.

+
install_targets(<dir> [RUNTIME_DIRECTORY dir] target target)
+
+
+

Create rules to install the listed targets into the given directory. +The directory <dir> is relative to the installation prefix, which is +stored in the variable CMAKE_INSTALL_PREFIX. If +RUNTIME_DIRECTORY is specified, then on systems with special runtime +files (Windows DLL), the files will be copied to that directory.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/link_directories.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/link_directories.html new file mode 100644 index 0000000000000000000000000000000000000000..2e7d0fb34e1b4f167277d6d3511e6d86610bbeca --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/link_directories.html @@ -0,0 +1,204 @@ + + + + + + + + + link_directories — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/link_libraries.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/link_libraries.html new file mode 100644 index 0000000000000000000000000000000000000000..08cacc10b6f7a2d2fed9797dd42156ac3863cabc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/link_libraries.html @@ -0,0 +1,153 @@ + + + + + + + + + link_libraries — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/list.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/list.html new file mode 100644 index 0000000000000000000000000000000000000000..188ff1e21a0a5f363e137f49b249fd9235e47313 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/list.html @@ -0,0 +1,502 @@ + + + + + + + + + list — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

list

+

Operations on semicolon-separated lists.

+
+

Synopsis

+
Reading
+  list(LENGTH <list> <out-var>)
+  list(GET <list> <element index> [<index> ...] <out-var>)
+  list(JOIN <list> <glue> <out-var>)
+  list(SUBLIST <list> <begin> <length> <out-var>)
+
+Search
+  list(FIND <list> <value> <out-var>)
+
+Modification
+  list(APPEND <list> [<element>...])
+  list(FILTER <list> {INCLUDE | EXCLUDE} REGEX <regex>)
+  list(INSERT <list> <index> [<element>...])
+  list(POP_BACK <list> [<out-var>...])
+  list(POP_FRONT <list> [<out-var>...])
+  list(PREPEND <list> [<element>...])
+  list(REMOVE_ITEM <list> <value>...)
+  list(REMOVE_AT <list> <index>...)
+  list(REMOVE_DUPLICATES <list>)
+  list(TRANSFORM <list> <ACTION> [...])
+
+Ordering
+  list(REVERSE <list>)
+  list(SORT <list> [...])
+
+
+

Introduction

+

The list subcommands APPEND, INSERT, FILTER, +PREPEND, POP_BACK, POP_FRONT, REMOVE_AT, +REMOVE_ITEM, REMOVE_DUPLICATES, REVERSE and +SORT may create new values for the list within the current CMake +variable scope. Similar to the set() command, the list command +creates new variable values in the current scope, even if the list itself is +actually defined in a parent scope. To propagate the results of these +operations upwards, use set() with PARENT_SCOPE, +set() with CACHE INTERNAL, or some other means of value +propagation.

+
+

Note

+

A list in cmake is a ; separated group of strings. To create a +list, the set() command can be used. For example, +set(var a b c d e) creates a list with a;b;c;d;e, and +set(var "a b c d e") creates a string or a list with one item in it. +(Note that macro arguments are not variables, and therefore cannot be used +in LIST commands.)

+

Individual elements may not contain an unequal number of [ and ] +characters, and may not end in a backslash (\). +See semicolon-separated lists for details.

+
+
+

Note

+

When specifying index values, if <element index> is 0 or greater, it +is indexed from the beginning of the list, with 0 representing the +first list element. If <element index> is -1 or lesser, it is indexed +from the end of the list, with -1 representing the last list element. +Be careful when counting with negative indices: they do not start from +0. -0 is equivalent to 0, the first list element.

+
+
+
+

Reading

+
+
+list(LENGTH <list> <output variable>)
+

Returns the list's length.

+
+ +
+
+list(GET <list> <element index> [<element index> ...] <output variable>)
+

Returns the list of elements specified by indices from the list.

+
+ +
+
+list(JOIN <list> <glue> <output variable>)
+
+

New in version 3.12.

+
+

Returns a string joining all list's elements using the glue string. +To join multiple strings, which are not part of a list, +use string(JOIN).

+
+ +
+
+list(SUBLIST <list> <begin> <length> <output variable>)
+
+

New in version 3.12.

+
+

Returns a sublist of the given list. +If <length> is 0, an empty list will be returned. +If <length> is -1 or the list is smaller than <begin>+<length> then +the remaining elements of the list starting at <begin> will be returned.

+
+ +
+ +
+

Modification

+
+
+list(APPEND <list> [<element> ...])
+

Appends elements to the list. If no variable named <list> exists in the +current scope its value is treated as empty and the elements are appended to +that empty list.

+
+ +
+
+list(FILTER <list> <INCLUDE|EXCLUDE> REGEX <regular_expression>)
+
+ +
+

New in version 3.6.

+
+

Includes or removes items from the list that match the mode's pattern. +In REGEX mode, items will be matched against the given regular expression.

+

For more information on regular expressions look under +string(REGEX).

+
+
+list(INSERT <list> <element_index> <element> [<element> ...])
+

Inserts elements to the list to the specified index. It is an +error to specify an out-of-range index. Valid indexes are 0 to N +where N is the length of the list, inclusive. An empty list +has length 0. If no variable named <list> exists in the +current scope its value is treated as empty and the elements are +inserted in that empty list.

+
+ +
+
+list(POP_BACK <list> [<out-var>...])
+
+

New in version 3.15.

+
+

If no variable name is given, removes exactly one element. Otherwise, +with N variable names provided, assign the last N elements' values +to the given variables and then remove the last N values from +<list>.

+
+ +
+
+list(POP_FRONT <list> [<out-var>...])
+
+

New in version 3.15.

+
+

If no variable name is given, removes exactly one element. Otherwise, +with N variable names provided, assign the first N elements' values +to the given variables and then remove the first N values from +<list>.

+
+ +
+
+list(PREPEND <list> [<element> ...])
+
+

New in version 3.15.

+
+

Insert elements to the 0th position in the list. If no variable named +<list> exists in the current scope its value is treated as empty and +the elements are prepended to that empty list.

+
+ +
+
+list(REMOVE_ITEM <list> <value> [<value> ...])
+

Removes all instances of the given items from the list.

+
+ +
+
+list(REMOVE_AT <list> <index> [<index> ...])
+

Removes items at given indices from the list.

+
+ +
+
+list(REMOVE_DUPLICATES <list>)
+

Removes duplicated items in the list. The relative order of items +is preserved, but if duplicates are encountered, +only the first instance is preserved.

+
+ +
+
+list(TRANSFORM <list> <ACTION> [<SELECTOR>] [OUTPUT_VARIABLE <output variable>])
+
+

New in version 3.12.

+
+

Transforms the list by applying an <ACTION> to all or, by specifying a +<SELECTOR>, to the selected elements of the list, storing the result +in-place or in the specified output variable.

+
+

Note

+

The TRANSFORM sub-command does not change the number of elements in the +list. If a <SELECTOR> is specified, only some elements will be changed, +the other ones will remain the same as before the transformation.

+
+

<ACTION> specifies the action to apply to the elements of the list. +The actions have exactly the same semantics as sub-commands of the +string() command. <ACTION> must be one of the following:

+
+
+
APPEND, PREPEND

Append, prepend specified value to each element of the list.

+
+
+list(TRANSFORM <list> (APPEND|PREPEND) <value> ...)
+
+ +
+
TOLOWER, TOUPPER

Convert each element of the list to lower, upper characters.

+
+
+list(TRANSFORM <list> (TOLOWER|TOUPPER) ...)
+
+ +
+
STRIP

Remove leading and trailing spaces from each element of the list.

+
+
+list(TRANSFORM <list> STRIP ...)
+
+ +
+
GENEX_STRIP

Strip any +generator expressions +from each element of the list.

+
+
+list(TRANSFORM <list> GENEX_STRIP ...)
+
+ +
+
REPLACE:

Match the regular expression as many times as possible and substitute +the replacement expression for the match for each element of the list +(same semantic as string(REGEX REPLACE)).

+
+
+list(TRANSFORM <list> REPLACE <regular_expression> <replace_expression> ...)
+
+ +
+
+
+

<SELECTOR> determines which elements of the list will be transformed. +Only one type of selector can be specified at a time. +When given, <SELECTOR> must be one of the following:

+
+
+
AT

Specify a list of indexes.

+
list(TRANSFORM <list> <ACTION> AT <index> [<index> ...] ...)
+
+
+
+
FOR

Specify a range with, optionally, +an increment used to iterate over the range.

+
list(TRANSFORM <list> <ACTION> FOR <start> <stop> [<step>] ...)
+
+
+
+
REGEX

Specify a regular expression. +Only elements matching the regular expression will be transformed.

+
list(TRANSFORM <list> <ACTION> REGEX <regular_expression> ...)
+
+
+
+
+
+
+ +
+
+

Ordering

+
+
+list(REVERSE <list>)
+

Reverses the contents of the list in-place.

+
+ +
+
+list(SORT <list> [COMPARE <compare>] [CASE <case>] [ORDER <order>])
+

Sorts the list in-place alphabetically.

+
+

New in version 3.13: Added the COMPARE, CASE, and ORDER options.

+
+
+

New in version 3.18: Added the COMPARE NATURAL option.

+
+

Use the COMPARE keyword to select the comparison method for sorting. +The <compare> option should be one of:

+
+
+
STRING

Sorts a list of strings alphabetically. +This is the default behavior if the COMPARE option is not given.

+
+
FILE_BASENAME

Sorts a list of pathnames of files by their basenames.

+
+
NATURAL

Sorts a list of strings using natural order +(see strverscmp(3) manual), i.e. such that contiguous digits +are compared as whole numbers. +For example: the following list 10.0 1.1 2.1 8.0 2.0 3.1 +will be sorted as 1.1 2.0 2.1 3.1 8.0 10.0 if the NATURAL +comparison is selected where it will be sorted as +1.1 10.0 2.0 2.1 3.1 8.0 with the STRING comparison.

+
+
+
+

Use the CASE keyword to select a case sensitive or case insensitive +sort mode. The <case> option should be one of:

+
+
+
SENSITIVE

List items are sorted in a case-sensitive manner. +This is the default behavior if the CASE option is not given.

+
+
INSENSITIVE

List items are sorted case insensitively. The order of +items which differ only by upper/lowercase is not specified.

+
+
+
+

To control the sort order, the ORDER keyword can be given. +The <order> option should be one of:

+
+
+
ASCENDING

Sorts the list in ascending order. +This is the default behavior when the ORDER option is not given.

+
+
DESCENDING

Sorts the list in descending order.

+
+
+
+
+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/load_cache.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/load_cache.html new file mode 100644 index 0000000000000000000000000000000000000000..7e3d80dcab02adef7dd73a3834503661d419205f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/load_cache.html @@ -0,0 +1,157 @@ + + + + + + + + + load_cache — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

load_cache

+

Load in the values from another project's CMake cache.

+
load_cache(pathToBuildDirectory READ_WITH_PREFIX prefix entry1...)
+
+
+

Reads the cache and store the requested entries in variables with their +name prefixed with the given prefix. This only reads the values, and +does not create entries in the local project's cache.

+
load_cache(pathToBuildDirectory [EXCLUDE entry1...]
+           [INCLUDE_INTERNALS entry1...])
+
+
+

Loads in the values from another cache and store them in the local +project's cache as internal entries. This is useful for a project +that depends on another project built in a different tree. EXCLUDE +option can be used to provide a list of entries to be excluded. +INCLUDE_INTERNALS can be used to provide a list of internal entries to +be included. Normally, no internal entries are brought in. Use of +this form of the command is strongly discouraged, but it is provided +for backward compatibility.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/load_command.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/load_command.html new file mode 100644 index 0000000000000000000000000000000000000000..7a7b5ece3ce762072f4ac8456c52633ba7595706 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/load_command.html @@ -0,0 +1,153 @@ + + + + + + + + + load_command — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

load_command

+

Disallowed since version 3.0. See CMake Policy CMP0031.

+

Load a command into a running CMake.

+
load_command(COMMAND_NAME <loc1> [loc2 ...])
+
+
+

The given locations are searched for a library whose name is +cmCOMMAND_NAME. If found, it is loaded as a module and the command is +added to the set of available CMake commands. Usually, +try_compile() is used before this command to compile the +module. If the command is successfully loaded a variable named

+
CMAKE_LOADED_COMMAND_<COMMAND_NAME>
+
+
+

will be set to the full path of the module that was loaded. Otherwise +the variable will not be set.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/macro.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/macro.html new file mode 100644 index 0000000000000000000000000000000000000000..2133da480cd5e0879afe77bdd06ed43311005c92 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/macro.html @@ -0,0 +1,279 @@ + + + + + + + + + macro — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

macro

+

Start recording a macro for later invocation as a command

+
macro(<name> [<arg1> ...])
+  <commands>
+endmacro()
+
+
+

Defines a macro named <name> that takes arguments named +<arg1>, ... Commands listed after macro, but before the +matching endmacro(), are not executed until the macro +is invoked.

+

Per legacy, the endmacro() command admits an optional +<name> argument. If used, it must be a verbatim repeat of the +argument of the opening macro command.

+

See the cmake_policy() command documentation for the behavior +of policies inside macros.

+

See the Macro vs Function section below for differences +between CMake macros and functions.

+
+

Invocation

+

The macro invocation is case-insensitive. A macro defined as

+
macro(foo)
+  <commands>
+endmacro()
+
+
+

can be invoked through any of

+
foo()
+Foo()
+FOO()
+cmake_language(CALL foo)
+
+
+

and so on. However, it is strongly recommended to stay with the +case chosen in the macro definition. Typically macros use +all-lowercase names.

+
+

New in version 3.18: The cmake_language(CALL ...) command can also be used to +invoke the macro.

+
+
+
+

Arguments

+

When a macro is invoked, the commands recorded in the macro are +first modified by replacing formal parameters (${arg1}, ...) +with the arguments passed, and then invoked as normal commands.

+

In addition to referencing the formal parameters you can reference the +values ${ARGC} which will be set to the number of arguments passed +into the function as well as ${ARGV0}, ${ARGV1}, ${ARGV2}, +... which will have the actual values of the arguments passed in. +This facilitates creating macros with optional arguments.

+

Furthermore, ${ARGV} holds the list of all arguments given to the +macro and ${ARGN} holds the list of arguments past the last expected +argument. +Referencing to ${ARGV#} arguments beyond ${ARGC} have undefined +behavior. Checking that ${ARGC} is greater than # is the only +way to ensure that ${ARGV#} was passed to the function as an extra +argument.

+
+
+

Macro vs Function

+

The macro command is very similar to the function() command. +Nonetheless, there are a few important differences.

+

In a function, ARGN, ARGC, ARGV and ARGV0, ARGV1, ... +are true variables in the usual CMake sense. In a macro, they are not, +they are string replacements much like the C preprocessor would do +with a macro. This has a number of consequences, as explained in +the Argument Caveats section below.

+

Another difference between macros and functions is the control flow. +A function is executed by transferring control from the calling +statement to the function body. A macro is executed as if the macro +body were pasted in place of the calling statement. This has the +consequence that a return() in a macro body does not +just terminate execution of the macro; rather, control is returned +from the scope of the macro call. To avoid confusion, it is recommended +to avoid return() in macros altogether.

+

Unlike a function, the CMAKE_CURRENT_FUNCTION, +CMAKE_CURRENT_FUNCTION_LIST_DIR, +CMAKE_CURRENT_FUNCTION_LIST_FILE, +CMAKE_CURRENT_FUNCTION_LIST_LINE variables are not +set for a macro.

+
+
+

Argument Caveats

+

Since ARGN, ARGC, ARGV, ARGV0 etc. are not variables, +you will NOT be able to use commands like

+
if(ARGV1) # ARGV1 is not a variable
+if(DEFINED ARGV2) # ARGV2 is not a variable
+if(ARGC GREATER 2) # ARGC is not a variable
+foreach(loop_var IN LISTS ARGN) # ARGN is not a variable
+
+
+

In the first case, you can use if(${ARGV1}). In the second and +third case, the proper way to check if an optional variable was +passed to the macro is to use if(${ARGC} GREATER 2). In the +last case, you can use foreach(loop_var ${ARGN}) but this will +skip empty arguments. If you need to include them, you can use

+
set(list_var "${ARGN}")
+foreach(loop_var IN LISTS list_var)
+
+
+

Note that if you have a variable with the same name in the scope from +which the macro is called, using unreferenced names will use the +existing variable instead of the arguments. For example:

+
macro(bar)
+  foreach(arg IN LISTS ARGN)
+    <commands>
+  endforeach()
+endmacro()
+
+function(foo)
+  bar(x y z)
+endfunction()
+
+foo(a b c)
+
+
+

Will loop over a;b;c and not over x;y;z as one might have expected. +If you want true CMake variables and/or better CMake scope control you +should look at the function command.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/make_directory.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/make_directory.html new file mode 100644 index 0000000000000000000000000000000000000000..402b0425fec0b8ce3b82a740b4204c39a671e4fa --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/make_directory.html @@ -0,0 +1,147 @@ + + + + + + + + + make_directory — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

make_directory

+
+

Deprecated since version 3.0: Use the file(MAKE_DIRECTORY) command instead.

+
+
make_directory(directory)
+
+
+

Creates the specified directory. Full paths should be given. Any +parent directories that do not exist will also be created. Use with +care.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/mark_as_advanced.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/mark_as_advanced.html new file mode 100644 index 0000000000000000000000000000000000000000..048627778c0377bd5d12b8fab079a246131be316 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/mark_as_advanced.html @@ -0,0 +1,159 @@ + + + + + + + + + mark_as_advanced — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

mark_as_advanced

+

Mark cmake cached variables as advanced.

+
mark_as_advanced([CLEAR|FORCE] <var1> ...)
+
+
+

Sets the advanced/non-advanced state of the named +cached variables.

+

An advanced variable will not be displayed in any +of the cmake GUIs unless the show advanced option is on. +In script mode, the advanced/non-advanced state has no effect.

+

If the keyword CLEAR is given +then advanced variables are changed back to unadvanced. +If the keyword FORCE is given +then the variables are made advanced. +If neither FORCE nor CLEAR is specified, +new values will be marked as advanced, but if a +variable already has an advanced/non-advanced state, +it will not be changed.

+
+

Changed in version 3.17: Variables passed to this command which are not already in the cache +are ignored. See policy CMP0102.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/math.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/math.html new file mode 100644 index 0000000000000000000000000000000000000000..01ffbb47a5f6e8867c1ebce993d4125223b40236 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/math.html @@ -0,0 +1,170 @@ + + + + + + + + + math — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

math

+

Evaluate a mathematical expression.

+
math(EXPR <variable> "<expression>" [OUTPUT_FORMAT <format>])
+
+
+

Evaluates a mathematical <expression> and sets <variable> to the +resulting value. The result of the expression must be representable as a +64-bit signed integer. Floating point inputs are invalid e.g. 1.1 * 10. +Non-integer results e.g. 3 / 2 are truncated.

+

The mathematical expression must be given as a string (i.e. enclosed in +double quotation marks). An example is "5 * (10 + 13)". +Supported operators are +, -, *, /, %, |, &, +^, ~, <<, >>, and (...); they have the same meaning +as in C code.

+
+

New in version 3.13: Hexadecimal numbers are recognized when prefixed with 0x, as in C code.

+
+
+

New in version 3.13: The result is formatted according to the option OUTPUT_FORMAT, +where <format> is one of

+
+
HEXADECIMAL

Hexadecimal notation as in C code, i. e. starting with "0x".

+
+
DECIMAL

Decimal notation. Which is also used if no OUTPUT_FORMAT option +is specified.

+
+
+
+

For example

+
math(EXPR value "100 * 0xA" OUTPUT_FORMAT DECIMAL)      # value is set to "1000"
+math(EXPR value "100 * 0xA" OUTPUT_FORMAT HEXADECIMAL)  # value is set to "0x3e8"
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/message.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/message.html new file mode 100644 index 0000000000000000000000000000000000000000..577fb5f21ca773de9fab441d5cd2278a7029a0fc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/message.html @@ -0,0 +1,372 @@ + + + + + + + + + message — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

message

+

Log a message.

+
+

Synopsis

+
General messages
+  message([<mode>] "message text" ...)
+
+Reporting checks
+  message(<checkState> "message text" ...)
+
+Configure Log
+  message(CONFIGURE_LOG <text>...)
+
+
+

General messages

+
message([<mode>] "message text" ...)
+
+
+

Record the specified message text in the log. If more than one message +string is given, they are concatenated into a single message with no +separator between the strings.

+

The optional <mode> keyword determines the type of message, which +influences the way the message is handled:

+
+
FATAL_ERROR

CMake Error, stop processing and generation.

+

The cmake(1) executable will return a non-zero +exit code.

+
+
SEND_ERROR

CMake Error, continue processing, but skip generation.

+
+
WARNING

CMake Warning, continue processing.

+
+
AUTHOR_WARNING

CMake Warning (dev), continue processing.

+
+
DEPRECATION

CMake Deprecation Error or Warning if variable +CMAKE_ERROR_DEPRECATED or CMAKE_WARN_DEPRECATED +is enabled, respectively, else no message.

+
+
(none) or NOTICE

Important message printed to stderr to attract user's attention.

+
+
STATUS

The main interesting messages that project users might be interested in. +Ideally these should be concise, no more than a single line, but still +informative.

+
+
VERBOSE

Detailed informational messages intended for project users. These messages +should provide additional details that won't be of interest in most cases, +but which may be useful to those building the project when they want deeper +insight into what's happening.

+
+
DEBUG

Detailed informational messages intended for developers working on the +project itself as opposed to users who just want to build it. These messages +will not typically be of interest to other users building the project and +will often be closely related to internal implementation details.

+
+
TRACE

Fine-grained messages with very low-level implementation details. Messages +using this log level would normally only be temporary and would expect to be +removed before releasing the project, packaging up the files, etc.

+
+
+
+

New in version 3.15: Added the NOTICE, VERBOSE, DEBUG, and TRACE levels.

+
+

The CMake command-line tool displays STATUS to TRACE messages on stdout +with the message preceded by two hyphens and a space. All other message types +are sent to stderr and are not prefixed with hyphens. The +CMake GUI displays all messages in its log area. +The curses interface shows STATUS to TRACE +messages one at a time on a status line and other messages in an +interactive pop-up box. The --log-level +command-line option to each of these tools can be used to control which +messages will be shown.

+
+

New in version 3.17: To make a log level persist between CMake runs, the +CMAKE_MESSAGE_LOG_LEVEL variable can be set instead. +Note that the command line option takes precedence over the cache variable.

+
+
+

New in version 3.16: Messages of log levels NOTICE and below will have each line preceded +by the content of the CMAKE_MESSAGE_INDENT variable (converted to +a single string by concatenating its list items). For STATUS to TRACE +messages, this indenting content will be inserted after the hyphens.

+
+
+

New in version 3.17: Messages of log levels NOTICE and below can also have each line preceded +with context of the form [some.context.example]. The content between the +square brackets is obtained by converting the CMAKE_MESSAGE_CONTEXT +list variable to a dot-separated string. The message context will always +appear before any indenting content but after any automatically added leading +hyphens. By default, message context is not shown, it has to be explicitly +enabled by giving the cmake --log-context +command-line option or by setting the CMAKE_MESSAGE_CONTEXT_SHOW +variable to true. See the CMAKE_MESSAGE_CONTEXT documentation for +usage examples.

+
+

CMake Warning and Error message text displays using a simple markup +language. Non-indented text is formatted in line-wrapped paragraphs +delimited by newlines. Indented text is considered pre-formatted.

+
+
+

Reporting checks

+
+

New in version 3.17.

+
+

A common pattern in CMake output is a message indicating the start of some +sort of check, followed by another message reporting the result of that check. +For example:

+
message(STATUS "Looking for someheader.h")
+#... do the checks, set checkSuccess with the result
+if(checkSuccess)
+  message(STATUS "Looking for someheader.h - found")
+else()
+  message(STATUS "Looking for someheader.h - not found")
+endif()
+
+
+

This can be more robustly and conveniently expressed using the CHECK_... +keyword form of the message() command:

+
message(<checkState> "message" ...)
+
+
+

where <checkState> must be one of the following:

+
+
+
CHECK_START

Record a concise message about the check about to be performed.

+
+
CHECK_PASS

Record a successful result for a check.

+
+
CHECK_FAIL

Record an unsuccessful result for a check.

+
+
+
+

When recording a check result, the command repeats the message from the most +recently started check for which no result has yet been reported, then some +separator characters and then the message text provided after the +CHECK_PASS or CHECK_FAIL keyword. Check messages are always reported +at STATUS log level.

+

Checks may be nested and every CHECK_START should have exactly one +matching CHECK_PASS or CHECK_FAIL. +The CMAKE_MESSAGE_INDENT variable can also be used to add +indenting to nested checks if desired. For example:

+
message(CHECK_START "Finding my things")
+list(APPEND CMAKE_MESSAGE_INDENT "  ")
+unset(missingComponents)
+
+message(CHECK_START "Finding partA")
+# ... do check, assume we find A
+message(CHECK_PASS "found")
+
+message(CHECK_START "Finding partB")
+# ... do check, assume we don't find B
+list(APPEND missingComponents B)
+message(CHECK_FAIL "not found")
+
+list(POP_BACK CMAKE_MESSAGE_INDENT)
+if(missingComponents)
+  message(CHECK_FAIL "missing components: ${missingComponents}")
+else()
+  message(CHECK_PASS "all components found")
+endif()
+
+
+

Output from the above would appear something like the following:

+
-- Finding my things
+--   Finding partA
+--   Finding partA - found
+--   Finding partB
+--   Finding partB - not found
+-- Finding my things - missing components: B
+
+
+
+
+

Configure Log

+
+

New in version 3.26.

+
+
message(CONFIGURE_LOG <text>...)
+
+
+

Record a configure-log message event +with the specified <text>. By convention, if the text contains more +than one line, the first line should be a summary of the event.

+

This mode is intended to record the details of a system inspection check +or other one-time operation guarded by a cache entry, but that is not +performed using try_compile() or try_run(), which +automatically log their details. Projects should avoid calling it every +time CMake runs. For example:

+
if (NOT DEFINED MY_CHECK_RESULT)
+  # Print check summary in configure output.
+  message(CHECK_START "My Check")
+
+  # ... perform system inspection, e.g., with execute_process ...
+
+  # Cache the result so we do not run the check again.
+  set(MY_CHECK_RESULT "${MY_CHECK_RESULT}" CACHE INTERNAL "My Check")
+
+  # Record the check details in the cmake-configure-log.
+  message(CONFIGURE_LOG
+    "My Check Result: ${MY_CHECK_RESULT}\n"
+    "${details}"
+  )
+
+  # Print check result in configure output.
+  if(MY_CHECK_RESULT)
+    message(CHECK_PASS "passed")
+  else()
+    message(CHECK_FAIL "failed")
+  endif()
+endif()
+
+
+

If no project is currently being configured, such as in +cmake -P script mode, +this command does nothing.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/option.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/option.html new file mode 100644 index 0000000000000000000000000000000000000000..27f2a06f99c53b08a1f3431ba70956c63ee49aec --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/option.html @@ -0,0 +1,149 @@ + + + + + + + + + option — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

option

+

Provide a boolean option that the user can optionally select.

+
option(<variable> "<help_text>" [value])
+
+
+

If no initial <value> is provided, boolean OFF is the default value. +If <variable> is already set as a normal or cache variable, +then the command does nothing (see policy CMP0077).

+

For options that depend on the values of other options, see +the module help for CMakeDependentOption.

+

In CMake project mode, a boolean cache variable is created with the option +value. In CMake script mode, a boolean variable is set with the option value.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/output_required_files.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/output_required_files.html new file mode 100644 index 0000000000000000000000000000000000000000..09558758aaf48805869aa23f3c8102261b86b596 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/output_required_files.html @@ -0,0 +1,150 @@ + + + + + + + + + output_required_files — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

output_required_files

+

Disallowed since version 3.0. See CMake Policy CMP0032.

+

Approximate C preprocessor dependency scanning.

+

This command exists only because ancient CMake versions provided it. +CMake handles preprocessor dependency scanning automatically using a +more advanced scanner.

+
output_required_files(srcfile outputfile)
+
+
+

Outputs a list of all the source files that are required by the +specified srcfile. This list is written into outputfile. This is +similar to writing out the dependencies for srcfile except that it +jumps from .h files into .cxx, .c and .cpp files if possible.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/project.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/project.html new file mode 100644 index 0000000000000000000000000000000000000000..639c009ef1f683c361bae441989123abeca4be7b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/project.html @@ -0,0 +1,343 @@ + + + + + + + + + project — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

project

+

Set the name of the project.

+
+

Synopsis

+
project(<PROJECT-NAME> [<language-name>...])
+project(<PROJECT-NAME>
+        [VERSION <major>[.<minor>[.<patch>[.<tweak>]]]]
+        [DESCRIPTION <project-description-string>]
+        [HOMEPAGE_URL <url-string>]
+        [LANGUAGES <language-name>...])
+
+
+

Sets the name of the project, and stores it in the variable +PROJECT_NAME. When called from the top-level +CMakeLists.txt also stores the project name in the +variable CMAKE_PROJECT_NAME.

+

Also sets the variables:

+
+
PROJECT_SOURCE_DIR, <PROJECT-NAME>_SOURCE_DIR

Absolute path to the source directory for the project.

+
+
PROJECT_BINARY_DIR, <PROJECT-NAME>_BINARY_DIR

Absolute path to the binary directory for the project.

+
+
PROJECT_IS_TOP_LEVEL, <PROJECT-NAME>_IS_TOP_LEVEL
+

New in version 3.21.

+
+

Boolean value indicating whether the project is top-level.

+
+
+

Further variables are set by the optional arguments described in the following. +If any of these arguments is not used, then the corresponding variables are +set to the empty string.

+
+
+

Options

+

The options are:

+
+
VERSION <version>

Optional; may not be used unless policy CMP0048 is +set to NEW.

+

Takes a <version> argument composed of non-negative integer components, +i.e. <major>[.<minor>[.<patch>[.<tweak>]]], +and sets the variables

+ +
+

New in version 3.12: When the project() command is called from the top-level +CMakeLists.txt, then the version is also stored in the variable +CMAKE_PROJECT_VERSION.

+
+
+
DESCRIPTION <project-description-string>
+

New in version 3.9.

+
+

Optional. +Sets the variables

+ +

to <project-description-string>. +It is recommended that this description is a relatively short string, +usually no more than a few words.

+

When the project() command is called from the top-level CMakeLists.txt, +then the description is also stored in the variable CMAKE_PROJECT_DESCRIPTION.

+
+

New in version 3.12: Added the <PROJECT-NAME>_DESCRIPTION variable.

+
+
+
HOMEPAGE_URL <url-string>
+

New in version 3.12.

+
+

Optional. +Sets the variables

+ +

to <url-string>, which should be the canonical home URL for the project.

+

When the project() command is called from the top-level CMakeLists.txt, +then the URL also is stored in the variable CMAKE_PROJECT_HOMEPAGE_URL.

+
+
LANGUAGES <language-name>...

Optional. +Can also be specified without LANGUAGES keyword per the first, short signature.

+

Selects which programming languages are needed to build the project.

+
+
+

Supported languages are C, CXX (i.e. C++), CSharp (i.e. C#), CUDA, +OBJC (i.e. Objective-C), OBJCXX (i.e. Objective-C++), Fortran, HIP, +ISPC, Swift, ASM, ASM_NASM, ASM_MARMASM, ASM_MASM, and ASM-ATT.

+
+
+

New in version 3.8: Added CSharp and CUDA support.

+
+
+

New in version 3.15: Added Swift support.

+
+
+

New in version 3.16: Added OBJC and OBJCXX support.

+
+
+

New in version 3.18: Added ISPC support.

+
+
+

New in version 3.21: Added HIP support.

+
+
+

New in version 3.26: Added ASM_MARMASM support.

+
+
+

If enabling ASM, list it last so that CMake can check whether +compilers for other languages like C work for assembly too.

+

By default C and CXX are enabled if no language options are given. +Specify language NONE, or use the LANGUAGES keyword and list no languages, +to skip enabling any languages.

+

The variables set through the VERSION, DESCRIPTION and HOMEPAGE_URL +options are intended for use as default values in package metadata and documentation.

+
+
+

Code Injection

+

A number of variables can be defined by the user to specify files to include +at different points during the execution of the project() command. +The following outlines the steps performed during a project() call:

+
    +
  • +

    New in version 3.15: For every project() call regardless of the project +name, include the file named by CMAKE_PROJECT_INCLUDE_BEFORE, +if set.

    +
    +
  • +
  • +

    New in version 3.17: If the project() command specifies <PROJECT-NAME> as its project +name, include the file named by +CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE, if set.

    +
    +
  • +
  • Set the various project-specific variables detailed in the Synopsis +and Options sections above.

  • +
  • For the very first project() call only:

    +
      +
    • If CMAKE_TOOLCHAIN_FILE is set, read it at least once. +It may be read multiple times and it may also be read again when +enabling languages later (see below).

    • +
    • Set the variables describing the host and target platforms. +Language-specific variables might or might not be set at this point. +On the first run, the only language-specific variables that might be +defined are those a toolchain file may have set. On subsequent runs, +language-specific variables cached from a previous run may be set.

    • +
    • +

      New in version 3.24: Include each file listed in CMAKE_PROJECT_TOP_LEVEL_INCLUDES, +if set. The variable is ignored by CMake thereafter.

      +
      +
    • +
    +
  • +
  • Enable any languages specified in the call, or the default languages if +none were provided. The toolchain file may be re-read when enabling a +language for the first time.

  • +
  • +

    New in version 3.15: For every project() call regardless of the project +name, include the file named by CMAKE_PROJECT_INCLUDE, +if set.

    +
    +
  • +
  • If the project() command specifies <PROJECT-NAME> as its project +name, include the file named by +CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE, if set.

  • +
+
+
+

Usage

+

The top-level CMakeLists.txt file for a project must contain a +literal, direct call to the project() command; loading one +through the include() command is not sufficient. If no such +call exists, CMake will issue a warning and pretend there is a +project(Project) at the top to enable the default languages +(C and CXX).

+
+

Note

+

Call the project() command near the top of the top-level +CMakeLists.txt, but after calling cmake_minimum_required(). +It is important to establish version and policy settings before invoking +other commands whose behavior they may affect and for this reason the +project() command will issue a warning if this order is not kept. +See also policy CMP0000.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/qt_wrap_cpp.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/qt_wrap_cpp.html new file mode 100644 index 0000000000000000000000000000000000000000..af4bb26be97fb88ced41f0a60f444903fa4823b2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/qt_wrap_cpp.html @@ -0,0 +1,154 @@ + + + + + + + + + qt_wrap_cpp — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

qt_wrap_cpp

+
+

Deprecated since version 3.14: This command was originally added to support Qt 3 before the +add_custom_command() command was sufficiently mature. The +FindQt4 module provides the qt4_wrap_cpp() macro, which +should be used instead for Qt 4 projects. For projects using Qt 5 or +later, use the equivalent macro provided by Qt itself (e.g. Qt 5 provides +qt5_wrap_cpp()).

+
+

Manually create Qt Wrappers.

+
qt_wrap_cpp(resultingLibraryName DestName SourceLists ...)
+
+
+

Produces moc files for all the .h files listed in the SourceLists. The +moc files will be added to the library using the DestName source list.

+

Consider updating the project to use the AUTOMOC target property +instead for a more automated way of invoking the moc tool.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/qt_wrap_ui.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/qt_wrap_ui.html new file mode 100644 index 0000000000000000000000000000000000000000..e74b1c7f2f2a279f2117fc640ec2e73a5a3b83b9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/qt_wrap_ui.html @@ -0,0 +1,157 @@ + + + + + + + + + qt_wrap_ui — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

qt_wrap_ui

+
+

Deprecated since version 3.14: This command was originally added to support Qt 3 before the +add_custom_command() command was sufficiently mature. The +FindQt4 module provides the qt4_wrap_ui() macro, which +should be used instead for Qt 4 projects. For projects using Qt 5 or +later, use the equivalent macro provided by Qt itself (e.g. Qt 5 provides +qt5_wrap_ui()).

+
+

Manually create Qt user interfaces Wrappers.

+
qt_wrap_ui(resultingLibraryName HeadersDestName
+           SourcesDestName SourceLists ...)
+
+
+

Produces .h and .cxx files for all the .ui files listed in the +SourceLists. The .h files will be added to the library using the +HeadersDestNamesource list. The .cxx files will be added to the +library using the SourcesDestNamesource list.

+

Consider updating the project to use the AUTOUIC target property +instead for a more automated way of invoking the uic tool.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/remove.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/remove.html new file mode 100644 index 0000000000000000000000000000000000000000..b37a592745d9428d190e44d5c46429ddf46729ae --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/remove.html @@ -0,0 +1,147 @@ + + + + + + + + + remove — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

remove

+
+

Deprecated since version 3.0: Use the list(REMOVE_ITEM) command instead.

+
+
remove(VAR VALUE VALUE ...)
+
+
+

Removes VALUE from the variable VAR. This is typically used to +remove entries from a vector (e.g. semicolon separated list). VALUE +is expanded.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/remove_definitions.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/remove_definitions.html new file mode 100644 index 0000000000000000000000000000000000000000..3ef2495e980053bb6aed924c9f5a6d63af75565e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/remove_definitions.html @@ -0,0 +1,144 @@ + + + + + + + + + remove_definitions — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

remove_definitions

+

Remove -D define flags added by add_definitions().

+
remove_definitions(-DFOO -DBAR ...)
+
+
+

Removes flags (added by add_definitions()) from the compiler +command line for sources in the current directory and below.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/return.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/return.html new file mode 100644 index 0000000000000000000000000000000000000000..74b9afcee7dd2a1d818e0cc21204ee7557a0fd4b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/return.html @@ -0,0 +1,237 @@ + + + + + + + + + return — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

return

+

Return from a file, directory or function.

+
return([PROPAGATE <var-name>...])
+
+
+

When this command is encountered in an included file (via include() or +find_package()), it causes processing of the current file to stop +and control is returned to the including file. If it is encountered in a +file which is not included by another file, e.g. a CMakeLists.txt, +deferred calls scheduled by cmake_language(DEFER) are invoked and +control is returned to the parent directory if there is one.

+

If return() is called in a function, control is returned to the caller +of that function. Note that a macro(), unlike a function(), +is expanded in place and therefore cannot handle return().

+

Policy CMP0140 controls the behavior regarding the arguments of the +command. All arguments are ignored unless that policy is set to NEW.

+
+
PROPAGATE
+

New in version 3.25.

+
+

This option sets or unsets the specified variables in the parent directory or +function caller scope. This is equivalent to set(PARENT_SCOPE) or +unset(PARENT_SCOPE) commands, except for the way it interacts +with the block() command, as described below.

+

The PROPAGATE option can be very useful in conjunction with the +block() command. A return will propagate the +specified variables through any enclosing block scopes created by the +block() commands. Inside a function, this ensures the variables +are propagated to the function's caller, regardless of any blocks within +the function. If not inside a function, it ensures the variables are +propagated to the parent file or directory scope. For example:

+
+
CMakeLists.txt
+
cmake_version_required(VERSION 3.25)
+project(example)
+
+set(var1 "top-value")
+
+block(SCOPE_FOR VARIABLES)
+  add_subdirectory(subDir)
+  # var1 has the value "block-nested"
+endblock()
+
+# var1 has the value "top-value"
+
+
+
+
+
subDir/CMakeLists.txt
+
function(multi_scopes result_var1 result_var2)
+  block(SCOPE_FOR VARIABLES)
+    # This would only propagate out of the immediate block, not to
+    # the caller of the function.
+    #set(${result_var1} "new-value" PARENT_SCOPE)
+    #unset(${result_var2} PARENT_SCOPE)
+
+    # This propagates the variables through the enclosing block and
+    # out to the caller of the function.
+    set(${result_var1} "new-value")
+    unset(${result_var2})
+    return(PROPAGATE ${result_var1} ${result_var2})
+  endblock()
+endfunction()
+
+set(var1 "some-value")
+set(var2 "another-value")
+
+multi_scopes(var1 var2)
+# Now var1 will hold "new-value" and var2 will be unset
+
+block(SCOPE_FOR VARIABLES)
+  # This return() will set var1 in the directory scope that included us
+  # via add_subdirectory(). The surrounding block() here does not limit
+  # propagation to the current file, but the block() in the parent
+  # directory scope does prevent propagation going any further.
+  set(var1 "block-nested")
+  return(PROPAGATE var1)
+endblock()
+
+
+
+
+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/separate_arguments.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/separate_arguments.html new file mode 100644 index 0000000000000000000000000000000000000000..c20357c5fc9dfa9d4b68276d5a04848737fa609c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/separate_arguments.html @@ -0,0 +1,205 @@ + + + + + + + + + separate_arguments — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

separate_arguments

+

Parse command-line arguments into a semicolon-separated list.

+
separate_arguments(<variable> <mode> [PROGRAM [SEPARATE_ARGS]] <args>)
+
+
+

Parses a space-separated string <args> into a list of items, +and stores this list in semicolon-separated standard form in <variable>.

+

This function is intended for parsing command-line arguments. +The entire command line must be passed as one string in the +argument <args>.

+

The exact parsing rules depend on the operating system. +They are specified by the <mode> argument which must +be one of the following keywords:

+
+
UNIX_COMMAND

Arguments are separated by unquoted whitespace. +Both single-quote and double-quote pairs are respected. +A backslash escapes the next literal character (\" is "); +there are no special escapes (\n is just n).

+
+
WINDOWS_COMMAND

A Windows command-line is parsed using the same +syntax the runtime library uses to construct argv at startup. It +separates arguments by whitespace that is not double-quoted. +Backslashes are literal unless they precede double-quotes. See the +MSDN article Parsing C Command-Line Arguments for details.

+
+
NATIVE_COMMAND
+

New in version 3.9.

+
+

Proceeds as in WINDOWS_COMMAND mode if the host system is Windows. +Otherwise proceeds as in UNIX_COMMAND mode.

+
+
PROGRAM
+

New in version 3.19.

+
+

The first item in <args> is assumed to be an executable and will be +searched in the system search path or left as a full path. If not found, +<variable> will be empty. Otherwise, <variable> is a list of 2 +elements:

+
+
    +
  1. Absolute path of the program

  2. +
  3. Any command-line arguments present in <args> as a string

  4. +
+
+

For example:

+
separate_arguments (out UNIX_COMMAND PROGRAM "cc -c main.c")
+
+
+
    +
  • First element of the list: /path/to/cc

  • +
  • Second element of the list: " -c main.c"

  • +
+
+
SEPARATE_ARGS

When this sub-option of PROGRAM option is specified, command-line +arguments will be split as well and stored in <variable>.

+

For example:

+
separate_arguments (out UNIX_COMMAND PROGRAM SEPARATE_ARGS "cc -c main.c")
+
+
+

The contents of out will be: /path/to/cc;-c;main.c

+
+
+
separate_arguments(<var>)
+
+
+

Convert the value of <var> to a semi-colon separated list. All +spaces are replaced with ';'. This helps with generating command +lines.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set.html new file mode 100644 index 0000000000000000000000000000000000000000..dcddb547064a4290882b5ee2421d6a1947a01bb1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set.html @@ -0,0 +1,275 @@ + + + + + + + + + set — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

set

+

Set a normal, cache, or environment variable to a given value. +See the cmake-language(7) variables +documentation for the scopes and interaction of normal variables +and cache entries.

+

Signatures of this command that specify a <value>... placeholder +expect zero or more arguments. Multiple arguments will be joined as +a semicolon-separated list to form the +actual variable value to be set.

+
+

Set Normal Variable

+
+
+set(<variable> <value>... [PARENT_SCOPE])
+

Set or unset <variable> in the current function or directory scope:

+
    +
  • If at least one <value>... is given, set the variable to that value.

  • +
  • If no value is given, unset the variable. This is equivalent to +unset(<variable>).

  • +
+

If the PARENT_SCOPE option is given the variable will be set in +the scope above the current scope. Each new directory or function() +command creates a new scope. A scope can also be created with the +block() command. This command will set the value of a variable into +the parent directory, calling function or encompassing scope (whichever is +applicable to the case at hand). The previous state of the variable's value +stays the same in the current scope (e.g., if it was undefined before, it is +still undefined and if it had a value, it is still that value).

+

The block(PROPAGATE) and return(PROPAGATE) commands +can be used as an alternate method to the set(PARENT_SCOPE) +and unset(PARENT_SCOPE) commands to update the parent scope.

+
+ +
+

Note

+

When evaluating Variable References of the form ${VAR}, CMake +first searches for a normal variable with that name. If no such normal +variable exists, CMake will then search for a cache entry with that name. +Because of this, unsetting a normal variable can expose a cache variable +that was previously hidden. To force a variable reference of the form +${VAR} to return an empty string, use set(<variable> ""), which +clears the normal variable but leaves it defined.

+
+
+
+

Set Cache Entry

+
+
+set(<variable> <value>... CACHE <type> <docstring> [FORCE])
+

Sets the given cache <variable> (cache entry). Since cache entries +are meant to provide user-settable values this does not overwrite +existing cache entries by default. Use the FORCE option to +overwrite existing entries.

+

The <type> must be specified as one of:

+
+
+
BOOL

Boolean ON/OFF value. +cmake-gui(1) offers a checkbox.

+
+
FILEPATH

Path to a file on disk. +cmake-gui(1) offers a file dialog.

+
+
PATH

Path to a directory on disk. +cmake-gui(1) offers a file dialog.

+
+
STRING

A line of text. +cmake-gui(1) offers a text field or a drop-down selection +if the STRINGS cache entry property is set.

+
+
INTERNAL

A line of text. +cmake-gui(1) does not show internal entries. +They may be used to store variables persistently across runs. +Use of this type implies FORCE.

+
+
+
+

The <docstring> must be specified as a line of text +providing a quick summary of the option +for presentation to cmake-gui(1) users.

+

If the cache entry does not exist prior to the call or the FORCE +option is given then the cache entry will be set to the given value.

+
+

Note

+

The content of the cache variable will not be directly accessible +if a normal variable of the same name already exists +(see rules of variable evaluation). +If policy CMP0126 is set to OLD, any normal variable +binding in the current scope will be removed.

+
+

It is possible for the cache entry to exist prior to the call but +have no type set if it was created on the cmake(1) command +line by a user through the -D<var>=<value> option +without specifying a type. In this case the set command will add the +type. Furthermore, if the <type> is PATH or FILEPATH +and the <value> provided on the command line is a relative path, +then the set command will treat the path as relative to the +current working directory and convert it to an absolute path.

+
+ +
+
+

Set Environment Variable

+
+
+set(ENV{<variable>} [<value>])
+

Sets an Environment Variable +to the given value. +Subsequent calls of $ENV{<variable>} will return this new value.

+

This command affects only the current CMake process, not the process +from which CMake was called, nor the system environment at large, +nor the environment of subsequent build or test processes.

+

If no argument is given after ENV{<variable>} or if <value> is +an empty string, then this command will clear any existing value of the +environment variable.

+

Arguments after <value> are ignored. If extra arguments are found, +then an author warning is issued.

+
+ +
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_directory_properties.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_directory_properties.html new file mode 100644 index 0000000000000000000000000000000000000000..8d8895243de6be93c7facfcab9f7b3459f763810 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_directory_properties.html @@ -0,0 +1,164 @@ + + + + + + + + + set_directory_properties — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

set_directory_properties

+

Set properties of the current directory and subdirectories.

+
set_directory_properties(PROPERTIES prop1 value1 [prop2 value2] ...)
+
+
+

Sets properties of the current directory and its subdirectories in key-value pairs.

+

See also the set_property(DIRECTORY) command.

+

See Properties on Directories for the list of properties known to CMake +and their individual documentation for the behavior of each property.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_property.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_property.html new file mode 100644 index 0000000000000000000000000000000000000000..5e72b041f66d7dce8575e156e7bc533d58f085dc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_property.html @@ -0,0 +1,253 @@ + + + + + + + + + set_property — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

set_property

+

Set a named property in a given scope.

+
set_property(<GLOBAL                      |
+              DIRECTORY [<dir>]           |
+              TARGET    [<target1> ...]   |
+              SOURCE    [<src1> ...]
+                        [DIRECTORY <dirs> ...]
+                        [TARGET_DIRECTORY <targets> ...] |
+              INSTALL   [<file1> ...]     |
+              TEST      [<test1> ...]     |
+              CACHE     [<entry1> ...]    >
+             [APPEND] [APPEND_STRING]
+             PROPERTY <name> [<value1> ...])
+
+
+

Sets one property on zero or more objects of a scope.

+

The first argument determines the scope in which the property is set. +It must be one of the following:

+
+
GLOBAL

Scope is unique and does not accept a name.

+
+
DIRECTORY

Scope defaults to the current directory but other directories +(already processed by CMake) may be named by full or relative path. +Relative paths are treated as relative to the current source directory. +See also the set_directory_properties() command.

+
+

New in version 3.19: <dir> may reference a binary directory.

+
+
+
TARGET

Scope may name zero or more existing targets. +See also the set_target_properties() command.

+

Alias Targets do not support setting target properties.

+
+
SOURCE

Scope may name zero or more source files. By default, source file properties +are only visible to targets added in the same directory (CMakeLists.txt).

+
+

New in version 3.18: Visibility can be set in other directory scopes using one or both of the +following sub-options:

+
+
DIRECTORY <dirs>...

The source file property will be set in each of the <dirs> +directories' scopes. CMake must already know about +each of these directories, either by having added them through a call to +add_subdirectory() or it being the top level source directory. +Relative paths are treated as relative to the current source directory.

+
+

New in version 3.19: <dirs> may reference a binary directory.

+
+
+
TARGET_DIRECTORY <targets>...

The source file property will be set in each of the directory scopes +where any of the specified <targets> were created (the <targets> +must therefore already exist).

+
+
+
+

See also the set_source_files_properties() command.

+
+
INSTALL
+

New in version 3.1.

+
+

Scope may name zero or more installed file paths. +These are made available to CPack to influence deployment.

+

Both the property key and value may use generator expressions. +Specific properties may apply to installed files and/or directories.

+

Path components have to be separated by forward slashes, +must be normalized and are case sensitive.

+

To reference the installation prefix itself with a relative path use ..

+

Currently installed file properties are only defined for +the WIX generator where the given paths are relative +to the installation prefix.

+
+
TEST

Scope is limited to the directory the command is called in. It may name zero +or more existing tests. See also command set_tests_properties().

+

Test property values may be specified using +generator expressions +for tests created by the add_test(NAME) signature.

+
+
CACHE

Scope must name zero or more existing cache entries.

+
+
+

The required PROPERTY option is immediately followed by the name of +the property to set. Remaining arguments are used to compose the +property value in the form of a semicolon-separated list.

+

If the APPEND option is given the list is appended to any existing +property value (except that empty values are ignored and not appended). +If the APPEND_STRING option is given the string is +appended to any existing property value as string, i.e. it results in a +longer string and not a list of strings. When using APPEND or +APPEND_STRING with a property defined to support INHERITED +behavior (see define_property()), no inheriting occurs when +finding the initial value to append to. If the property is not already +directly set in the nominated scope, the command will behave as though +APPEND or APPEND_STRING had not been given.

+
+

Note

+

The GENERATED source file property may be globally visible. +See its documentation for details.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_source_files_properties.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_source_files_properties.html new file mode 100644 index 0000000000000000000000000000000000000000..f432d1a4d3c59a601029ea680043e659d3b28bc9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_source_files_properties.html @@ -0,0 +1,191 @@ + + + + + + + + + set_source_files_properties — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

set_source_files_properties

+

Source files can have properties that affect how they are built.

+
set_source_files_properties(<files> ...
+                            [DIRECTORY <dirs> ...]
+                            [TARGET_DIRECTORY <targets> ...]
+                            PROPERTIES <prop1> <value1>
+                            [<prop2> <value2>] ...)
+
+
+

Sets properties associated with source files using a key/value paired +list.

+
+

New in version 3.18: By default, source file properties are only visible to targets added in the +same directory (CMakeLists.txt). Visibility can be set in other directory +scopes using one or both of the following options:

+
+
+
DIRECTORY <dirs>...

The source file properties will be set in each of the <dirs> +directories' scopes. CMake must already know about each of these +source directories, either by having added them through a call to +add_subdirectory() or it being the top level source directory. +Relative paths are treated as relative to the current source directory.

+
+
TARGET_DIRECTORY <targets>...

The source file properties will be set in each of the directory scopes +where any of the specified <targets> were created (the <targets> +must therefore already exist).

+
+
+

Use get_source_file_property() to get property values. +See also the set_property(SOURCE) command.

+
+

Note

+

The GENERATED source file property may be globally visible. +See its documentation for details.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_target_properties.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_target_properties.html new file mode 100644 index 0000000000000000000000000000000000000000..f686e8391369414d4642eb6090b6813b1e0232a6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_target_properties.html @@ -0,0 +1,169 @@ + + + + + + + + + set_target_properties — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

set_target_properties

+

Targets can have properties that affect how they are built.

+
set_target_properties(target1 target2 ...
+                      PROPERTIES prop1 value1
+                      prop2 value2 ...)
+
+
+

Sets properties on targets. The syntax for the command is to list all +the targets you want to change, and then provide the values you want to +set next. You can use any prop value pair you want and extract it +later with the get_property() or get_target_property() +command.

+

Alias Targets do not support setting target properties.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_tests_properties.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_tests_properties.html new file mode 100644 index 0000000000000000000000000000000000000000..d67076ef978019c92368e5bb546f5af5dac95519 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/set_tests_properties.html @@ -0,0 +1,166 @@ + + + + + + + + + set_tests_properties — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

set_tests_properties

+

Set a property of the tests.

+
set_tests_properties(test1 [test2...] PROPERTIES prop1 value1 prop2 value2)
+
+
+

Sets a property for the tests. If the test is not found, CMake +will report an error.

+

Test property values may be specified using +generator expressions +for tests created by the add_test(NAME) signature.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/site_name.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/site_name.html new file mode 100644 index 0000000000000000000000000000000000000000..4874dc40ae67632ad1b3c12e2d1f88317696d8c7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/site_name.html @@ -0,0 +1,145 @@ + + + + + + + + + site_name — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

site_name

+

Set the given variable to the name of the computer.

+
site_name(variable)
+
+
+

On UNIX-like platforms, if the variable HOSTNAME is set, its value +will be executed as a command expected to print out the host name, +much like the hostname command-line tool.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/source_group.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/source_group.html new file mode 100644 index 0000000000000000000000000000000000000000..2cabcc047e6f31c9d6215aa8f751b53685ea00b8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/source_group.html @@ -0,0 +1,196 @@ + + + + + + + + + source_group — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

source_group

+

Define a grouping for source files in IDE project generation. +There are two different signatures to create source groups.

+
source_group(<name> [FILES <src>...] [REGULAR_EXPRESSION <regex>])
+source_group(TREE <root> [PREFIX <prefix>] [FILES <src>...])
+
+
+

Defines a group into which sources will be placed in project files. +This is intended to set up file tabs in Visual Studio. +The group is scoped in the directory where the command is called, +and applies to sources in targets created in that directory.

+

The options are:

+
+
TREE
+

New in version 3.8.

+
+

CMake will automatically detect, from <src> files paths, source groups +it needs to create, to keep structure of source groups analogically to the +actual files and directories structure in the project. Paths of <src> +files will be cut to be relative to <root>. The command fails if the +paths within src do not start with root.

+
+
PREFIX
+

New in version 3.8.

+
+

Source group and files located directly in <root> path, will be placed +in <prefix> source groups.

+
+
FILES

Any source file specified explicitly will be placed in group +<name>. Relative paths are interpreted with respect to the +current source directory.

+
+
REGULAR_EXPRESSION

Any source file whose name matches the regular expression will +be placed in group <name>.

+
+
+

If a source file matches multiple groups, the last group that +explicitly lists the file with FILES will be favored, if any. +If no group explicitly lists the file, the last group whose +regular expression matches the file will be favored.

+

The <name> of the group and <prefix> argument may contain forward +slashes or backslashes to specify subgroups. Backslashes need to be escaped +appropriately:

+
source_group(base/subdir ...)
+source_group(outer\\inner ...)
+source_group(TREE <root> PREFIX sources\\inc ...)
+
+
+
+

New in version 3.18: Allow using forward slashes (/) to specify subgroups.

+
+

For backwards compatibility, the short-hand signature

+
source_group(<name> <regex>)
+
+
+

is equivalent to

+
source_group(<name> REGULAR_EXPRESSION <regex>)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/string.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/string.html new file mode 100644 index 0000000000000000000000000000000000000000..9e19fe454906e696ebe18f0bcafb173f670e77fe --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/string.html @@ -0,0 +1,738 @@ + + + + + + + + + string — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

string

+

String operations.

+
+

Synopsis

+
Search and Replace
+  string(FIND <string> <substring> <out-var> [...])
+  string(REPLACE <match-string> <replace-string> <out-var> <input>...)
+  string(REGEX MATCH <match-regex> <out-var> <input>...)
+  string(REGEX MATCHALL <match-regex> <out-var> <input>...)
+  string(REGEX REPLACE <match-regex> <replace-expr> <out-var> <input>...)
+
+Manipulation
+  string(APPEND <string-var> [<input>...])
+  string(PREPEND <string-var> [<input>...])
+  string(CONCAT <out-var> [<input>...])
+  string(JOIN <glue> <out-var> [<input>...])
+  string(TOLOWER <string> <out-var>)
+  string(TOUPPER <string> <out-var>)
+  string(LENGTH <string> <out-var>)
+  string(SUBSTRING <string> <begin> <length> <out-var>)
+  string(STRIP <string> <out-var>)
+  string(GENEX_STRIP <string> <out-var>)
+  string(REPEAT <string> <count> <out-var>)
+
+Comparison
+  string(COMPARE <op> <string1> <string2> <out-var>)
+
+Hashing
+  string(<HASH> <out-var> <input>)
+
+Generation
+  string(ASCII <number>... <out-var>)
+  string(HEX <string> <out-var>)
+  string(CONFIGURE <string> <out-var> [...])
+  string(MAKE_C_IDENTIFIER <string> <out-var>)
+  string(RANDOM [<option>...] <out-var>)
+  string(TIMESTAMP <out-var> [<format string>] [UTC])
+  string(UUID <out-var> ...)
+
+JSON
+  string(JSON <out-var> [ERROR_VARIABLE <error-var>]
+         {GET | TYPE | LENGTH | REMOVE}
+         <json-string> <member|index> [<member|index> ...])
+  string(JSON <out-var> [ERROR_VARIABLE <error-var>]
+         MEMBER <json-string>
+         [<member|index> ...] <index>)
+  string(JSON <out-var> [ERROR_VARIABLE <error-var>]
+         SET <json-string>
+         <member|index> [<member|index> ...] <value>)
+  string(JSON <out-var> [ERROR_VARIABLE <error-var>]
+         EQUAL <json-string1> <json-string2>)
+
+
+

Search and Replace

+
+

Search and Replace With Plain Strings

+
+
+string(FIND <string> <substring> <output_variable> [REVERSE])
+

Return the position where the given <substring> was found in +the supplied <string>. If the REVERSE flag was used, the command +will search for the position of the last occurrence of the specified +<substring>. If the <substring> is not found, a position of -1 is +returned.

+

The string(FIND) subcommand treats all strings as ASCII-only characters. +The index stored in <output_variable> will also be counted in bytes, +so strings containing multi-byte characters may lead to unexpected results.

+
+ +
+
+string(REPLACE <match_string> <replace_string> <output_variable> <input> [<input>...])
+

Replace all occurrences of <match_string> in the <input> +with <replace_string> and store the result in the <output_variable>.

+
+ +
+
+

Search and Replace With Regular Expressions

+
+
+string(REGEX MATCH <regular_expression> <output_variable> <input> [<input>...])
+

Match the <regular_expression> once and store the match in the +<output_variable>. +All <input> arguments are concatenated before matching. +Regular expressions are specified in the subsection just below.

+
+ +
+
+string(REGEX MATCHALL <regular_expression> <output_variable> <input> [<input>...])
+

Match the <regular_expression> as many times as possible and store the +matches in the <output_variable> as a list. +All <input> arguments are concatenated before matching.

+
+ +
+
+string(REGEX REPLACE <regular_expression> <replacement_expression> <output_variable> <input> [<input>...])
+

Match the <regular_expression> as many times as possible and substitute +the <replacement_expression> for the match in the output. +All <input> arguments are concatenated before matching.

+

The <replacement_expression> may refer to parenthesis-delimited +subexpressions of the match using \1, \2, ..., \9. Note that +two backslashes (\\1) are required in CMake code to get a backslash +through argument parsing.

+
+ +
+
+

Regex Specification

+

The following characters have special meaning in regular expressions:

+
+
^

Matches at beginning of input

+
+
$

Matches at end of input

+
+
.

Matches any single character

+
+
\<char>

Matches the single character specified by <char>. Use this to +match special regex characters, e.g. \. for a literal . +or \\ for a literal backslash \. Escaping a non-special +character is unnecessary but allowed, e.g. \a matches a.

+
+
[ ]

Matches any character(s) inside the brackets

+
+
[^ ]

Matches any character(s) not inside the brackets

+
+
-

Inside brackets, specifies an inclusive range between +characters on either side e.g. [a-f] is [abcdef] +To match a literal - using brackets, make it the first +or the last character e.g. [+*/-] matches basic +mathematical operators.

+
+
*

Matches preceding pattern zero or more times

+
+
+

Matches preceding pattern one or more times

+
+
?

Matches preceding pattern zero or once only

+
+
|

Matches a pattern on either side of the |

+
+
()

Saves a matched subexpression, which can be referenced +in the REGEX REPLACE operation.

+
+

New in version 3.9: All regular expression-related commands, including e.g. +if(MATCHES), save subgroup matches in the variables +CMAKE_MATCH_<n> for <n> 0..9.

+
+
+
+

*, + and ? have higher precedence than concatenation. | +has lower precedence than concatenation. This means that the regular +expression ^ab+d$ matches abbd but not ababd, and the regular +expression ^(ab|cd)$ matches ab but not abd.

+

CMake language Escape Sequences such as \t, \r, \n, +and \\ may be used to construct literal tabs, carriage returns, +newlines, and backslashes (respectively) to pass in a regex. For example:

+
    +
  • The quoted argument "[ \t\r\n]" specifies a regex that matches +any single whitespace character.

  • +
  • The quoted argument "[/\\]" specifies a regex that matches +a single forward slash / or backslash \.

  • +
  • The quoted argument "[A-Za-z0-9_]" specifies a regex that matches +any single "word" character in the C locale.

  • +
  • The quoted argument "\\(\\a\\+b\\)" specifies a regex that matches +the exact string (a+b). Each \\ is parsed in a quoted argument +as just \, so the regex itself is actually \(\a\+\b\). This +can alternatively be specified in a Bracket Argument without +having to escape the backslashes, e.g. [[\(\a\+\b\)]].

  • +
+
+
+
+

Manipulation

+
+
+string(APPEND <string_variable> [<input>...])
+
+

New in version 3.4.

+
+

Append all the <input> arguments to the string.

+
+ +
+
+string(PREPEND <string_variable> [<input>...])
+
+

New in version 3.10.

+
+

Prepend all the <input> arguments to the string.

+
+ +
+
+string(CONCAT <output_variable> [<input>...])
+

Concatenate all the <input> arguments together and store +the result in the named <output_variable>.

+
+ +
+
+string(JOIN <glue> <output_variable> [<input>...])
+
+

New in version 3.12.

+
+

Join all the <input> arguments together using the <glue> +string and store the result in the named <output_variable>.

+

To join a list's elements, prefer to use the JOIN operator +from the list() command. This allows for the elements to have +special characters like ; in them.

+
+ +
+
+string(TOLOWER <string> <output_variable>)
+

Convert <string> to lower characters.

+
+ +
+
+string(TOUPPER <string> <output_variable>)
+

Convert <string> to upper characters.

+
+ +
+
+string(LENGTH <string> <output_variable>)
+

Store in an <output_variable> a given string's length in bytes. +Note that this means if <string> contains multi-byte characters, +the result stored in <output_variable> will not be +the number of characters.

+
+ +
+
+string(SUBSTRING <string> <begin> <length> <output_variable>)
+

Store in an <output_variable> a substring of a given <string>. If +<length> is -1 the remainder of the string starting at <begin> +will be returned.

+
+

Changed in version 3.2: If <string> is shorter than <length> +then the end of the string is used instead. +Previous versions of CMake reported an error in this case.

+
+

Both <begin> and <length> are counted in bytes, so care must +be exercised if <string> could contain multi-byte characters.

+
+ +
+
+string(STRIP <string> <output_variable>)
+

Store in an <output_variable> a substring of a given <string> +with leading and trailing spaces removed.

+
+ +
+
+string(GENEX_STRIP <string> <output_variable>)
+
+

New in version 3.1.

+
+

Strip any generator expressions +from the input <string> and store the result +in the <output_variable>.

+
+ +
+
+string(REPEAT <string> <count> <output_variable>)
+
+

New in version 3.15.

+
+

Produce the output string as the input <string> +repeated <count> times.

+
+ +
+
+

Comparison

+
+
+string(COMPARE LESS <string1> <string2> <output_variable>)
+
+string(COMPARE GREATER <string1> <string2> <output_variable>)
+
+string(COMPARE EQUAL <string1> <string2> <output_variable>)
+
+string(COMPARE NOTEQUAL <string1> <string2> <output_variable>)
+
+string(COMPARE LESS_EQUAL <string1> <string2> <output_variable>)
+
+string(COMPARE GREATER_EQUAL <string1> <string2> <output_variable>)
+

Compare the strings and store true or false in the <output_variable>.

+
+

New in version 3.7: Added the LESS_EQUAL and GREATER_EQUAL options.

+
+
+ +
+
+

Hashing

+
+
+string(<HASH> <output_variable> <input>)
+

Compute a cryptographic hash of the <input> string. +The supported <HASH> algorithm names are:

+
+
MD5

Message-Digest Algorithm 5, RFC 1321.

+
+
SHA1

US Secure Hash Algorithm 1, RFC 3174.

+
+
SHA224

US Secure Hash Algorithms, RFC 4634.

+
+
SHA256

US Secure Hash Algorithms, RFC 4634.

+
+
SHA384

US Secure Hash Algorithms, RFC 4634.

+
+
SHA512

US Secure Hash Algorithms, RFC 4634.

+
+
SHA3_224

Keccak SHA-3.

+
+
SHA3_256

Keccak SHA-3.

+
+
SHA3_384

Keccak SHA-3.

+
+
SHA3_512

Keccak SHA-3.

+
+
+
+

New in version 3.8: Added the SHA3_* hash algorithms.

+
+
+ +
+
+

Generation

+
+
+string(ASCII <number> [<number> ...] <output_variable>)
+

Convert all numbers into corresponding ASCII characters.

+
+ +
+
+string(HEX <string> <output_variable>)
+
+

New in version 3.18.

+
+

Convert each byte in the input <string> to its hexadecimal representation +and store the concatenated hex digits in the <output_variable>. +Letters in the output (a through f) are in lowercase.

+
+ +
+
+string(CONFIGURE <string> <output_variable> [@ONLY] [ESCAPE_QUOTES])
+

Transform a <string> like configure_file() transforms a file.

+
+ +
+
+string(MAKE_C_IDENTIFIER <string> <output_variable>)
+

Convert each non-alphanumeric character in the input <string> to an +underscore and store the result in the <output_variable>. If the first +character of the <string> is a digit, an underscore will also be +prepended to the result.

+
+ +
+
+string(RANDOM [LENGTH <length>] [ALPHABET <alphabet>] [RANDOM_SEED <seed>] <output_variable>)
+

Return a random string of given <length> consisting of +characters from the given <alphabet>. Default length is 5 characters +and default alphabet is all numbers and upper and lower case letters. +If an integer RANDOM_SEED is given, its value will be used to seed the +random number generator.

+
+ +
+
+string(TIMESTAMP <output_variable> [<format_string>] [UTC])
+

Write a string representation of the current date +and/or time to the <output_variable>.

+

If the command is unable to obtain a timestamp, the <output_variable> +will be set to the empty string "".

+

The optional UTC flag requests the current date/time representation to +be in Coordinated Universal Time (UTC) rather than local time.

+

The optional <format_string> may contain the following format +specifiers:

+
+
%%
+

New in version 3.8.

+
+

A literal percent sign (%).

+
+
%d

The day of the current month (01-31).

+
+
%H

The hour on a 24-hour clock (00-23).

+
+
%I

The hour on a 12-hour clock (01-12).

+
+
%j

The day of the current year (001-366).

+
+
%m

The month of the current year (01-12).

+
+
%b
+

New in version 3.7.

+
+

Abbreviated month name (e.g. Oct).

+
+
%B
+

New in version 3.10.

+
+

Full month name (e.g. October).

+
+
%M

The minute of the current hour (00-59).

+
+
%s
+

New in version 3.6.

+
+

Seconds since midnight (UTC) 1-Jan-1970 (UNIX time).

+
+
%S

The second of the current minute. 60 represents a leap second. (00-60)

+
+
%f
+

New in version 3.23.

+
+

The microsecond of the current second (000000-999999).

+
+
%U

The week number of the current year (00-53).

+
+
%V
+

New in version 3.22.

+
+

The ISO 8601 week number of the current year (01-53).

+
+
%w

The day of the current week. 0 is Sunday. (0-6)

+
+
%a
+

New in version 3.7.

+
+

Abbreviated weekday name (e.g. Fri).

+
+
%A
+

New in version 3.10.

+
+

Full weekday name (e.g. Friday).

+
+
%y

The last two digits of the current year (00-99).

+
+
%Y

The current year.

+
+
%z
+

New in version 3.26.

+
+

The offset of the time zone from UTC, in hours and minutes, +with format +hhmm or -hhmm.

+
+
%Z
+

New in version 3.26.

+
+

The time zone name.

+
+
+

Unknown format specifiers will be ignored and copied to the output +as-is.

+

If no explicit <format_string> is given, it will default to:

+
%Y-%m-%dT%H:%M:%S    for local time.
+%Y-%m-%dT%H:%M:%SZ   for UTC.
+
+
+
+

New in version 3.8: If the SOURCE_DATE_EPOCH environment variable is set, +its value will be used instead of the current time. +See https://reproducible-builds.org/specs/source-date-epoch/ for details.

+
+
+ +
+
+string(UUID <output_variable> NAMESPACE <namespace> NAME <name> TYPE <MD5|SHA1> [UPPER])
+
+

New in version 3.1.

+
+

Create a universally unique identifier (aka GUID) as per RFC4122 +based on the hash of the combined values of <namespace> +(which itself has to be a valid UUID) and <name>. +The hash algorithm can be either MD5 (Version 3 UUID) or +SHA1 (Version 5 UUID). +A UUID has the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx +where each x represents a lower case hexadecimal character. +Where required, an uppercase representation can be requested +with the optional UPPER flag.

+
+ +
+
+

JSON

+
+

New in version 3.19.

+
+

Functionality for querying a JSON string.

+
+

Note

+

In each of the following JSON-related subcommands, if the optional +ERROR_VARIABLE argument is given, errors will be reported in +<error-variable> and the <out-var> will be set to +<member|index>-[<member|index>...]-NOTFOUND with the path elements +up to the point where the error occurred, or just NOTFOUND if there +is no relevant path. If an error occurs but the ERROR_VARIABLE +option is not present, a fatal error message is generated. If no error +occurs, the <error-variable> will be set to NOTFOUND.

+
+
+
+string(JSON <out-var> [ERROR_VARIABLE <error-variable>] GET <json-string> <member|index> [<member|index> ...])
+

Get an element from <json-string> at the location given +by the list of <member|index> arguments. +Array and object elements will be returned as a JSON string. +Boolean elements will be returned as ON or OFF. +Null elements will be returned as an empty string. +Number and string types will be returned as strings.

+
+ +
+
+string(JSON <out-var> [ERROR_VARIABLE <error-variable>] TYPE <json-string> <member|index> [<member|index> ...])
+

Get the type of an element in <json-string> at the location +given by the list of <member|index> arguments. The <out-var> +will be set to one of NULL, NUMBER, STRING, BOOLEAN, +ARRAY, or OBJECT.

+
+ +
+
+string(JSON <out-var> [ERROR_VARIABLE <error-var>] MEMBER <json-string> [<member|index> ...] <index>)
+

Get the name of the <index>-th member in <json-string> +at the location given by the list of <member|index> arguments. +Requires an element of object type.

+
+ +
+
+string(JSON <out-var> [ERROR_VARIABLE <error-variable>] LENGTH <json-string> [<member|index> ...])
+

Get the length of an element in <json-string> at the location +given by the list of <member|index> arguments. +Requires an element of array or object type.

+
+ +
+
+string(JSON <out-var> [ERROR_VARIABLE <error-variable>] REMOVE <json-string> <member|index> [<member|index> ...])
+

Remove an element from <json-string> at the location +given by the list of <member|index> arguments. The JSON string +without the removed element will be stored in <out-var>.

+
+ +
+
+string(JSON <out-var> [ERROR_VARIABLE <error-variable>] SET <json-string> <member|index> [<member|index> ...] <value>)
+

Set an element in <json-string> at the location +given by the list of <member|index> arguments to <value>. +The contents of <value> should be valid JSON. +If <json-string> is an array, <value> can be appended to the end of +the array by using a number greater or equal to the array length as the +<member|index> argument.

+
+ +
+
+string(JSON <out-var> [ERROR_VARIABLE <error-var>] EQUAL <json-string1> <json-string2>)
+

Compare the two JSON objects given by <json-string1> +and <json-string2> for equality. The contents of <json-string1> +and <json-string2> should be valid JSON. The <out-var> +will be set to a true value if the JSON objects are considered equal, +or a false value otherwise.

+
+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/subdir_depends.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/subdir_depends.html new file mode 100644 index 0000000000000000000000000000000000000000..2189723296a822e2a9393e30d77a5f07d4a1c100 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/subdir_depends.html @@ -0,0 +1,145 @@ + + + + + + + + + subdir_depends — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

subdir_depends

+

Disallowed since version 3.0. See CMake Policy CMP0029.

+

Does nothing.

+
subdir_depends(subdir dep1 dep2 ...)
+
+
+

Does not do anything. This command used to help projects order +parallel builds correctly. This functionality is now automatic.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/subdirs.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/subdirs.html new file mode 100644 index 0000000000000000000000000000000000000000..97e668453390e674822500c6d3ffffc188e1db08 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/subdirs.html @@ -0,0 +1,158 @@ + + + + + + + + + subdirs — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

subdirs

+
+

Deprecated since version 3.0: Use the add_subdirectory() command instead.

+
+

Add a list of subdirectories to the build.

+
subdirs(dir1 dir2 ...[EXCLUDE_FROM_ALL exclude_dir1 exclude_dir2 ...]
+        [PREORDER] )
+
+
+

Add a list of subdirectories to the build. The add_subdirectory() +command should be used instead of subdirs although subdirs will still +work. This will cause any CMakeLists.txt files in the sub directories +to be processed by CMake. Any directories after the PREORDER flag are +traversed first by makefile builds, the PREORDER flag has no effect on +IDE projects. Any directories after the EXCLUDE_FROM_ALL marker will +not be included in the top level makefile or project file. This is +useful for having CMake create makefiles or projects for a set of +examples in a project. You would want CMake to generate makefiles or +project files for all the examples at the same time, but you would not +want them to show up in the top level project or be built each time +make is run from the top.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_compile_definitions.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_compile_definitions.html new file mode 100644 index 0000000000000000000000000000000000000000..b126cd2dc97590b21144eb83da207afada589270 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_compile_definitions.html @@ -0,0 +1,200 @@ + + + + + + + + + target_compile_definitions — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

target_compile_definitions

+

Add compile definitions to a target.

+
target_compile_definitions(<target>
+  <INTERFACE|PUBLIC|PRIVATE> [items1...]
+  [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...])
+
+
+

Specifies compile definitions to use when compiling a given <target>. The +named <target> must have been created by a command such as +add_executable() or add_library() and must not be an +ALIAS target.

+

The INTERFACE, PUBLIC and PRIVATE keywords are required to +specify the scope of the following arguments. +PRIVATE and PUBLIC items will populate the COMPILE_DEFINITIONS +property of <target>. PUBLIC and INTERFACE items will populate the +INTERFACE_COMPILE_DEFINITIONS property of <target>. +The following arguments specify compile definitions. Repeated calls for the +same <target> append items in the order called.

+
+

New in version 3.11: Allow setting INTERFACE items on IMPORTED targets.

+
+

Arguments to target_compile_definitions may use generator expressions +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+

Any leading -D on an item will be removed. Empty items are ignored. +For example, the following are all equivalent:

+
target_compile_definitions(foo PUBLIC FOO)
+target_compile_definitions(foo PUBLIC -DFOO)  # -D removed
+target_compile_definitions(foo PUBLIC "" FOO) # "" ignored
+target_compile_definitions(foo PUBLIC -D FOO) # -D becomes "", then ignored
+
+
+

Definitions may optionally have values:

+
target_compile_definitions(foo PUBLIC FOO=1)
+
+
+

Note that many compilers treat -DFOO as equivalent to -DFOO=1, but +other tools may not recognize this in all circumstances (e.g. IntelliSense).

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_compile_features.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_compile_features.html new file mode 100644 index 0000000000000000000000000000000000000000..b175be450759acdd9987e862e106f5026db74f43 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_compile_features.html @@ -0,0 +1,193 @@ + + + + + + + + + target_compile_features — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

target_compile_features

+
+

New in version 3.1.

+
+

Add expected compiler features to a target.

+
target_compile_features(<target> <PRIVATE|PUBLIC|INTERFACE> <feature> [...])
+
+
+

Specifies compiler features required when compiling a given target. If the +feature is not listed in the CMAKE_C_COMPILE_FEATURES, +CMAKE_CUDA_COMPILE_FEATURES, or CMAKE_CXX_COMPILE_FEATURES +variables, then an error will be reported by CMake. If the use of the feature requires +an additional compiler flag, such as -std=gnu++11, the flag will be added +automatically.

+

The INTERFACE, PUBLIC and PRIVATE keywords are required to +specify the scope of the features. PRIVATE and PUBLIC items will +populate the COMPILE_FEATURES property of <target>. +PUBLIC and INTERFACE items will populate the +INTERFACE_COMPILE_FEATURES property of <target>. +Repeated calls for the same <target> append items.

+
+

New in version 3.11: Allow setting INTERFACE items on IMPORTED targets.

+
+

The named <target> must have been created by a command such as +add_executable() or add_library() and must not be an +ALIAS target.

+
+

for more on defining buildsystem properties.

+
+

Arguments to target_compile_features may use generator expressions +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-compile-features(7) +manual for information on compile features and a list of supported compilers.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_compile_options.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_compile_options.html new file mode 100644 index 0000000000000000000000000000000000000000..443220806ce0844e9406272a52d66c9118e26bf7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_compile_options.html @@ -0,0 +1,224 @@ + + + + + + + + + target_compile_options — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

target_compile_options

+

Add compile options to a target.

+
target_compile_options(<target> [BEFORE]
+  <INTERFACE|PUBLIC|PRIVATE> [items1...]
+  [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...])
+
+
+

Adds options to the COMPILE_OPTIONS or +INTERFACE_COMPILE_OPTIONS target properties. These options +are used when compiling the given <target>, which must have been +created by a command such as add_executable() or +add_library() and must not be an ALIAS target.

+
+

Note

+

These options are not used when linking the target. +See the target_link_options() command for that.

+
+
+

Arguments

+

If BEFORE is specified, the content will be prepended to the property +instead of being appended. See policy CMP0101 which affects +whether BEFORE will be ignored in certain cases.

+

The INTERFACE, PUBLIC and PRIVATE keywords are required to +specify the scope of the following arguments. +PRIVATE and PUBLIC items will populate the COMPILE_OPTIONS +property of <target>. PUBLIC and INTERFACE items will populate the +INTERFACE_COMPILE_OPTIONS property of <target>. +The following arguments specify compile options. Repeated calls for the same +<target> append items in the order called.

+
+

New in version 3.11: Allow setting INTERFACE items on IMPORTED targets.

+
+

Arguments to target_compile_options may use generator expressions +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+
+
+

Option De-duplication

+

The final set of options used for a target is constructed by +accumulating options from the current target and the usage requirements of +its dependencies. The set of options is de-duplicated to avoid repetition.

+
+

New in version 3.12: While beneficial for individual options, the de-duplication step can break +up option groups. For example, -option A -option B becomes +-option A B. One may specify a group of options using shell-like +quoting along with a SHELL: prefix. The SHELL: prefix is dropped, +and the rest of the option string is parsed using the +separate_arguments() UNIX_COMMAND mode. For example, +"SHELL:-option A" "SHELL:-option B" becomes -option A -option B.

+
+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_include_directories.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_include_directories.html new file mode 100644 index 0000000000000000000000000000000000000000..1af682729ebe023777c7a7eaffe124cb10992ea1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_include_directories.html @@ -0,0 +1,237 @@ + + + + + + + + + target_include_directories — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

target_include_directories

+

Add include directories to a target.

+
target_include_directories(<target> [SYSTEM] [AFTER|BEFORE]
+  <INTERFACE|PUBLIC|PRIVATE> [items1...]
+  [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...])
+
+
+

Specifies include directories to use when compiling a given target. +The named <target> must have been created by a command such +as add_executable() or add_library() and must not be an +ALIAS target.

+

By using AFTER or BEFORE explicitly, you can select between appending +and prepending, independent of the default.

+

The INTERFACE, PUBLIC and PRIVATE keywords are required to specify +the scope of the following arguments. +PRIVATE and PUBLIC items will populate the INCLUDE_DIRECTORIES +property of <target>. PUBLIC and INTERFACE items will populate the +INTERFACE_INCLUDE_DIRECTORIES property of <target>. +The following arguments specify include directories.

+
+

New in version 3.11: Allow setting INTERFACE items on IMPORTED targets.

+
+

Repeated calls for the same <target> append items in the order called.

+

If SYSTEM is specified, the compiler will be told the directories +are meant as system include directories on some platforms. This may +have effects such as suppressing warnings or skipping the contained +headers in dependency calculations (see compiler documentation). +Additionally, system include directories are searched after normal +include directories regardless of the order specified.

+

If SYSTEM is used together with PUBLIC or INTERFACE, the +INTERFACE_SYSTEM_INCLUDE_DIRECTORIES target property will be +populated with the specified directories.

+

Arguments to target_include_directories may use generator expressions +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+

Specified include directories may be absolute paths or relative paths. +A relative path will be interpreted as relative to the current source +directory (i.e. CMAKE_CURRENT_SOURCE_DIR) and converted to an +absolute path before storing it in the associated target property. +If the path starts with a generator expression, it will always be assumed +to be an absolute path (with one exception noted below) and will be used +unmodified.

+

Include directories usage requirements commonly differ between the build-tree +and the install-tree. The BUILD_INTERFACE and +INSTALL_INTERFACE generator expressions can be used to describe +separate usage requirements based on the usage location. Relative paths +are allowed within the INSTALL_INTERFACE expression and are +interpreted as relative to the installation prefix. Relative paths should not +be used in BUILD_INTERFACE expressions because they will not be +converted to absolute. For example:

+
target_include_directories(mylib PUBLIC
+  $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/include/mylib>
+  $<INSTALL_INTERFACE:include/mylib>  # <prefix>/include/mylib
+)
+
+
+
+

Creating Relocatable Packages

+

Note that it is not advisable to populate the INSTALL_INTERFACE of +the INTERFACE_INCLUDE_DIRECTORIES of a target with absolute paths to the include +directories of dependencies. That would hard-code into installed packages +the include directory paths for dependencies +as found on the machine the package was made on.

+

The INSTALL_INTERFACE of the INTERFACE_INCLUDE_DIRECTORIES is only +suitable for specifying the required include directories for headers +provided with the target itself, not those provided by the transitive +dependencies listed in its INTERFACE_LINK_LIBRARIES target +property. Those dependencies should themselves be targets that specify +their own header locations in INTERFACE_INCLUDE_DIRECTORIES.

+

See the Creating Relocatable Packages section of the +cmake-packages(7) manual for discussion of additional care +that must be taken when specifying usage requirements while creating +packages for redistribution.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_link_directories.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_link_directories.html new file mode 100644 index 0000000000000000000000000000000000000000..e14e07fde62f3b1c58e81272d49f9d30ed79a5a0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_link_directories.html @@ -0,0 +1,213 @@ + + + + + + + + + target_link_directories — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_link_libraries.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_link_libraries.html new file mode 100644 index 0000000000000000000000000000000000000000..c2bb780472ffbd1354dac5f8546d4f41f559c47e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_link_libraries.html @@ -0,0 +1,545 @@ + + + + + + + + + target_link_libraries — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_link_options.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_link_options.html new file mode 100644 index 0000000000000000000000000000000000000000..5549bc9ff4548910c510016909d927a8f5e24b0f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_link_options.html @@ -0,0 +1,258 @@ + + + + + + + + + target_link_options — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_precompile_headers.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_precompile_headers.html new file mode 100644 index 0000000000000000000000000000000000000000..a7a9c22b50a548dbb02683ea47cee8cf1224c319 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_precompile_headers.html @@ -0,0 +1,268 @@ + + + + + + + + + target_precompile_headers — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

target_precompile_headers

+
+

New in version 3.16.

+
+

Add a list of header files to precompile.

+

Precompiling header files can speed up compilation by creating a partially +processed version of some header files, and then using that version during +compilations rather than repeatedly parsing the original headers.

+
+

Main Form

+
target_precompile_headers(<target>
+  <INTERFACE|PUBLIC|PRIVATE> [header1...]
+  [<INTERFACE|PUBLIC|PRIVATE> [header2...] ...])
+
+
+

The command adds header files to the PRECOMPILE_HEADERS and/or +INTERFACE_PRECOMPILE_HEADERS target properties of <target>. +The named <target> must have been created by a command such as +add_executable() or add_library() and must not be an +ALIAS target.

+

The INTERFACE, PUBLIC and PRIVATE keywords are required to +specify the scope of the following arguments. +PRIVATE and PUBLIC items will populate the PRECOMPILE_HEADERS +property of <target>. PUBLIC and INTERFACE items will populate the +INTERFACE_PRECOMPILE_HEADERS property of <target> +(IMPORTED targets only support INTERFACE items). +Repeated calls for the same <target> will append items in the order called.

+

Projects should generally avoid using PUBLIC or INTERFACE for targets +that will be exported, or they should at least use +the $<BUILD_INTERFACE:...> generator expression to prevent precompile +headers from appearing in an installed exported target. Consumers of a target +should typically be in control of what precompile headers they use, not have +precompile headers forced on them by the targets being consumed (since +precompile headers are not typically usage requirements). A notable exception +to this is where an interface library is created +to define a commonly used set of precompile headers in one place and then other +targets link to that interface library privately. In this case, the interface +library exists specifically to propagate the precompile headers to its +consumers and the consumer is effectively still in control, since it decides +whether to link to the interface library or not.

+

The list of header files is used to generate a header file named +cmake_pch.h|xx which is used to generate the precompiled header file +(.pch, .gch, .pchi) artifact. The cmake_pch.h|xx header +file will be force included (-include for GCC, /FI for MSVC) to +all source files, so sources do not need to have #include "pch.h".

+

Header file names specified with angle brackets (e.g. <unordered_map>) or +explicit double quotes (escaped for the cmake-language(7), +e.g. [["other_header.h"]]) will be treated as is, and include directories +must be available for the compiler to find them. Other header file names +(e.g. project_header.h) are interpreted as being relative to the current +source directory (e.g. CMAKE_CURRENT_SOURCE_DIR) and will be +included by absolute path. For example:

+
target_precompile_headers(myTarget
+  PUBLIC
+    project_header.h
+  PRIVATE
+    [["other_header.h"]]
+    <unordered_map>
+)
+
+
+
+

for more on defining buildsystem properties.

+
+

Arguments to target_precompile_headers may use generator expressions +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. The $<COMPILE_LANGUAGE:...> generator +expression is particularly useful for specifying a language-specific header +to precompile for only one language (e.g. CXX and not C). In this +case, header file names that are not explicitly in double quotes or angle +brackets must be specified by absolute path. Also, when specifying angle +brackets inside a generator expression, be sure to encode the closing +> as $<ANGLE-R>. For example:

+
target_precompile_headers(mylib PRIVATE
+  "$<$<COMPILE_LANGUAGE:CXX>:${CMAKE_CURRENT_SOURCE_DIR}/cxx_only.h>"
+  "$<$<COMPILE_LANGUAGE:C>:<stddef.h$<ANGLE-R>>"
+  "$<$<COMPILE_LANGUAGE:CXX>:<cstddef$<ANGLE-R>>"
+)
+
+
+
+
+

Reusing Precompile Headers

+

The command also supports a second signature which can be used to specify that +one target re-uses a precompiled header file artifact from another target +instead of generating its own:

+
target_precompile_headers(<target> REUSE_FROM <other_target>)
+
+
+

This form sets the PRECOMPILE_HEADERS_REUSE_FROM property to +<other_target> and adds a dependency such that <target> will depend +on <other_target>. CMake will halt with an error if the +PRECOMPILE_HEADERS property of <target> is already set when +the REUSE_FROM form is used.

+
+

Note

+

The REUSE_FROM form requires the same set of compiler options, +compiler flags and compiler definitions for both <target> and +<other_target>. Some compilers (e.g. GCC) may issue a warning if the +precompiled header file cannot be used (-Winvalid-pch).

+
+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_sources.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_sources.html new file mode 100644 index 0000000000000000000000000000000000000000..1a9c1361c438805d71e2862c6f43e78f96ac75bd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/target_sources.html @@ -0,0 +1,331 @@ + + + + + + + + + target_sources — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

target_sources

+
+

New in version 3.1.

+
+

Add sources to a target.

+
target_sources(<target>
+  <INTERFACE|PUBLIC|PRIVATE> [items1...]
+  [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...])
+
+
+

Specifies sources to use when building a target and/or its dependents. +The named <target> must have been created by a command such as +add_executable() or add_library() or +add_custom_target() and must not be an +ALIAS target. The <items> may use +generator expressions.

+
+

New in version 3.20: <target> can be a custom target.

+
+

The INTERFACE, PUBLIC and PRIVATE keywords are required to +specify the scope of the source file paths +(<items>) that follow them. PRIVATE and PUBLIC items will +populate the SOURCES property of <target>, which are used when +building the target itself. PUBLIC and INTERFACE items will populate the +INTERFACE_SOURCES property of <target>, which are used +when building dependents. A target created by add_custom_target() +can only have PRIVATE scope.

+

Repeated calls for the same <target> append items in the order called.

+
+

New in version 3.3: Allow exporting targets with INTERFACE_SOURCES.

+
+
+

New in version 3.11: Allow setting INTERFACE items on +IMPORTED targets.

+
+
+

Changed in version 3.13: Relative source file paths are interpreted as being relative to the current +source directory (i.e. CMAKE_CURRENT_SOURCE_DIR). +See policy CMP0076.

+
+

A path that begins with a generator expression is left unmodified. +When a target's SOURCE_DIR property differs from +CMAKE_CURRENT_SOURCE_DIR, use absolute paths in generator +expressions to ensure the sources are correctly assigned to the target.

+
# WRONG: starts with generator expression, but relative path used
+target_sources(MyTarget PRIVATE "$<$<CONFIG:Debug>:dbgsrc.cpp>")
+
+# CORRECT: absolute path used inside the generator expression
+target_sources(MyTarget PRIVATE "$<$<CONFIG:Debug>:${CMAKE_CURRENT_SOURCE_DIR}/dbgsrc.cpp>")
+
+
+

See the cmake-buildsystem(7) manual for more on defining +buildsystem properties.

+
+

File Sets

+
+

New in version 3.23.

+
+
target_sources(<target>
+  [<INTERFACE|PUBLIC|PRIVATE>
+   [FILE_SET <set> [TYPE <type>] [BASE_DIRS <dirs>...] [FILES <files>...]]...
+  ]...)
+
+
+

Adds a file set to a target, or adds files to an existing file set. Targets +have zero or more named file sets. Each file set has a name, a type, a scope of +INTERFACE, PUBLIC, or PRIVATE, one or more base directories, and +files within those directories. The acceptable types include:

+

HEADERS

+
+

Sources intended to be used via a language's #include mechanism.

+
+

CXX_MODULES

+
+
+

Note

+

Experimental. Gated by CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API

+
+

Sources which contain C++ interface module or partition units (i.e., those +using the export keyword). This file set type may not have an +INTERFACE scope except on IMPORTED targets.

+
+

The optional default file sets are named after their type. The target may not +be a custom target or FRAMEWORK target.

+

Files in a PRIVATE or PUBLIC file set are marked as source files for +the purposes of IDE integration. Additionally, files in HEADERS file sets +have their HEADER_FILE_ONLY property set to TRUE. Files in an +INTERFACE or PUBLIC file set can be installed with the +install(TARGETS) command, and exported with the +install(EXPORT) and export() commands.

+

Each target_sources(FILE_SET) entry starts with INTERFACE, PUBLIC, or +PRIVATE and accepts the following arguments:

+

FILE_SET <set>

+
+

The name of the file set to create or add to. It must contain only letters, +numbers and underscores. Names starting with a capital letter are reserved +for built-in file sets predefined by CMake. The only predefined set names +are those matching the acceptable types. All other set names must not start +with a capital letter or +underscore.

+
+

TYPE <type>

+
+

Every file set is associated with a particular type of file. Only types +specified above may be used and it is an error to specify anything else. As +a special case, if the name of the file set is one of the types, the type +does not need to be specified and the TYPE <type> arguments can be +omitted. For all other file set names, TYPE is required.

+
+

BASE_DIRS <dirs>...

+
+

An optional list of base directories of the file set. Any relative path +is treated as relative to the current source directory +(i.e. CMAKE_CURRENT_SOURCE_DIR). If no BASE_DIRS are +specified when the file set is first created, the value of +CMAKE_CURRENT_SOURCE_DIR is added. This argument supports +generator expressions.

+

No two base directories for a file set may be sub-directories of each other. +This requirement must be met across all base directories added to a file set, +not just those within a single call to target_sources().

+
+

FILES <files>...

+
+

An optional list of files to add to the file set. Each file must be in +one of the base directories, or a subdirectory of one of the base +directories. This argument supports +generator expressions.

+

If relative paths are specified, they are considered relative to +CMAKE_CURRENT_SOURCE_DIR at the time target_sources() is +called. An exception to this is a path starting with $<. Such paths +are treated as relative to the target's source directory after evaluation +of generator expressions.

+
+

The following target properties are set by target_sources(FILE_SET), +but they should not generally be manipulated directly:

+

For file sets of type HEADERS:

+ +

For file sets of type CXX_MODULES:

+ +

Target properties related to include directories are also modified by +target_sources(FILE_SET) as follows:

+

INCLUDE_DIRECTORIES

+
+

If the TYPE is HEADERS, and the scope of the file set is PRIVATE +or PUBLIC, all of the BASE_DIRS of the file set are wrapped in +$<BUILD_INTERFACE> and appended to this property.

+
+

INTERFACE_INCLUDE_DIRECTORIES

+
+

If the TYPE is HEADERS, and the scope of the file set is +INTERFACE or PUBLIC, all of the BASE_DIRS of the file set are +wrapped in $<BUILD_INTERFACE> and appended to this property.

+
+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/try_compile.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/try_compile.html new file mode 100644 index 0000000000000000000000000000000000000000..3d5f897ca398fbb800f0caabc9f26633435f95c0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/try_compile.html @@ -0,0 +1,486 @@ + + + + + + + + + try_compile — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

try_compile

+ +

Try building some code.

+
+

Try Compiling Whole Projects

+
try_compile(<compileResultVar> PROJECT <projectName>
+            SOURCE_DIR <srcdir>
+            [BINARY_DIR <bindir>]
+            [TARGET <targetName>]
+            [LOG_DESCRIPTION <text>]
+            [NO_CACHE]
+            [NO_LOG]
+            [CMAKE_FLAGS <flags>...]
+            [OUTPUT_VARIABLE <var>])
+
+
+
+

New in version 3.25.

+
+

Try building a project. Build success returns TRUE and build failure +returns FALSE in <compileResultVar>.

+

In this form, <srcdir> should contain a complete CMake project with a +CMakeLists.txt file and all sources. The <bindir> and <srcdir> +will not be deleted after this command is run. Specify <targetName> to +build a specific target instead of the all or ALL_BUILD target. See +below for the meaning of other options.

+
+

Changed in version 3.24: CMake variables describing platform settings, and those listed by the +CMAKE_TRY_COMPILE_PLATFORM_VARIABLES variable, are propagated +into the project's build configuration. See policy CMP0137. +Previously this was only done by the +source file signature.

+
+
+

New in version 3.26: This command records a +configure-log try_compile event +if the NO_LOG option is not specified.

+
+

This command supports an alternate signature for CMake older than 3.25. +The signature above is recommended for clarity.

+
try_compile(<compileResultVar> <bindir> <srcdir>
+            <projectName> [<targetName>]
+            [CMAKE_FLAGS <flags>...]
+            [OUTPUT_VARIABLE <var>])
+
+
+
+
+

Try Compiling Source Files

+
try_compile(<compileResultVar>
+            <SOURCES <srcfile...>                 |
+             SOURCE_FROM_CONTENT <name> <content> |
+             SOURCE_FROM_VAR <name> <var>         |
+             SOURCE_FROM_FILE <name> <path>       >...
+            [LOG_DESCRIPTION <text>]
+            [NO_CACHE]
+            [NO_LOG]
+            [CMAKE_FLAGS <flags>...]
+            [COMPILE_DEFINITIONS <defs>...]
+            [LINK_OPTIONS <options>...]
+            [LINK_LIBRARIES <libs>...]
+            [OUTPUT_VARIABLE <var>]
+            [COPY_FILE <fileName> [COPY_FILE_ERROR <var>]]
+            [<LANG>_STANDARD <std>]
+            [<LANG>_STANDARD_REQUIRED <bool>]
+            [<LANG>_EXTENSIONS <bool>]
+            )
+
+
+
+

New in version 3.25.

+
+

Try building an executable or static library from one or more source files +(which one is determined by the CMAKE_TRY_COMPILE_TARGET_TYPE +variable). Build success returns TRUE and build failure returns FALSE +in <compileResultVar>.

+

In this form, one or more source files must be provided. Additionally, one of +SOURCES and/or SOURCE_FROM_* must precede other keywords.

+

If CMAKE_TRY_COMPILE_TARGET_TYPE is unset or is set to +EXECUTABLE, the sources must include a definition for main and CMake +will create a CMakeLists.txt file to build the source(s) as an executable. +If CMAKE_TRY_COMPILE_TARGET_TYPE is set to STATIC_LIBRARY, +a static library will be built instead and no definition for main is +required. For an executable, the generated CMakeLists.txt file would +contain something like the following:

+
add_definitions(<expanded COMPILE_DEFINITIONS from caller>)
+include_directories(${INCLUDE_DIRECTORIES})
+link_directories(${LINK_DIRECTORIES})
+add_executable(cmTryCompileExec <srcfile>...)
+target_link_options(cmTryCompileExec PRIVATE <LINK_OPTIONS from caller>)
+target_link_libraries(cmTryCompileExec ${LINK_LIBRARIES})
+
+
+

CMake automatically generates, for each try_compile operation, a +unique directory under ${CMAKE_BINARY_DIR}/CMakeFiles/CMakeScratch +with an unspecified name. These directories are cleaned automatically unless +--debug-trycompile is passed to cmake. +Such directories from previous runs are also unconditionally cleaned at the +beginning of any cmake execution.

+

This command supports an alternate signature for CMake older than 3.25. +The signature above is recommended for clarity.

+
try_compile(<compileResultVar> <bindir> <srcfile|SOURCES srcfile...>
+            [CMAKE_FLAGS <flags>...]
+            [COMPILE_DEFINITIONS <defs>...]
+            [LINK_OPTIONS <options>...]
+            [LINK_LIBRARIES <libs>...]
+            [OUTPUT_VARIABLE <var>]
+            [COPY_FILE <fileName> [COPY_FILE_ERROR <var>]]
+            [<LANG>_STANDARD <std>]
+            [<LANG>_STANDARD_REQUIRED <bool>]
+            [<LANG>_EXTENSIONS <bool>]
+            )
+
+
+

In this version, try_compile will use <bindir>/CMakeFiles/CMakeTmp for +its operation, and all such files will be cleaned automatically. +For debugging, --debug-trycompile can be +passed to cmake to avoid this clean. However, multiple sequential +try_compile operations, if given the same <bindir>, will reuse this +single output directory, such that you can only debug one such try_compile +call at a time. Use of the newer signature is recommended to simplify +debugging of multiple try_compile operations.

+

The options are:

+
+
CMAKE_FLAGS <flags>...

Specify flags of the form -DVAR:TYPE=VALUE to be passed +to the cmake(1) command-line used to drive the test build. +The above example shows how values for variables +INCLUDE_DIRECTORIES, LINK_DIRECTORIES, and LINK_LIBRARIES +are used.

+
+
COMPILE_DEFINITIONS <defs>...

Specify -Ddefinition arguments to pass to add_definitions() +in the generated test project.

+
+
COPY_FILE <fileName>

Copy the built executable or static library to the given <fileName>.

+
+
COPY_FILE_ERROR <var>

Use after COPY_FILE to capture into variable <var> any error +message encountered while trying to copy the file.

+
+
LINK_LIBRARIES <libs>...

Specify libraries to be linked in the generated project. +The list of libraries may refer to system libraries and to +Imported Targets from the calling project.

+

If this option is specified, any -DLINK_LIBRARIES=... value +given to the CMAKE_FLAGS option will be ignored.

+
+
LINK_OPTIONS <options>...
+

New in version 3.14.

+
+

Specify link step options to pass to target_link_options() or to +set the STATIC_LIBRARY_OPTIONS target property in the generated +project, depending on the CMAKE_TRY_COMPILE_TARGET_TYPE variable.

+
+
LOG_DESCRIPTION <text>
+

New in version 3.26.

+
+

Specify a non-empty text description of the purpose of the check. +This is recorded in the cmake-configure-log(7) entry.

+
+
NO_CACHE
+

New in version 3.25.

+
+

The result will be stored in a normal variable rather than a cache entry.

+

The result variable is normally cached so that a simple pattern can be used +to avoid repeating the test on subsequent executions of CMake:

+
if(NOT DEFINED RESULTVAR)
+  # ...(check-specific setup code)...
+  try_compile(RESULTVAR ...)
+  # ...(check-specific logging and cleanup code)...
+endif()
+
+
+

If the guard variable and result variable are not the same (for example, if +the test is part of a larger inspection), NO_CACHE may be useful to avoid +leaking the intermediate result variable into the cache.

+
+
NO_LOG
+

New in version 3.26.

+
+

Do not record a cmake-configure-log(7) entry for this call.

+
+
OUTPUT_VARIABLE <var>

Store the output from the build process in the given variable.

+
+
SOURCE_FROM_CONTENT <name> <content>
+

New in version 3.25.

+
+

Write <content> to a file named <name> in the operation directory. +This can be used to bypass the need to separately write a source file when +the contents of the file are dynamically specified. The specified <name> +is not allowed to contain path components.

+

SOURCE_FROM_CONTENT may be specified multiple times.

+
+
SOURCE_FROM_FILE <name> <path>
+

New in version 3.25.

+
+

Copy <path> to a file named <name> in the operation directory. This +can be used to consolidate files into the operation directory, which may be +useful if a source which already exists (i.e. as a stand-alone file in a +project's source repository) needs to refer to other file(s) created by +SOURCE_FROM_*. (Otherwise, SOURCES is usually more convenient.) The +specified <name> is not allowed to contain path components.

+
+
SOURCE_FROM_VAR <name> <var>
+

New in version 3.25.

+
+

Write the contents of <var> to a file named <name> in the operation +directory. This is the same as SOURCE_FROM_CONTENT, but takes the +contents from the specified CMake variable, rather than directly, which may +be useful when passing arguments through a function which wraps +try_compile. The specified <name> is not allowed to contain path +components.

+

SOURCE_FROM_VAR may be specified multiple times.

+
+
<LANG>_STANDARD <std>
+

New in version 3.8.

+
+

Specify the C_STANDARD, CXX_STANDARD, +OBJC_STANDARD, OBJCXX_STANDARD, +or CUDA_STANDARD target property of the generated project.

+
+
<LANG>_STANDARD_REQUIRED <bool>
+

New in version 3.8.

+
+

Specify the C_STANDARD_REQUIRED, +CXX_STANDARD_REQUIRED, OBJC_STANDARD_REQUIRED, +OBJCXX_STANDARD_REQUIRED,or CUDA_STANDARD_REQUIRED +target property of the generated project.

+
+
<LANG>_EXTENSIONS <bool>
+

New in version 3.8.

+
+

Specify the C_EXTENSIONS, CXX_EXTENSIONS, +OBJC_EXTENSIONS, OBJCXX_EXTENSIONS, +or CUDA_EXTENSIONS target property of the generated project.

+
+
+
+
+

Other Behavior Settings

+
+

New in version 3.4: If set, the following variables are passed in to the generated +try_compile CMakeLists.txt to initialize compile target properties with +default values:

+ +

If CMP0056 is set to NEW, then +CMAKE_EXE_LINKER_FLAGS is passed in as well.

+
+
+

Changed in version 3.14: If CMP0083 is set to NEW, then in order to obtain correct +behavior at link time, the check_pie_supported() command from the +CheckPIESupported module must be called before using the +try_compile command.

+
+

The current settings of CMP0065 and CMP0083 are propagated +through to the generated test project.

+

Set variable CMAKE_TRY_COMPILE_CONFIGURATION to choose a build +configuration:

+
    +
  • For multi-config generators, this selects which configuration to build.

  • +
  • For single-config generators, this sets CMAKE_BUILD_TYPE in +the test project.

  • +
+
+

New in version 3.6: Set the CMAKE_TRY_COMPILE_TARGET_TYPE variable to specify +the type of target used for the source file signature.

+
+
+

New in version 3.6: Set the CMAKE_TRY_COMPILE_PLATFORM_VARIABLES variable to specify +variables that must be propagated into the test project. This variable is +meant for use only in toolchain files and is only honored by the +try_compile() command for the source files form, not when given a whole +project.

+
+
+

Changed in version 3.8: If CMP0067 is set to NEW, or any of the <LANG>_STANDARD, +<LANG>_STANDARD_REQUIRED, or <LANG>_EXTENSIONS options are used, +then the language standard variables are honored:

+ +

Their values are used to set the corresponding target properties in +the generated project (unless overridden by an explicit option).

+
+
+

Changed in version 3.14: For the Green Hills MULTI generator, the GHS toolset and target +system customization cache variables are also propagated into the test +project.

+
+
+

New in version 3.24: The CMAKE_TRY_COMPILE_NO_PLATFORM_VARIABLES variable may be +set to disable passing platform variables into the test project.

+
+
+

New in version 3.25: If CMP0141 is set to NEW, one can use +CMAKE_MSVC_DEBUG_INFORMATION_FORMAT to specify the MSVC debug +information format.

+
+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/try_run.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/try_run.html new file mode 100644 index 0000000000000000000000000000000000000000..69ad5ffa4eb9a7005caf0ac48fa4d947bff869d0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/try_run.html @@ -0,0 +1,303 @@ + + + + + + + + + try_run — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

try_run

+ +

Try compiling and then running some code.

+
+

Try Compiling and Running Source Files

+
try_run(<runResultVar> <compileResultVar>
+        <SOURCES <srcfile...>                 |
+         SOURCE_FROM_CONTENT <name> <content> |
+         SOURCE_FROM_VAR <name> <var>         |
+         SOURCE_FROM_FILE <name> <path>       >...
+        [LOG_DESCRIPTION <text>]
+        [NO_CACHE]
+        [NO_LOG]
+        [CMAKE_FLAGS <flags>...]
+        [COMPILE_DEFINITIONS <defs>...]
+        [LINK_OPTIONS <options>...]
+        [LINK_LIBRARIES <libs>...]
+        [COMPILE_OUTPUT_VARIABLE <var>]
+        [COPY_FILE <fileName> [COPY_FILE_ERROR <var>]]
+        [<LANG>_STANDARD <std>]
+        [<LANG>_STANDARD_REQUIRED <bool>]
+        [<LANG>_EXTENSIONS <bool>]
+        [RUN_OUTPUT_VARIABLE <var>]
+        [RUN_OUTPUT_STDOUT_VARIABLE <var>]
+        [RUN_OUTPUT_STDERR_VARIABLE <var>]
+        [WORKING_DIRECTORY <var>]
+        [ARGS <args>...]
+        )
+
+
+
+

New in version 3.25.

+
+

Try building an executable from one or more source files. Build success +returns TRUE and build failure returns FALSE in <compileResultVar>. +If the build succeeds, this runs the executable and stores the exit code in +<runResultVar>. If the executable was built, but failed to run, then +<runResultVar> will be set to FAILED_TO_RUN. See command +try_compile() for documentation of options common to both commands, +and for information on how the test project is constructed to build the source +file.

+

One or more source files must be provided. Additionally, one of SOURCES +and/or SOURCE_FROM_* must precede other keywords.

+
+

New in version 3.26: This command records a +configure-log try_run event +if the NO_LOG option is not specified.

+
+

This command supports an alternate signature for CMake older than 3.25. +The signature above is recommended for clarity.

+
try_run(<runResultVar> <compileResultVar>
+        <bindir> <srcfile|SOURCES srcfile...>
+        [CMAKE_FLAGS <flags>...]
+        [COMPILE_DEFINITIONS <defs>...]
+        [LINK_OPTIONS <options>...]
+        [LINK_LIBRARIES <libs>...]
+        [COMPILE_OUTPUT_VARIABLE <var>]
+        [COPY_FILE <fileName> [COPY_FILE_ERROR <var>]]
+        [<LANG>_STANDARD <std>]
+        [<LANG>_STANDARD_REQUIRED <bool>]
+        [<LANG>_EXTENSIONS <bool>]
+        [RUN_OUTPUT_VARIABLE <var>]
+        [OUTPUT_VARIABLE <var>]
+        [WORKING_DIRECTORY <var>]
+        [ARGS <args>...]
+        )
+
+
+

The options specific to try_run are:

+
+
COMPILE_OUTPUT_VARIABLE <var>

Report the compile step build output in a given variable.

+
+
OUTPUT_VARIABLE <var>

Report the compile build output and the output from running the executable +in the given variable. This option exists for legacy reasons and is only +supported by the old try_run signature. +Prefer COMPILE_OUTPUT_VARIABLE and RUN_OUTPUT_VARIABLE instead.

+
+
RUN_OUTPUT_VARIABLE <var>

Report the output from running the executable in a given variable.

+
+
RUN_OUTPUT_STDOUT_VARIABLE <var>
+

New in version 3.25.

+
+

Report the output of stdout from running the executable in a given variable.

+
+
RUN_OUTPUT_STDERR_VARIABLE <var>
+

New in version 3.25.

+
+

Report the output of stderr from running the executable in a given variable.

+
+
WORKING_DIRECTORY <var>
+

New in version 3.20.

+
+

Run the executable in the given directory. If no WORKING_DIRECTORY is +specified, the executable will run in <bindir> or the current build +directory.

+
+
ARGS <args>...

Additional arguments to pass to the executable when running it.

+
+
+
+
+

Other Behavior Settings

+

Set variable CMAKE_TRY_COMPILE_CONFIGURATION to choose a build +configuration:

+
    +
  • For multi-config generators, this selects which configuration to build.

  • +
  • For single-config generators, this sets CMAKE_BUILD_TYPE in +the test project.

  • +
+
+
+

Behavior when Cross Compiling

+
+

New in version 3.3: Use CMAKE_CROSSCOMPILING_EMULATOR when running cross-compiled binaries.

+
+

When cross compiling, the executable compiled in the first step +usually cannot be run on the build host. The try_run command checks +the CMAKE_CROSSCOMPILING variable to detect whether CMake is in +cross-compiling mode. If that is the case, it will still try to compile +the executable, but it will not try to run the executable unless the +CMAKE_CROSSCOMPILING_EMULATOR variable is set. Instead it +will create cache variables which must be filled by the user or by +presetting them in some CMake script file to the values the executable +would have produced if it had been run on its actual target platform. +These cache entries are:

+
+
<runResultVar>

Exit code if the executable were to be run on the target platform.

+
+
<runResultVar>__TRYRUN_OUTPUT

Output from stdout and stderr if the executable were to be run on +the target platform. This is created only if the +RUN_OUTPUT_VARIABLE or OUTPUT_VARIABLE option was used.

+
+
+

In order to make cross compiling your project easier, use try_run +only if really required. If you use try_run, use the +RUN_OUTPUT_STDOUT_VARIABLE, RUN_OUTPUT_STDERR_VARIABLE, +RUN_OUTPUT_VARIABLE or OUTPUT_VARIABLE options only if really +required. Using them will require that when cross-compiling, the cache +variables will have to be set manually to the output of the executable. +You can also "guard" the calls to try_run with an if() +block checking the CMAKE_CROSSCOMPILING variable and +provide an easy-to-preset alternative for this case.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/unset.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/unset.html new file mode 100644 index 0000000000000000000000000000000000000000..520df3a6f6ffb5c0963ebad2cdb1bb78341998c6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/unset.html @@ -0,0 +1,191 @@ + + + + + + + + + unset — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

unset

+

Unset a variable, cache variable, or environment variable.

+
+

Unset Normal Variable or Cache Entry

+
unset(<variable> [CACHE | PARENT_SCOPE])
+
+
+

Removes a normal variable from the current scope, causing it +to become undefined. If CACHE is present, then a cache variable +is removed instead of a normal variable.

+

If PARENT_SCOPE is present then the variable is removed from the scope +above the current scope. See the same option in the set() command +for further details.

+
+

Note

+

When evaluating Variable References of the form ${VAR}, CMake +first searches for a normal variable with that name. If no such normal +variable exists, CMake will then search for a cache entry with that name. +Because of this, unsetting a normal variable can expose a cache variable +that was previously hidden. To force a variable reference of the form +${VAR} to return an empty string, use set(<variable> ""), which +clears the normal variable but leaves it defined.

+
+
+
+

Unset Environment Variable

+
unset(ENV{<variable>})
+
+
+

Removes <variable> from the currently available +Environment Variables. +Subsequent calls of $ENV{<variable>} will return the empty string.

+

This command affects only the current CMake process, not the process +from which CMake was called, nor the system environment at large, +nor the environment of subsequent build or test processes.

+
+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/use_mangled_mesa.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/use_mangled_mesa.html new file mode 100644 index 0000000000000000000000000000000000000000..b2c014422bf88dcc10b2da65987b2f6064b1bc55 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/use_mangled_mesa.html @@ -0,0 +1,147 @@ + + + + + + + + + use_mangled_mesa — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

use_mangled_mesa

+

Disallowed since version 3.0. See CMake Policy CMP0030.

+

Copy mesa headers for use in combination with system GL.

+
use_mangled_mesa(PATH_TO_MESA OUTPUT_DIRECTORY)
+
+
+

The path to mesa includes, should contain gl_mangle.h. The mesa +headers are copied to the specified output directory. This allows +mangled mesa headers to override other GL headers by being added to +the include directory path earlier.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/utility_source.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/utility_source.html new file mode 100644 index 0000000000000000000000000000000000000000..29ca85495e0caa946d029afba9de24794b98274b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/utility_source.html @@ -0,0 +1,155 @@ + + + + + + + + + utility_source — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

utility_source

+

Disallowed since version 3.0. See CMake Policy CMP0034.

+

Specify the source tree of a third-party utility.

+
utility_source(cache_entry executable_name
+               path_to_source [file1 file2 ...])
+
+
+

When a third-party utility's source is included in the distribution, +this command specifies its location and name. The cache entry will +not be set unless the path_to_source and all listed files exist. It +is assumed that the source tree of the utility will have been built +before it is needed.

+

When cross compiling CMake will print a warning if a utility_source() +command is executed, because in many cases it is used to build an +executable which is executed later on. This doesn't work when cross +compiling, since the executable can run only on their target platform. +So in this case the cache entry has to be adjusted manually so it +points to an executable which is runnable on the build host.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/variable_requires.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/variable_requires.html new file mode 100644 index 0000000000000000000000000000000000000000..429a2213a53502a3e23675c2e38c35980e1359db --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/variable_requires.html @@ -0,0 +1,153 @@ + + + + + + + + + variable_requires — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

variable_requires

+

Disallowed since version 3.0. See CMake Policy CMP0035.

+

Use the if() command instead.

+

Assert satisfaction of an option's required variables.

+
variable_requires(TEST_VARIABLE RESULT_VARIABLE
+                  REQUIRED_VARIABLE1
+                  REQUIRED_VARIABLE2 ...)
+
+
+

The first argument (TEST_VARIABLE) is the name of the variable to be +tested, if that variable is false nothing else is done. If +TEST_VARIABLE is true, then the next argument (RESULT_VARIABLE) +is a variable that is set to true if all the required variables are set. +The rest of the arguments are variables that must be true or not set +to NOTFOUND to avoid an error. If any are not true, an error is +reported.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/variable_watch.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/variable_watch.html new file mode 100644 index 0000000000000000000000000000000000000000..819af49a67fb90391707fc4ab7adcc3230ba9791 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/variable_watch.html @@ -0,0 +1,175 @@ + + + + + + + + + variable_watch — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

variable_watch

+

Watch the CMake variable for change.

+
variable_watch(<variable> [<command>])
+
+
+

If the specified <variable> changes and no <command> is given, +a message will be printed to inform about the change.

+

If <command> is given, this command will be executed instead. +The command will receive the following arguments: +COMMAND(<variable> <access> <value> <current_list_file> <stack>)

+
+
<variable>

Name of the variable being accessed.

+
+
<access>

One of READ_ACCESS, UNKNOWN_READ_ACCESS, MODIFIED_ACCESS, +UNKNOWN_MODIFIED_ACCESS, or REMOVED_ACCESS. The UNKNOWN_ +values are only used when the variable has never been set. Once set, +they are never used again during the same CMake run, even if the +variable is later unset.

+
+
<value>

The value of the variable. On a modification, this is the new +(modified) value of the variable. On removal, the value is empty.

+
+
<current_list_file>

Full path to the file doing the access.

+
+
<stack>

List of absolute paths of all files currently on the stack of file +inclusion, with the bottom-most file first and the currently +processed file (that is, current_list_file) last.

+
+
+

Note that for some accesses such as list(APPEND), the watcher +is executed twice, first with a read access and then with a write one. +Also note that an if(DEFINED) query on the variable does not +register as an access and the watcher is not executed.

+

Only non-cache variables can be watched using this command. Access to +cache variables is never watched. However, the existence of a cache +variable var causes accesses to the non-cache variable var to +not use the UNKNOWN_ prefix, even if a non-cache variable var +has never existed.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/while.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/while.html new file mode 100644 index 0000000000000000000000000000000000000000..3c82a1abbf3241a166ca147aed81227d70a551ea --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/while.html @@ -0,0 +1,174 @@ + + + + + + + + + while — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

while

+

Evaluate a group of commands while a condition is true

+
while(<condition>)
+  <commands>
+endwhile()
+
+
+

All commands between while and the matching endwhile() are recorded +without being invoked. Once the endwhile() is evaluated, the +recorded list of commands is invoked as long as the <condition> is true.

+

The <condition> has the same syntax and is evaluated using the same logic +as described at length for the if() command.

+

The commands break() and continue() provide means to +escape from the normal control flow.

+

Per legacy, the endwhile() command admits +an optional <condition> argument. +If used, it must be a verbatim repeat of the argument of the opening +while command.

+
+

See Also

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/write_file.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/write_file.html new file mode 100644 index 0000000000000000000000000000000000000000..651295b93f20d1bd50339df6a5b07a9c880b87f2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/command/write_file.html @@ -0,0 +1,153 @@ + + + + + + + + + write_file — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

write_file

+
+

Deprecated since version 3.0: Use the file(WRITE) command instead.

+
+
write_file(filename "message to write"... [APPEND])
+
+
+

The first argument is the file name, the rest of the arguments are +messages to write. If the argument APPEND is specified, then the +message will be appended.

+

NOTE 1: file(WRITE) and file(APPEND) do exactly +the same as this one but add some more functionality.

+

NOTE 2: When using write_file the produced file cannot be used as an +input to CMake (CONFIGURE_FILE, source file ...) because it will lead +to an infinite loop. Use configure_file() if you want to +generate input files to CMake.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_DESKTOP_SHORTCUTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_DESKTOP_SHORTCUTS.html new file mode 100644 index 0000000000000000000000000000000000000000..6509cfb5832054cd188aebe2959171b8256c3421 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_DESKTOP_SHORTCUTS.html @@ -0,0 +1,144 @@ + + + + + + + + + CPACK_DESKTOP_SHORTCUTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_DESKTOP_SHORTCUTS

+
+

New in version 3.3.

+
+

Species a list of shortcut names that should be created on the Desktop +for this file.

+

The property is currently only supported by the CPack WIX Generator.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_NEVER_OVERWRITE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_NEVER_OVERWRITE.html new file mode 100644 index 0000000000000000000000000000000000000000..e177359b456aed3bb93dfdb095360b4aeb6e34ae --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_NEVER_OVERWRITE.html @@ -0,0 +1,143 @@ + + + + + + + + + CPACK_NEVER_OVERWRITE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_NEVER_OVERWRITE

+
+

New in version 3.1.

+
+

Request that this file not be overwritten on install or reinstall.

+

The property is currently only supported by the CPack WIX Generator.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_PERMANENT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_PERMANENT.html new file mode 100644 index 0000000000000000000000000000000000000000..8b4eee08a0c3712da1348ed1877cfa4110054137 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_PERMANENT.html @@ -0,0 +1,143 @@ + + + + + + + + + CPACK_PERMANENT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_PERMANENT

+
+

New in version 3.1.

+
+

Request that this file not be removed on uninstall.

+

The property is currently only supported by the CPack WIX Generator.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_STARTUP_SHORTCUTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_STARTUP_SHORTCUTS.html new file mode 100644 index 0000000000000000000000000000000000000000..f76bae5b179a3936bfe502b683a443415ec4e636 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_STARTUP_SHORTCUTS.html @@ -0,0 +1,144 @@ + + + + + + + + + CPACK_STARTUP_SHORTCUTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_STARTUP_SHORTCUTS

+
+

New in version 3.3.

+
+

Species a list of shortcut names that should be created in the Startup folder +for this file.

+

The property is currently only supported by the CPack WIX Generator.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_START_MENU_SHORTCUTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_START_MENU_SHORTCUTS.html new file mode 100644 index 0000000000000000000000000000000000000000..a8f7ae18d6513700eaabaa7026c36d973e4aabe3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_START_MENU_SHORTCUTS.html @@ -0,0 +1,144 @@ + + + + + + + + + CPACK_START_MENU_SHORTCUTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_START_MENU_SHORTCUTS

+
+

New in version 3.3.

+
+

Species a list of shortcut names that should be created in the Start Menu +for this file.

+

The property is currently only supported by the CPack WIX Generator.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_WIX_ACL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_WIX_ACL.html new file mode 100644 index 0000000000000000000000000000000000000000..3109c05b71561ac7f0eb58ab6cbccc79d9cd1808 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_inst/CPACK_WIX_ACL.html @@ -0,0 +1,155 @@ + + + + + + + + + CPACK_WIX_ACL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_WIX_ACL

+
+

New in version 3.1.

+
+

Specifies access permissions for files or directories +installed by a WiX installer.

+

The property can contain multiple list entries, +each of which has to match the following format.

+
<user>[@<domain>]=<permission>[,<permission>]
+
+
+

<user> and <domain> specify the windows user and domain for which the +<Permission> element should be generated.

+

<permission> is any of the YesNoType attributes listed here:

+
http://wixtoolset.org/documentation/manual/v3/xsd/wix/permission.html
+
+
+

The property is currently only supported by the CPack WIX Generator.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ADDITIONAL_CLEAN_FILES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ADDITIONAL_CLEAN_FILES.html new file mode 100644 index 0000000000000000000000000000000000000000..d095413f069084a1a2ed679dcd140feef929e889 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ADDITIONAL_CLEAN_FILES.html @@ -0,0 +1,157 @@ + + + + + + + + + ADDITIONAL_CLEAN_FILES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ADDITIONAL_CLEAN_FILES

+
+

New in version 3.15.

+
+

A ;-list of files or directories that will be +removed as a part of the global clean target. It can be used to specify +files and directories that are generated as part of building the target or +that are directly associated with the target in some way (e.g. created as a +result of running the target).

+

For custom targets, if such files can be captured as outputs or byproducts +instead, then that should be preferred over adding them to this property. +If an additional clean file is used by multiple targets or isn't +target-specific, then the ADDITIONAL_CLEAN_FILES directory +property may be the more appropriate property to use.

+

Relative paths are allowed and are interpreted relative to the +current binary directory.

+

Contents of ADDITIONAL_CLEAN_FILES may use +generator expressions.

+

This property only works for the Ninja and the Makefile +generators. It is ignored by other generators.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AIX_EXPORT_ALL_SYMBOLS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AIX_EXPORT_ALL_SYMBOLS.html new file mode 100644 index 0000000000000000000000000000000000000000..876db7a5d6f6eb50ab2decff2d0a12d1921b1816 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AIX_EXPORT_ALL_SYMBOLS.html @@ -0,0 +1,149 @@ + + + + + + + + + AIX_EXPORT_ALL_SYMBOLS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AIX_EXPORT_ALL_SYMBOLS

+
+

New in version 3.17.

+
+

On AIX, CMake automatically exports all symbols from shared libraries, and +from executables with the ENABLE_EXPORTS target property set. +Explicitly disable this boolean property to suppress the behavior and +export no symbols by default. In this case it is expected that the project +will use other means to export some symbols.

+

This property is initialized by the value of +the CMAKE_AIX_EXPORT_ALL_SYMBOLS variable if it is set +when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ALIASED_TARGET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ALIASED_TARGET.html new file mode 100644 index 0000000000000000000000000000000000000000..42b42891278bcf6ada02eea316c4056bae1bc854 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ALIASED_TARGET.html @@ -0,0 +1,141 @@ + + + + + + + + + ALIASED_TARGET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ALIASED_TARGET

+

Name of target aliased by this target.

+

If this is an Alias Target, this property contains +the name of the target aliased.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ALIAS_GLOBAL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ALIAS_GLOBAL.html new file mode 100644 index 0000000000000000000000000000000000000000..2d7fdc806dbd0771ec1aec5053bccd7dd36a162f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ALIAS_GLOBAL.html @@ -0,0 +1,154 @@ + + + + + + + + + ALIAS_GLOBAL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ALIAS_GLOBAL

+
+

New in version 3.18.

+
+

Read-only property indicating of whether an ALIAS target +is globally visible.

+

The boolean value of this property is TRUE for aliases to +IMPORTED targets created +with the GLOBAL options to add_executable() or +add_library(), FALSE otherwise. It is undefined for +targets built within the project.

+
+

Note

+

Promoting an IMPORTED target from LOCAL +to GLOBAL scope by changing the value or IMPORTED_GLOBAL +target property do not change the scope of local aliases.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_ANT_ADDITIONAL_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_ANT_ADDITIONAL_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..e686ec30beae52a06445fada5b0ddcccfb3d5fea --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_ANT_ADDITIONAL_OPTIONS.html @@ -0,0 +1,146 @@ + + + + + + + + + ANDROID_ANT_ADDITIONAL_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_ANT_ADDITIONAL_OPTIONS

+
+

New in version 3.4.

+
+

Set the additional options for Android Ant build system. This is +a string value containing all command line options for the Ant build. +This property is initialized by the value of the +CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS variable if it is +set when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_API.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_API.html new file mode 100644 index 0000000000000000000000000000000000000000..bdf9c59f7f2f200689e73ac8d74214c94c5f2f3e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_API.html @@ -0,0 +1,145 @@ + + + + + + + + + ANDROID_API — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_API

+
+

New in version 3.1.

+
+

When Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition, this property sets the Android target API version (e.g. 15). +The version number must be a positive decimal integer. This property is +initialized by the value of the CMAKE_ANDROID_API variable if +it is set when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_API_MIN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_API_MIN.html new file mode 100644 index 0000000000000000000000000000000000000000..02241da0ca3c50d1f232cf718d49df0568226c39 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_API_MIN.html @@ -0,0 +1,145 @@ + + + + + + + + + ANDROID_API_MIN — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_API_MIN

+
+

New in version 3.2.

+
+

Set the Android MIN API version (e.g. 9). The version number +must be a positive decimal integer. This property is initialized by +the value of the CMAKE_ANDROID_API_MIN variable if it is set +when a target is created. Native code builds using this API version.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_ARCH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_ARCH.html new file mode 100644 index 0000000000000000000000000000000000000000..41f2266e6695d9437af90a3232dd42599419d880 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_ARCH.html @@ -0,0 +1,154 @@ + + + + + + + + + ANDROID_ARCH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_ARCH

+
+

New in version 3.4.

+
+

When Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition, this property sets the Android target architecture.

+

This is a string property that could be set to the one of +the following values:

+
    +
  • armv7-a: "ARMv7-A (armv7-a)"

  • +
  • armv7-a-hard: "ARMv7-A, hard-float ABI (armv7-a)"

  • +
  • arm64-v8a: "ARMv8-A, 64bit (arm64-v8a)"

  • +
  • x86: "x86 (x86)"

  • +
  • x86_64: "x86_64 (x86_64)"

  • +
+

This property is initialized by the value of the +CMAKE_ANDROID_ARCH variable if it is set +when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_ASSETS_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_ASSETS_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..3875b17db519500a6f252f900a9957a7e861df32 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_ASSETS_DIRECTORIES.html @@ -0,0 +1,147 @@ + + + + + + + + + ANDROID_ASSETS_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_ASSETS_DIRECTORIES

+
+

New in version 3.4.

+
+

Set the Android assets directories to copy into the main assets +folder before build. This a string property that contains the +directory paths separated by semicolon. +This property is initialized by the value of the +CMAKE_ANDROID_ASSETS_DIRECTORIES variable if it is set when +a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_GUI.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_GUI.html new file mode 100644 index 0000000000000000000000000000000000000000..3bf0c16d0e35b7b55dc05ad794a513133761ffa3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_GUI.html @@ -0,0 +1,150 @@ + + + + + + + + + ANDROID_GUI — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_GUI

+
+

New in version 3.1.

+
+

When Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition, this property specifies whether to build an executable as an +application package on Android.

+

When this property is set to true the executable when built for Android +will be created as an application package. This property is initialized +by the value of the CMAKE_ANDROID_GUI variable if it is set +when a target is created.

+

Add the AndroidManifest.xml source file explicitly to the +target add_executable() command invocation to specify the +root directory of the application package source.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_JAR_DEPENDENCIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_JAR_DEPENDENCIES.html new file mode 100644 index 0000000000000000000000000000000000000000..e756345e52f546e6d42d25d7879e007224336dfd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_JAR_DEPENDENCIES.html @@ -0,0 +1,145 @@ + + + + + + + + + ANDROID_JAR_DEPENDENCIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_JAR_DEPENDENCIES

+
+

New in version 3.4.

+
+

Set the Android property that specifies JAR dependencies. +This is a string value property. This property is initialized +by the value of the CMAKE_ANDROID_JAR_DEPENDENCIES +variable if it is set when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_JAR_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_JAR_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..ae6e646be40cc941e0951527ab9beb698437d254 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_JAR_DIRECTORIES.html @@ -0,0 +1,150 @@ + + + + + + + + + ANDROID_JAR_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_JAR_DIRECTORIES

+
+

New in version 3.4.

+
+

Set the Android property that specifies directories to search for +the JAR libraries.

+

This a string property that contains the directory paths separated by +semicolons. This property is initialized by the value of the +CMAKE_ANDROID_JAR_DIRECTORIES variable if it is set when +a target is created.

+

Contents of ANDROID_JAR_DIRECTORIES may use "generator expressions" +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_JAVA_SOURCE_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_JAVA_SOURCE_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..8542e08d62177390a96d656bf49160ac3b8e5003 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_JAVA_SOURCE_DIR.html @@ -0,0 +1,146 @@ + + + + + + + + + ANDROID_JAVA_SOURCE_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_JAVA_SOURCE_DIR

+
+

New in version 3.4.

+
+

Set the Android property that defines the Java source code root directories. +This a string property that contains the directory paths separated by semicolon. +This property is initialized by the value of the +CMAKE_ANDROID_JAVA_SOURCE_DIR variable if it is set +when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_NATIVE_LIB_DEPENDENCIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_NATIVE_LIB_DEPENDENCIES.html new file mode 100644 index 0000000000000000000000000000000000000000..7bdc0b72645ca60aaf94d2f9b586dcf450ba2bff --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_NATIVE_LIB_DEPENDENCIES.html @@ -0,0 +1,150 @@ + + + + + + + + + ANDROID_NATIVE_LIB_DEPENDENCIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_NATIVE_LIB_DEPENDENCIES

+
+

New in version 3.4.

+
+

Set the Android property that specifies the .so dependencies. +This is a string property.

+

This property is initialized by the value of the +CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES variable if it is set +when a target is created.

+

Contents of ANDROID_NATIVE_LIB_DEPENDENCIES may use +"generator expressions" with the syntax $<...>. See the +cmake-generator-expressions(7) manual for +available expressions.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_NATIVE_LIB_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_NATIVE_LIB_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..cef0b873e4665ba76c7d8482f5bcdb1ff923ae61 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_NATIVE_LIB_DIRECTORIES.html @@ -0,0 +1,151 @@ + + + + + + + + + ANDROID_NATIVE_LIB_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_NATIVE_LIB_DIRECTORIES

+
+

New in version 3.4.

+
+

Set the Android property that specifies directories to search for the .so +libraries.

+

This a string property that contains the directory paths separated +by semicolons.

+

This property is initialized by the value of the +CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES variable if it is set when a +target is created.

+

Contents of ANDROID_NATIVE_LIB_DIRECTORIES may use "generator expressions" +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_PROCESS_MAX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_PROCESS_MAX.html new file mode 100644 index 0000000000000000000000000000000000000000..025a0d06530d2034b5b35b3487cd269148e3da12 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_PROCESS_MAX.html @@ -0,0 +1,146 @@ + + + + + + + + + ANDROID_PROCESS_MAX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_PROCESS_MAX

+
+

New in version 3.4.

+
+

Set the Android property that defines the maximum number of a +parallel Android NDK compiler processes (e.g. 4). +This property is initialized by the value of the +CMAKE_ANDROID_PROCESS_MAX variable if it is set +when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_PROGUARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_PROGUARD.html new file mode 100644 index 0000000000000000000000000000000000000000..9e32be3739fbacb76be6cb2a21bd68817bda4e08 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_PROGUARD.html @@ -0,0 +1,147 @@ + + + + + + + + + ANDROID_PROGUARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_PROGUARD

+
+

New in version 3.4.

+
+

When this property is set to true that enables the ProGuard tool to shrink, +optimize, and obfuscate the code by removing unused code and renaming +classes, fields, and methods with semantically obscure names. +This property is initialized by the value of the +CMAKE_ANDROID_PROGUARD variable if it is set +when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_PROGUARD_CONFIG_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_PROGUARD_CONFIG_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..ed72f66ab55642f0a23504a8779f6eefa6374838 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_PROGUARD_CONFIG_PATH.html @@ -0,0 +1,147 @@ + + + + + + + + + ANDROID_PROGUARD_CONFIG_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_PROGUARD_CONFIG_PATH

+
+

New in version 3.4.

+
+

Set the Android property that specifies the location of the ProGuard +config file. Leave empty to use the default one. +This a string property that contains the path to ProGuard config file. +This property is initialized by the value of the +CMAKE_ANDROID_PROGUARD_CONFIG_PATH variable if it is set +when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_SECURE_PROPS_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_SECURE_PROPS_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..d9edb2fbb16bc236558cdd6e011124cdb0a957e8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_SECURE_PROPS_PATH.html @@ -0,0 +1,146 @@ + + + + + + + + + ANDROID_SECURE_PROPS_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_SECURE_PROPS_PATH

+
+

New in version 3.4.

+
+

Set the Android property that states the location of the secure properties file. +This is a string property that contains the file path. +This property is initialized by the value of the +CMAKE_ANDROID_SECURE_PROPS_PATH variable +if it is set when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_SKIP_ANT_STEP.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_SKIP_ANT_STEP.html new file mode 100644 index 0000000000000000000000000000000000000000..471f2dc7008fac049ecec1dee6f8fe62491cf064 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_SKIP_ANT_STEP.html @@ -0,0 +1,144 @@ + + + + + + + + + ANDROID_SKIP_ANT_STEP — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_SKIP_ANT_STEP

+
+

New in version 3.4.

+
+

Set the Android property that defines whether or not to skip the Ant build step. +This is a boolean property initialized by the value of the +CMAKE_ANDROID_SKIP_ANT_STEP variable if it is set when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_STL_TYPE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_STL_TYPE.html new file mode 100644 index 0000000000000000000000000000000000000000..4964d28da6336802a7e4145ab8b27217c3ea9f87 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ANDROID_STL_TYPE.html @@ -0,0 +1,164 @@ + + + + + + + + + ANDROID_STL_TYPE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID_STL_TYPE

+
+

New in version 3.4.

+
+

When Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition, this property specifies the type of STL support for the project. +This is a string property that could set to the one of the following values:

+
+
none

No C++ Support

+
+
system

Minimal C++ without STL

+
+
gabi++_static

GAbi++ Static

+
+
gabi++_shared

GAbi++ Shared

+
+
gnustl_static

GNU libstdc++ Static

+
+
gnustl_shared

GNU libstdc++ Shared

+
+
stlport_static

STLport Static

+
+
stlport_shared

STLport Shared

+
+
+

This property is initialized by the value of the +CMAKE_ANDROID_STL_TYPE variable if it is set when a target is +created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..64d410ae872dd1821b7d03ad9ab0cd4b56d188e4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_DIRECTORY.html @@ -0,0 +1,162 @@ + + + + + + + + + ARCHIVE_OUTPUT_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ARCHIVE_OUTPUT_DIRECTORY

+

Output directory in which to build ARCHIVE target files.

+

This property specifies the directory into which archive target files +should be built. The property value may use +generator expressions. +Multi-configuration generators (Visual Studio, +Xcode, Ninja Multi-Config) append a +per-configuration subdirectory to the specified directory unless a generator +expression is used.

+

This property is initialized by the value of the +CMAKE_ARCHIVE_OUTPUT_DIRECTORY variable if it is set when a target is created.

+
+

Note

+

On macOS, this property will be ignored for the linker import files (e.g. +.tbd files, see ENABLE_EXPORTS property for details) when:

+
    +
  • The FRAMEWORK is set, because the framework layout cannot be +changed.

  • +
  • The Xcode generator is used, due to the limitations and +constraints of the Xcode tool.

  • +
+

In both cases, the linker import files will be generated in the same directory as the shared +library.

+
+

See also the ARCHIVE_OUTPUT_DIRECTORY_<CONFIG> target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_DIRECTORY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_DIRECTORY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..e00483692c30f3b7fe5f012a3e735c3246364e65 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_DIRECTORY_CONFIG.html @@ -0,0 +1,149 @@ + + + + + + + + + ARCHIVE_OUTPUT_DIRECTORY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ARCHIVE_OUTPUT_DIRECTORY_<CONFIG>

+

Per-configuration output directory for +ARCHIVE target files.

+

This is a per-configuration version of the +ARCHIVE_OUTPUT_DIRECTORY target property, but +multi-configuration generators (VS, Xcode) do NOT append a +per-configuration subdirectory to the specified directory. This +property is initialized by the value of the +CMAKE_ARCHIVE_OUTPUT_DIRECTORY_<CONFIG> variable if +it is set when a target is created.

+

Contents of ARCHIVE_OUTPUT_DIRECTORY_<CONFIG> may use +generator expressions.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..caaa0e45c702b14853444607d3f042d18c880e13 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_NAME.html @@ -0,0 +1,156 @@ + + + + + + + + + ARCHIVE_OUTPUT_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ARCHIVE_OUTPUT_NAME

+

Output name for ARCHIVE target files.

+

This property specifies the base name for archive target files. It +overrides OUTPUT_NAME and OUTPUT_NAME_<CONFIG> +properties.

+
+

Note

+

On macOS, this property will be ignored for the linker import files (e.g. +.tbd files, see ENABLE_EXPORTS property for details) when:

+
    +
  • The FRAMEWORK is set, because the framework layout cannot be +changed.

  • +
  • The Xcode generator is used, due to the limitations and +constraints of the Xcode tool.

  • +
+

In both cases, the linker import files will be generated with the same name as the shared +library.

+
+

See also the ARCHIVE_OUTPUT_NAME_<CONFIG> target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_NAME_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_NAME_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..c55ac4976cf7a60a0e996039d0543b0c0b24d639 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ARCHIVE_OUTPUT_NAME_CONFIG.html @@ -0,0 +1,142 @@ + + + + + + + + + ARCHIVE_OUTPUT_NAME_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ARCHIVE_OUTPUT_NAME_<CONFIG>

+

Per-configuration output name for +ARCHIVE target files.

+

This is the configuration-specific version of the +ARCHIVE_OUTPUT_NAME target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_BUILD_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_BUILD_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..c697fc40692dc33c633d1fe62774ea1f09d2e63a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_BUILD_DIR.html @@ -0,0 +1,151 @@ + + + + + + + + + AUTOGEN_BUILD_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOGEN_BUILD_DIR

+
+

New in version 3.9.

+
+

Directory where AUTOMOC, AUTOUIC and AUTORCC +generate files for the target.

+

The directory is created on demand and automatically added to the +ADDITIONAL_CLEAN_FILES target property.

+

When unset or empty the directory <dir>/<target-name>_autogen is used where +<dir> is CMAKE_CURRENT_BINARY_DIR and <target-name> +is NAME.

+

By default AUTOGEN_BUILD_DIR is unset.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_ORIGIN_DEPENDS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_ORIGIN_DEPENDS.html new file mode 100644 index 0000000000000000000000000000000000000000..9a48349b56eee4174b9465047ff78ca524657e7a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_ORIGIN_DEPENDS.html @@ -0,0 +1,181 @@ + + + + + + + + + AUTOGEN_ORIGIN_DEPENDS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOGEN_ORIGIN_DEPENDS

+
+

New in version 3.14.

+
+

Switch for forwarding origin target dependencies to the corresponding +_autogen target.

+

Targets which have their AUTOMOC or AUTOUIC property +ON have a corresponding _autogen target which generates +moc and uic files. As this _autogen target is created at +generate-time, it is not possible to define dependencies of it using +e.g. add_dependencies(). Instead the +AUTOGEN_ORIGIN_DEPENDS target property decides whether the origin +target dependencies should be forwarded to the _autogen target or not.

+

By default AUTOGEN_ORIGIN_DEPENDS is initialized from +CMAKE_AUTOGEN_ORIGIN_DEPENDS which is ON by default.

+

In total the dependencies of the _autogen target are composed from

+
    +
  • forwarded origin target dependencies +(enabled by default via AUTOGEN_ORIGIN_DEPENDS)

  • +
  • additional user defined dependencies from AUTOGEN_TARGET_DEPENDS

  • +
+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+

Note

+

Disabling AUTOGEN_ORIGIN_DEPENDS is useful to avoid building of +origin target dependencies when building the _autogen target only. +This is especially interesting when a +global autogen target is enabled.

+

When the _autogen target doesn't require all the origin target's +dependencies, and AUTOGEN_ORIGIN_DEPENDS is disabled, it might be +necessary to extend AUTOGEN_TARGET_DEPENDS to add missing +dependencies.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_TARGET_DEPENDS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_TARGET_DEPENDS.html new file mode 100644 index 0000000000000000000000000000000000000000..2c3a58873bb50dddc23fb3e2c5f021d24a6be214 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_TARGET_DEPENDS.html @@ -0,0 +1,178 @@ + + + + + + + + + AUTOGEN_TARGET_DEPENDS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOGEN_TARGET_DEPENDS

+

Additional target dependencies of the corresponding _autogen target.

+

Targets which have their AUTOMOC or AUTOUIC property +ON have a corresponding _autogen target which generates +moc and uic files. As this _autogen target is created at +generate-time, it is not possible to define dependencies of it using +e.g. add_dependencies(). Instead the +AUTOGEN_TARGET_DEPENDS target property can be set to a +;-list of additional dependencies for the +_autogen target. Dependencies can be target names or file names.

+

In total the dependencies of the _autogen target are composed from

+
    +
  • forwarded origin target dependencies +(enabled by default via AUTOGEN_ORIGIN_DEPENDS)

  • +
  • additional user defined dependencies from AUTOGEN_TARGET_DEPENDS

  • +
+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+

Use cases

+

If AUTOMOC or AUTOUIC depends on a file that is either

+ +

it must be added to AUTOGEN_TARGET_DEPENDS.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_USE_SYSTEM_INCLUDE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_USE_SYSTEM_INCLUDE.html new file mode 100644 index 0000000000000000000000000000000000000000..42b177eb12525b5128515b188388a36f1ebcdb32 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOGEN_USE_SYSTEM_INCLUDE.html @@ -0,0 +1,152 @@ + + + + + + + + + AUTOGEN_USE_SYSTEM_INCLUDE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOGEN_USE_SYSTEM_INCLUDE

+
+

New in version 3.27.

+
+

AUTOGEN_USE_SYSTEM_INCLUDE is a boolean property that can be set +on a target to indicate that the autogen target include directory should +be added as a system include directory or normal include directory to the +target.

+

If this property is not set, the autogen target include directory is added +as a system include directory by default. See policy CMP0151.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+

This property is initialized by the +CMAKE_AUTOGEN_USE_SYSTEM_INCLUDE variable if it is set when +a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_COMPILER_PREDEFINES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_COMPILER_PREDEFINES.html new file mode 100644 index 0000000000000000000000000000000000000000..5499614a92a311de0b92a6bd80ffb785496727e5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_COMPILER_PREDEFINES.html @@ -0,0 +1,159 @@ + + + + + + + + + AUTOMOC_COMPILER_PREDEFINES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOMOC_COMPILER_PREDEFINES

+
+

New in version 3.10.

+
+

Boolean value used by AUTOMOC to determine if the +compiler pre definitions file moc_predefs.h should be generated.

+

CMake generates a moc_predefs.h file with compiler pre definitions +from the output of the command defined in +CMAKE_CXX_COMPILER_PREDEFINES_COMMAND +when

+ +

The moc_predefs.h file, which is generated in AUTOGEN_BUILD_DIR, +is passed to moc as the argument to the --include option.

+

By default AUTOMOC_COMPILER_PREDEFINES is initialized from +CMAKE_AUTOMOC_COMPILER_PREDEFINES, which is ON by default.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_DEPEND_FILTERS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_DEPEND_FILTERS.html new file mode 100644 index 0000000000000000000000000000000000000000..d61a2a2f0bfda3f9328da3a63528cda3ba087120 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_DEPEND_FILTERS.html @@ -0,0 +1,247 @@ + + + + + + + + + AUTOMOC_DEPEND_FILTERS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOMOC_DEPEND_FILTERS

+
+

New in version 3.9.

+
+

Filter definitions used by AUTOMOC to extract file names from a +source file that are registered as additional dependencies for the +moc file of the source file.

+

Filters are defined as KEYWORD;REGULAR_EXPRESSION pairs. First the file +content is searched for KEYWORD. If it is found at least once, then file +names are extracted by successively searching for REGULAR_EXPRESSION and +taking the first match group.

+

The file name found in the first match group is searched for

+
    +
  • first in the vicinity of the source file

  • +
  • and afterwards in the target's INCLUDE_DIRECTORIES.

  • +
+

If any of the extracted files changes, then the moc file for the source +file gets rebuilt even when the source file itself doesn't change.

+

If any of the extracted files is GENERATED or if it is not in the +target's sources, then it might be necessary to add it to the +_autogen target dependencies. +See AUTOGEN_TARGET_DEPENDS for reference.

+

By default AUTOMOC_DEPEND_FILTERS is initialized from +CMAKE_AUTOMOC_DEPEND_FILTERS, which is empty by default.

+

From Qt 5.15.0 on this variable is ignored as moc is able to output the correct +dependencies.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+

Example 1

+

A header file my_class.hpp uses a custom macro JSON_FILE_MACRO which +is defined in an other header macros.hpp. +We want the moc file of my_class.hpp to depend on the file name +argument of JSON_FILE_MACRO:

+
// my_class.hpp
+class My_Class : public QObject
+{
+  Q_OBJECT
+  JSON_FILE_MACRO ( "info.json" )
+...
+};
+
+
+

In CMakeLists.txt we add a filter to +CMAKE_AUTOMOC_DEPEND_FILTERS like this:

+
list( APPEND CMAKE_AUTOMOC_DEPEND_FILTERS
+  "JSON_FILE_MACRO"
+  "[\n][ \t]*JSON_FILE_MACRO[ \t]*\\([ \t]*\"([^\"]+)\""
+)
+
+
+

We assume info.json is a plain (not GENERATED) file that is +listed in the target's source. Therefore we do not need to add it to +AUTOGEN_TARGET_DEPENDS.

+
+
+

Example 2

+

In the target my_target a header file complex_class.hpp uses a +custom macro JSON_BASED_CLASS which is defined in an other header +macros.hpp:

+
// macros.hpp
+...
+#define JSON_BASED_CLASS(name, json) \
+class name : public QObject \
+{ \
+  Q_OBJECT \
+  Q_PLUGIN_METADATA(IID "demo" FILE json) \
+  name() {} \
+};
+...
+
+
+
// complex_class.hpp
+#pragma once
+JSON_BASED_CLASS(Complex_Class, "meta.json")
+// end of file
+
+
+

Since complex_class.hpp doesn't contain a Q_OBJECT macro it would be +ignored by AUTOMOC. We change this by adding JSON_BASED_CLASS +to CMAKE_AUTOMOC_MACRO_NAMES:

+
list(APPEND CMAKE_AUTOMOC_MACRO_NAMES "JSON_BASED_CLASS")
+
+
+

We want the moc file of complex_class.hpp to depend on +meta.json. So we add a filter to +CMAKE_AUTOMOC_DEPEND_FILTERS:

+
list(APPEND CMAKE_AUTOMOC_DEPEND_FILTERS
+  "JSON_BASED_CLASS"
+  "[\n^][ \t]*JSON_BASED_CLASS[ \t]*\\([^,]*,[ \t]*\"([^\"]+)\""
+)
+
+
+

Additionally we assume meta.json is GENERATED which is +why we have to add it to AUTOGEN_TARGET_DEPENDS:

+
set_property(TARGET my_target APPEND PROPERTY AUTOGEN_TARGET_DEPENDS "meta.json")
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_EXECUTABLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_EXECUTABLE.html new file mode 100644 index 0000000000000000000000000000000000000000..aaf8fc276dab087128e04153dd724d2bd2fb95e8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_EXECUTABLE.html @@ -0,0 +1,151 @@ + + + + + + + + + AUTOMOC_EXECUTABLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOMOC_EXECUTABLE

+
+

New in version 3.14.

+
+

AUTOMOC_EXECUTABLE is file path pointing to the moc +executable to use for AUTOMOC enabled files. Setting +this property will make CMake skip the automatic detection of the +moc binary as well as the sanity-tests normally run to ensure +that the binary is available and working as expected.

+

Usually this property does not need to be set. Only consider this +property if auto-detection of moc can not work -- e.g. because +you are building the moc binary as part of your project.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_MOC_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_MOC_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..b9865ba4a1c3872e91dc2f3045d2ff38c2e2df03 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_MOC_OPTIONS.html @@ -0,0 +1,194 @@ + + + + + + + + + AUTOMOC_MOC_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOMOC_MOC_OPTIONS

+

Additional options for moc when using AUTOMOC

+

This property is only used if the AUTOMOC property is ON +for this target. In this case, it holds additional command line +options which will be used when moc is executed during the build, i.e. +it is equivalent to the optional OPTIONS argument of the +qt4_wrap_cpp() macro.

+

This property is initialized by the value of the +CMAKE_AUTOMOC_MOC_OPTIONS variable if it is set when a target +is created, or an empty string otherwise.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+

EXAMPLE

+

In this example, the moc tool is invoked with the -D_EXTRA_DEFINE +option when generating the moc file for object.cpp.

+
+
CMakeLists.txt
add_executable(mocOptions object.cpp main.cpp)
+set_property(TARGET mocOptions PROPERTY AUTOMOC ON)
+target_compile_options(mocOptions PRIVATE "-D_EXTRA_DEFINE")
+set_property(TARGET mocOptions PROPERTY AUTOMOC_MOC_OPTIONS "-D_EXTRA_DEFINE")
+target_link_libraries(mocOptions Qt6::Core)
+
+
+
+
object.hpp
#ifndef Object_HPP
+#define Object_HPP
+
+#include <QObject>
+
+#ifdef _EXTRA_DEFINE
+class Object : public QObject
+{
+Q_OBJECT
+public:
+
+  Object();
+
+};
+#endif
+
+#endif
+
+
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_PATH_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_PATH_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..0face1d931cc1b877fbd8e6465cceac3fb9616df --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOMOC_PATH_PREFIX.html @@ -0,0 +1,176 @@ + + + + + + + + + AUTOMOC_PATH_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOMOC_PATH_PREFIX

+
+

New in version 3.16.

+
+

When this property is ON, CMake will generate the -p path prefix +option for moc on AUTOMOC enabled Qt targets.

+

To generate the path prefix, CMake tests if the header compiled by moc +is in any of the target +include directories. If so, CMake will +compute the relative path accordingly. If the header is not in the +include directories, CMake will omit +the -p path prefix option. moc usually generates a +relative include path in that case.

+

AUTOMOC_PATH_PREFIX is initialized from the variable +CMAKE_AUTOMOC_PATH_PREFIX, which is OFF by default.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+

Reproducible builds

+

For reproducible builds it is recommended to keep headers that are moc +compiled in one of the target +include directories and set +AUTOMOC_PATH_PREFIX to ON. This ensures that:

+
    +
  • moc output files are identical on different build setups,

  • +
  • moc output files will compile correctly when the source and/or +build directory is a symbolic link.

  • +
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTORCC.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTORCC.html new file mode 100644 index 0000000000000000000000000000000000000000..0c008a18d3eff610518bc7287614e8e6f3537581 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTORCC.html @@ -0,0 +1,194 @@ + + + + + + + + + AUTORCC — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTORCC

+

Should the target be processed with auto-rcc (for Qt projects).

+

AUTORCC is a boolean specifying whether CMake will handle +the Qt rcc code generator automatically, i.e. without having to use +commands like QT4_ADD_RESOURCES(), QT5_ADD_RESOURCES(), +etc. Currently, Qt versions 4 to 6 are supported.

+

When this property is ON, CMake will handle .qrc files added +as target sources at build time and invoke rcc accordingly. +This property is initialized by the value of the CMAKE_AUTORCC +variable if it is set when a target is created.

+

By default AUTORCC is processed by a +custom command. +If the .qrc file is GENERATED, a +custom target is used instead.

+

When there are multiple .qrc files with the same name, CMake will +generate unspecified unique output file names for rcc. Therefore, if +Q_INIT_RESOURCE() or Q_CLEANUP_RESOURCE() need to be used, the +.qrc file name must be unique.

+
+

Modifiers

+

AUTORCC_EXECUTABLE: +The rcc executable will be detected automatically, but can be forced to +a certain binary by setting this target property.

+

AUTORCC_OPTIONS: +Additional command line options for rcc can be set via this target +property. The corresponding AUTORCC_OPTIONS source file property +can be used to specify options to be applied only to a specific .qrc file.

+

SKIP_AUTORCC: +.qrc files can be excluded from AUTORCC processing by +setting this source file property.

+

SKIP_AUTOGEN: +Source files can be excluded from AUTOMOC, +AUTOUIC and AUTORCC processing by +setting this source file property.

+

AUTOGEN_SOURCE_GROUP: +This global property can be used to group files generated by +AUTOMOC or AUTORCC together in an IDE, e.g. in MSVS.

+

AUTOGEN_TARGETS_FOLDER: +This global property can be used to group AUTOMOC, +AUTOUIC and AUTORCC targets together in an IDE, +e.g. in MSVS.

+

CMAKE_GLOBAL_AUTORCC_TARGET: +A global autorcc target that depends on all AUTORCC targets +in the project will be generated when this variable is ON.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTORCC_EXECUTABLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTORCC_EXECUTABLE.html new file mode 100644 index 0000000000000000000000000000000000000000..a24e35ee062095d4f307391747f7a115576f3dfe --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTORCC_EXECUTABLE.html @@ -0,0 +1,151 @@ + + + + + + + + + AUTORCC_EXECUTABLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTORCC_EXECUTABLE

+
+

New in version 3.14.

+
+

AUTORCC_EXECUTABLE is file path pointing to the rcc +executable to use for AUTORCC enabled files. Setting +this property will make CMake skip the automatic detection of the +rcc binary as well as the sanity-tests normally run to ensure +that the binary is available and working as expected.

+

Usually this property does not need to be set. Only consider this +property if auto-detection of rcc can not work -- e.g. because +you are building the rcc binary as part of your project.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTORCC_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTORCC_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..85463a726be923f88db272812b7a726abe63ffbc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTORCC_OPTIONS.html @@ -0,0 +1,168 @@ + + + + + + + + + AUTORCC_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTORCC_OPTIONS

+

Additional options for rcc when using AUTORCC

+

This property holds additional command line options which will be used +when rcc is executed during the build via AUTORCC, +i.e. it is equivalent to the optional OPTIONS argument of the +qt4_add_resources() macro.

+

This property is initialized by the value of the +CMAKE_AUTORCC_OPTIONS variable if it is set when a target is +created, or an empty string otherwise.

+

The options set on the target may be overridden by AUTORCC_OPTIONS +set on the .qrc source file.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+

EXAMPLE

+
# ...
+set_property(TARGET tgt PROPERTY AUTORCC_OPTIONS "--compress;9")
+# ...
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOUIC.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOUIC.html new file mode 100644 index 0000000000000000000000000000000000000000..41de890ca0fe8f870e436b97b2427a16f45e9265 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOUIC.html @@ -0,0 +1,214 @@ + + + + + + + + + AUTOUIC — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOUIC

+

Should the target be processed with auto-uic (for Qt projects).

+

AUTOUIC is a boolean specifying whether CMake will handle +the Qt uic code generator automatically, i.e. without having to use +commands like QT4_WRAP_UI(), QT5_WRAP_UI(), etc. +Currently, Qt versions 4 to 6 are supported.

+

This property is initialized by the value of the CMAKE_AUTOUIC +variable if it is set when a target is created.

+

When this property is ON, CMake will scan the header and source files at +build time and invoke uic accordingly.

+
+

Header and source file processing

+

At build time, CMake scans each header and source file from the +target's sources for include statements of the form

+
#include "ui_<ui_base>.h"
+
+
+

Once such an include statement is found in a file, CMake searches for the +uic input file <ui_base>.ui

+ +

If the <ui_base>.ui file was found, uic is called on it to generate +ui_<ui_base>.h in the directory

+
    +
  • <AUTOGEN_BUILD_DIR>/include for single configuration generators or in

  • +
  • <AUTOGEN_BUILD_DIR>/include_<CONFIG> for +multi configuration generators.

  • +
+

Where <AUTOGEN_BUILD_DIR> is the value of the target property +AUTOGEN_BUILD_DIR.

+

The include directory is automatically added to the target's +INCLUDE_DIRECTORIES.

+
+
+

Modifiers

+

AUTOUIC_EXECUTABLE: +The uic executable will be detected automatically, but can be forced to +a certain binary using this target property.

+

AUTOUIC_OPTIONS: +Additional command line options for uic can be set via this target +property. The corresponding AUTOUIC_OPTIONS source file property +can be used to specify options to be applied only to a specific +<base_name>.ui file.

+

SKIP_AUTOUIC: +Source files can be excluded from AUTOUIC processing by setting +this source file property.

+

SKIP_AUTOGEN: +Source files can be excluded from AUTOMOC, +AUTOUIC and AUTORCC processing by +setting this source file property.

+

AUTOGEN_TARGETS_FOLDER: +This global property can be used to group AUTOMOC, +AUTOUIC and AUTORCC targets together in an IDE, +e.g. in MSVS.

+

CMAKE_GLOBAL_AUTOGEN_TARGET: +A global autogen target, that depends on all AUTOMOC or +AUTOUIC generated <ORIGIN>_autogen targets in the project, +will be generated when this variable is ON.

+

AUTOGEN_PARALLEL: +This target property controls the number of moc or uic processes to +start in parallel during builds.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOUIC_EXECUTABLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOUIC_EXECUTABLE.html new file mode 100644 index 0000000000000000000000000000000000000000..ba01f9f565e7540941227c2ac386c87e07a52687 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/AUTOUIC_EXECUTABLE.html @@ -0,0 +1,151 @@ + + + + + + + + + AUTOUIC_EXECUTABLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

AUTOUIC_EXECUTABLE

+
+

New in version 3.14.

+
+

AUTOUIC_EXECUTABLE is file path pointing to the uic +executable to use for AUTOUIC enabled files. Setting +this property will make CMake skip the automatic detection of the +uic binary as well as the sanity-tests normally run to ensure +that the binary is available and working as expected.

+

Usually this property does not need to be set. Only consider this +property if auto-detection of uic can not work -- e.g. because +you are building the uic binary as part of your project.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BINARY_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BINARY_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..048838836a3f56c6e262105a6a9a9bcfb0ec64dc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BINARY_DIR.html @@ -0,0 +1,144 @@ + + + + + + + + + BINARY_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

BINARY_DIR

+
+

New in version 3.4.

+
+

This read-only property reports the value of the +CMAKE_CURRENT_BINARY_DIR variable in the directory in which +the target was defined.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_RPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_RPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..3564bf5d6be6624b6a90ba6cb818e3f886aa85ec --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_RPATH.html @@ -0,0 +1,166 @@ + + + + + + + + + BUILD_RPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

BUILD_RPATH

+
+

New in version 3.8.

+
+

A semicolon-separated list specifying +runtime path (RPATH) entries to add to binaries linked in the +build tree (for platforms that support it). By default, CMake sets +the runtime path of binaries in the build tree to contain search +paths it knows are needed to find the shared libraries they link. +Projects may set BUILD_RPATH to specify additional search paths.

+

The build-tree runtime path will not be used for binaries in the +install tree. It will be replaced with the install-tree runtime path +during the installation step. See also the INSTALL_RPATH +target property.

+

This property is initialized by the value of the variable +CMAKE_BUILD_RPATH if it is set when a target is created.

+

This property supports +generator expressions.

+

Other settings that affect the build-tree runtime path include:

+
    +
  • The CMAKE_SKIP_RPATH variable completely disables runtime +paths in both the build tree and install tree.

  • +
  • The SKIP_BUILD_RPATH target property disables setting any +runtime path in the build tree.

  • +
  • The BUILD_RPATH_USE_ORIGIN target property causes the +automatically-generated runtime path to use entries relative to $ORIGIN.

  • +
  • The BUILD_WITH_INSTALL_RPATH target property causes binaries +in the build tree to be built with the install-tree runtime path.

  • +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_RPATH_USE_ORIGIN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_RPATH_USE_ORIGIN.html new file mode 100644 index 0000000000000000000000000000000000000000..4af5734161523b740389bd434df862bc6a6b4e8c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_RPATH_USE_ORIGIN.html @@ -0,0 +1,158 @@ + + + + + + + + + BUILD_RPATH_USE_ORIGIN — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

BUILD_RPATH_USE_ORIGIN

+
+

New in version 3.14.

+
+

Whether to use relative paths for the build RPATH.

+

This property is initialized by the value of the variable +CMAKE_BUILD_RPATH_USE_ORIGIN.

+

On platforms that support runtime paths (RPATH) with the +$ORIGIN token, setting this property to TRUE enables relative +paths in the build RPATH for executables and shared libraries that +point to shared libraries in the same build tree.

+

Normally the build RPATH of a binary contains absolute paths +to the directory of each shared library it links to. The RPATH +entries for directories contained within the build tree can be made +relative to enable relocatable builds and to help achieve reproducible +builds by omitting the build directory from the build environment.

+

This property has no effect on platforms that do not support the +$ORIGIN token in RPATH, or when the CMAKE_SKIP_RPATH +variable is set. The runtime path set through the +BUILD_RPATH target property is also unaffected by this +property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_WITH_INSTALL_NAME_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_WITH_INSTALL_NAME_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..f5acd38cd660796e164ad7608b8724cd9d122524 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_WITH_INSTALL_NAME_DIR.html @@ -0,0 +1,149 @@ + + + + + + + + + BUILD_WITH_INSTALL_NAME_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

BUILD_WITH_INSTALL_NAME_DIR

+
+

New in version 3.9.

+
+

BUILD_WITH_INSTALL_NAME_DIR is a boolean specifying whether the macOS +install_name of a target in the build tree uses the directory given by +INSTALL_NAME_DIR. This setting only applies to targets on macOS.

+

This property is initialized by the value of the variable +CMAKE_BUILD_WITH_INSTALL_NAME_DIR if it is set when a target is +created.

+

If this property is not set and policy CMP0068 is not NEW, the +value of BUILD_WITH_INSTALL_RPATH is used in its place.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_WITH_INSTALL_RPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_WITH_INSTALL_RPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..2e780484e3e4144cd9f7f7cc3f3a5867045b0275 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUILD_WITH_INSTALL_RPATH.html @@ -0,0 +1,148 @@ + + + + + + + + + BUILD_WITH_INSTALL_RPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

BUILD_WITH_INSTALL_RPATH

+

BUILD_WITH_INSTALL_RPATH is a boolean specifying whether to link the target +in the build tree with the INSTALL_RPATH. This takes precedence +over SKIP_BUILD_RPATH and avoids the need for relinking before +installation.

+

This property is initialized by the value of the +CMAKE_BUILD_WITH_INSTALL_RPATH variable if it is set when a target +is created.

+

If policy CMP0068 is not NEW, this property also controls use of +INSTALL_NAME_DIR in the build tree on macOS. Either way, the +BUILD_WITH_INSTALL_NAME_DIR target property takes precedence.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUNDLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUNDLE.html new file mode 100644 index 0000000000000000000000000000000000000000..fd166519184587d9e89b9a95f5a8779e0c337320 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUNDLE.html @@ -0,0 +1,143 @@ + + + + + + + + + BUNDLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

BUNDLE

+

This target is a CFBundle on the macOS.

+

If a module library target has this property set to true it will be +built as a CFBundle when built on the mac. It will have the directory +structure required for a CFBundle and will be suitable to be used for +creating Browser Plugins or other application resources.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUNDLE_EXTENSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUNDLE_EXTENSION.html new file mode 100644 index 0000000000000000000000000000000000000000..07e81cf004ab8c744a215ca2a30540d839f8e381 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/BUNDLE_EXTENSION.html @@ -0,0 +1,142 @@ + + + + + + + + + BUNDLE_EXTENSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

BUNDLE_EXTENSION

+

The file extension used to name a BUNDLE, a FRAMEWORK, +or a MACOSX_BUNDLE target on the macOS and iOS.

+

The default value is bundle, framework, or app for the respective +target types.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMMON_LANGUAGE_RUNTIME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMMON_LANGUAGE_RUNTIME.html new file mode 100644 index 0000000000000000000000000000000000000000..864cae06802901d74bfa252d0840c6d5e9440e67 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMMON_LANGUAGE_RUNTIME.html @@ -0,0 +1,174 @@ + + + + + + + + + COMMON_LANGUAGE_RUNTIME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMMON_LANGUAGE_RUNTIME

+
+

New in version 3.12.

+
+

By setting this target property, the target is configured to build with +C++/CLI support.

+

The Visual Studio generator defines the clr parameter depending on +the value of the COMMON_LANGUAGE_RUNTIME target property:

+

Not Set (default)

+
+

Native C++.

+
+

"" (set but empty)

+
+

Mixed unmanaged/managed C++ using .NET Framework.

+
+
+
netcore
+

New in version 3.26.

+
+

Mixed unmanaged/managed C++ using .NET Core.

+

This required VS 2019's v142 toolset or higher.

+
+
+

pure

+
+

Managed C++.

+
+

safe

+
+

Managed C++.

+
+

This property is only evaluated Visual Studio Generators for +VS 2010 and above.

+

To be able to build managed C++ targets with VS 2017 and above the component +C++/CLI support must be installed, which may not be done by default.

+

See also IMPORTED_COMMON_LANGUAGE_RUNTIME

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_BOOL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_BOOL.html new file mode 100644 index 0000000000000000000000000000000000000000..5e4b214f2750c47a869bc5ffb38fabaa23e47c8a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_BOOL.html @@ -0,0 +1,152 @@ + + + + + + + + + COMPATIBLE_INTERFACE_BOOL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPATIBLE_INTERFACE_BOOL

+

Properties which must be compatible with their link interface

+

The COMPATIBLE_INTERFACE_BOOL property may contain a list of +properties for this target which must be consistent when evaluated as a +boolean with the INTERFACE variant of the property in all linked +dependees. For example, if a property FOO appears in the list, then +for each dependee, the INTERFACE_FOO property content in all of its +dependencies must be consistent with each other, and with the FOO +property in the depender.

+

Consistency in this sense has the meaning that if the property is set, +then it must have the same boolean value as all others, and if the +property is not set, then it is ignored.

+

Note that for each dependee, the set of properties specified in this +property must not intersect with the set specified in any of the other +Compatible Interface Properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MAX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MAX.html new file mode 100644 index 0000000000000000000000000000000000000000..f528b74bbc10a3e9cb8a6336c4520460de455582 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MAX.html @@ -0,0 +1,151 @@ + + + + + + + + + COMPATIBLE_INTERFACE_NUMBER_MAX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPATIBLE_INTERFACE_NUMBER_MAX

+

Properties whose maximum value from the link interface will be used.

+

The COMPATIBLE_INTERFACE_NUMBER_MAX property may contain a list of +properties for this target whose maximum value may be read at generate +time when evaluated in the INTERFACE variant of the property in all +linked dependees. For example, if a property FOO appears in the list, +then for each dependee, the INTERFACE_FOO property content in all of +its dependencies will be compared with each other and with the FOO +property in the depender. When reading the FOO property at generate +time, the maximum value will be returned. If the property is not set, +then it is ignored.

+

Note that for each dependee, the set of properties specified in this +property must not intersect with the set specified in any of the other +Compatible Interface Properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MIN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MIN.html new file mode 100644 index 0000000000000000000000000000000000000000..657f34b74b48844741792add9ba63ed82cf8a332 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MIN.html @@ -0,0 +1,151 @@ + + + + + + + + + COMPATIBLE_INTERFACE_NUMBER_MIN — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPATIBLE_INTERFACE_NUMBER_MIN

+

Properties whose maximum value from the link interface will be used.

+

The COMPATIBLE_INTERFACE_NUMBER_MIN property may contain a list of +properties for this target whose minimum value may be read at generate +time when evaluated in the INTERFACE variant of the property of all +linked dependees. For example, if a +property FOO appears in the list, then for each dependee, the +INTERFACE_FOO property content in all of its dependencies will be +compared with each other and with the FOO property in the depender. +When reading the FOO property at generate time, the minimum value +will be returned. If the property is not set, then it is ignored.

+

Note that for each dependee, the set of properties specified in this +property must not intersect with the set specified in any of the other +Compatible Interface Properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_STRING.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_STRING.html new file mode 100644 index 0000000000000000000000000000000000000000..d0fb6b9d75c7f851bc9a1ebdfd983b7478e930ae --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPATIBLE_INTERFACE_STRING.html @@ -0,0 +1,149 @@ + + + + + + + + + COMPATIBLE_INTERFACE_STRING — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPATIBLE_INTERFACE_STRING

+

Properties which must be string-compatible with their link interface

+

The COMPATIBLE_INTERFACE_STRING property may contain a list of +properties for this target which must be the same when evaluated as a +string in the INTERFACE variant of the property all linked dependees. +For example, if a property FOO appears in the list, then for each +dependee, the INTERFACE_FOO property content in all of its +dependencies must be equal with each other, and with the FOO property +in the depender. If the property is not set, then it is ignored.

+

Note that for each dependee, the set of properties specified in this +property must not intersect with the set specified in any of the other +Compatible Interface Properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_DEFINITIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_DEFINITIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..f8035578f065a28e8ce69f949c8869f208488ef7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_DEFINITIONS.html @@ -0,0 +1,175 @@ + + + + + + + + + COMPILE_DEFINITIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPILE_DEFINITIONS

+

Preprocessor definitions for compiling a target's sources.

+

The COMPILE_DEFINITIONS property may be set to a semicolon-separated +list of preprocessor definitions using the syntax VAR or VAR=value. +Function-style definitions are not supported. CMake will +automatically escape the value correctly for the native build system +(note that CMake language syntax may require escapes to specify some +values).

+

CMake will automatically drop some definitions that are not supported +by the native build tool.

+
+

New in version 3.26: Any leading -D on an item will be removed.

+
+

Disclaimer: Most native build tools have poor support for escaping +certain values. CMake has work-arounds for many cases but some values +may just not be possible to pass correctly. If a value does not seem +to be escaped correctly, do not attempt to work-around the problem by +adding escape sequences to the value. Your work-around may break in a +future version of CMake that has improved escape support. Instead +consider defining the macro in a (configured) header file. Then +report the limitation. Known limitations include:

+
#          - broken almost everywhere
+;          - broken in VS IDE 7.0 and Borland Makefiles
+,          - broken in VS IDE
+%          - broken in some cases in NMake
+& |        - broken in some cases on MinGW
+^ < > \"   - broken in most Make tools on Windows
+
+
+

CMake does not reject these values outright because they do work in +some cases. Use with caution.

+

Contents of COMPILE_DEFINITIONS may use "generator expressions" with the +syntax $<...>. See the cmake-generator-expressions(7) manual +for available expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+

The corresponding COMPILE_DEFINITIONS_<CONFIG> property may +be set to specify per-configuration definitions. Generator expressions +should be preferred instead of setting the alternative property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_FEATURES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_FEATURES.html new file mode 100644 index 0000000000000000000000000000000000000000..d0f918806661df1959070f85d990be8930041ab6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_FEATURES.html @@ -0,0 +1,149 @@ + + + + + + + + + COMPILE_FEATURES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPILE_FEATURES

+
+

New in version 3.1.

+
+

Compiler features enabled for this target.

+

The list of features in this property are a subset of the features listed +in the CMAKE_C_COMPILE_FEATURES, CMAKE_CUDA_COMPILE_FEATURES, and +CMAKE_CXX_COMPILE_FEATURES variables.

+

Contents of COMPILE_FEATURES may use "generator expressions" with the +syntax $<...>. See the cmake-generator-expressions(7) manual for +available expressions. See the cmake-compile-features(7) manual +for information on compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..06e2a9f8e13b35b88fbb1492abaf1e05d7671459 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_OPTIONS.html @@ -0,0 +1,181 @@ + + + + + + + + + COMPILE_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPILE_OPTIONS

+

List of options to pass to the compiler.

+

This property holds a semicolon-separated list +of options specified so far for its target. Use the +target_compile_options() command to append more options. +The options will be added after flags in the +CMAKE_<LANG>_FLAGS and CMAKE_<LANG>_FLAGS_<CONFIG> +variables, but before those propagated from dependencies by the +INTERFACE_COMPILE_OPTIONS property.

+

This property adds compile options for all languages in a target. +Use the COMPILE_LANGUAGE generator expression to specify +per-language compile options.

+

This property is initialized by the COMPILE_OPTIONS directory +property when a target is created, and is used by the generators to set +the options for the compiler.

+

Contents of COMPILE_OPTIONS may use "generator expressions" with the +syntax $<...>. See the cmake-generator-expressions(7) manual +for available expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+
+

Option De-duplication

+

The final set of options used for a target is constructed by +accumulating options from the current target and the usage requirements of +its dependencies. The set of options is de-duplicated to avoid repetition.

+
+

New in version 3.12: While beneficial for individual options, the de-duplication step can break +up option groups. For example, -option A -option B becomes +-option A B. One may specify a group of options using shell-like +quoting along with a SHELL: prefix. The SHELL: prefix is dropped, +and the rest of the option string is parsed using the +separate_arguments() UNIX_COMMAND mode. For example, +"SHELL:-option A" "SHELL:-option B" becomes -option A -option B.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..7a7b9348ddbb2fa80ab96cd795774e3060196c86 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_NAME.html @@ -0,0 +1,152 @@ + + + + + + + + + COMPILE_PDB_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPILE_PDB_NAME

+
+

New in version 3.1.

+
+

Output name for the MS debug symbol .pdb file generated by the +compiler while building source files.

+

This property specifies the base name for the debug symbols file. +If not set, the default is unspecified.

+
+

Note

+

The compiler-generated program database files are specified by the +/Fd compiler flag and are not the same as linker-generated +program database files specified by the /pdb linker flag. +Use the PDB_NAME property to specify the latter.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_NAME_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_NAME_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..3b76b2a824c649af5e75da78cec00e8f11b31f0e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_NAME_CONFIG.html @@ -0,0 +1,151 @@ + + + + + + + + + COMPILE_PDB_NAME_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPILE_PDB_NAME_<CONFIG>

+
+

New in version 3.1.

+
+

Per-configuration output name for the MS debug symbol .pdb file +generated by the compiler while building source files.

+

This is the configuration-specific version of COMPILE_PDB_NAME.

+
+

Note

+

The compiler-generated program database files are specified by the +/Fd compiler flag and are not the same as linker-generated +program database files specified by the /pdb linker flag. +Use the PDB_NAME_<CONFIG> property to specify the latter.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..ee7dcdb2056092cb8a73a2c5c1c3b9d917a18297 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY.html @@ -0,0 +1,154 @@ + + + + + + + + + COMPILE_PDB_OUTPUT_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPILE_PDB_OUTPUT_DIRECTORY

+
+

New in version 3.1.

+
+

Output directory for the MS debug symbol .pdb file +generated by the compiler while building source files.

+

This property specifies the directory into which the MS debug symbols +will be placed by the compiler. This property is initialized by the +value of the CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY variable +if it is set when a target is created.

+
+

Note

+

The compiler-generated program database files are specified by the +/Fd compiler flag and are not the same as linker-generated +program database files specified by the /pdb linker flag. +Use the PDB_OUTPUT_DIRECTORY property to specify the latter.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..d0ad60ea73245b2db52dd88c3d2199132078a78b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.html @@ -0,0 +1,157 @@ + + + + + + + + + COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG>

+
+

New in version 3.1.

+
+

Per-configuration output directory for the MS debug symbol .pdb file +generated by the compiler while building source files.

+

This is a per-configuration version of +COMPILE_PDB_OUTPUT_DIRECTORY, +but multi-configuration generators (Visual Studio, Xcode) do NOT append a +per-configuration subdirectory to the specified directory. This +property is initialized by the value of the +CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG> variable +if it is set when a target is created.

+
+

Note

+

The compiler-generated program database files are specified by the +/Fd compiler flag and are not the same as linker-generated +program database files specified by the /pdb linker flag. +Use the PDB_OUTPUT_DIRECTORY_<CONFIG> property to specify the latter.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_WARNING_AS_ERROR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_WARNING_AS_ERROR.html new file mode 100644 index 0000000000000000000000000000000000000000..1dd02e5443a4b638f3b554dca17b2cc1b72e4bbc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/COMPILE_WARNING_AS_ERROR.html @@ -0,0 +1,172 @@ + + + + + + + + + COMPILE_WARNING_AS_ERROR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

COMPILE_WARNING_AS_ERROR

+
+

New in version 3.24.

+
+

Specify whether to treat warnings on compile as errors. +If enabled, adds a flag to treat warnings on compile as errors. +If the cmake --compile-no-warning-as-error option is given +on the cmake(1) command line, this property is ignored.

+

This property is not implemented for all compilers. It is silently ignored +if there is no implementation for the compiler being used. The currently +implemented compiler IDs are:

+
    +
  • GNU

  • +
  • Clang

  • +
  • AppleClang

  • +
  • Fujitsu

  • +
  • FujitsuClang

  • +
  • IBMClang

  • +
  • Intel

  • +
  • IntelLLVM

  • +
  • LCC

  • +
  • MSVC

  • +
  • NVHPC

  • +
  • NVIDIA (CUDA)

  • +
  • QCC

  • +
  • SunPro

  • +
  • Tasking

  • +
  • TI

  • +
  • VisualAge

  • +
  • XL

  • +
  • XLClang

  • +
+

This property is initialized by the value of the variable +CMAKE_COMPILE_WARNING_AS_ERROR if it is set when a target is +created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CONFIG_OUTPUT_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CONFIG_OUTPUT_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..364f0eb2574e3be2da522e7a71c9014002c54c51 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CONFIG_OUTPUT_NAME.html @@ -0,0 +1,142 @@ + + + + + + + + + <CONFIG>_OUTPUT_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<CONFIG>_OUTPUT_NAME

+

Old per-configuration target file base name. +Use OUTPUT_NAME_<CONFIG> instead.

+

This is a configuration-specific version of the OUTPUT_NAME +target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CONFIG_POSTFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CONFIG_POSTFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..a6af8affe9708111d9d4c2b6d8598a21e6738c29 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CONFIG_POSTFIX.html @@ -0,0 +1,146 @@ + + + + + + + + + <CONFIG>_POSTFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<CONFIG>_POSTFIX

+

Postfix to append to the target file name for configuration <CONFIG>.

+

When building with configuration <CONFIG> the value of this property +is appended to the target file name built on disk. For non-executable +targets, this property is initialized by the value of the +CMAKE_<CONFIG>_POSTFIX variable if it is set when a target is +created. This property is ignored on macOS for Frameworks and App Bundles.

+

For macOS see also the FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG> +target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CROSSCOMPILING_EMULATOR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CROSSCOMPILING_EMULATOR.html new file mode 100644 index 0000000000000000000000000000000000000000..2dc249a84f0d74f7d1384c6df2ef1d7096df4bb1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CROSSCOMPILING_EMULATOR.html @@ -0,0 +1,152 @@ + + + + + + + + + CROSSCOMPILING_EMULATOR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CROSSCOMPILING_EMULATOR

+
+

New in version 3.3.

+
+

Use the given emulator to run executables created when crosscompiling. +This command will be added as a prefix to add_test(), +add_custom_command(), and add_custom_target() commands +for built target system executables.

+
+

New in version 3.15: If this property contains a semicolon-separated list, then the first value is the command and remaining values are its +arguments.

+
+

This property is initialized by the value of the +CMAKE_CROSSCOMPILING_EMULATOR variable if it is set when a target +is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_ARCHITECTURES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_ARCHITECTURES.html new file mode 100644 index 0000000000000000000000000000000000000000..b0c71431712f38697ae56bdafa2837cf89ad3492 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_ARCHITECTURES.html @@ -0,0 +1,198 @@ + + + + + + + + + CUDA_ARCHITECTURES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CUDA_ARCHITECTURES

+
+

New in version 3.18.

+
+

List of architectures to generate device code for.

+

An architecture can be suffixed by either -real or -virtual to specify +the kind of architecture to generate code for. +If no suffix is given then code is generated for both real and virtual +architectures.

+

A non-empty false value (e.g. OFF) disables adding architectures. +This is intended to support packagers and rare cases where full control +over the passed flags is required.

+

This property is initialized by the value of the CMAKE_CUDA_ARCHITECTURES +variable if it is set when a target is created.

+

The CUDA_ARCHITECTURES target property must be set to a non-empty value on targets +that compile CUDA sources, or it is an error. See policy CMP0104.

+

The CUDA_ARCHITECTURES may be set to one of the following special values:

+
+
all
+

New in version 3.23.

+
+

Compile for all supported major and minor real architectures, +and the highest major virtual architecture.

+
+
all-major
+

New in version 3.23.

+
+

Compile for all supported major real architectures, and the highest +major virtual architecture.

+
+
native
+

New in version 3.24.

+
+

Compile for the architecture(s) of the host's GPU(s).

+
+
+
+

Examples

+
set_target_properties(tgt PROPERTIES CUDA_ARCHITECTURES "35;50;72")
+
+
+

Generates code for real and virtual architectures 30, 50 and 72.

+
set_property(TARGET tgt PROPERTY CUDA_ARCHITECTURES 70-real 72-virtual)
+
+
+

Generates code for real architecture 70 and virtual architecture 72.

+
set_property(TARGET tgt PROPERTY CUDA_ARCHITECTURES OFF)
+
+
+

CMake will not pass any architecture flags to the compiler.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_CUBIN_COMPILATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_CUBIN_COMPILATION.html new file mode 100644 index 0000000000000000000000000000000000000000..17bd6d2256471549c0b47dbf071dbf3934f3f243 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_CUBIN_COMPILATION.html @@ -0,0 +1,148 @@ + + + + + + + + + CUDA_CUBIN_COMPILATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CUDA_CUBIN_COMPILATION

+
+

New in version 3.27.

+
+

Compile CUDA sources to .cubin files instead of .obj files +within Object Libraries.

+

For example:

+
add_library(mycubin OBJECT a.cu b.cu)
+set_property(TARGET mycubin PROPERTY CUDA_CUBIN_COMPILATION ON)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..babf7173cfe6de125bf1e9fe2a9b9322b34d5d75 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_EXTENSIONS.html @@ -0,0 +1,154 @@ + + + + + + + + + CUDA_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CUDA_EXTENSIONS

+
+

New in version 3.8.

+
+

Boolean specifying whether compiler specific extensions are requested.

+

This property specifies whether compiler specific extensions should be +used. For some compilers, this results in adding a flag such +as -std=gnu++11 instead of -std=c++11 to the compile line. This +property is ON by default. The basic CUDA/C++ standard level is +controlled by the CUDA_STANDARD target property.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_CUDA_EXTENSIONS variable if set when a target is created +and otherwise by the value of +CMAKE_CUDA_EXTENSIONS_DEFAULT +(see CMP0128).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_FATBIN_COMPILATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_FATBIN_COMPILATION.html new file mode 100644 index 0000000000000000000000000000000000000000..afdb0d7489be9af61431726911c9778fd97a975e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_FATBIN_COMPILATION.html @@ -0,0 +1,148 @@ + + + + + + + + + CUDA_FATBIN_COMPILATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CUDA_FATBIN_COMPILATION

+
+

New in version 3.27.

+
+

Compile CUDA sources to .fatbin files instead of .obj files +within Object Libraries.

+

For example:

+
add_library(myfbins OBJECT a.cu b.cu)
+set_property(TARGET myfbins PROPERTY CUDA_FATBIN_COMPILATION ON)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_OPTIX_COMPILATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_OPTIX_COMPILATION.html new file mode 100644 index 0000000000000000000000000000000000000000..eec52ff98412b29b7b6bc8b3f5089b8f1c1eb916 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_OPTIX_COMPILATION.html @@ -0,0 +1,148 @@ + + + + + + + + + CUDA_OPTIX_COMPILATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CUDA_OPTIX_COMPILATION

+
+

New in version 3.27.

+
+

Compile CUDA sources to .optixir files instead of .obj files +within Object Libraries.

+

For example:

+
add_library(myoptix OBJECT a.cu b.cu)
+set_property(TARGET myoptix PROPERTY CUDA_OPTIX_COMPILATION ON)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_PTX_COMPILATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_PTX_COMPILATION.html new file mode 100644 index 0000000000000000000000000000000000000000..d52205537dd50667ce6488c49ad2a0821e556a6c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_PTX_COMPILATION.html @@ -0,0 +1,148 @@ + + + + + + + + + CUDA_PTX_COMPILATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CUDA_PTX_COMPILATION

+
+

New in version 3.9.

+
+

Compile CUDA sources to .ptx files instead of .obj files +within Object Libraries.

+

For example:

+
add_library(myptx OBJECT a.cu b.cu)
+set_property(TARGET myptx PROPERTY CUDA_PTX_COMPILATION ON)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_RESOLVE_DEVICE_SYMBOLS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_RESOLVE_DEVICE_SYMBOLS.html new file mode 100644 index 0000000000000000000000000000000000000000..2da635e2a792be7adcc0f11bb3028b541a3cdebb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_RESOLVE_DEVICE_SYMBOLS.html @@ -0,0 +1,161 @@ + + + + + + + + + CUDA_RESOLVE_DEVICE_SYMBOLS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CUDA_RESOLVE_DEVICE_SYMBOLS

+
+

New in version 3.9.

+
+

CUDA only: Enables device linking for the specific library target where +required.

+

If set, this will tell the required compilers to enable device linking +on the library target. Device linking is an additional link step +required by some CUDA compilers when CUDA_SEPARABLE_COMPILATION is +enabled. Normally device linking is deferred until a shared library or +executable is generated, allowing for multiple static libraries to resolve +device symbols at the same time when they are used by a shared library or +executable.

+

If this property or CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS is unset, +static libraries are treated as if it is disabled while shared, module, +and executable targets behave as if it is on.

+

If CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS has been defined, +this property is initialized to the value the variable and overriding +the default behavior.

+

Note that device linking is not supported for Object Libraries.

+

For instance:

+
set_property(TARGET mystaticlib PROPERTY CUDA_RESOLVE_DEVICE_SYMBOLS ON)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_RUNTIME_LIBRARY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_RUNTIME_LIBRARY.html new file mode 100644 index 0000000000000000000000000000000000000000..1f70e4196ffd488c5b6990ba1ea2569fcfd15803 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_RUNTIME_LIBRARY.html @@ -0,0 +1,165 @@ + + + + + + + + + CUDA_RUNTIME_LIBRARY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CUDA_RUNTIME_LIBRARY

+
+

New in version 3.17.

+
+

Select the CUDA runtime library for use by compilers targeting the CUDA language.

+

The allowed case insensitive values are:

+
+
None

Link with -cudart=none or equivalent flag(s) to use no CUDA +runtime library.

+
+
Shared

Link with -cudart=shared or equivalent flag(s) to use a +dynamically-linked CUDA runtime library.

+
+
Static

Link with -cudart=static or equivalent flag(s) to use a +statically-linked CUDA runtime library.

+
+
+

Contents of CUDA_RUNTIME_LIBRARY may use +generator expressions.

+

If that property is not set then CMake uses an appropriate default +value based on the compiler to select the CUDA runtime library.

+
+

Note

+

This property has effect only when the CUDA language is enabled. To +control the CUDA runtime linking when only using the CUDA SDK with the +C or C++ language we recommend using the FindCUDAToolkit +module.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_SEPARABLE_COMPILATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_SEPARABLE_COMPILATION.html new file mode 100644 index 0000000000000000000000000000000000000000..96c63ce4d42c52d8aa04b4524ab4b7246be30330 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_SEPARABLE_COMPILATION.html @@ -0,0 +1,151 @@ + + + + + + + + + CUDA_SEPARABLE_COMPILATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CUDA_SEPARABLE_COMPILATION

+
+

New in version 3.8.

+
+

CUDA only: Enables separate compilation of device code

+

If set this will enable separable compilation for all CUDA files for +the given target.

+

For instance:

+
set_property(TARGET myexe PROPERTY CUDA_SEPARABLE_COMPILATION ON)
+
+
+

This property is initialized by the value of the +CMAKE_CUDA_SEPARABLE_COMPILATION variable if it is set when a +target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..344f6d8c2415da48d58000c8418e582c9c3bee66 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CUDA_STANDARD_REQUIRED.html @@ -0,0 +1,153 @@ + + + + + + + + + CUDA_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CUDA_STANDARD_REQUIRED

+
+

New in version 3.8.

+
+

Boolean describing whether the value of CUDA_STANDARD is a requirement.

+

If this property is set to ON, then the value of the +CUDA_STANDARD target property is treated as a requirement. If this +property is OFF or unset, the CUDA_STANDARD target property is +treated as optional and may "decay" to a previous standard if the requested is +not available. For compilers that have no notion of a standard level, such as +MSVC 1800 (Visual Studio 2013) and lower, this has no effect.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_CUDA_STANDARD_REQUIRED variable if it is set when a +target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..23f4e14c183a900901270521fd19d234cad10d1b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_EXTENSIONS.html @@ -0,0 +1,154 @@ + + + + + + + + + CXX_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CXX_EXTENSIONS

+
+

New in version 3.1.

+
+

Boolean specifying whether compiler specific extensions are requested.

+

This property specifies whether compiler specific extensions should be +used. For some compilers, this results in adding a flag such +as -std=gnu++11 instead of -std=c++11 to the compile line. This +property is ON by default. The basic C++ standard level is +controlled by the CXX_STANDARD target property.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_CXX_EXTENSIONS variable if set when a target is created +and otherwise by the value of +CMAKE_CXX_EXTENSIONS_DEFAULT (see +CMP0128).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_DIRS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_DIRS.html new file mode 100644 index 0000000000000000000000000000000000000000..6f140bfeff23a426aa2a5460e9cbdfa173ac651d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_DIRS.html @@ -0,0 +1,153 @@ + + + + + + + + + CXX_MODULE_DIRS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CXX_MODULE_DIRS

+
+

New in version 3.25.

+
+
+

Note

+

Experimental. Gated by CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API

+
+

Semicolon-separated list of base directories of the target's default +C++ module set (i.e. the file set with name and type CXX_MODULES). The +property supports +generator expressions.

+

This property is normally only set by target_sources(FILE_SET) +rather than being manipulated directly.

+

See CXX_MODULE_DIRS_<NAME> for the list of base directories in +other C++ module sets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_DIRS_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_DIRS_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..8e9c66d4082c39ae6338aabf8d011dbdc7d97ace --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_DIRS_NAME.html @@ -0,0 +1,153 @@ + + + + + + + + + CXX_MODULE_DIRS_<NAME> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CXX_MODULE_DIRS_<NAME>

+
+

New in version 3.25.

+
+
+

Note

+

Experimental. Gated by CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API

+
+

Semicolon-separated list of base directories of the target's <NAME> C++ +module set, which has the set type CXX_MODULES. The property supports +generator expressions.

+

This property is normally only set by target_sources(FILE_SET) +rather than being manipulated directly.

+

See CXX_MODULE_DIRS for the list of base directories in the +default C++ module set. See CXX_MODULE_SETS for the file set names +of all C++ module sets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_SET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_SET.html new file mode 100644 index 0000000000000000000000000000000000000000..0552fc1e904cea60d7112268ee93c3fcd66e66ca --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_SET.html @@ -0,0 +1,154 @@ + + + + + + + + + CXX_MODULE_SET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CXX_MODULE_SET

+
+

New in version 3.25.

+
+
+

Note

+

Experimental. Gated by CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API

+
+

Semicolon-separated list of files in the target's default C++ module set, +(i.e. the file set with name and type CXX_MODULES). If any of the paths +are relative, they are computed relative to the target's source directory. The +property supports +generator expressions.

+

This property is normally only set by target_sources(FILE_SET) +rather than being manipulated directly.

+

See CXX_MODULE_SET_<NAME> for the list of files in other C++ +module sets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_SETS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_SETS.html new file mode 100644 index 0000000000000000000000000000000000000000..50d8f4c0deda67863e2a368036354ea1493d4e66 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_SETS.html @@ -0,0 +1,152 @@ + + + + + + + + + CXX_MODULE_SETS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CXX_MODULE_SETS

+
+

New in version 3.25.

+
+
+

Note

+

Experimental. Gated by CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API

+
+

Read-only list of the target's PRIVATE and PUBLIC C++ module sets (i.e. +all file sets with the type CXX_MODULES). Files listed in these file sets +are treated as source files for the purpose of IDE integration.

+

C++ module sets may be defined using the target_sources() command +FILE_SET option with type CXX_MODULES.

+

See also CXX_MODULE_SET_<NAME>, CXX_MODULE_SET and +INTERFACE_CXX_MODULE_SETS.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_SET_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_SET_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..5ef297f1b7bdf9f085c2274c8f63898582f39f51 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_MODULE_SET_NAME.html @@ -0,0 +1,154 @@ + + + + + + + + + CXX_MODULE_SET_<NAME> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CXX_MODULE_SET_<NAME>

+
+

New in version 3.25.

+
+
+

Note

+

Experimental. Gated by CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API

+
+

Semicolon-separated list of files in the target's <NAME> C++ module set, +which has the set type CXX_MODULES. If any of the paths are relative, they +are computed relative to the target's source directory. The property supports +generator expressions.

+

This property is normally only set by target_sources(FILE_SET) +rather than being manipulated directly.

+

See CXX_MODULE_SET for the list of files in the default C++ module +set. See CXX_MODULE_SETS for the file set names of all C++ module +sets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_SCAN_FOR_MODULES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_SCAN_FOR_MODULES.html new file mode 100644 index 0000000000000000000000000000000000000000..e7564e7b0a8d506c6722910cd24e323988d998ad --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_SCAN_FOR_MODULES.html @@ -0,0 +1,160 @@ + + + + + + + + + CXX_SCAN_FOR_MODULES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CXX_SCAN_FOR_MODULES

+
+

New in version 3.26.

+
+

CXX_SCAN_FOR_MODULES is a boolean specifying whether CMake will scan C++ +sources in the target for module dependencies. See also the +CXX_SCAN_FOR_MODULES for per-source settings which, if set, +overrides the target-wide settings.

+

This property is initialized by the value of the +CMAKE_CXX_SCAN_FOR_MODULES variable if it is set when a target is +created.

+

When this property is set ON or unset, CMake will scan the target's +CXX sources at build time and add module dependency information to the +compile line as necessary. When this property is set OFF, CMake will not +scan the target's CXX sources at build time.

+

Note that scanning is only performed if C++20 or higher is enabled for the +target. Scanning for modules in the target's sources belonging to file sets +of type CXX_MODULES is always performed.

+
+

Note

+

This setting is meaningful only when experimental support for C++ modules +has been enabled by the CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API gate.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_STANDARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_STANDARD.html new file mode 100644 index 0000000000000000000000000000000000000000..56f6b322a29a3f2932d3de1233e4a85fcbf11e1a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_STANDARD.html @@ -0,0 +1,194 @@ + + + + + + + + + CXX_STANDARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CXX_STANDARD

+
+

New in version 3.1.

+
+

The C++ standard whose features are requested to build this target.

+

This property specifies the C++ standard whose features are requested +to build this target. For some compilers, this results in adding a +flag such as -std=gnu++11 to the compile line. For compilers that +have no notion of a standard level, such as Microsoft Visual C++ before +2015 Update 3, this has no effect.

+

Supported values are:

+
+
98

C++98

+
+
11

C++11

+
+
14

C++14

+
+
17
+

New in version 3.8.

+
+

C++17

+
+
20
+

New in version 3.12.

+
+

C++20

+
+
23
+

New in version 3.20.

+
+

C++23

+
+
26
+

New in version 3.25.

+
+

C++26. CMake 3.25 and later recognize 26 as a valid value, +no version has support for any compiler.

+
+
+

If the value requested does not result in a compile flag being added for +the compiler in use, a previous standard flag will be added instead. This +means that using:

+
set_property(TARGET tgt PROPERTY CXX_STANDARD 11)
+
+
+

with a compiler which does not support -std=gnu++11 or an equivalent +flag will not result in an error or warning, but will instead add the +-std=gnu++98 flag if supported. This "decay" behavior may be controlled +with the CXX_STANDARD_REQUIRED target property. +Additionally, the CXX_EXTENSIONS target property may be used to +control whether compiler-specific extensions are enabled on a per-target basis.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_CXX_STANDARD variable if it is set when a target +is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..0e280483e26380a0978b9d59e13c1b46cc649cc9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/CXX_STANDARD_REQUIRED.html @@ -0,0 +1,153 @@ + + + + + + + + + CXX_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CXX_STANDARD_REQUIRED

+
+

New in version 3.1.

+
+

Boolean describing whether the value of CXX_STANDARD is a requirement.

+

If this property is set to ON, then the value of the +CXX_STANDARD target property is treated as a requirement. If this +property is OFF or unset, the CXX_STANDARD target property is +treated as optional and may "decay" to a previous standard if the requested is +not available. For compilers that have no notion of a standard level, such as +MSVC 1800 (Visual Studio 2013) and lower, this has no effect.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_CXX_STANDARD_REQUIRED variable if it is set when a +target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/C_STANDARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/C_STANDARD.html new file mode 100644 index 0000000000000000000000000000000000000000..c351e3da39f7471a6976d10a2f05364ee80f153b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/C_STANDARD.html @@ -0,0 +1,183 @@ + + + + + + + + + C_STANDARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

C_STANDARD

+
+

New in version 3.1.

+
+

The C standard whose features are requested to build this target.

+

This property specifies the C standard whose features are requested +to build this target. For some compilers, this results in adding a +flag such as -std=gnu11 to the compile line. For compilers that +have no notion of a C standard level, such as Microsoft Visual C++ before +VS 16.7, this property has no effect.

+

Supported values are:

+
+
90

C89/C90

+
+
99

C99

+
+
11

C11

+
+
17
+

New in version 3.21.

+
+

C17

+
+
23
+

New in version 3.21.

+
+

C23

+
+
+

If the value requested does not result in a compile flag being added for +the compiler in use, a previous standard flag will be added instead. This +means that using:

+
set_property(TARGET tgt PROPERTY C_STANDARD 11)
+
+
+

with a compiler which does not support -std=gnu11 or an equivalent +flag will not result in an error or warning, but will instead add the +-std=gnu99 or -std=gnu90 flag if supported. This "decay" behavior may +be controlled with the C_STANDARD_REQUIRED target property. +Additionally, the C_EXTENSIONS target property may be used to +control whether compiler-specific extensions are enabled on a per-target basis.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_C_STANDARD variable if it is set when a target +is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/C_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/C_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..68db58fc1af741d96d761cb4f84f9770264b04a4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/C_STANDARD_REQUIRED.html @@ -0,0 +1,153 @@ + + + + + + + + + C_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

C_STANDARD_REQUIRED

+
+

New in version 3.1.

+
+

Boolean describing whether the value of C_STANDARD is a requirement.

+

If this property is set to ON, then the value of the +C_STANDARD target property is treated as a requirement. If this +property is OFF or unset, the C_STANDARD target property is +treated as optional and may "decay" to a previous standard if the requested is +not available. For compilers that have no notion of a C standard level, such +as Microsoft Visual C++ before VS 16.7, this property has no effect.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_C_STANDARD_REQUIRED variable if it is set when a +target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEFINE_SYMBOL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEFINE_SYMBOL.html new file mode 100644 index 0000000000000000000000000000000000000000..1ec94b90ef01dc4a0b4b4bdd5b64b900f11662b2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEFINE_SYMBOL.html @@ -0,0 +1,149 @@ + + + + + + + + + DEFINE_SYMBOL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

DEFINE_SYMBOL

+

Define a symbol when compiling this target's sources.

+

DEFINE_SYMBOL sets the name of the preprocessor symbol defined when +compiling sources in a shared library. If not set here then it is set +to target_EXPORTS by default (with some substitutions if the target is +not a valid C identifier). This is useful for headers to know whether +they are being included from inside their library or outside to +properly setup dllexport/dllimport decorations on Windows.

+

On POSIX platforms, this can optionally be used to control the visibility +of symbols.

+

CMake provides support for such decorations with the GenerateExportHeader +module.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEPLOYMENT_ADDITIONAL_FILES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEPLOYMENT_ADDITIONAL_FILES.html new file mode 100644 index 0000000000000000000000000000000000000000..cb906f4309a9b7872edc6bd1cb7af3637b11c45a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEPLOYMENT_ADDITIONAL_FILES.html @@ -0,0 +1,155 @@ + + + + + + + + + DEPLOYMENT_ADDITIONAL_FILES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

DEPLOYMENT_ADDITIONAL_FILES

+
+

New in version 3.13.

+
+

Set the WinCE project AdditionalFiles in DeploymentTool in .vcproj +files generated by the Visual Studio 9 2008 generator. +This is useful when you want to debug on remote WinCE device. +Specify additional files that will be copied to the device. +For example:

+
set_property(TARGET ${TARGET} PROPERTY
+  DEPLOYMENT_ADDITIONAL_FILES "english.lng|local_folder|remote_folder|0"
+  "german.lng|local_folder|remote_folder|0")
+
+
+

produces:

+
<DeploymentTool AdditionalFiles="english.lng|local_folder|remote_folder|0;german.lng|local_folder|remote_folder|0" ... />
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEPLOYMENT_REMOTE_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEPLOYMENT_REMOTE_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..7a07023b02ea8d26c219485a6f69b3f4600055dc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEPLOYMENT_REMOTE_DIRECTORY.html @@ -0,0 +1,155 @@ + + + + + + + + + DEPLOYMENT_REMOTE_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

DEPLOYMENT_REMOTE_DIRECTORY

+
+

New in version 3.6.

+
+

Set the WinCE project RemoteDirectory in DeploymentTool and +RemoteExecutable in DebuggerTool in .vcproj files generated +by the Visual Studio 9 2008 generator. +This is useful when you want to debug on remote WinCE device. +For example:

+
set_property(TARGET ${TARGET} PROPERTY
+  DEPLOYMENT_REMOTE_DIRECTORY "\\FlashStorage")
+
+
+

produces:

+
<DeploymentTool RemoteDirectory="\FlashStorage" ... />
+<DebuggerTool RemoteExecutable="\FlashStorage\target_file" ... />
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEPRECATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEPRECATION.html new file mode 100644 index 0000000000000000000000000000000000000000..772d037ef4ef14b0ac87fa264fef76e565c5db79 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DEPRECATION.html @@ -0,0 +1,149 @@ + + + + + + + + + DEPRECATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

DEPRECATION

+
+

New in version 3.17.

+
+

Deprecation message from imported target's developer.

+

DEPRECATION is the message regarding a deprecation status to be displayed +to downstream users of a target.

+

The message is formatted as follows:

+
    +
  • Lines that do not start in whitespace are wrapped as paragraph text.

  • +
  • Lines that start in whitespace are preserved as preformatted text.

  • +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DISABLE_PRECOMPILE_HEADERS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DISABLE_PRECOMPILE_HEADERS.html new file mode 100644 index 0000000000000000000000000000000000000000..f604866b2f4e2cdd2b1ec17056d8188d6d8073df --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DISABLE_PRECOMPILE_HEADERS.html @@ -0,0 +1,145 @@ + + + + + + + + + DISABLE_PRECOMPILE_HEADERS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

DISABLE_PRECOMPILE_HEADERS

+
+

New in version 3.16.

+
+

Disables the precompilation of header files specified by +PRECOMPILE_HEADERS property.

+

If the property is not set, CMake will use the value provided +by CMAKE_DISABLE_PRECOMPILE_HEADERS.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DLL_NAME_WITH_SOVERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DLL_NAME_WITH_SOVERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..80ccdaa4e36e73f8136cc5f1924f80811a0aa9b9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DLL_NAME_WITH_SOVERSION.html @@ -0,0 +1,151 @@ + + + + + + + + + DLL_NAME_WITH_SOVERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

DLL_NAME_WITH_SOVERSION

+
+

New in version 3.27.

+
+

This property control whether the SOVERSION target +property are added to the filename of generated DLL filenames +for the Windows platform, which is selected when the +WIN32 variable is set.

+

The value of the listed property is appended to the +basename of the runtime component of the shared library +target as -<SOVERSION>.

+

Please note that setting this property has no effect +if versioned filenames are globally disabled with the +CMAKE_PLATFORM_NO_VERSIONED_SONAME variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DOTNET_SDK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DOTNET_SDK.html new file mode 100644 index 0000000000000000000000000000000000000000..12c8ff82cbdb824c43b9d39e0e02030d4d3b0215 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DOTNET_SDK.html @@ -0,0 +1,158 @@ + + + + + + + + + DOTNET_SDK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

DOTNET_SDK

+
+

New in version 3.23.

+
+

Specify the .NET SDK for C# projects. For example: Microsoft.NET.Sdk.

+

This property tells Visual Studio Generators for VS 2019 and +above to generate a .NET SDK-style project using the specified SDK. +The property is meaningful only to these generators, and only in C# +targets. It is ignored for C++ projects, even if they are managed +(e.g. using COMMON_LANGUAGE_RUNTIME).

+

This property must be a non-empty string to generate .NET SDK-style projects. +CMake does not perform any validations for the value of the property.

+

This property may be initialized for all targets using the +CMAKE_DOTNET_SDK variable.

+
+

Note

+

The Visual Studio Generators in this version of CMake have not +yet learned to support add_custom_command() in .NET SDK-style +projects. It is currently an error to attach a custom command to a +target with the DOTNET_SDK property set.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DOTNET_TARGET_FRAMEWORK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DOTNET_TARGET_FRAMEWORK.html new file mode 100644 index 0000000000000000000000000000000000000000..f463f7fd8b5402d0ee64b98c7dc2bfd806eeb3a1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DOTNET_TARGET_FRAMEWORK.html @@ -0,0 +1,148 @@ + + + + + + + + + DOTNET_TARGET_FRAMEWORK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

DOTNET_TARGET_FRAMEWORK

+
+

New in version 3.17.

+
+

Specify the .NET target framework.

+

Used to specify the .NET target framework for C++/CLI and C#. For +example: netcoreapp2.1.

+

This property is only evaluated for Visual Studio Generators +VS 2010 and above.

+

Can be initialized for all targets using the variable +CMAKE_DOTNET_TARGET_FRAMEWORK.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DOTNET_TARGET_FRAMEWORK_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DOTNET_TARGET_FRAMEWORK_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..98d229d5f47d34dde1962898b97c7ac5ad73c204 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/DOTNET_TARGET_FRAMEWORK_VERSION.html @@ -0,0 +1,150 @@ + + + + + + + + + DOTNET_TARGET_FRAMEWORK_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

DOTNET_TARGET_FRAMEWORK_VERSION

+
+

New in version 3.12.

+
+

Specify the .NET target framework version.

+

Used to specify the .NET target framework version for C++/CLI and C#. +For example: v4.5.

+

This property is only evaluated for Visual Studio Generators +VS 2010 and above.

+

To initialize this variable for all targets set +CMAKE_DOTNET_TARGET_FRAMEWORK or +CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION. If both are set, +the latter is ignored.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ENABLE_EXPORTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ENABLE_EXPORTS.html new file mode 100644 index 0000000000000000000000000000000000000000..0a87de26e174b547bc79a9f0e06b872258b398f9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ENABLE_EXPORTS.html @@ -0,0 +1,188 @@ + + + + + + + + + ENABLE_EXPORTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ENABLE_EXPORTS

+

Specify whether an executable or a shared library exports symbols.

+

Normally an executable does not export any symbols because it is the +final program. It is possible for an executable to export symbols to +be used by loadable modules. When this property is set to true CMake +will allow other targets to "link" to the executable with the +target_link_libraries() command. On all platforms a target-level +dependency on the executable is created for targets that link to it. +Handling of the executable on the link lines of the loadable modules +varies by platform:

+
    +
  • On Windows-based systems (including Cygwin) an "import library" is +created along with the executable to list the exported symbols. +Loadable modules link to the import library to get the symbols.

  • +
  • On macOS, loadable modules link to the executable itself using the +-bundle_loader flag.

  • +
  • On AIX, a linker "import file" is created along with the executable +to list the exported symbols for import when linking other targets. +Loadable modules link to the import file to get the symbols.

  • +
  • On other platforms, loadable modules are simply linked without +referencing the executable since the dynamic loader will +automatically bind symbols when the module is loaded.

  • +
+

This property is initialized by the value of the +CMAKE_EXECUTABLE_ENABLE_EXPORTS variable, if it is set when an +executable target is created. If CMAKE_EXECUTABLE_ENABLE_EXPORTS +is not set, the CMAKE_ENABLE_EXPORTS variable is used to initialize +the property instead for backward compatibility reasons. +See below for alternative initialization behavior for shared library targets.

+
+

New in version 3.27: On Apple platforms, to link with a shared library (either a bare library or a +framework), a linker import file can be used instead of the actual shared +library. These linker import files are also known as text-based stubs, and +they have a .tbd file extension.

+

The generation of these linker import files, as well as their consumption, is +controlled by this property. When this property is set to true on a shared +library target, CMake will generate a .tbd file for the library. +Other targets that link to the shared library target will then use this +.tbd file when linking rather than linking to the shared library binary.

+
+

Note

+

For backward compatibility reasons, this property will be ignored if the +XCODE_ATTRIBUTE_GENERATE_TEXT_BASED_STUBS +target property or the +CMAKE_XCODE_ATTRIBUTE_GENERATE_TEXT_BASED_STUBS +variable is set to false.

+
+

For shared library targets, this property is initialized by the value of the +CMAKE_SHARED_LIBRARY_ENABLE_EXPORTS variable, if it is set when +the target is created.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXCLUDE_FROM_ALL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXCLUDE_FROM_ALL.html new file mode 100644 index 0000000000000000000000000000000000000000..0ac4e4a38adf8435a7a55b4ad51136005aac778e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXCLUDE_FROM_ALL.html @@ -0,0 +1,158 @@ + + + + + + + + + EXCLUDE_FROM_ALL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

EXCLUDE_FROM_ALL

+

Set this target property to a true (or false) value to exclude (or include) +the target from the "all" target of the containing directory and its +ancestors. If excluded, running e.g. make in the containing directory +or its ancestors will not build the target by default.

+

If this target property is not set then the target will be included in +the "all" target of the containing directory. Furthermore, it will be +included in the "all" target of its ancestor directories unless the +EXCLUDE_FROM_ALL directory property is set.

+

With EXCLUDE_FROM_ALL set to false or not set at all, the target +will be brought up to date as part of doing a make install or its +equivalent for the CMake generator being used.

+

If a target has EXCLUDE_FROM_ALL set to true, it may still be listed +in an install(TARGETS) command, but the user is responsible for +ensuring that the target's build artifacts are not missing or outdated when +an install is performed.

+

This property may use "generator expressions" with the syntax $<...>. See +the cmake-generator-expressions(7) manual for available expressions.

+

Only the "Ninja Multi-Config" generator supports a property value that varies by +configuration. For all other generators the value of this property must be the +same for all configurations.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXCLUDE_FROM_DEFAULT_BUILD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXCLUDE_FROM_DEFAULT_BUILD.html new file mode 100644 index 0000000000000000000000000000000000000000..3422cba2f2b8f72d5040219749dba8719af27276 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXCLUDE_FROM_DEFAULT_BUILD.html @@ -0,0 +1,142 @@ + + + + + + + + + EXCLUDE_FROM_DEFAULT_BUILD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

EXCLUDE_FROM_DEFAULT_BUILD

+

Exclude target from Build Solution.

+

This property is only used by Visual Studio generators. +When set to TRUE, the target will not be built when you press +Build Solution.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXCLUDE_FROM_DEFAULT_BUILD_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXCLUDE_FROM_DEFAULT_BUILD_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..a0dfb241e860ba66c61c5bbf7acb12ba68490983 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXCLUDE_FROM_DEFAULT_BUILD_CONFIG.html @@ -0,0 +1,144 @@ + + + + + + + + + EXCLUDE_FROM_DEFAULT_BUILD_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

EXCLUDE_FROM_DEFAULT_BUILD_<CONFIG>

+

Per-configuration version of target exclusion from Build Solution.

+

This is the configuration-specific version of +EXCLUDE_FROM_DEFAULT_BUILD. If the generic +EXCLUDE_FROM_DEFAULT_BUILD is also set on a target, +EXCLUDE_FROM_DEFAULT_BUILD_<CONFIG> takes +precedence in configurations for which it has a value.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXPORT_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXPORT_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..de477ed3a72dc9804bdb32254d57db2f10b455af --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXPORT_NAME.html @@ -0,0 +1,142 @@ + + + + + + + + + EXPORT_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

EXPORT_NAME

+

Exported name for target files.

+

This sets the name for the IMPORTED target generated by the +install(EXPORT) and export() commands. +If not set, the logical target name is used by default.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXPORT_NO_SYSTEM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXPORT_NO_SYSTEM.html new file mode 100644 index 0000000000000000000000000000000000000000..737e362a1b5ee527e091352ca523f43adca5459d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXPORT_NO_SYSTEM.html @@ -0,0 +1,148 @@ + + + + + + + + + EXPORT_NO_SYSTEM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

EXPORT_NO_SYSTEM

+
+

New in version 3.25.

+
+

This property affects the behavior of the install(EXPORT) and +export() commands when they install or export the target respectively. +When EXPORT_NO_SYSTEM is set to true, those commands generate an imported +target with SYSTEM property set to false.

+

See the NO_SYSTEM_FROM_IMPORTED target property to set this +behavior on the target consuming the include directories rather than the +one providing them.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXPORT_PROPERTIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXPORT_PROPERTIES.html new file mode 100644 index 0000000000000000000000000000000000000000..38794f33b94a0b7d98eb1ca543f71c9c2a5d573d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EXPORT_PROPERTIES.html @@ -0,0 +1,157 @@ + + + + + + + + + EXPORT_PROPERTIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

EXPORT_PROPERTIES

+
+

New in version 3.12.

+
+

List additional properties to export for a target.

+

This property contains a list of property names that should be exported by +the install(EXPORT) and export() commands. By default +only a limited number of properties are exported. This property can be used +to additionally export other properties as well.

+

Properties starting with INTERFACE_ or IMPORTED_ are not allowed as +they are reserved for internal CMake use.

+

Properties containing generator expressions are also not allowed.

+
+

Note

+

Since CMake 3.19, Interface Libraries may have arbitrary +target properties. If a project exports an interface library +with custom properties, the resulting package may not work with +dependents configured by older versions of CMake that reject the +custom properties.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EchoString.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EchoString.html new file mode 100644 index 0000000000000000000000000000000000000000..28a11fe36e1963a5b4924443e1914460a61063e0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/EchoString.html @@ -0,0 +1,141 @@ + + + + + + + + + EchoString — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

EchoString

+

A message to be displayed when the target is built.

+

A message to display on some generators (such as Makefile Generators) +when the target is built.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FOLDER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FOLDER.html new file mode 100644 index 0000000000000000000000000000000000000000..7d3dac3b4eb1c162122e5aaee40127216e152fd7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FOLDER.html @@ -0,0 +1,152 @@ + + + + + + + + + FOLDER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

FOLDER

+

For IDEs that present targets using a folder hierarchy, this property +specifies the name of the folder to place the target under. +To nest folders, use FOLDER values such as GUI/Dialogs with / +characters separating folder levels. Targets with no FOLDER property +will appear as top level entities. Targets with the same FOLDER +property value will appear in the same folder as siblings.

+

Only some CMake generators honor the FOLDER property +(e.g. Xcode or any of the +Visual Studio generators). +Those generators that don't will simply ignore it.

+

This property is initialized by the value of the variable +CMAKE_FOLDER if it is set when a target is created.

+

The global property USE_FOLDERS must be set to true, otherwise +the FOLDER property is ignored.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FRAMEWORK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FRAMEWORK.html new file mode 100644 index 0000000000000000000000000000000000000000..efa8faf6b1e22e9538f0172c280ee2706a8cfef7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FRAMEWORK.html @@ -0,0 +1,167 @@ + + + + + + + + + FRAMEWORK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

FRAMEWORK

+

Build SHARED or STATIC library as Framework Bundle on the macOS and iOS.

+

If such a library target has this property set to TRUE it will be +built as a framework when built on the macOS and iOS. It will have the +directory structure required for a framework and will be suitable to +be used with the -framework option. This property is initialized by the +value of the CMAKE_FRAMEWORK variable if it is set when a target is +created.

+

To customize Info.plist file in the framework, use +MACOSX_FRAMEWORK_INFO_PLIST target property.

+

For macOS see also the FRAMEWORK_VERSION target property.

+

Example of creation dynamicFramework:

+
add_library(dynamicFramework SHARED
+            dynamicFramework.c
+            dynamicFramework.h
+)
+set_target_properties(dynamicFramework PROPERTIES
+  FRAMEWORK TRUE
+  FRAMEWORK_VERSION C
+  MACOSX_FRAMEWORK_IDENTIFIER com.cmake.dynamicFramework
+  MACOSX_FRAMEWORK_INFO_PLIST Info.plist
+  # "current version" in semantic format in Mach-O binary file
+  VERSION 16.4.0
+  # "compatibility version" in semantic format in Mach-O binary file
+  SOVERSION 1.0.0
+  PUBLIC_HEADER dynamicFramework.h
+  XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "iPhone Developer"
+)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..a8408da4ef428e34d82fab63c90405efbaedc484 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.html @@ -0,0 +1,161 @@ + + + + + + + + + FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG>

+
+

New in version 3.18.

+
+

Postfix to append to the framework file name for configuration <CONFIG>, +when using a multi-config generator (like Xcode and Ninja Multi-Config).

+

When building with configuration <CONFIG> the value of this property +is appended to the framework file name built on disk.

+

For example, given a framework called my_fw, a value of _debug +for the FRAMEWORK_MULTI_CONFIG_POSTFIX_DEBUG property, and +Debug;Release in CMAKE_CONFIGURATION_TYPES, the following +relevant files would be created for the Debug and Release +configurations:

+
    +
  • Release/my_fw.framework/my_fw

  • +
  • Release/my_fw.framework/Versions/A/my_fw

  • +
  • Debug/my_fw.framework/my_fw_debug

  • +
  • Debug/my_fw.framework/Versions/A/my_fw_debug

  • +
+

For framework targets, this property is initialized by the value of the +CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG> variable if it +is set when a target is created.

+

This property is ignored for non-framework targets, and when using single +config generators.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FRAMEWORK_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FRAMEWORK_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..6002297ba8d54c9da92d6e6046f6a7939774fa28 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/FRAMEWORK_VERSION.html @@ -0,0 +1,145 @@ + + + + + + + + + FRAMEWORK_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

FRAMEWORK_VERSION

+
+

New in version 3.4.

+
+

Version of a framework created using the FRAMEWORK target +property (e.g. A).

+

This property only affects macOS, as iOS doesn't have versioned +directory structure.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Fortran_BUILDING_INSTRINSIC_MODULES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Fortran_BUILDING_INSTRINSIC_MODULES.html new file mode 100644 index 0000000000000000000000000000000000000000..e09bbd38603d887d0f7ae155d1db61aacc006a22 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Fortran_BUILDING_INSTRINSIC_MODULES.html @@ -0,0 +1,150 @@ + + + + + + + + + Fortran_BUILDING_INSTRINSIC_MODULES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

Fortran_BUILDING_INSTRINSIC_MODULES

+
+

New in version 3.22.

+
+

Instructs the CMake Fortran preprocessor that the target is building +Fortran intrinsics for building a Fortran compiler.

+

This property is off by default and should be turned only on projects +that build a Fortran compiler. It should not be turned on for projects +that use a Fortran compiler.

+

Turning this property on will correctly add dependencies for building +Fortran intrinsic modules whereas turning the property off will ignore +Fortran intrinsic modules in the dependency graph as they are supplied +by the compiler itself.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Fortran_FORMAT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Fortran_FORMAT.html new file mode 100644 index 0000000000000000000000000000000000000000..f8f8a70dde89e363729d99110146f5c75cd662d9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Fortran_FORMAT.html @@ -0,0 +1,145 @@ + + + + + + + + + Fortran_FORMAT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

Fortran_FORMAT

+

Set to FIXED or FREE to indicate the Fortran source layout.

+

This property tells CMake whether the Fortran source files in a target +use fixed-format or free-format. CMake will pass the corresponding +format flag to the compiler. Use the source-specific Fortran_FORMAT +property to change the format of a specific source file. If the +variable CMAKE_Fortran_FORMAT is set when a target is created its +value is used to initialize this property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Fortran_MODULE_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Fortran_MODULE_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..d4e08c987ef66d90cd66d075ebe38bc013489bc2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Fortran_MODULE_DIRECTORY.html @@ -0,0 +1,157 @@ + + + + + + + + + Fortran_MODULE_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

Fortran_MODULE_DIRECTORY

+

Specify output directory for Fortran modules provided by the target.

+

If the target contains Fortran source files that provide modules and +the compiler supports a module output directory this specifies the +directory in which the modules will be placed. When this property is +not set the modules will be placed in the build directory +corresponding to the target's source directory. If the variable +CMAKE_Fortran_MODULE_DIRECTORY is set when a target is created its +value is used to initialize this property.

+

When using one of the Visual Studio Generators with the Intel Fortran +plugin installed in Visual Studio, a subdirectory named after the +configuration will be appended to the path where modules are created. +For example, if Fortran_MODULE_DIRECTORY is set to C:/some/path, +modules will end up in C:/some/path/Debug (or +C:/some/path/Release etc.) when an Intel Fortran .vfproj file is +generated, and in C:/some/path when any other generator is used.

+

Note that some compilers will automatically search the module output +directory for modules USEd during compilation but others will not. If +your sources USE modules their location must be specified by +INCLUDE_DIRECTORIES regardless of this property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/GENERATOR_FILE_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/GENERATOR_FILE_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..70eb5bd4e66cf4c4627ae9056b94f26fb72a8034 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/GENERATOR_FILE_NAME.html @@ -0,0 +1,143 @@ + + + + + + + + + GENERATOR_FILE_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

GENERATOR_FILE_NAME

+

Generator's file for this target.

+

An internal property used by some generators to record the name of the +project or dsp file associated with this target. Note that at +configure time, this property is only set for targets created by +include_external_msproject().

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/GHS_INTEGRITY_APP.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/GHS_INTEGRITY_APP.html new file mode 100644 index 0000000000000000000000000000000000000000..439b857e8e5e933d71b3be74b1d20e6568a1a66f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/GHS_INTEGRITY_APP.html @@ -0,0 +1,146 @@ + + + + + + + + + GHS_INTEGRITY_APP — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

GHS_INTEGRITY_APP

+
+

New in version 3.14.

+
+

ON / OFF boolean to determine if an executable target should +be treated as an Integrity Application.

+

If no value is set and if a .int file is added as a source file to the +executable target it will be treated as an Integrity Application.

+

Supported on Green Hills MULTI.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/GNUtoMS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/GNUtoMS.html new file mode 100644 index 0000000000000000000000000000000000000000..e87d149ab63975dc1eb74190b8dc925669d8e918 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/GNUtoMS.html @@ -0,0 +1,150 @@ + + + + + + + + + GNUtoMS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

GNUtoMS

+

Convert GNU import library (.dll.a) to MS format (.lib).

+

When linking a shared library or executable that exports symbols using +GNU tools on Windows (MinGW/MSYS) with Visual Studio installed convert +the import library (.dll.a) from GNU to MS format (.lib). Both import +libraries will be installed by install(TARGETS) and exported by +install(EXPORT) and export() to be linked +by applications with either GNU- or MS-compatible tools.

+

If the variable CMAKE_GNUtoMS is set when a target is created its +value is used to initialize this property. The variable must be set +prior to the first command that enables a language such as project() +or enable_language(). CMake provides the variable as an option to the +user automatically when configuring on Windows with GNU tools.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HAS_CXX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HAS_CXX.html new file mode 100644 index 0000000000000000000000000000000000000000..b4bfcb15c7d10e876a6c66247b25fcd1220e65b6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HAS_CXX.html @@ -0,0 +1,141 @@ + + + + + + + + + HAS_CXX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

HAS_CXX

+

Link the target using the C++ linker tool (obsolete).

+

This is equivalent to setting the LINKER_LANGUAGE +property to CXX.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_DIRS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_DIRS.html new file mode 100644 index 0000000000000000000000000000000000000000..b8c5bbe94db5ddacd31d9331ffb727f0f6f65e5c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_DIRS.html @@ -0,0 +1,148 @@ + + + + + + + + + HEADER_DIRS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

HEADER_DIRS

+
+

New in version 3.23.

+
+

Semicolon-separated list of base directories of the target's default +header set (i.e. the file set with name and type HEADERS). The property +supports generator expressions.

+

This property is normally only set by target_sources(FILE_SET) +rather than being manipulated directly.

+

See HEADER_DIRS_<NAME> for the list of base directories in +other header sets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_DIRS_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_DIRS_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..2f2a5b8efdb493670982da1a1919082e1bea657a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_DIRS_NAME.html @@ -0,0 +1,149 @@ + + + + + + + + + HEADER_DIRS_<NAME> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

HEADER_DIRS_<NAME>

+
+

New in version 3.23.

+
+

Semicolon-separated list of base directories of the target's <NAME> +header set, which has the set type HEADERS. The property supports +generator expressions.

+

This property is normally only set by target_sources(FILE_SET) +rather than being manipulated directly.

+

See HEADER_DIRS for the list of base directories in the +default header set. See HEADER_SETS for the file set names of all +header sets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_SET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_SET.html new file mode 100644 index 0000000000000000000000000000000000000000..0299397c90b30df27c80e20d58804580a22e139b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_SET.html @@ -0,0 +1,149 @@ + + + + + + + + + HEADER_SET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

HEADER_SET

+
+

New in version 3.23.

+
+

Semicolon-separated list of files in the target's default header set, +(i.e. the file set with name and type HEADERS). If any of the paths +are relative, they are computed relative to the target's source directory. +The property supports +generator expressions.

+

This property is normally only set by target_sources(FILE_SET) +rather than being manipulated directly.

+

See HEADER_SET_<NAME> for the list of files in other header sets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_SETS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_SETS.html new file mode 100644 index 0000000000000000000000000000000000000000..9fd17b34c5587652bbe1f2d8e23e2b2901cd57df --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_SETS.html @@ -0,0 +1,149 @@ + + + + + + + + + HEADER_SETS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

HEADER_SETS

+
+

New in version 3.23.

+
+

Read-only list of the target's PRIVATE and PUBLIC header sets (i.e. +all file sets with the type HEADERS). Files listed in these file sets are +treated as source files for the purpose of IDE integration. The files also +have their HEADER_FILE_ONLY property set to TRUE.

+

Header sets may be defined using the target_sources() command +FILE_SET option with type HEADERS.

+

See also HEADER_SET_<NAME>, HEADER_SET and +INTERFACE_HEADER_SETS.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_SET_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_SET_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..06763159ba49639b6048c28924a81b59aeea8a16 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HEADER_SET_NAME.html @@ -0,0 +1,149 @@ + + + + + + + + + HEADER_SET_<NAME> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

HEADER_SET_<NAME>

+
+

New in version 3.23.

+
+

Semicolon-separated list of files in the target's <NAME> header set, +which has the set type HEADERS. If any of the paths are relative, +they are computed relative to the target's source directory. The property +supports generator expressions.

+

This property is normally only set by target_sources(FILE_SET) +rather than being manipulated directly.

+

See HEADER_SET for the list of files in the default header set. +See HEADER_SETS for the file set names of all header sets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HIP_ARCHITECTURES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HIP_ARCHITECTURES.html new file mode 100644 index 0000000000000000000000000000000000000000..15a82c7951d10fc75c2beed3c89c379b60562914 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HIP_ARCHITECTURES.html @@ -0,0 +1,168 @@ + + + + + + + + + HIP_ARCHITECTURES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

HIP_ARCHITECTURES

+
+

New in version 3.21.

+
+

List of AMD GPU architectures to generate device code for.

+

A non-empty false value (e.g. OFF) disables adding architectures. +This is intended to support packagers and rare cases where full control +over the passed flags is required.

+

This property is initialized by the value of the CMAKE_HIP_ARCHITECTURES +variable if it is set when a target is created.

+

The HIP compilation model has two modes: whole and separable. Whole compilation +generates device code at compile time. Separable compilation generates device +code at link time. Therefore the HIP_ARCHITECTURES target property should +be set on targets that compile or link with any HIP sources.

+
+

Examples

+
set_property(TARGET tgt PROPERTY HIP_ARCHITECTURES gfx801 gfx900)
+
+
+

Generates code for both gfx801 and gfx900.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HIP_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HIP_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..6baf1d0a5320be3942023fa0d59df3622b8c95f9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HIP_EXTENSIONS.html @@ -0,0 +1,154 @@ + + + + + + + + + HIP_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

HIP_EXTENSIONS

+
+

New in version 3.21.

+
+

Boolean specifying whether compiler specific extensions are requested.

+

This property specifies whether compiler specific extensions should be +used. For some compilers, this results in adding a flag such +as -std=gnu++11 instead of -std=c++11 to the compile line. This +property is ON by default. The basic HIP/C++ standard level is +controlled by the HIP_STANDARD target property.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_HIP_EXTENSIONS variable if set when a target is created +and otherwise by the value of +CMAKE_HIP_EXTENSIONS_DEFAULT (see +CMP0128).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HIP_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HIP_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..82d40e8a969a494ab4469afe5c6265d75e085587 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/HIP_STANDARD_REQUIRED.html @@ -0,0 +1,152 @@ + + + + + + + + + HIP_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

HIP_STANDARD_REQUIRED

+
+

New in version 3.21.

+
+

Boolean describing whether the value of HIP_STANDARD is a requirement.

+

If this property is set to ON, then the value of the +HIP_STANDARD target property is treated as a requirement. If this +property is OFF or unset, the HIP_STANDARD target property is +treated as optional and may "decay" to a previous standard if the requested is +not available.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_HIP_STANDARD_REQUIRED variable if it is set when a +target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPLICIT_DEPENDS_INCLUDE_TRANSFORM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPLICIT_DEPENDS_INCLUDE_TRANSFORM.html new file mode 100644 index 0000000000000000000000000000000000000000..746a45cec79f3199b7ccf88a76479670bf80ee12 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPLICIT_DEPENDS_INCLUDE_TRANSFORM.html @@ -0,0 +1,159 @@ + + + + + + + + + IMPLICIT_DEPENDS_INCLUDE_TRANSFORM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPLICIT_DEPENDS_INCLUDE_TRANSFORM

+

Specify #include line transforms for dependencies in a target.

+

This property specifies rules to transform macro-like #include lines +during implicit dependency scanning of C and C++ source files. The +list of rules must be semicolon-separated with each entry of the form +A_MACRO(%)=value-with-% (the % must be literal). During dependency +scanning occurrences of A_MACRO(...) on #include lines will be +replaced by the value given with the macro argument substituted for +%. For example, the entry

+
MYDIR(%)=<mydir/%>
+
+
+

will convert lines of the form

+
#include MYDIR(myheader.h)
+
+
+

to

+
#include <mydir/myheader.h>
+
+
+

allowing the dependency to be followed.

+

This property applies to sources in the target on which it is set.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED.html new file mode 100644 index 0000000000000000000000000000000000000000..79e10d07f7da035b2ec0be0e0ca98c7b5ce2be56 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED.html @@ -0,0 +1,142 @@ + + + + + + + + + IMPORTED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED

+

Read-only indication of whether a target is IMPORTED.

+

The boolean value of this property is True for targets created with +the IMPORTED option to add_executable() or add_library(). +It is False for targets built within the project.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_COMMON_LANGUAGE_RUNTIME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_COMMON_LANGUAGE_RUNTIME.html new file mode 100644 index 0000000000000000000000000000000000000000..80b4a5445546dbc6f85c7cb87fe0fa7d00cd8a1a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_COMMON_LANGUAGE_RUNTIME.html @@ -0,0 +1,144 @@ + + + + + + + + + IMPORTED_COMMON_LANGUAGE_RUNTIME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_COMMON_LANGUAGE_RUNTIME

+
+

New in version 3.12.

+
+

Property to define if the target uses C++/CLI.

+

Ignored for non-imported targets.

+

See also the COMMON_LANGUAGE_RUNTIME target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_CONFIGURATIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_CONFIGURATIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..9ad395752930dcde48f2bdbf32c1333909c3b65a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_CONFIGURATIONS.html @@ -0,0 +1,155 @@ + + + + + + + + + IMPORTED_CONFIGURATIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_CONFIGURATIONS

+

Configurations provided for an imported target.

+

Set this to the list of configuration names available for an imported +target. For each configuration named, the imported target's artifacts +must be specified in other target properties:

+ +

The configuration names correspond to those defined in the project from +which the target is imported. If the importing project uses a different +set of configurations, the names may be mapped using the +MAP_IMPORTED_CONFIG_<CONFIG> target property.

+

The IMPORTED_CONFIGURATIONS property is ignored for non-imported targets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_GLOBAL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_GLOBAL.html new file mode 100644 index 0000000000000000000000000000000000000000..2ab46f1db8eb6804a12fe343284fb5b70fc1942a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_GLOBAL.html @@ -0,0 +1,166 @@ + + + + + + + + + IMPORTED_GLOBAL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_GLOBAL

+
+

New in version 3.11.

+
+

Indication of whether an IMPORTED target is +globally visible.

+

The boolean value of this property is True for targets created with the +IMPORTED GLOBAL options to add_executable() or +add_library(). It is always False for targets built within the +project.

+

For targets created with the IMPORTED option to +add_executable() or add_library() but without the +additional option GLOBAL this is False, too. However, setting this +property for such a locally IMPORTED target to True promotes that +target to global scope. This promotion can only be done in the same +directory where that IMPORTED target was created in the first place.

+
+

Note

+

Once an imported target has been made global, it cannot be changed back to +non-global. Therefore, if a project sets this property, it may only +provide a value of True. CMake will issue an error if the project tries to +set the property to a non-True value, even if the value was already False.

+
+
+

Note

+

Local ALIAS targets created before promoting an +IMPORTED target from LOCAL to GLOBAL, keep +their initial scope (see ALIAS_GLOBAL target property).

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_IMPLIB.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_IMPLIB.html new file mode 100644 index 0000000000000000000000000000000000000000..5c3d253998d666b21cbddd85388951b1b988766d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_IMPLIB.html @@ -0,0 +1,157 @@ + + + + + + + + + IMPORTED_IMPLIB — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_IMPLIB

+

Full path to the import library for an IMPORTED target.

+

This property may be set:

+
    +
  • On DLL platforms, to the location of the .lib part of the DLL.

  • +
  • On AIX, to an import file (e.g. .imp) created for executables that export +symbols (see the ENABLE_EXPORTS target property).

  • +
  • On macOS, to an import file (e.g. .tbd) created for shared libraries (see +the ENABLE_EXPORTS target property). For frameworks this is the +location of the .tbd file symlink just inside the framework folder.

  • +
+

The IMPORTED_IMPLIB target property may be overridden for a +given configuration <CONFIG> by the configuration-specific +IMPORTED_IMPLIB_<CONFIG> target property. Furthermore, +the MAP_IMPORTED_CONFIG_<CONFIG> target property may be +used to map between a project's configurations and those of an imported +target. If none of these is set then the name of any other configuration +listed in the IMPORTED_CONFIGURATIONS target property may be +selected and its IMPORTED_IMPLIB_<CONFIG> value used.

+

This property is ignored for non-imported targets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_IMPLIB_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_IMPLIB_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..3ab78599687fddca27fcc050d69b1f5ebada6005 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_IMPLIB_CONFIG.html @@ -0,0 +1,141 @@ + + + + + + + + + IMPORTED_IMPLIB_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_IMPLIB_<CONFIG>

+

<CONFIG>-specific version of IMPORTED_IMPLIB property.

+

Configuration names correspond to those provided by the project from +which the target is imported.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LIBNAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LIBNAME.html new file mode 100644 index 0000000000000000000000000000000000000000..e86dd38bb4d723aa914181acf5f3e1b71e4ed798 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LIBNAME.html @@ -0,0 +1,158 @@ + + + + + + + + + IMPORTED_LIBNAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_LIBNAME

+
+

New in version 3.8.

+
+

Specify the link library name for an imported +Interface Library.

+

An interface library builds no library file itself but does specify +usage requirements for its consumers. The IMPORTED_LIBNAME +property may be set to specify a single library name to be placed +on the link line in place of the interface library target name as +a requirement for using the interface.

+

This property is intended for use in naming libraries provided by +a platform SDK for which the full path to a library file may not +be known. The value may be a plain library name such as foo +but may not be a path (e.g. /usr/lib/libfoo.so) or a flag +(e.g. -Wl,...). The name is never treated as a library target +name even if it happens to name one.

+

The IMPORTED_LIBNAME property is allowed only on +imported Interface Libraries +and is rejected on targets of other types (for which +the IMPORTED_LOCATION target property may be used).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LIBNAME_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LIBNAME_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..01ba11ab353a02f7aed157c92654cc483efac672 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LIBNAME_CONFIG.html @@ -0,0 +1,144 @@ + + + + + + + + + IMPORTED_LIBNAME_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_LIBNAME_<CONFIG>

+
+

New in version 3.8.

+
+

<CONFIG>-specific version of IMPORTED_LIBNAME property.

+

Configuration names correspond to those provided by the project from +which the target is imported.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_DEPENDENT_LIBRARIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_DEPENDENT_LIBRARIES.html new file mode 100644 index 0000000000000000000000000000000000000000..f0da36c9f3ca658ad86828f3abd177cee026e84b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_DEPENDENT_LIBRARIES.html @@ -0,0 +1,148 @@ + + + + + + + + + IMPORTED_LINK_DEPENDENT_LIBRARIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_DEPENDENT_LIBRARIES_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_DEPENDENT_LIBRARIES_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..ec00841be92ddc80f8003d52cec239d960432242 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_DEPENDENT_LIBRARIES_CONFIG.html @@ -0,0 +1,142 @@ + + + + + + + + + IMPORTED_LINK_DEPENDENT_LIBRARIES_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LANGUAGES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LANGUAGES.html new file mode 100644 index 0000000000000000000000000000000000000000..c80cbbae1128a59243f1c0defa53ee606e85bbe5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LANGUAGES.html @@ -0,0 +1,147 @@ + + + + + + + + + IMPORTED_LINK_INTERFACE_LANGUAGES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LANGUAGES_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LANGUAGES_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..0c9dcdcaabbd61376b6a8982e6d05437823c3bb6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LANGUAGES_CONFIG.html @@ -0,0 +1,142 @@ + + + + + + + + + IMPORTED_LINK_INTERFACE_LANGUAGES_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LIBRARIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LIBRARIES.html new file mode 100644 index 0000000000000000000000000000000000000000..e6bce884245bd256b95aa303b21bfc5efb2eb2b4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LIBRARIES.html @@ -0,0 +1,148 @@ + + + + + + + + + IMPORTED_LINK_INTERFACE_LIBRARIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LIBRARIES_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LIBRARIES_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..ff2fafc9ca313a924b1b554af06f5b524c8ca8f5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_LIBRARIES_CONFIG.html @@ -0,0 +1,145 @@ + + + + + + + + + IMPORTED_LINK_INTERFACE_LIBRARIES_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_MULTIPLICITY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_MULTIPLICITY.html new file mode 100644 index 0000000000000000000000000000000000000000..a052e8f5a9cbb58169a1049d17bc18c50b705c8e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_MULTIPLICITY.html @@ -0,0 +1,140 @@ + + + + + + + + + IMPORTED_LINK_INTERFACE_MULTIPLICITY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_MULTIPLICITY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_MULTIPLICITY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..5cf09b923c644e876c12cff05628af4753ff3001 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LINK_INTERFACE_MULTIPLICITY_CONFIG.html @@ -0,0 +1,141 @@ + + + + + + + + + IMPORTED_LINK_INTERFACE_MULTIPLICITY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LOCATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LOCATION.html new file mode 100644 index 0000000000000000000000000000000000000000..86198673550f12fd2bbabc22619e2bf28e4ac78f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LOCATION.html @@ -0,0 +1,162 @@ + + + + + + + + + IMPORTED_LOCATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_LOCATION

+

Full path to the main file on disk for an IMPORTED target.

+

Set this to the location of an IMPORTED target file on disk. For +executables this is the location of the executable file. For STATIC +libraries and modules this is the location of the library or module. +For SHARED libraries on non-DLL platforms this is the location of the +shared library. For application bundles on macOS this is the location of +the executable file inside Contents/MacOS within the bundle folder. +For frameworks on macOS this is the location of the +library file symlink just inside the framework folder. For DLLs this +is the location of the .dll part of the library. For UNKNOWN +libraries this is the location of the file to be linked. Ignored for +non-imported targets.

+

The IMPORTED_LOCATION target property may be overridden for a +given configuration <CONFIG> by the configuration-specific +IMPORTED_LOCATION_<CONFIG> target property. Furthermore, +the MAP_IMPORTED_CONFIG_<CONFIG> target property may be +used to map between a project's configurations and those of an imported +target. If none of these is set then the name of any other configuration +listed in the IMPORTED_CONFIGURATIONS target property may be +selected and its IMPORTED_LOCATION_<CONFIG> value used.

+

To get the location of an imported target read one of the LOCATION +or LOCATION_<CONFIG> properties.

+

For platforms with import libraries (e.g. Windows, AIX or macOS) see also +IMPORTED_IMPLIB.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LOCATION_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LOCATION_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..f290f055d22784879d612d5916ec340397ae3c69 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_LOCATION_CONFIG.html @@ -0,0 +1,141 @@ + + + + + + + + + IMPORTED_LOCATION_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_LOCATION_<CONFIG>

+

<CONFIG>-specific version of IMPORTED_LOCATION property.

+

Configuration names correspond to those provided by the project from +which the target is imported.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_NO_SONAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_NO_SONAME.html new file mode 100644 index 0000000000000000000000000000000000000000..19b9199c0ea059652248eed75ba9d50f8c79370f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_NO_SONAME.html @@ -0,0 +1,143 @@ + + + + + + + + + IMPORTED_NO_SONAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_NO_SONAME

+

Specifies that an IMPORTED shared library target has no soname.

+

Set this property to true for an imported shared library file that has +no soname field. CMake may adjust generated link commands for some +platforms to prevent the linker from using the path to the library in +place of its missing soname. Ignored for non-imported targets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_NO_SONAME_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_NO_SONAME_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..986f5610e947fa15479a4fa12d9daa1706cbf24b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_NO_SONAME_CONFIG.html @@ -0,0 +1,141 @@ + + + + + + + + + IMPORTED_NO_SONAME_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_NO_SONAME_<CONFIG>

+

<CONFIG>-specific version of IMPORTED_NO_SONAME property.

+

Configuration names correspond to those provided by the project from +which the target is imported.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_NO_SYSTEM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_NO_SYSTEM.html new file mode 100644 index 0000000000000000000000000000000000000000..92af42de37f83c6c35622192f8758c00dc1e91a9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_NO_SYSTEM.html @@ -0,0 +1,172 @@ + + + + + + + + + IMPORTED_NO_SYSTEM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_NO_SYSTEM

+
+

New in version 3.23.

+
+
+

Deprecated since version 3.25: IMPORTED_NO_SYSTEM is deprecated. Please use the following alternatives +instead:

+
    +
  • Set SYSTEM to false if you don't want a target's include +directories to be treated as system directories when compiling consumers.

  • +
  • Set EXPORT_NO_SYSTEM to true if you don't want the include +directories of the imported target generated by install(EXPORT) +and export() commands to be treated as system directories when +compiling consumers.

  • +
+
+

Setting IMPORTED_NO_SYSTEM to true on an +imported target specifies that it is not a +system target. This has the following effects:

+
    +
  • Entries of INTERFACE_INCLUDE_DIRECTORIES are not treated +as system include directories when compiling consumers (regardless of +the value of the consumed target's SYSTEM property), as they +would be by default. Entries of +INTERFACE_SYSTEM_INCLUDE_DIRECTORIES are not affected, +and will always be treated as system include directories.

  • +
  • On Apple platforms, when the target is a framework, it will not be treated as +system.

  • +
+

This property can also be enabled on a non-imported target. Doing so does +not affect the build system, but does tell the install(EXPORT) and +export() commands to enable it on the imported targets they generate.

+

See the NO_SYSTEM_FROM_IMPORTED target property to set this +behavior on the target consuming the include directories rather than +the one providing them.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_OBJECTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_OBJECTS.html new file mode 100644 index 0000000000000000000000000000000000000000..89b003d17070649245b9267bc5f60093572d3143 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_OBJECTS.html @@ -0,0 +1,227 @@ + + + + + + + + + IMPORTED_OBJECTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_OBJECTS

+
+

New in version 3.9.

+
+

A semicolon-separated list of absolute paths +to the object files on disk for an imported +object library.

+

Ignored for non-imported targets.

+

Projects may skip IMPORTED_OBJECTS if the configuration-specific +property IMPORTED_OBJECTS_<CONFIG> is set instead, except in +situations as noted in the section below.

+
+

Xcode Generator Considerations

+
+

New in version 3.20.

+
+

For Apple platforms, a project may be built for more than one architecture. +This is controlled by the CMAKE_OSX_ARCHITECTURES variable. +For all but the Xcode generator, CMake invokes compilers once +per source file and passes multiple -arch flags, leading to a single +object file which will be a universal binary. Such object files work well +when listed in the IMPORTED_OBJECTS of a separate CMake build, even for +the Xcode generator. But producing such object files with the +Xcode generator is more difficult, since it invokes the compiler +once per architecture for each source file. Unlike the other generators, +it does not generate universal object file binaries.

+

A further complication with the Xcode generator is that when +targeting device platforms (iOS, tvOS or watchOS), the Xcode +generator has the ability to use either the device or simulator SDK without +needing CMake to be re-run. The SDK can be selected at build time. +But since some architectures can be supported by both the device and the +simulator SDKs (e.g. arm64 with Xcode 12 or later), not all combinations +can be represented in a single universal binary. The only solution in this +case is to have multiple object files.

+

IMPORTED_OBJECTS doesn't support generator expressions, so every file +it lists needs to be valid for every architecture and SDK. If incorporating +object files that are not universal binaries, the path and/or file name of +each object file has to somehow encapsulate the different architectures and +SDKs. With the Xcode generator, Xcode variables of the form +$(...) can be used to represent these aspects and Xcode will substitute +the appropriate values at build time. CMake doesn't interpret these +variables and embeds them unchanged in the Xcode project file. +$(CURRENT_ARCH) can be used to represent the architecture, while +$(EFFECTIVE_PLATFORM_NAME) can be used to differentiate between SDKs.

+

The following shows one example of how these two variables can be used to +refer to an object file whose location depends on both the SDK and the +architecture:

+
add_library(someObjs OBJECT IMPORTED)
+
+set_property(TARGET someObjs PROPERTY IMPORTED_OBJECTS
+  # Quotes are required because of the ()
+  "/path/to/somewhere/objects$(EFFECTIVE_PLATFORM_NAME)/$(CURRENT_ARCH)/func.o"
+)
+
+# Example paths:
+#   /path/to/somewhere/objects-iphoneos/arm64/func.o
+#   /path/to/somewhere/objects-iphonesimulator/x86_64/func.o
+
+
+

In some cases, you may want to have configuration-specific object files +as well. The $(CONFIGURATION) Xcode variable is often used for this and +can be used in conjunction with the others mentioned above:

+
add_library(someObjs OBJECT IMPORTED)
+set_property(TARGET someObjs PROPERTY IMPORTED_OBJECTS
+  "/path/to/somewhere/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)/$(CURRENT_ARCH)/func.o"
+)
+
+# Example paths:
+#   /path/to/somewhere/Release-iphoneos/arm64/func.o
+#   /path/to/somewhere/Debug-iphonesimulator/x86_64/func.o
+
+
+

When any Xcode variable is used, CMake is not able to fully evaluate the +path(s) at configure time. One consequence of this is that the +configuration-specific IMPORTED_OBJECTS_<CONFIG> properties cannot +be used, since CMake cannot determine whether an object file exists at a +particular <CONFIG> location. The IMPORTED_OBJECTS property must be +used for these situations and the configuration-specific aspects of the path +should be handled by the $(CONFIGURATION) Xcode variable.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_OBJECTS_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_OBJECTS_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..2a844981065d4bbb59470bd6a049f1c913179e24 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_OBJECTS_CONFIG.html @@ -0,0 +1,163 @@ + + + + + + + + + IMPORTED_OBJECTS_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_OBJECTS_<CONFIG>

+
+

New in version 3.9.

+
+

<CONFIG>-specific version of IMPORTED_OBJECTS property.

+

Configuration names correspond to those provided by the project from +which the target is imported.

+
+

Xcode Generator Considerations

+

Do not use this <CONFIG>-specific property if you need to use Xcode +variables like $(CURRENT_ARCH) or $(EFFECTIVE_PLATFORM_NAME) in +the value. The <CONFIG>-specific properties will be ignored in such +cases because CMake cannot determine whether a file exists at the +configuration-specific path at configuration time. For such cases, use +IMPORTED_OBJECTS instead.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_SONAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_SONAME.html new file mode 100644 index 0000000000000000000000000000000000000000..42ae96a75bc439115df17c7f4b4d945fbf5bb37d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_SONAME.html @@ -0,0 +1,142 @@ + + + + + + + + + IMPORTED_SONAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_SONAME

+

The soname of an IMPORTED target of shared library type.

+

Set this to the soname embedded in an imported shared library. This +is meaningful only on platforms supporting the feature. Ignored for +non-imported targets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_SONAME_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_SONAME_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..85770f96b5b68a83f51a95a1cb8df701d98ae38c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORTED_SONAME_CONFIG.html @@ -0,0 +1,141 @@ + + + + + + + + + IMPORTED_SONAME_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORTED_SONAME_<CONFIG>

+

<CONFIG>-specific version of IMPORTED_SONAME property.

+

Configuration names correspond to those provided by the project from +which the target is imported.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORT_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORT_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..9adb44676a8b643273e029e33d1901b3e47397b8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORT_PREFIX.html @@ -0,0 +1,143 @@ + + + + + + + + + IMPORT_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORT_PREFIX

+

What comes before the import library name.

+

Similar to the target property PREFIX, but used for import libraries +(typically corresponding to a DLL) instead of regular libraries. A +target property that can be set to override the prefix (such as lib) +on an import library name.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORT_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORT_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..15e150ea16844bd6138e57fde70dc7b1565a6a7d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IMPORT_SUFFIX.html @@ -0,0 +1,143 @@ + + + + + + + + + IMPORT_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IMPORT_SUFFIX

+

What comes after the import library name.

+

Similar to the target property SUFFIX, but used +for import libraries (typically corresponding to a DLL) instead of +regular libraries. A target property that can be set to override +the suffix (such as .lib) on an import library name.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INCLUDE_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INCLUDE_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..fa94d9d8958ea0402f037be3024be63920e01352 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INCLUDE_DIRECTORIES.html @@ -0,0 +1,155 @@ + + + + + + + + + INCLUDE_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INCLUDE_DIRECTORIES

+

List of preprocessor include file search directories.

+

This property specifies the list of directories given so far to the +target_include_directories() command. In addition to accepting +values from that command, values may be set directly on any +target using the set_property() command. A target gets its +initial value for this property from the value of the +INCLUDE_DIRECTORIES directory property. Both directory and +target property values are adjusted by calls to the +include_directories() command.

+

The value of this property is used by the generators to set the include +paths for the compiler.

+

Relative paths should not be added to this property directly. Use one of +the commands above instead to handle relative paths.

+

Contents of INCLUDE_DIRECTORIES may use cmake-generator-expressions(7) with +the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) +manual for more on defining buildsystem properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INSTALL_REMOVE_ENVIRONMENT_RPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INSTALL_REMOVE_ENVIRONMENT_RPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..887c260e5d9881e0fdff686150f8a4adbf8a4d03 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INSTALL_REMOVE_ENVIRONMENT_RPATH.html @@ -0,0 +1,152 @@ + + + + + + + + + INSTALL_REMOVE_ENVIRONMENT_RPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INSTALL_REMOVE_ENVIRONMENT_RPATH

+
+

New in version 3.16.

+
+

Controls whether toolchain-defined rpaths should be removed during installation.

+

When a target is being installed, CMake may need to rewrite its rpath +information. This occurs when the install rpath (as specified by the +INSTALL_RPATH target property) has different contents to the rpath +that the target was built with. Some toolchains insert their own rpath +contents into the binary as part of the build. By default, CMake will +preserve those extra inserted contents in the install rpath. For those +scenarios where such toolchain-inserted entries need to be discarded during +install, set the INSTALL_REMOVE_ENVIRONMENT_RPATH target property to true.

+

This property is initialized by the value of +CMAKE_INSTALL_REMOVE_ENVIRONMENT_RPATH when the target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INSTALL_RPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INSTALL_RPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..179b8a5fd0922b4db5d7d3600fc1b82cf17c3d9a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INSTALL_RPATH.html @@ -0,0 +1,165 @@ + + + + + + + + + INSTALL_RPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INSTALL_RPATH

+

The rpath to use for installed targets.

+

By default, the install rpath is empty. It can be set using this property, +which is a semicolon-separated list specifying the rpath to use in installed +targets (for platforms that support it). This property is initialized +by the value of the variable CMAKE_INSTALL_RPATH if it is set +when a target is created. +Beside setting the install rpath manually, using the +INSTALL_RPATH_USE_LINK_PATH target property it can also be +generated automatically by CMake.

+

Normally CMake uses the build tree for the RPATH when building executables +etc on systems that use RPATH, see the BUILD_RPATH target +property. When the software is installed +the targets are edited (or relinked) by CMake (see +CMAKE_NO_BUILTIN_CHRPATH) to have the install RPATH. +This editing during installation can be avoided via +the BUILD_WITH_INSTALL_RPATH target property.

+

For handling toolchain-dependent RPATH entries the +INSTALL_REMOVE_ENVIRONMENT_RPATH can be used. +Runtime paths can be disabled completely via the CMAKE_SKIP_RPATH +variable.

+

Because the rpath may contain ${ORIGIN}, which coincides with CMake syntax, +the contents of INSTALL_RPATH are properly escaped in the +cmake_install.cmake script (see policy CMP0095.)

+

This property supports +generator expressions.

+

On Apple platforms, refer to the INSTALL_NAME_DIR target property. +Under Windows, the TARGET_RUNTIME_DLLS generator expression is related.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INSTALL_RPATH_USE_LINK_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INSTALL_RPATH_USE_LINK_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..ce9cfbc16a864dcc3e711b3ae01b90b4cae0f33d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INSTALL_RPATH_USE_LINK_PATH.html @@ -0,0 +1,147 @@ + + + + + + + + + INSTALL_RPATH_USE_LINK_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_AUTOMOC_MACRO_NAMES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_AUTOMOC_MACRO_NAMES.html new file mode 100644 index 0000000000000000000000000000000000000000..cbdac90a7b6b7dd47b30256ff2f42303363e698b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_AUTOMOC_MACRO_NAMES.html @@ -0,0 +1,229 @@ + + + + + + + + + INTERFACE_AUTOMOC_MACRO_NAMES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_AUTOMOC_MACRO_NAMES

+
+

New in version 3.27.

+
+

A semicolon-separated list of macro names for +AUTOMOC to be propagated to consumers.

+

When a target with AUTOMOC enabled links to a library that sets +INTERFACE_AUTOMOC_MACRO_NAMES, the target inherits the listed macro names +and merges them with those specified in its own AUTOMOC_MACRO_NAMES +property. The target will then automatically generate MOC files for source +files that contain the inherited macro names too, not just the macro names +specified in its own AUTOMOC_MACRO_NAMES property.

+

By default INTERFACE_AUTOMOC_MACRO_NAMES is empty.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+

Example 1

+

In this example, myapp inherits the macro names STATIC_LIB_1 and +STATIC_LIB_2 from static_lib. The moc tool will then automatically +be run on any of the myapp sources which contain STATIC_LIB_1 or +STATIC_LIB_2.

+
set(AUTOMOC ON)
+add_executable(myapp main.cpp)
+target_link_libraries(myapp PRIVATE static_lib)
+
+add_library(static_lib STATIC static.cpp)
+set_property(TARGET static_lib PROPERTY
+  INTERFACE_AUTOMOC_MACRO_NAMES "STATIC_LIB_1;STATIC_LIB_2"
+)
+
+
+
+
+

Example 2

+

In this example, the INTERFACE_AUTOMOC_MACRO_NAMES target property of the +various *_deep_lib libraries will propagate to shared_lib, +static_lib and interface_lib. Because the linking relationships are +specified as PUBLIC and INTERFACE, those macro names will also further +propagate transitively up to app.

+
set(AUTOMOC ON)
+
+add_library(shared_deep_lib SHARED deep_lib.cpp)
+add_library(static_deep_lib STATIC deep_lib.cpp)
+add_library(interface_deep_lib INTERFACE)
+
+set_property(TARGET shared_deep_lib PROPERTY
+  INTERFACE_AUTOMOC_MACRO_NAMES "SHARED_LINK_LIB"
+)
+set_property(TARGET static_deep_lib PROPERTY
+  INTERFACE_AUTOMOC_MACRO_NAMES "STATIC_LINK_LIB"
+)
+set_property(TARGET interface_deep_lib PROPERTY
+  INTERFACE_AUTOMOC_MACRO_NAMES "INTERFACE_LINK_LIB"
+)
+
+add_library(shared_lib SHARED lib.cpp)
+add_library(static_lib STATIC lib.cpp)
+add_library(interface_lib INTERFACE)
+
+# PUBLIC and INTERFACE here ensure the macro names propagate to any
+# consumers of shared_lib, static_lib or interface_lib too
+target_link_libraries(shared_lib PUBLIC shared_deep_lib)
+target_link_libraries(static_lib PUBLIC static_deep_lib)
+target_link_libraries(interface_lib INTERFACE interface_deep_lib)
+
+# This consumer will receive all three of the above custom macro names as
+# transitive usage requirements
+add_executable(app main.cpp)
+target_link_libraries(app PRIVATE shared_lib static_lib interface_lib)
+
+
+

In the above:

+
    +
  • shared_lib sources will be processed by moc if they contain +SHARED_LINK_LIB.

  • +
  • static_lib sources will be processed by moc if they contain +STATIC_LINK_LIB.

  • +
  • app sources will be processed by moc if they contain +SHARED_LINK_LIB, STATIC_LINK_LIB or INTERFACE_LINK_LIB.

  • +
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_AUTOUIC_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_AUTOUIC_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..c6fcdd145253009dc04325932ff81087907732b6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_AUTOUIC_OPTIONS.html @@ -0,0 +1,147 @@ + + + + + + + + + INTERFACE_AUTOUIC_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_AUTOUIC_OPTIONS

+

List of interface options to pass to uic.

+

Targets may populate this property to publish the options +required to use when invoking uic. Consuming targets can add entries to their +own AUTOUIC_OPTIONS property such as +$<TARGET_PROPERTY:foo,INTERFACE_AUTOUIC_OPTIONS> to use the uic options +specified in the interface of foo. This is done automatically by +the target_link_libraries() command.

+

This property supports generator expressions. See the +cmake-generator-expressions(7) manual for available expressions.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_COMPILE_DEFINITIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_COMPILE_DEFINITIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..b7e53ff9ac46ec226a61613fa78c186ca782a4fe --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_COMPILE_DEFINITIONS.html @@ -0,0 +1,150 @@ + + + + + + + + + INTERFACE_COMPILE_DEFINITIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_COMPILE_DEFINITIONS

+

List of public compile definitions requirements for a library.

+

Targets may populate this property to publish the compile definitions +required to compile against the headers for the target. The target_compile_definitions() +command populates this property with values given to the PUBLIC and +INTERFACE keywords. Projects may also get and set the property directly.

+

When target dependencies are specified using target_link_libraries(), +CMake will read this property from all target dependencies to determine the +build properties of the consumer.

+

Contents of INTERFACE_COMPILE_DEFINITIONS may use "generator expressions" +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) +-manual for more on defining buildsystem properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_COMPILE_FEATURES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_COMPILE_FEATURES.html new file mode 100644 index 0000000000000000000000000000000000000000..d643ca7c53c416cf66ead9fe6eb92b3a60b26167 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_COMPILE_FEATURES.html @@ -0,0 +1,155 @@ + + + + + + + + + INTERFACE_COMPILE_FEATURES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_COMPILE_FEATURES

+
+

New in version 3.1.

+
+

List of public compile features requirements for a library.

+

Targets may populate this property to publish the compile features +required to compile against the headers for the target. The target_compile_features() +command populates this property with values given to the PUBLIC and +INTERFACE keywords. Projects may also get and set the property directly.

+

When target dependencies are specified using target_link_libraries(), +CMake will read this property from all target dependencies to determine the +build properties of the consumer.

+

Contents of INTERFACE_COMPILE_FEATURES may use "generator expressions" +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) +-manual for more on defining buildsystem properties.

+

See the cmake-compile-features(7) manual for information on compile +features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_COMPILE_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_COMPILE_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..c7f8bb0fa97abcff2165dd13acd16f911c0d7caf --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_COMPILE_OPTIONS.html @@ -0,0 +1,150 @@ + + + + + + + + + INTERFACE_COMPILE_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_COMPILE_OPTIONS

+

List of public compile options requirements for a library.

+

Targets may populate this property to publish the compile options +required to compile against the headers for the target. The target_compile_options() +command populates this property with values given to the PUBLIC and +INTERFACE keywords. Projects may also get and set the property directly.

+

When target dependencies are specified using target_link_libraries(), +CMake will read this property from all target dependencies to determine the +build properties of the consumer.

+

Contents of INTERFACE_COMPILE_OPTIONS may use "generator expressions" +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) +-manual for more on defining buildsystem properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_CXX_MODULE_SETS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_CXX_MODULE_SETS.html new file mode 100644 index 0000000000000000000000000000000000000000..0974ff226c3b28b788f9df39b6c030ee60b89c02 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_CXX_MODULE_SETS.html @@ -0,0 +1,152 @@ + + + + + + + + + INTERFACE_CXX_MODULE_SETS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_CXX_MODULE_SETS

+
+

New in version 3.25.

+
+
+

Note

+

Experimental. Gated by CMAKE_EXPERIMENTAL_CXX_MODULE_CMAKE_API

+
+

Read-only list of the target's PUBLIC C++ module sets (i.e. all file sets +with the type CXX_MODULES). Files listed in these C++ module sets can be +installed with install(TARGETS) and exported with +install(EXPORT) and export().

+

C++ module sets may be defined using the target_sources() command +FILE_SET option with type CXX_MODULES.

+

See also CXX_MODULE_SETS.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_HEADER_SETS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_HEADER_SETS.html new file mode 100644 index 0000000000000000000000000000000000000000..8940e9be17321bd197796004c8b87e749a23a96d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_HEADER_SETS.html @@ -0,0 +1,148 @@ + + + + + + + + + INTERFACE_HEADER_SETS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_HEADER_SETS

+
+

New in version 3.23.

+
+

Read-only list of the target's INTERFACE and PUBLIC header sets (i.e. +all file sets with the type HEADERS). Files listed in these header sets +can be installed with install(TARGETS) and exported with +install(EXPORT) and export().

+

Header sets may be defined using the target_sources() command +FILE_SET option with type HEADERS.

+

See also HEADER_SETS.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_HEADER_SETS_TO_VERIFY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_HEADER_SETS_TO_VERIFY.html new file mode 100644 index 0000000000000000000000000000000000000000..b3cf5a29b23588762eae79a40192dcbba4826957 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_HEADER_SETS_TO_VERIFY.html @@ -0,0 +1,148 @@ + + + + + + + + + INTERFACE_HEADER_SETS_TO_VERIFY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_HEADER_SETS_TO_VERIFY

+
+

New in version 3.24.

+
+

Used to specify which PUBLIC and INTERFACE header sets of a target +should be verified.

+

This property contains a semicolon-separated list of header sets which +should be verified if VERIFY_INTERFACE_HEADER_SETS is set to +TRUE. If the list is empty, all PUBLIC and INTERFACE header sets +are verified. (If the project does not want to verify any header sets on the +target, simply set VERIFY_INTERFACE_HEADER_SETS to FALSE.)

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..70fc02d03d4f289957a86f43f1fa49f0e82c1dc8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html @@ -0,0 +1,190 @@ + + + + + + + + + INTERFACE_INCLUDE_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_INCLUDE_DIRECTORIES

+

List of public include directories requirements for a library.

+

Targets may populate this property to publish the include directories +required to compile against the headers for the target. The target_include_directories() +command populates this property with values given to the PUBLIC and +INTERFACE keywords. Projects may also get and set the property directly.

+

When target dependencies are specified using target_link_libraries(), +CMake will read this property from all target dependencies to determine the +build properties of the consumer.

+

Contents of INTERFACE_INCLUDE_DIRECTORIES may use "generator expressions" +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) +-manual for more on defining buildsystem properties.

+

Include directories usage requirements commonly differ between the build-tree +and the install-tree. The BUILD_INTERFACE and INSTALL_INTERFACE +generator expressions can be used to describe separate usage requirements +based on the usage location. Relative paths are allowed within the +INSTALL_INTERFACE expression and are interpreted relative to the +installation prefix. For example:

+
target_include_directories(mylib INTERFACE
+  $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/include/mylib>
+  $<INSTALL_INTERFACE:include/mylib>  # <prefix>/include/mylib
+)
+
+
+
+

Creating Relocatable Packages

+

Note that it is not advisable to populate the INSTALL_INTERFACE of +the INTERFACE_INCLUDE_DIRECTORIES of a target with absolute paths to the include +directories of dependencies. That would hard-code into installed packages +the include directory paths for dependencies +as found on the machine the package was made on.

+

The INSTALL_INTERFACE of the INTERFACE_INCLUDE_DIRECTORIES is only +suitable for specifying the required include directories for headers +provided with the target itself, not those provided by the transitive +dependencies listed in its INTERFACE_LINK_LIBRARIES target +property. Those dependencies should themselves be targets that specify +their own header locations in INTERFACE_INCLUDE_DIRECTORIES.

+

See the Creating Relocatable Packages section of the +cmake-packages(7) manual for discussion of additional care +that must be taken when specifying usage requirements while creating +packages for redistribution.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_DEPENDS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_DEPENDS.html new file mode 100644 index 0000000000000000000000000000000000000000..a1da01681c53a568d000f3a4ab4d6468159de62b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_DEPENDS.html @@ -0,0 +1,165 @@ + + + + + + + + + INTERFACE_LINK_DEPENDS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..f8d137589146125852f9e8bcdde84d8fe8f67221 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_DIRECTORIES.html @@ -0,0 +1,153 @@ + + + + + + + + + INTERFACE_LINK_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_LIBRARIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_LIBRARIES.html new file mode 100644 index 0000000000000000000000000000000000000000..4c04dfdc034a7d37be4545aadc785d19066144b3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_LIBRARIES.html @@ -0,0 +1,195 @@ + + + + + + + + + INTERFACE_LINK_LIBRARIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_LIBRARIES_DIRECT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_LIBRARIES_DIRECT.html new file mode 100644 index 0000000000000000000000000000000000000000..5421623c08ac986e293b3144731db8c0ae94a570 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_LIBRARIES_DIRECT.html @@ -0,0 +1,368 @@ + + + + + + + + + INTERFACE_LINK_LIBRARIES_DIRECT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE.html new file mode 100644 index 0000000000000000000000000000000000000000..d31a0a5b3ee239907ee553e934a9570d549f8917 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE.html @@ -0,0 +1,172 @@ + + + + + + + + + INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..09ae9afbe0ed4c47ff2a4c400a2fea766072af62 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_LINK_OPTIONS.html @@ -0,0 +1,153 @@ + + + + + + + + + INTERFACE_LINK_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_POSITION_INDEPENDENT_CODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_POSITION_INDEPENDENT_CODE.html new file mode 100644 index 0000000000000000000000000000000000000000..297aaef6d0a0421c76249f1cec919ec3878de2f7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_POSITION_INDEPENDENT_CODE.html @@ -0,0 +1,155 @@ + + + + + + + + + INTERFACE_POSITION_INDEPENDENT_CODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_POSITION_INDEPENDENT_CODE

+

Whether consumers need to create a position-independent target

+

The INTERFACE_POSITION_INDEPENDENT_CODE property informs consumers of +this target whether they must set their +POSITION_INDEPENDENT_CODE property to ON. If this +property is set to ON, then the POSITION_INDEPENDENT_CODE +property on all consumers will be set to ON. Similarly, if this +property is set to OFF, then the POSITION_INDEPENDENT_CODE +property on all consumers will be set to OFF. If this property is +undefined, then consumers will determine their +POSITION_INDEPENDENT_CODE property by other means. Consumers +must ensure that the targets that they link to have a consistent +requirement for their INTERFACE_POSITION_INDEPENDENT_CODE property.

+

Contents of INTERFACE_POSITION_INDEPENDENT_CODE may use +"generator expressions" with the syntax $<...>. See the +cmake-generator-expressions(7) manual for available expressions. +See the cmake-buildsystem(7) manual for more on defining buildsystem +properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_PRECOMPILE_HEADERS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_PRECOMPILE_HEADERS.html new file mode 100644 index 0000000000000000000000000000000000000000..0acdfe91a0c368249f4b64c4da9b1cbfc79fa967 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_PRECOMPILE_HEADERS.html @@ -0,0 +1,152 @@ + + + + + + + + + INTERFACE_PRECOMPILE_HEADERS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_PRECOMPILE_HEADERS

+
+

New in version 3.16.

+
+

List of interface header files to precompile into consuming targets.

+

Targets may populate this property to publish the header files +for consuming targets to precompile. The target_precompile_headers() +command populates this property with values given to the PUBLIC and +INTERFACE keywords. Projects may also get and set the property directly. +See the discussion in target_precompile_headers() for guidance on +appropriate use of this property for installed or exported targets.

+

Contents of INTERFACE_PRECOMPILE_HEADERS may use "generator expressions" +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) +manual for more on defining buildsystem properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_SOURCES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_SOURCES.html new file mode 100644 index 0000000000000000000000000000000000000000..35e6b297b62ce5be7974ab25ba79d12de247fb04 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_SOURCES.html @@ -0,0 +1,153 @@ + + + + + + + + + INTERFACE_SOURCES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_SOURCES

+
+

New in version 3.1.

+
+

List of interface sources to compile into consuming targets.

+

Targets may populate this property to publish the sources +for consuming targets to compile. The target_sources() command +populates this property with values given to the PUBLIC and +INTERFACE keywords. Projects may also get and set the property directly.

+

When target dependencies are specified using target_link_libraries(), +CMake will read this property from all target dependencies to determine the +sources of the consumer.

+

Contents of INTERFACE_SOURCES may use "generator expressions" +with the syntax $<...>. See the cmake-generator-expressions(7) +manual for available expressions. See the cmake-buildsystem(7) +manual for more on defining buildsystem properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_SYSTEM_INCLUDE_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_SYSTEM_INCLUDE_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..714afeb57519bca625652faf46b77eb42bac5a84 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERFACE_SYSTEM_INCLUDE_DIRECTORIES.html @@ -0,0 +1,161 @@ + + + + + + + + + INTERFACE_SYSTEM_INCLUDE_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERFACE_SYSTEM_INCLUDE_DIRECTORIES

+

List of public system include directories for a library.

+

Targets may populate this property to publish the include directories +which contain system headers, and therefore should not result in +compiler warnings. Additionally, system include directories are searched +after normal include directories regardless of the order specified.

+

When the target_include_directories() command is given the +SYSTEM keyword, it populates this property with values provided after the +PUBLIC and INTERFACE keywords.

+

Projects may also get and set the property directly, but must be aware that +adding directories to this property does not make those directories used +during compilation. Adding directories to this property marks directories +as system directories which otherwise would be used in a non-system manner. +This can appear similar to duplication, so prefer the high-level +target_include_directories() command with the SYSTEM keyword +and avoid setting the property directly.

+

When target dependencies are specified using target_link_libraries(), +CMake will read this property from all target dependencies to mark the +same include directories as containing system headers.

+

Contents of INTERFACE_SYSTEM_INCLUDE_DIRECTORIES may use "generator +expressions" with the syntax $<...>. See the +cmake-generator-expressions(7) manual for available expressions. +See the cmake-buildsystem(7) manual for more on defining +buildsystem properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERPROCEDURAL_OPTIMIZATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERPROCEDURAL_OPTIMIZATION.html new file mode 100644 index 0000000000000000000000000000000000000000..7c3c80f0e15c21513df75aa6a584c0061c130184 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERPROCEDURAL_OPTIMIZATION.html @@ -0,0 +1,149 @@ + + + + + + + + + INTERPROCEDURAL_OPTIMIZATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERPROCEDURAL_OPTIMIZATION

+

Enable interprocedural optimization for a target.

+

If set to true, enables interprocedural optimizations if they are +known to be supported by the compiler. Depending +on value of policy CMP0069, the error will be reported or ignored, +if interprocedural optimization is enabled but not supported.

+

This property is initialized by the +CMAKE_INTERPROCEDURAL_OPTIMIZATION variable if it is set when a +target is created.

+

There is also the per-configuration INTERPROCEDURAL_OPTIMIZATION_<CONFIG> +target property, which overrides INTERPROCEDURAL_OPTIMIZATION +if it is set.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERPROCEDURAL_OPTIMIZATION_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERPROCEDURAL_OPTIMIZATION_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..d3afacef79296475fa4574aea1bbcf1107b49c16 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/INTERPROCEDURAL_OPTIMIZATION_CONFIG.html @@ -0,0 +1,145 @@ + + + + + + + + + INTERPROCEDURAL_OPTIMIZATION_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

INTERPROCEDURAL_OPTIMIZATION_<CONFIG>

+

Per-configuration interprocedural optimization for a target.

+

This is a per-configuration version of INTERPROCEDURAL_OPTIMIZATION. +If set, this property overrides the generic property for the named +configuration.

+

This property is initialized by the +CMAKE_INTERPROCEDURAL_OPTIMIZATION_<CONFIG> variable if it is set +when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IOS_INSTALL_COMBINED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IOS_INSTALL_COMBINED.html new file mode 100644 index 0000000000000000000000000000000000000000..a58148b6ed8c811b4652658f55793c8845585267 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/IOS_INSTALL_COMBINED.html @@ -0,0 +1,153 @@ + + + + + + + + + IOS_INSTALL_COMBINED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

IOS_INSTALL_COMBINED

+
+

New in version 3.5.

+
+

Build a combined (device and simulator) target when installing.

+

When this property is set to set to false (which is the default) then it will +either be built with the device SDK or the simulator SDK depending on the SDK +set. But if this property is set to true then the target will at install time +also be built for the corresponding SDK and combined into one library.

+
+

Note

+

If a selected architecture is available for both: device SDK and simulator +SDK it will be built for the SDK selected by CMAKE_OSX_SYSROOT +and removed from the corresponding SDK.

+
+

This feature requires at least Xcode version 6.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ISPC_HEADER_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ISPC_HEADER_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..3bdaa5360fcbe520cf3311a1e9cd6d4756578c71 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ISPC_HEADER_DIRECTORY.html @@ -0,0 +1,148 @@ + + + + + + + + + ISPC_HEADER_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ISPC_HEADER_DIRECTORY

+
+

New in version 3.19.

+
+

Specify relative output directory for ISPC headers provided by the target.

+

If the target contains ISPC source files, this specifies the directory in which +the generated headers will be placed. Relative paths are treated with respect to +the value of CMAKE_CURRENT_BINARY_DIR. When this property is not set, the +headers will be placed a generator defined build directory. If the variable +CMAKE_ISPC_HEADER_DIRECTORY is set when a target is created +its value is used to initialize this property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ISPC_HEADER_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ISPC_HEADER_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..62d6cac01fdd13c5afa989c225e76c758a52d8d1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ISPC_HEADER_SUFFIX.html @@ -0,0 +1,147 @@ + + + + + + + + + ISPC_HEADER_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ISPC_HEADER_SUFFIX

+
+

New in version 3.19.2.

+
+

Specify output suffix to be used for ISPC generated headers provided by the target.

+

This property is initialized by the value of the CMAKE_ISPC_HEADER_SUFFIX +variable if it is set when a target is created.

+

If the target contains ISPC source files, this specifies the header suffix to +be used for the generated headers.

+

The default value is _ispc.h.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ISPC_INSTRUCTION_SETS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ISPC_INSTRUCTION_SETS.html new file mode 100644 index 0000000000000000000000000000000000000000..9fdab68d487b63f26f0ed5264369497b0047d517 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/ISPC_INSTRUCTION_SETS.html @@ -0,0 +1,163 @@ + + + + + + + + + ISPC_INSTRUCTION_SETS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ISPC_INSTRUCTION_SETS

+
+

New in version 3.19.

+
+

List of instruction set architectures to generate code for.

+

This property is initialized by the value of the CMAKE_ISPC_INSTRUCTION_SETS +variable if it is set when a target is created.

+

The ISPC_INSTRUCTION_SETS target property must be used when generating for multiple +instruction sets so that CMake can track what object files will be generated.

+
+

Examples

+
set_property(TARGET tgt PROPERTY ISPC_INSTRUCTION_SETS avx2-i32x4 avx512skx-i32x835)
+
+
+

Generates code for avx2 and avx512skx target architectures.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/JOB_POOL_COMPILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/JOB_POOL_COMPILE.html new file mode 100644 index 0000000000000000000000000000000000000000..4bd63c7a5c84d36de1aa7a43bd0bdba2db15c717 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/JOB_POOL_COMPILE.html @@ -0,0 +1,148 @@ + + + + + + + + + JOB_POOL_COMPILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

JOB_POOL_COMPILE

+

Ninja only: Pool used for compiling.

+

The number of parallel compile processes could be limited by defining +pools with the global JOB_POOLS +property and then specifying here the pool name.

+

For instance:

+
set_property(TARGET myexe PROPERTY JOB_POOL_COMPILE ten_jobs)
+
+
+

This property is initialized by the value of +CMAKE_JOB_POOL_COMPILE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/JOB_POOL_LINK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/JOB_POOL_LINK.html new file mode 100644 index 0000000000000000000000000000000000000000..8b2be24af9e7c972788bb9dd0fa6feecf87d2fab --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/JOB_POOL_LINK.html @@ -0,0 +1,147 @@ + + + + + + + + + JOB_POOL_LINK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/JOB_POOL_PRECOMPILE_HEADER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/JOB_POOL_PRECOMPILE_HEADER.html new file mode 100644 index 0000000000000000000000000000000000000000..26d5fbaa61eee06f307680d49e3c13ee2db30178 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/JOB_POOL_PRECOMPILE_HEADER.html @@ -0,0 +1,154 @@ + + + + + + + + + JOB_POOL_PRECOMPILE_HEADER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

JOB_POOL_PRECOMPILE_HEADER

+
+

New in version 3.17.

+
+

Ninja only: Pool used for generating pre-compiled headers.

+

The number of parallel compile processes could be limited by defining +pools with the global JOB_POOLS +property and then specifying here the pool name.

+

For instance:

+
set_property(TARGET myexe PROPERTY JOB_POOL_PRECOMPILE_HEADER two_jobs)
+
+
+

This property is initialized by the value of +CMAKE_JOB_POOL_PRECOMPILE_HEADER.

+

If neither JOB_POOL_PRECOMPILE_HEADER nor +CMAKE_JOB_POOL_PRECOMPILE_HEADER are set then +JOB_POOL_COMPILE will be used for this task.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CLANG_TIDY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CLANG_TIDY.html new file mode 100644 index 0000000000000000000000000000000000000000..5729aedf9c2e51f376454357de4b32fc57f5c05f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CLANG_TIDY.html @@ -0,0 +1,171 @@ + + + + + + + + + <LANG>_CLANG_TIDY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<LANG>_CLANG_TIDY

+
+

New in version 3.6.

+
+

This property is implemented only when <LANG> is C, CXX, OBJC +or OBJCXX.

+

Specify a semicolon-separated list containing +a command line for the clang-tidy tool. The Makefile Generators +and the Ninja generator will run this tool along with the +compiler and report a warning if the tool reports any problems.

+

The specified clang-tidy command line will be invoked with additional +arguments specifying the source file and, after --, the full compiler +command line.

+
+

Changed in version 3.25: If the specified clang-tidy command line includes the -p option, +it will be invoked without -- and the full compiler command line. +clang-tidy will look up the source file in the specified compiler +commands database.

+
+

This property is initialized by the value of +the CMAKE_<LANG>_CLANG_TIDY variable if it is set +when a target is created.

+
+

New in version 3.27: This property supports +generator expressions.

+
+
+

New in version 3.27: SKIP_LINTING can be set on individual source files to exclude +them from the linting tools defined by <LANG>_CPPLINT, +<LANG>_CLANG_TIDY, <LANG>_CPPCHECK, and +<LANG>_INCLUDE_WHAT_YOU_USE. When SKIP_LINTING is +set to true on a source file, those tools will not be run on that specific +file.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CLANG_TIDY_EXPORT_FIXES_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CLANG_TIDY_EXPORT_FIXES_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..8cdc524e8819eecf6b0b39c8ed1d4414f502f016 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CLANG_TIDY_EXPORT_FIXES_DIR.html @@ -0,0 +1,162 @@ + + + + + + + + + <LANG>_CLANG_TIDY_EXPORT_FIXES_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<LANG>_CLANG_TIDY_EXPORT_FIXES_DIR

+
+

New in version 3.26.

+
+

This property is implemented only when <LANG> is C, CXX, OBJC +or OBJCXX, and only has an effect when <LANG>_CLANG_TIDY is +set.

+

Specify a directory for the clang-tidy tool to put .yaml files +containing its suggested changes in. This can be used for automated mass +refactoring by clang-tidy. Each object file that gets compiled will have a +corresponding .yaml file in this directory. After the build is completed, +you can run clang-apply-replacements on this directory to simultaneously +apply all suggested changes to the code base. If this property is not an +absolute directory, it is assumed to be relative to the target's binary +directory. This property should be preferred over adding an --export-fixes +or --fix argument directly to the <LANG>_CLANG_TIDY property.

+

When this property is set, CMake takes ownership of the specified directory, +and may create, modify, or delete files and directories within the directory +at any time during configure or build time. Users should use a dedicated +directory for exporting clang-tidy fixes to avoid having files deleted or +overwritten by CMake. Users should not create, modify, or delete files in this +directory.

+

This property is initialized by the value of +the CMAKE_<LANG>_CLANG_TIDY_EXPORT_FIXES_DIR variable if it is set +when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_COMPILER_LAUNCHER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_COMPILER_LAUNCHER.html new file mode 100644 index 0000000000000000000000000000000000000000..252f3017263528ff6dd2f39b303a05ab1d0160d5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_COMPILER_LAUNCHER.html @@ -0,0 +1,154 @@ + + + + + + + + + <LANG>_COMPILER_LAUNCHER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<LANG>_COMPILER_LAUNCHER

+
+

New in version 3.4.

+
+

This property is implemented only when <LANG> is C, CXX, +Fortran, HIP, ISPC, OBJC, OBJCXX, or CUDA.

+

Specify a semicolon-separated list containing a command line +for a compiler launching tool. The Makefile Generators and the +Ninja generator will run this tool and pass the compiler and +its arguments to the tool. Some example tools are distcc and ccache.

+

This property is initialized by the value of +the CMAKE_<LANG>_COMPILER_LAUNCHER variable if it is set +when a target is created.

+
+

New in version 3.25: The property value may use +generator expressions.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CPPCHECK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CPPCHECK.html new file mode 100644 index 0000000000000000000000000000000000000000..eddafe5cb99d26e2b1375f7eb8de514d090b5007 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CPPCHECK.html @@ -0,0 +1,163 @@ + + + + + + + + + <LANG>_CPPCHECK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<LANG>_CPPCHECK

+
+

New in version 3.10.

+
+

This property is supported only when <LANG> is C or CXX.

+

Specify a semicolon-separated list containing a command line +for the cppcheck static analysis tool. The Makefile Generators +and the Ninja generator will run cppcheck along with the +compiler and report any problems. If the command-line specifies the +exit code options to cppcheck then the build will fail if the +tool returns non-zero.

+

This property is initialized by the value of the +CMAKE_<LANG>_CPPCHECK variable if it is set when a target is +created.

+
+

New in version 3.27: This property supports +generator expressions.

+
+
+

New in version 3.27: SKIP_LINTING can be set on individual source files to exclude +them from the linting tools defined by <LANG>_CPPLINT, +<LANG>_CLANG_TIDY, <LANG>_CPPCHECK, and +<LANG>_INCLUDE_WHAT_YOU_USE. When SKIP_LINTING is +set to true on a source file, those tools will not be run on that specific +file.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CPPLINT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CPPLINT.html new file mode 100644 index 0000000000000000000000000000000000000000..8ada976604bfeda24933578b34a335c5a183a5b5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_CPPLINT.html @@ -0,0 +1,161 @@ + + + + + + + + + <LANG>_CPPLINT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<LANG>_CPPLINT

+
+

New in version 3.8.

+
+

This property is supported only when <LANG> is C or CXX.

+

Specify a semicolon-separated list containing a command line +for the cpplint style checker. The Makefile Generators and the +Ninja generator will run cpplint along with the compiler +and report any problems.

+

This property is initialized by the value of the +CMAKE_<LANG>_CPPLINT variable if it is set when a target is +created.

+
+

New in version 3.27: This property supports +generator expressions.

+
+
+

New in version 3.27: SKIP_LINTING can be set on individual source files to exclude +them from the linting tools defined by <LANG>_CPPLINT, +<LANG>_CLANG_TIDY, <LANG>_CPPCHECK, and +<LANG>_INCLUDE_WHAT_YOU_USE. When SKIP_LINTING is +set to true on a source file, those tools will not be run on that specific +file.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..304e316ea6f866308fd475d9c610caa2705bfe08 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_EXTENSIONS.html @@ -0,0 +1,156 @@ + + + + + + + + + <LANG>_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<LANG>_EXTENSIONS

+

The variations are:

+ +

These properties specify whether compiler-specific extensions are requested.

+

These properties are initialized by the value of the +CMAKE_<LANG>_EXTENSIONS variable if it is set when a target is +created and otherwise by the value of +CMAKE_<LANG>_EXTENSIONS_DEFAULT (see CMP0128).

+

For supported CMake versions see the respective pages. +To control language standard versions see <LANG>_STANDARD.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_INCLUDE_WHAT_YOU_USE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_INCLUDE_WHAT_YOU_USE.html new file mode 100644 index 0000000000000000000000000000000000000000..f4debea842acff07711c10e68eeab0ef669f69b6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_INCLUDE_WHAT_YOU_USE.html @@ -0,0 +1,161 @@ + + + + + + + + + <LANG>_INCLUDE_WHAT_YOU_USE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<LANG>_INCLUDE_WHAT_YOU_USE

+
+

New in version 3.3.

+
+

This property is implemented only when <LANG> is C or CXX.

+

Specify a semicolon-separated list containing a command +line for the include-what-you-use tool. The Makefile Generators +and the Ninja generator will run this tool along with the +compiler and report a warning if the tool reports any problems.

+

This property is initialized by the value of +the CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE variable if it is set +when a target is created.

+
+

New in version 3.27: This property supports +generator expressions.

+
+
+

New in version 3.27: SKIP_LINTING can be set on individual source files to exclude +them from the linting tools defined by <LANG>_CPPLINT, +<LANG>_CLANG_TIDY, <LANG>_CPPCHECK, and +<LANG>_INCLUDE_WHAT_YOU_USE. When SKIP_LINTING is +set to true on a source file, those tools will not be run on that specific +file.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_STANDARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_STANDARD.html new file mode 100644 index 0000000000000000000000000000000000000000..65146b2430c2f7aa7be2aabd333c89191f0eeb20 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_STANDARD.html @@ -0,0 +1,164 @@ + + + + + + + + + <LANG>_STANDARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<LANG>_STANDARD

+

The variations are:

+ +

These properties specify language standard versions which are requested. When a +newer standard is specified than is supported by the compiler, then it will +fallback to the latest supported standard. This "decay" behavior may be +controlled with the <LANG>_STANDARD_REQUIRED target property.

+

Note that the actual language standard used may be higher than that specified +by <LANG>_STANDARD, regardless of the value of +<LANG>_STANDARD_REQUIRED. In particular, +transitive usage requirements or the use of +compile features can raise the required +language standard above what <LANG>_STANDARD specifies.

+

These properties are initialized by the value of the +CMAKE_<LANG>_STANDARD variable if it is set when a target is +created.

+

For supported values and CMake versions see the respective pages. +To control compiler-specific extensions see <LANG>_EXTENSIONS.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..4e475bda38152d33328ab85acd44278e0619dd8b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_STANDARD_REQUIRED.html @@ -0,0 +1,164 @@ + + + + + + + + + <LANG>_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<LANG>_STANDARD_REQUIRED

+

The variations are:

+ +

These properties specify whether the value of <LANG>_STANDARD is a +requirement. When false or unset, the <LANG>_STANDARD target +property is treated as optional and may "decay" to a previous standard if the +requested standard is not available. When <LANG>_STANDARD_REQUIRED is set +to true, <LANG>_STANDARD becomes a hard requirement and a fatal +error will be issued if that requirement cannot be met.

+

Note that the actual language standard used may be higher than that specified +by <LANG>_STANDARD, regardless of the value of +<LANG>_STANDARD_REQUIRED. In particular, +transitive usage requirements or the use of +compile features can raise the required +language standard above what <LANG>_STANDARD specifies.

+

These properties are initialized by the value of the +CMAKE_<LANG>_STANDARD_REQUIRED variable if it is set when a target +is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_VISIBILITY_PRESET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_VISIBILITY_PRESET.html new file mode 100644 index 0000000000000000000000000000000000000000..2596de5967e7e7fb752ddb8704d98d57b99bd9b0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LANG_VISIBILITY_PRESET.html @@ -0,0 +1,146 @@ + + + + + + + + + <LANG>_VISIBILITY_PRESET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<LANG>_VISIBILITY_PRESET

+

Value for symbol visibility compile flags

+

The <LANG>_VISIBILITY_PRESET property determines the value passed in a +visibility related compile option, such as -fvisibility= for <LANG>. +This property affects compilation in sources of all types of targets +(subject to policy CMP0063).

+

This property is initialized by the value of the +CMAKE_<LANG>_VISIBILITY_PRESET variable if it is set when a +target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LIBRARY_OUTPUT_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LIBRARY_OUTPUT_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..ad40d515b8203d023532b28a70c1b3cfe936c715 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LIBRARY_OUTPUT_DIRECTORY.html @@ -0,0 +1,149 @@ + + + + + + + + + LIBRARY_OUTPUT_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

LIBRARY_OUTPUT_DIRECTORY

+

Output directory in which to build LIBRARY target files.

+

This property specifies the directory into which library target files +should be built. The property value may use +generator expressions. +Multi-configuration generators (Visual Studio, +Xcode, Ninja Multi-Config) append a +per-configuration subdirectory to the specified directory unless a generator +expression is used.

+

This property is initialized by the value of the +CMAKE_LIBRARY_OUTPUT_DIRECTORY variable if it is set when a target is created.

+

See also the LIBRARY_OUTPUT_DIRECTORY_<CONFIG> target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LIBRARY_OUTPUT_DIRECTORY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LIBRARY_OUTPUT_DIRECTORY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..c4dbca52eb312e50da0532616955a4f451e8cf72 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LIBRARY_OUTPUT_DIRECTORY_CONFIG.html @@ -0,0 +1,150 @@ + + + + + + + + + LIBRARY_OUTPUT_DIRECTORY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

LIBRARY_OUTPUT_DIRECTORY_<CONFIG>

+

Per-configuration output directory for +LIBRARY target files.

+

This is a per-configuration version of the +LIBRARY_OUTPUT_DIRECTORY target property, but +multi-configuration generators (Visual Studio Generators, +Xcode) do NOT append a +per-configuration subdirectory to the specified directory. This +property is initialized by the value of the +CMAKE_LIBRARY_OUTPUT_DIRECTORY_<CONFIG> variable if +it is set when a target is created.

+

Contents of LIBRARY_OUTPUT_DIRECTORY_<CONFIG> may use +generator expressions.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINKER_LANGUAGE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINKER_LANGUAGE.html new file mode 100644 index 0000000000000000000000000000000000000000..e283864049adaa94b32a5b1025987ce70128c10b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINKER_LANGUAGE.html @@ -0,0 +1,149 @@ + + + + + + + + + LINKER_LANGUAGE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

LINKER_LANGUAGE

+

Specifies language whose compiler will invoke the linker.

+

For executables, shared libraries, and modules, this sets the language +whose compiler is used to link the target (such as "C" or "CXX"). A +typical value for an executable is the language of the source file +providing the program entry point (main). If not set, the language +with the highest linker preference value is the default. Details of +the linker preferences are considered internal, but some limited +discussion can be found under the internal +CMAKE_<LANG>_LINKER_PREFERENCE variables.

+

If this property is not set by the user, it will be calculated at +generate-time by CMake.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_DEPENDS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_DEPENDS.html new file mode 100644 index 0000000000000000000000000000000000000000..76656f1c2ce20fd142221270151867cc0f50b31f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_DEPENDS.html @@ -0,0 +1,150 @@ + + + + + + + + + LINK_DEPENDS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_DEPENDS_NO_SHARED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_DEPENDS_NO_SHARED.html new file mode 100644 index 0000000000000000000000000000000000000000..91c0d86557c842b3f067d688ef124bd579cdb2ee --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_DEPENDS_NO_SHARED.html @@ -0,0 +1,148 @@ + + + + + + + + + LINK_DEPENDS_NO_SHARED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..06610c86909c0984578c7fff17eaaf11b9c0e761 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_DIRECTORIES.html @@ -0,0 +1,153 @@ + + + + + + + + + LINK_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_LIBRARIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_LIBRARIES.html new file mode 100644 index 0000000000000000000000000000000000000000..3b6860c921a642f0a1e15239af1f507bf287eb59 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_LIBRARIES.html @@ -0,0 +1,178 @@ + + + + + + + + + LINK_INTERFACE_LIBRARIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_LIBRARIES_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_LIBRARIES_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..9e444aa7af679fd87402a633736ef5bcdc358499 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_LIBRARIES_CONFIG.html @@ -0,0 +1,167 @@ + + + + + + + + + LINK_INTERFACE_LIBRARIES_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_MULTIPLICITY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_MULTIPLICITY.html new file mode 100644 index 0000000000000000000000000000000000000000..d95a17e2637ddb0773de80ac6e25d5d7a54a9a09 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_MULTIPLICITY.html @@ -0,0 +1,146 @@ + + + + + + + + + LINK_INTERFACE_MULTIPLICITY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_MULTIPLICITY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_MULTIPLICITY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..fbf65d20070637289ae4abe0322d92ad4d919c87 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_INTERFACE_MULTIPLICITY_CONFIG.html @@ -0,0 +1,142 @@ + + + + + + + + + LINK_INTERFACE_MULTIPLICITY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_LIBRARIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_LIBRARIES.html new file mode 100644 index 0000000000000000000000000000000000000000..37df6fa2fce96e4da5ba4f24209f65112fae7eb5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_LIBRARIES.html @@ -0,0 +1,170 @@ + + + + + + + + + LINK_LIBRARIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_LIBRARY_OVERRIDE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_LIBRARY_OVERRIDE.html new file mode 100644 index 0000000000000000000000000000000000000000..151304cbfee9b80aa209a22970c53c7cf919980d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_LIBRARY_OVERRIDE.html @@ -0,0 +1,194 @@ + + + + + + + + + LINK_LIBRARY_OVERRIDE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..d773702479a0cacee0fe82365296d5cb6e2d681d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_OPTIONS.html @@ -0,0 +1,224 @@ + + + + + + + + + LINK_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_SEARCH_START_STATIC.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_SEARCH_START_STATIC.html new file mode 100644 index 0000000000000000000000000000000000000000..a6077c196564f335f7a4eed48b279e354214b40a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_SEARCH_START_STATIC.html @@ -0,0 +1,154 @@ + + + + + + + + + LINK_SEARCH_START_STATIC — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_WHAT_YOU_USE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_WHAT_YOU_USE.html new file mode 100644 index 0000000000000000000000000000000000000000..5a9a730416abd91dabf7f5dfe5da8f1a0053e66b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LINK_WHAT_YOU_USE.html @@ -0,0 +1,158 @@ + + + + + + + + + LINK_WHAT_YOU_USE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LOCATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LOCATION.html new file mode 100644 index 0000000000000000000000000000000000000000..91c15e2a4c2f8067d21309d2236baf19a17a1552 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/LOCATION.html @@ -0,0 +1,160 @@ + + + + + + + + + LOCATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

LOCATION

+

Read-only location of a target on disk.

+

For an imported target, this read-only property returns the value of +the LOCATION_<CONFIG> property for an unspecified configuration +<CONFIG> provided by the target.

+

For a non-imported target, this property is provided for compatibility +with CMake 2.4 and below. It was meant to get the location of an +executable target's output file for use in add_custom_command(). The +path may contain a build-system-specific portion that is replaced at +build time with the configuration getting built (such as +$(ConfigurationName) in VS). In CMake 2.6 and above +add_custom_command() automatically recognizes a target name in its +COMMAND and DEPENDS options and computes the target location. In +CMake 2.8.4 and above add_custom_command() recognizes +generator expressions +to refer to target locations anywhere in the command. +Therefore this property is not needed for creating custom commands.

+

Do not set properties that affect the location of a target after +reading this property. These include properties whose names match +(RUNTIME|LIBRARY|ARCHIVE)_OUTPUT_(NAME|DIRECTORY)(_<CONFIG>)?, +(IMPLIB_)?(PREFIX|SUFFIX), or "LINKER_LANGUAGE". Failure to follow +this rule is not diagnosed and leaves the location of the target +undefined.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACHO_COMPATIBILITY_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACHO_COMPATIBILITY_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..e7133dbc6ff909e14a0f0411f9cd3f3bfc720a6d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACHO_COMPATIBILITY_VERSION.html @@ -0,0 +1,160 @@ + + + + + + + + + MACHO_COMPATIBILITY_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MACHO_COMPATIBILITY_VERSION

+
+

New in version 3.17.

+
+

What compatibility version number is this target for Mach-O binaries.

+

For shared libraries on Mach-O systems (e.g. macOS, iOS) +the MACHO_COMPATIBILITY_VERSION property corresponds to the +compatibility version and MACHO_CURRENT_VERSION corresponds to +the current version. These are both embedded in the shared library binary +and can be checked with the otool -L <binary> command.

+

It should be noted that the MACHO_CURRENT_VERSION and +MACHO_COMPATIBILITY_VERSION properties do not affect the file +names or version-related symlinks that CMake generates for the library. +The VERSION and SOVERSION target properties still +control the file and symlink names. The install_name is also still +controlled by SOVERSION.

+

When MACHO_CURRENT_VERSION and MACHO_COMPATIBILITY_VERSION +are not given, VERSION and SOVERSION are used for +the version details to be embedded in the binaries respectively. +The MACHO_CURRENT_VERSION and MACHO_COMPATIBILITY_VERSION +properties only need to be given if the project needs to decouple the file +and symlink naming from the version details embedded in the binaries +(e.g. to match libtool conventions).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACHO_CURRENT_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACHO_CURRENT_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..4e55e54e88b3c82d2cd68e3f5cb4601fb2f68fe7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACHO_CURRENT_VERSION.html @@ -0,0 +1,160 @@ + + + + + + + + + MACHO_CURRENT_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MACHO_CURRENT_VERSION

+
+

New in version 3.17.

+
+

What current version number is this target for Mach-O binaries.

+

For shared libraries on Mach-O systems (e.g. macOS, iOS) +the MACHO_COMPATIBILITY_VERSION property corresponds to the +compatibility version and MACHO_CURRENT_VERSION corresponds to the +current version. These are both embedded in the shared library binary +and can be checked with the otool -L <binary> command.

+

It should be noted that the MACHO_CURRENT_VERSION and +MACHO_COMPATIBILITY_VERSION properties do not affect the file +names or version-related symlinks that CMake generates for the library. +The VERSION and SOVERSION target properties still +control the file and symlink names. The install_name is also still +controlled by SOVERSION.

+

When MACHO_CURRENT_VERSION and MACHO_COMPATIBILITY_VERSION +are not given, VERSION and SOVERSION are used for +the version details to be embedded in the binaries respectively. +The MACHO_CURRENT_VERSION and MACHO_COMPATIBILITY_VERSION +properties only need to be given if the project needs to decouple the file +and symlink naming from the version details embedded in the binaries +(e.g. to match libtool conventions).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_BUNDLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_BUNDLE.html new file mode 100644 index 0000000000000000000000000000000000000000..81cd8975c7ed0f606ba82cfcb4ea93f9aad9d204 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_BUNDLE.html @@ -0,0 +1,146 @@ + + + + + + + + + MACOSX_BUNDLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MACOSX_BUNDLE

+

Build an executable as an Application Bundle on macOS or iOS.

+

When this property is set to TRUE the executable when built on macOS +or iOS will be created as an application bundle. This makes it +a GUI executable that can be launched from the Finder. See the +MACOSX_BUNDLE_INFO_PLIST target property for information about +creation of the Info.plist file for the application bundle. +This property is initialized by the value of the variable +CMAKE_MACOSX_BUNDLE if it is set when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_BUNDLE_INFO_PLIST.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_BUNDLE_INFO_PLIST.html new file mode 100644 index 0000000000000000000000000000000000000000..8081de31a3e36b73da59cb5ba6839d4111b33853 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_BUNDLE_INFO_PLIST.html @@ -0,0 +1,168 @@ + + + + + + + + + MACOSX_BUNDLE_INFO_PLIST — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MACOSX_BUNDLE_INFO_PLIST

+

Specify a custom Info.plist template for a macOS and iOS Application Bundle.

+

An executable target with MACOSX_BUNDLE enabled will be built as an +application bundle on macOS. By default its Info.plist file is created +by configuring a template called MacOSXBundleInfo.plist.in located in the +CMAKE_MODULE_PATH. This property specifies an alternative template +file name which may be a full path.

+

The following target properties may be set to specify content to be +configured into the file:

+
+
MACOSX_BUNDLE_BUNDLE_NAME

Sets CFBundleName.

+
+
MACOSX_BUNDLE_BUNDLE_VERSION

Sets CFBundleVersion.

+
+
MACOSX_BUNDLE_COPYRIGHT

Sets NSHumanReadableCopyright.

+
+
MACOSX_BUNDLE_GUI_IDENTIFIER

Sets CFBundleIdentifier.

+
+
MACOSX_BUNDLE_ICON_FILE

Sets CFBundleIconFile.

+
+
MACOSX_BUNDLE_INFO_STRING

Sets CFBundleGetInfoString.

+
+
MACOSX_BUNDLE_LONG_VERSION_STRING

Sets CFBundleLongVersionString.

+
+
MACOSX_BUNDLE_SHORT_VERSION_STRING

Sets CFBundleShortVersionString.

+
+
+

CMake variables of the same name may be set to affect all targets in a +directory that do not have each specific property set. If a custom +Info.plist is specified by this property it may of course hard-code +all the settings instead of using the target properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_FRAMEWORK_INFO_PLIST.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_FRAMEWORK_INFO_PLIST.html new file mode 100644 index 0000000000000000000000000000000000000000..10bb0412a85723fe2725ed9bed9e29a147df4887 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_FRAMEWORK_INFO_PLIST.html @@ -0,0 +1,160 @@ + + + + + + + + + MACOSX_FRAMEWORK_INFO_PLIST — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MACOSX_FRAMEWORK_INFO_PLIST

+

Specify a custom Info.plist template for a macOS and iOS Framework.

+

A library target with FRAMEWORK enabled will be built as a +framework on macOS. By default its Info.plist file is created by +configuring a template called MacOSXFrameworkInfo.plist.in located in the +CMAKE_MODULE_PATH. This property specifies an alternative template +file name which may be a full path.

+

The following target properties may be set to specify content to be +configured into the file:

+
+
MACOSX_FRAMEWORK_BUNDLE_VERSION

Sets CFBundleVersion.

+
+
MACOSX_FRAMEWORK_ICON_FILE

Sets CFBundleIconFile.

+
+
MACOSX_FRAMEWORK_IDENTIFIER

Sets CFBundleIdentifier.

+
+
MACOSX_FRAMEWORK_SHORT_VERSION_STRING

Sets CFBundleShortVersionString.

+
+
+

CMake variables of the same name may be set to affect all targets in a +directory that do not have each specific property set. If a custom +Info.plist is specified by this property it may of course hard-code +all the settings instead of using the target properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_RPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_RPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..fba57bf70a8f5b9f13eb7a9b3c3a5942c3ba820b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MACOSX_RPATH.html @@ -0,0 +1,154 @@ + + + + + + + + + MACOSX_RPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MACOSX_RPATH

+

Whether this target on macOS or iOS is located at runtime using rpaths.

+

When this property is set to TRUE, the directory portion of +the install_name field of this shared library will be @rpath +unless overridden by INSTALL_NAME_DIR. This indicates +the shared library is to be found at runtime using runtime +paths (rpaths).

+

This property is initialized by the value of the variable +CMAKE_MACOSX_RPATH if it is set when a target is +created.

+

Runtime paths will also be embedded in binaries using this target and +can be controlled by the INSTALL_RPATH target property on +the target linking to this target.

+

Policy CMP0042 was introduced to change the default value of +MACOSX_RPATH to TRUE. This is because use of @rpath is a +more flexible and powerful alternative to @executable_path and +@loader_path.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MAP_IMPORTED_CONFIG_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MAP_IMPORTED_CONFIG_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..f10f69d13e5a1643f391e14d7e12cff40fce999c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MAP_IMPORTED_CONFIG_CONFIG.html @@ -0,0 +1,204 @@ + + + + + + + + + MAP_IMPORTED_CONFIG_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MAP_IMPORTED_CONFIG_<CONFIG>

+

Map from project configuration to +imported target's configuration.

+

Set this to the list of configurations of an imported target that may +be used for the current project's <CONFIG> configuration. Targets +imported from another project may not provide the same set of +configuration names available in the current project. Setting this +property tells CMake what imported configurations are suitable for use +when building the <CONFIG> configuration. The first configuration in +the list found to be provided by the imported target (i.e. via +IMPORTED_LOCATION_<CONFIG> for the mapped-to <CONFIG>) +is selected. As a special case, an empty list element refers to the +configuration-less imported target location +(i.e. IMPORTED_LOCATION).

+

If this property is set and no matching configurations are available, +then the imported target is considered to be not found. This property +is ignored for non-imported targets.

+

This property is initialized by the value of the +CMAKE_MAP_IMPORTED_CONFIG_<CONFIG> variable if it is set when a +target is created.

+
+

Example

+

For example creating imported C++ library foo:

+
add_library(foo STATIC IMPORTED)
+
+
+

Use foo_debug path for Debug build type:

+
set_property(
+  TARGET foo APPEND PROPERTY IMPORTED_CONFIGURATIONS DEBUG
+  )
+
+set_target_properties(foo PROPERTIES
+  IMPORTED_LINK_INTERFACE_LANGUAGES_DEBUG "CXX"
+  IMPORTED_LOCATION_DEBUG "${foo_debug}"
+  )
+
+
+

Use foo_release path for Release build type:

+
set_property(
+  TARGET foo APPEND PROPERTY IMPORTED_CONFIGURATIONS RELEASE
+  )
+
+set_target_properties(foo PROPERTIES
+  IMPORTED_LINK_INTERFACE_LANGUAGES_RELEASE "CXX"
+  IMPORTED_LOCATION_RELEASE "${foo_release}"
+  )
+
+
+

Use Release version of library for MinSizeRel and RelWithDebInfo +build types:

+
set_target_properties(foo PROPERTIES
+  MAP_IMPORTED_CONFIG_MINSIZEREL Release
+  MAP_IMPORTED_CONFIG_RELWITHDEBINFO Release
+  )
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MSVC_DEBUG_INFORMATION_FORMAT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MSVC_DEBUG_INFORMATION_FORMAT.html new file mode 100644 index 0000000000000000000000000000000000000000..9dbb9101b021433dbce92d4933f4b8cf43536872 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/MSVC_DEBUG_INFORMATION_FORMAT.html @@ -0,0 +1,180 @@ + + + + + + + + + MSVC_DEBUG_INFORMATION_FORMAT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MSVC_DEBUG_INFORMATION_FORMAT

+
+

New in version 3.25.

+
+

Select debug information format when targeting the MSVC ABI.

+

The allowed values are:

+
+
Embedded

Compile with -Z7 or equivalent flag(s) to produce object files +with full symbolic debugging information.

+
+
ProgramDatabase

Compile with -Zi or equivalent flag(s) to produce a program +database that contains all the symbolic debugging information.

+
+
EditAndContinue

Compile with -ZI or equivalent flag(s) to produce a program +database that supports the Edit and Continue feature.

+
+
+

The value is ignored on compilers not targeting the MSVC ABI, but an +unsupported value will be rejected as an error when using a compiler +targeting the MSVC ABI.

+

The value may also be the empty string (""), in which case no debug +information format flag will be added explicitly by CMake.

+

Use generator expressions to +support per-configuration specification. For example, the code:

+
add_executable(foo foo.c)
+set_property(TARGET foo PROPERTY
+  MSVC_DEBUG_INFORMATION_FORMAT "$<$<CONFIG:Debug,RelWithDebInfo>:ProgramDatabase>")
+
+
+

selects for the target foo the program database debug information format +for the Debug configuration.

+

This property is initialized from the value of the +CMAKE_MSVC_DEBUG_INFORMATION_FORMAT variable, if it is set. +If this property is not set, CMake selects a debug information format using +the default value $<$<CONFIG:Debug,RelWithDebInfo>:ProgramDatabase>, if +supported by the compiler, and otherwise +$<$<CONFIG:Debug,RelWithDebInfo>:Embedded>.

+
+

Note

+

This property has effect only when policy CMP0141 is set to NEW +prior to the first project() or enable_language() command +that enables a language using a compiler targeting the MSVC ABI.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..6a9e92293421cd3682256f9ce1eb37d37ba5cb82 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/NAME.html @@ -0,0 +1,140 @@ + + + + + + + + + NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

NAME

+

Logical name for the target.

+

Read-only logical name for the target as used by CMake.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/NO_SONAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/NO_SONAME.html new file mode 100644 index 0000000000000000000000000000000000000000..aa36101dd288ff9ab447e01d6d0f45a965bb59c7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/NO_SONAME.html @@ -0,0 +1,148 @@ + + + + + + + + + NO_SONAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

NO_SONAME

+

Whether to set soname when linking a shared library.

+

Enable this boolean property if a generated SHARED library +should not have soname set. Default is to set soname on all +shared libraries as long as the platform supports it. +Generally, use this property only for leaf private libraries or +plugins. If you use it on normal shared libraries which other targets +link against, on some platforms a linker will insert a full path to +the library (as specified at link time) into the dynamic section of +the dependent binary. Therefore, once installed, dynamic loader may +eventually fail to locate the library for the binary.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/NO_SYSTEM_FROM_IMPORTED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/NO_SYSTEM_FROM_IMPORTED.html new file mode 100644 index 0000000000000000000000000000000000000000..98d375a5ea970c8353f381b04594f900fff96ffa --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/NO_SYSTEM_FROM_IMPORTED.html @@ -0,0 +1,160 @@ + + + + + + + + + NO_SYSTEM_FROM_IMPORTED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

NO_SYSTEM_FROM_IMPORTED

+

Do not treat include directories from the interfaces of consumed +Imported Targets as system directories.

+

When the consumed target's SYSTEM property is set to true, the +contents of the INTERFACE_INCLUDE_DIRECTORIES target property are +treated as system includes or, on Apple platforms, when the target is a +framework, it will be treated as system. By default, SYSTEM is +true for imported targets and false for other target types. If the +NO_SYSTEM_FROM_IMPORTED property is set to true on a consuming target, +compilation of sources in that consuming target will not treat the contents of +the INTERFACE_INCLUDE_DIRECTORIES of consumed imported targets as +system includes, even if that imported target's SYSTEM property +is false.

+

Directories listed in the INTERFACE_SYSTEM_INCLUDE_DIRECTORIES +property of consumed targets are not affected by NO_SYSTEM_FROM_IMPORTED. +Those directories will always be treated as system include directories by +consumers.

+

This property is initialized by the value of the +CMAKE_NO_SYSTEM_FROM_IMPORTED variable if it is set when a target +is created.

+

See the EXPORT_NO_SYSTEM target property to set this behavior +on the target providing the include directories rather than the target +consuming them.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJCXX_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJCXX_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..71d71edf191796b6dc2917c40bd1f403a2884785 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJCXX_EXTENSIONS.html @@ -0,0 +1,156 @@ + + + + + + + + + OBJCXX_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

OBJCXX_EXTENSIONS

+
+

New in version 3.16.

+
+

Boolean specifying whether compiler specific extensions are requested.

+

This property specifies whether compiler specific extensions should be +used. For some compilers, this results in adding a flag such +as -std=gnu++11 instead of -std=c++11 to the compile line. This +property is ON by default. The basic ObjC++ standard level is +controlled by the OBJCXX_STANDARD target property.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

If the property is not set, and the project has set the CXX_EXTENSIONS, +the value of CXX_EXTENSIONS is set for OBJCXX_EXTENSIONS.

+

This property is initialized by the value of +the CMAKE_OBJCXX_EXTENSIONS variable if set when a target is +created and otherwise by the value of +CMAKE_OBJCXX_EXTENSIONS_DEFAULT +(see CMP0128).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJCXX_STANDARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJCXX_STANDARD.html new file mode 100644 index 0000000000000000000000000000000000000000..1da5297ade67cb690cf6615f8826c9bffbe7c952 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJCXX_STANDARD.html @@ -0,0 +1,188 @@ + + + + + + + + + OBJCXX_STANDARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

OBJCXX_STANDARD

+
+

New in version 3.16.

+
+

The ObjC++ standard whose features are requested to build this target.

+

This property specifies the ObjC++ standard whose features are requested +to build this target. For some compilers, this results in adding a +flag such as -std=gnu++11 to the compile line.

+

Supported values are:

+
+
98

Objective C++98

+
+
11

Objective C++11

+
+
14

Objective C++14

+
+
17

Objective C++17

+
+
20

Objective C++20

+
+
23
+

New in version 3.20.

+
+

Objective C++23

+
+
26
+

New in version 3.25.

+
+

Objective C++26. CMake 3.25 and later recognize 26 as a valid value, +no version has support for any compiler.

+
+
+

If the value requested does not result in a compile flag being added for +the compiler in use, a previous standard flag will be added instead. This +means that using:

+
set_property(TARGET tgt PROPERTY OBJCXX_STANDARD 11)
+
+
+

with a compiler which does not support -std=gnu++11 or an equivalent +flag will not result in an error or warning, but will instead add the +-std=gnu++98 flag if supported. This "decay" behavior may be controlled +with the OBJCXX_STANDARD_REQUIRED target property. +Additionally, the OBJCXX_EXTENSIONS target property may be used to +control whether compiler-specific extensions are enabled on a per-target basis.

+

If the property is not set, and the project has set the CXX_STANDARD, +the value of CXX_STANDARD is set for OBJCXX_STANDARD.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_OBJCXX_STANDARD variable if it is set when a target +is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJCXX_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJCXX_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..6a57e29f07690a04840a738aa1dd07fb47291260 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJCXX_STANDARD_REQUIRED.html @@ -0,0 +1,154 @@ + + + + + + + + + OBJCXX_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

OBJCXX_STANDARD_REQUIRED

+
+

New in version 3.16.

+
+

Boolean describing whether the value of OBJCXX_STANDARD is a requirement.

+

If this property is set to ON, then the value of the +OBJCXX_STANDARD target property is treated as a requirement. If this +property is OFF or unset, the OBJCXX_STANDARD target property is +treated as optional and may "decay" to a previous standard if the requested is +not available.

+

If the property is not set, and the project has set the CXX_STANDARD_REQUIRED, +the value of CXX_STANDARD_REQUIRED is set for OBJCXX_STANDARD_REQUIRED.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_OBJCXX_STANDARD_REQUIRED variable if it is set when a +target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJC_STANDARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJC_STANDARD.html new file mode 100644 index 0000000000000000000000000000000000000000..a16ee1377c841f205f0ed45cfa84066dea66587b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJC_STANDARD.html @@ -0,0 +1,173 @@ + + + + + + + + + OBJC_STANDARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

OBJC_STANDARD

+
+

New in version 3.16.

+
+

The OBJC standard whose features are requested to build this target.

+

This property specifies the OBJC standard whose features are requested +to build this target. For some compilers, this results in adding a +flag such as -std=gnu11 to the compile line.

+

Supported values are:

+
+
90

Objective C89/C90

+
+
99

Objective C99

+
+
11

Objective C11

+
+
+

If the value requested does not result in a compile flag being added for +the compiler in use, a previous standard flag will be added instead. This +means that using:

+
set_property(TARGET tgt PROPERTY OBJC_STANDARD 11)
+
+
+

with a compiler which does not support -std=gnu11 or an equivalent +flag will not result in an error or warning, but will instead add the +-std=gnu99 or -std=gnu90 flag if supported. This "decay" behavior may +be controlled with the OBJC_STANDARD_REQUIRED target property. +Additionally, the OBJC_EXTENSIONS target property may be used to +control whether compiler-specific extensions are enabled on a per-target basis.

+

If the property is not set, and the project has set the C_STANDARD, +the value of C_STANDARD is set for OBJC_STANDARD.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_OBJC_STANDARD variable if it is set when a target +is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJC_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJC_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..f101d17fb7483adabafe99a42bd9a18192b29ff1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OBJC_STANDARD_REQUIRED.html @@ -0,0 +1,154 @@ + + + + + + + + + OBJC_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

OBJC_STANDARD_REQUIRED

+
+

New in version 3.16.

+
+

Boolean describing whether the value of OBJC_STANDARD is a requirement.

+

If this property is set to ON, then the value of the +OBJC_STANDARD target property is treated as a requirement. If this +property is OFF or unset, the OBJC_STANDARD target property is +treated as optional and may "decay" to a previous standard if the requested is +not available.

+

If the property is not set, and the project has set the C_STANDARD_REQUIRED, +the value of C_STANDARD_REQUIRED is set for OBJC_STANDARD_REQUIRED.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+

This property is initialized by the value of +the CMAKE_OBJC_STANDARD_REQUIRED variable if it is set when a +target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OPTIMIZE_DEPENDENCIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OPTIMIZE_DEPENDENCIES.html new file mode 100644 index 0000000000000000000000000000000000000000..8035a5a6390c7a3ff09496697749ea4fc66f1339 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OPTIMIZE_DEPENDENCIES.html @@ -0,0 +1,176 @@ + + + + + + + + + OPTIMIZE_DEPENDENCIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

OPTIMIZE_DEPENDENCIES

+
+

New in version 3.19.

+
+

Activates dependency optimization of static and object libraries.

+

When this property is set to true, some dependencies for a static or object +library may be removed at generation time if they are not necessary to build +the library, since static and object libraries don't actually link against +anything.

+

If a static or object library has dependency optimization enabled, it first +discards all dependencies. Then, it looks through all of the direct and +indirect dependencies that it initially had, and adds them back if they meet +any of the following criteria:

+
    +
  • The dependency was added to the library by add_dependencies().

  • +
  • The dependency was added to the library through a source file in the library +generated by a custom command that uses the dependency.

  • +
  • The dependency has any PRE_BUILD, PRE_LINK, or POST_BUILD custom +commands associated with it.

  • +
  • The dependency contains any source files that were generated by a custom +command.

  • +
  • The dependency contains any languages which produce side effects that are +relevant to the library. Currently, all languages except C, C++, Objective-C, +Objective-C++, assembly, and CUDA are assumed to produce side effects. +However, side effects from one language are assumed not to be relevant to +another (for example, a Fortran library is assumed to not have any side +effects that are relevant for a Swift library.)

  • +
+

As an example, assume you have a static Fortran library which depends on a +static C library, which in turn depends on a static Fortran library. The +top-level Fortran library has optimization enabled, but the middle C library +does not. If you build the top Fortran library, the bottom Fortran library will +also build, but not the middle C library, since the C library does not have any +side effects that are relevant for the Fortran library. However, if you build +the middle C library, the bottom Fortran library will also build, even though +it does not have any side effects that are relevant to the C library, since the +C library does not have optimization enabled.

+

This property is initialized by the value of the +CMAKE_OPTIMIZE_DEPENDENCIES variable when the target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OSX_ARCHITECTURES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OSX_ARCHITECTURES.html new file mode 100644 index 0000000000000000000000000000000000000000..c1edeb5ec3e2efdcfd0388fdfd61f2d1cfecf055 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OSX_ARCHITECTURES.html @@ -0,0 +1,145 @@ + + + + + + + + + OSX_ARCHITECTURES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

OSX_ARCHITECTURES

+

Target specific architectures for macOS.

+

The OSX_ARCHITECTURES property sets the target binary architecture for +targets on macOS (-arch). This property is initialized by the value of the +variable CMAKE_OSX_ARCHITECTURES if it is set when a target is +created. Use OSX_ARCHITECTURES_<CONFIG> to set the binary +architectures on a per-configuration basis, where <CONFIG> is an +upper-case name (e.g. OSX_ARCHITECTURES_DEBUG).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OSX_ARCHITECTURES_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OSX_ARCHITECTURES_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..c25c3086c7869e7a3cf51a1ebf2ea296a12cc2dd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OSX_ARCHITECTURES_CONFIG.html @@ -0,0 +1,141 @@ + + + + + + + + + OSX_ARCHITECTURES_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

OSX_ARCHITECTURES_<CONFIG>

+

Per-configuration macOS and iOS binary architectures for a target.

+

This property is the configuration-specific version of +OSX_ARCHITECTURES.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OUTPUT_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OUTPUT_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..060ff8c62e75d39121480acf6aca35fd0c1465de --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OUTPUT_NAME.html @@ -0,0 +1,155 @@ + + + + + + + + + OUTPUT_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

OUTPUT_NAME

+

Output name for target files.

+

This sets the base name for output files created for an executable or +library target. If not set, the logical target name is used by +default during generation. The value is not set by default during +configuration.

+

Contents of OUTPUT_NAME and the variants listed below may use +generator expressions.

+

See also the variants:

+ +
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OUTPUT_NAME_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OUTPUT_NAME_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..d3ea1fc8df935f30c287a2872d511bc6b3706d17 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/OUTPUT_NAME_CONFIG.html @@ -0,0 +1,141 @@ + + + + + + + + + OUTPUT_NAME_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

OUTPUT_NAME_<CONFIG>

+

Per-configuration target file base name.

+

This is the configuration-specific version of the OUTPUT_NAME +target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PCH_INSTANTIATE_TEMPLATES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PCH_INSTANTIATE_TEMPLATES.html new file mode 100644 index 0000000000000000000000000000000000000000..9a963aeac95f625461b61566053875db99fb5511 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PCH_INSTANTIATE_TEMPLATES.html @@ -0,0 +1,148 @@ + + + + + + + + + PCH_INSTANTIATE_TEMPLATES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PCH_INSTANTIATE_TEMPLATES

+
+

New in version 3.19.

+
+

When this property is set to true, the precompiled header compiler options +will contain a flag to instantiate templates during the generation of the PCH +if supported. This can significantly improve compile times. Supported in Clang +since version 11.

+

This property is initialized by the value of the +CMAKE_PCH_INSTANTIATE_TEMPLATES variable if it is set when a target +is created. If that variable is not set, the property defaults to ON.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PCH_WARN_INVALID.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PCH_WARN_INVALID.html new file mode 100644 index 0000000000000000000000000000000000000000..c5ada9165e82140d7103b68adfcb78f24449291f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PCH_WARN_INVALID.html @@ -0,0 +1,147 @@ + + + + + + + + + PCH_WARN_INVALID — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PCH_WARN_INVALID

+
+

New in version 3.18.

+
+

When this property is set to true, the precompile header compiler options +will contain a compiler flag which should warn about invalid precompiled +headers e.g. -Winvalid-pch for GNU compiler.

+

This property is initialized by the value of the +CMAKE_PCH_WARN_INVALID variable if it is set when a target is +created. If that variable is not set, the property defaults to ON.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..d7a279e53a5b28740a9c25f2a70505411c46e0f9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_NAME.html @@ -0,0 +1,153 @@ + + + + + + + + + PDB_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PDB_NAME

+

Output name for the MS debug symbol .pdb file generated by the +linker for an executable or shared library target.

+

This property specifies the base name for the debug symbols file. +If not set, the OUTPUT_NAME target property value or +logical target name is used by default.

+
+

Note

+

This property does not apply to STATIC library targets because no linker +is invoked to produce them so they have no linker-generated .pdb file +containing debug symbols.

+

The linker-generated program database files are specified by the +/pdb linker flag and are not the same as compiler-generated +program database files specified by the /Fd compiler flag. +Use the COMPILE_PDB_NAME property to specify the latter.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_NAME_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_NAME_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..337b73d564bff909f5df4e15fc83f7ee7175eda3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_NAME_CONFIG.html @@ -0,0 +1,151 @@ + + + + + + + + + PDB_NAME_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PDB_NAME_<CONFIG>

+

Per-configuration output name for the MS debug symbol .pdb file +generated by the linker for an executable or shared library target.

+

This is the configuration-specific version of PDB_NAME.

+
+

Note

+

This property does not apply to STATIC library targets because no linker +is invoked to produce them so they have no linker-generated .pdb file +containing debug symbols.

+

The linker-generated program database files are specified by the +/pdb linker flag and are not the same as compiler-generated +program database files specified by the /Fd compiler flag. +Use the COMPILE_PDB_NAME_<CONFIG> property to specify the latter.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_OUTPUT_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_OUTPUT_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..2742f340c50d85d717a0cf89d64862624b12c026 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_OUTPUT_DIRECTORY.html @@ -0,0 +1,159 @@ + + + + + + + + + PDB_OUTPUT_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PDB_OUTPUT_DIRECTORY

+

Output directory for the MS debug symbols .pdb file +generated by the linker for an executable or shared library target.

+

This property specifies the directory into which the MS debug symbols +will be placed by the linker. The property value may use +generator expressions. +Multi-configuration generators append a per-configuration +subdirectory to the specified directory unless a generator expression +is used.

+

This property is initialized by the value of the +CMAKE_PDB_OUTPUT_DIRECTORY variable if it is +set when a target is created.

+
+

Note

+

This property does not apply to STATIC library targets because no linker +is invoked to produce them so they have no linker-generated .pdb file +containing debug symbols.

+

The linker-generated program database files are specified by the +/pdb linker flag and are not the same as compiler-generated +program database files specified by the /Fd compiler flag. +Use the COMPILE_PDB_OUTPUT_DIRECTORY property to specify the latter.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_OUTPUT_DIRECTORY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_OUTPUT_DIRECTORY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..b166117344cc6754513f2673e1b1d8b7c7aec8a6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PDB_OUTPUT_DIRECTORY_CONFIG.html @@ -0,0 +1,159 @@ + + + + + + + + + PDB_OUTPUT_DIRECTORY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PDB_OUTPUT_DIRECTORY_<CONFIG>

+

Per-configuration output directory for the MS debug symbol .pdb file +generated by the linker for an executable or shared library target.

+

This is a per-configuration version of PDB_OUTPUT_DIRECTORY, +but multi-configuration generators (Visual Studio Generators, +Xcode) do NOT append a +per-configuration subdirectory to the specified directory. This +property is initialized by the value of the +CMAKE_PDB_OUTPUT_DIRECTORY_<CONFIG> variable if it is +set when a target is created.

+

Contents of PDB_OUTPUT_DIRECTORY_<CONFIG> may use +generator expressions.

+
+

Note

+

This property does not apply to STATIC library targets because no linker +is invoked to produce them so they have no linker-generated .pdb file +containing debug symbols.

+

The linker-generated program database files are specified by the +/pdb linker flag and are not the same as compiler-generated +program database files specified by the /Fd compiler flag. +Use the COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG> property to specify the latter.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/POSITION_INDEPENDENT_CODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/POSITION_INDEPENDENT_CODE.html new file mode 100644 index 0000000000000000000000000000000000000000..60044191d945ba2d44403a31be31dedddee811a3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/POSITION_INDEPENDENT_CODE.html @@ -0,0 +1,150 @@ + + + + + + + + + POSITION_INDEPENDENT_CODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

POSITION_INDEPENDENT_CODE

+

Whether to create a position-independent target

+

The POSITION_INDEPENDENT_CODE property determines whether position +independent executables or shared libraries will be created. This +property is True by default for SHARED and MODULE library +targets and False otherwise. This property is initialized by the value +of the CMAKE_POSITION_INDEPENDENT_CODE variable if it is set +when a target is created.

+
+

Note

+

For executable targets, the link step is controlled by the CMP0083 +policy and the CheckPIESupported module.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/POST_INSTALL_SCRIPT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/POST_INSTALL_SCRIPT.html new file mode 100644 index 0000000000000000000000000000000000000000..c692443e09b2868469e56f2de0e426615c773004 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/POST_INSTALL_SCRIPT.html @@ -0,0 +1,143 @@ + + + + + + + + + POST_INSTALL_SCRIPT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

POST_INSTALL_SCRIPT

+

Deprecated install support.

+

The PRE_INSTALL_SCRIPT and POST_INSTALL_SCRIPT properties are +the old way to specify CMake scripts to run before and after installing a +target. They are used only when the old INSTALL_TARGETS command is +used to install the target. Use the install() command instead.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRECOMPILE_HEADERS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRECOMPILE_HEADERS.html new file mode 100644 index 0000000000000000000000000000000000000000..f21c786dfe007e2f0deb05ba27d164b5d6cea730 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRECOMPILE_HEADERS.html @@ -0,0 +1,148 @@ + + + + + + + + + PRECOMPILE_HEADERS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PRECOMPILE_HEADERS

+
+

New in version 3.16.

+
+

List of header files to precompile.

+

This property holds a semicolon-separated list +of header files to precompile specified so far for its target. +Use the target_precompile_headers() command to append more header +files.

+

This property supports +generator expressions.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRECOMPILE_HEADERS_REUSE_FROM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRECOMPILE_HEADERS_REUSE_FROM.html new file mode 100644 index 0000000000000000000000000000000000000000..f83df205e66ec0bcd4aa910fe84f7fcb237f0f43 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRECOMPILE_HEADERS_REUSE_FROM.html @@ -0,0 +1,144 @@ + + + + + + + + + PRECOMPILE_HEADERS_REUSE_FROM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PRECOMPILE_HEADERS_REUSE_FROM

+
+

New in version 3.16.

+
+

Target from which to reuse the precompiled headers build artifact.

+

See the second signature of target_precompile_headers() command +for more detailed information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..c65398e29ce281798b6182877eb9019282611de5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PREFIX.html @@ -0,0 +1,141 @@ + + + + + + + + + PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PREFIX

+

What comes before the library name.

+

A target property that can be set to override the prefix (such as +lib) on a library name.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRE_INSTALL_SCRIPT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRE_INSTALL_SCRIPT.html new file mode 100644 index 0000000000000000000000000000000000000000..19973ac981795a6b8d0938b4165a90a58f81a32e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRE_INSTALL_SCRIPT.html @@ -0,0 +1,143 @@ + + + + + + + + + PRE_INSTALL_SCRIPT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PRE_INSTALL_SCRIPT

+

Deprecated install support.

+

The PRE_INSTALL_SCRIPT and POST_INSTALL_SCRIPT properties are +the old way to specify CMake scripts to run before and after installing a +target. They are used only when the old INSTALL_TARGETS command is +used to install the target. Use the install() command instead.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRIVATE_HEADER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRIVATE_HEADER.html new file mode 100644 index 0000000000000000000000000000000000000000..1630118245f189f8209515a6a7990472e261d86b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PRIVATE_HEADER.html @@ -0,0 +1,145 @@ + + + + + + + + + PRIVATE_HEADER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PRIVATE_HEADER

+

Specify private header files in a FRAMEWORK shared library target.

+

Shared library targets marked with the FRAMEWORK property generate +frameworks on macOS, iOS and normal shared libraries on other platforms. +This property may be set to a list of header files to be placed in the +PrivateHeaders directory inside the framework folder. On non-Apple +platforms these headers may be installed using the PRIVATE_HEADER +option to the install(TARGETS) command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PROJECT_LABEL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PROJECT_LABEL.html new file mode 100644 index 0000000000000000000000000000000000000000..3fe11ba1b72ff32a3cf48e595e3c22368cd66327 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PROJECT_LABEL.html @@ -0,0 +1,141 @@ + + + + + + + + + PROJECT_LABEL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PROJECT_LABEL

+

Change the name of a target in an IDE.

+

Can be used to change the name of the target in an IDE like Visual +Studio.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PUBLIC_HEADER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PUBLIC_HEADER.html new file mode 100644 index 0000000000000000000000000000000000000000..9b4b54b23a69dd57fd3dfc885ed11a6c545c75c6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/PUBLIC_HEADER.html @@ -0,0 +1,145 @@ + + + + + + + + + PUBLIC_HEADER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PUBLIC_HEADER

+

Specify public header files in a FRAMEWORK shared library target.

+

Shared library targets marked with the FRAMEWORK property generate +frameworks on macOS, iOS and normal shared libraries on other platforms. +This property may be set to a list of header files to be placed in the +Headers directory inside the framework folder. On non-Apple platforms +these headers may be installed using the PUBLIC_HEADER option to the +install(TARGETS) command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RESOURCE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RESOURCE.html new file mode 100644 index 0000000000000000000000000000000000000000..b8f59384d6af750e2e8297e78d44422d9e23da3a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RESOURCE.html @@ -0,0 +1,190 @@ + + + + + + + + + RESOURCE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

RESOURCE

+

Specify resource files in a FRAMEWORK or BUNDLE.

+

Target marked with the FRAMEWORK or BUNDLE property +generate framework or application bundle (both macOS and iOS is supported) +or normal shared libraries on other platforms. +This property may be set to a list of files to be placed in the corresponding +directory (eg. Resources directory for macOS) inside the bundle. +On non-Apple platforms these files may be installed using the RESOURCE +option to the install(TARGETS) command.

+

Following example of Application Bundle:

+
add_executable(ExecutableTarget
+  addDemo.c
+  resourcefile.txt
+  appresourcedir/appres.txt)
+
+target_link_libraries(ExecutableTarget heymath mul)
+
+set(RESOURCE_FILES
+  resourcefile.txt
+  appresourcedir/appres.txt)
+
+set_target_properties(ExecutableTarget PROPERTIES
+  MACOSX_BUNDLE TRUE
+  MACOSX_FRAMEWORK_IDENTIFIER org.cmake.ExecutableTarget
+  RESOURCE "${RESOURCE_FILES}")
+
+
+

will produce flat structure for iOS systems:

+
ExecutableTarget.app
+  appres.txt
+  ExecutableTarget
+  Info.plist
+  resourcefile.txt
+
+
+

For macOS systems it will produce following directory structure:

+
ExecutableTarget.app/
+  Contents
+    Info.plist
+    MacOS
+      ExecutableTarget
+    Resources
+      appres.txt
+      resourcefile.txt
+
+
+

For Linux, such CMake script produce following files:

+
ExecutableTarget
+Resources
+  appres.txt
+  resourcefile.txt
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RULE_LAUNCH_COMPILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RULE_LAUNCH_COMPILE.html new file mode 100644 index 0000000000000000000000000000000000000000..f980936dab723a848eacc9be7360078212290cc1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RULE_LAUNCH_COMPILE.html @@ -0,0 +1,148 @@ + + + + + + + + + RULE_LAUNCH_COMPILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

RULE_LAUNCH_COMPILE

+

Specify a launcher for compile rules.

+
+

Note

+

This property is intended for internal use by ctest(1). Projects +and developers should use the <LANG>_COMPILER_LAUNCHER target +properties or the associated CMAKE_<LANG>_COMPILER_LAUNCHER +variables instead.

+
+

See the global property of the same name +for details. This overrides the global and directory property for a target.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RULE_LAUNCH_CUSTOM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RULE_LAUNCH_CUSTOM.html new file mode 100644 index 0000000000000000000000000000000000000000..9f0fbee62d97b40f8423abd54668fd5ec3f5c3b8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RULE_LAUNCH_CUSTOM.html @@ -0,0 +1,141 @@ + + + + + + + + + RULE_LAUNCH_CUSTOM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

RULE_LAUNCH_CUSTOM

+

Specify a launcher for custom rules.

+

See the global property of the same name for details. This overrides +the global and directory property for a target.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RULE_LAUNCH_LINK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RULE_LAUNCH_LINK.html new file mode 100644 index 0000000000000000000000000000000000000000..aa5145684ce9a159de6f82caa9ad65a42a68d6a4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RULE_LAUNCH_LINK.html @@ -0,0 +1,148 @@ + + + + + + + + + RULE_LAUNCH_LINK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..f47a8c5862f8edcb4a39d105927c8d376e423c1f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_DIRECTORY.html @@ -0,0 +1,149 @@ + + + + + + + + + RUNTIME_OUTPUT_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

RUNTIME_OUTPUT_DIRECTORY

+

Output directory in which to build RUNTIME target files.

+

This property specifies the directory into which runtime target files +should be built. The property value may use +generator expressions. +Multi-configuration generators (Visual Studio, +Xcode, Ninja Multi-Config) append a +per-configuration subdirectory to the specified directory unless a generator +expression is used.

+

This property is initialized by the value of the +CMAKE_RUNTIME_OUTPUT_DIRECTORY variable if it is set when a target is created.

+

See also the RUNTIME_OUTPUT_DIRECTORY_<CONFIG> target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_DIRECTORY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_DIRECTORY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..6d1735e5468fca1e901c55ad1459bb37bce4d33c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_DIRECTORY_CONFIG.html @@ -0,0 +1,150 @@ + + + + + + + + + RUNTIME_OUTPUT_DIRECTORY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

RUNTIME_OUTPUT_DIRECTORY_<CONFIG>

+

Per-configuration output directory for +RUNTIME target files.

+

This is a per-configuration version of the +RUNTIME_OUTPUT_DIRECTORY target property, but +multi-configuration generators (Visual Studio Generators, +Xcode) do NOT append a +per-configuration subdirectory to the specified directory. This +property is initialized by the value of the +CMAKE_RUNTIME_OUTPUT_DIRECTORY_<CONFIG> variable if +it is set when a target is created.

+

Contents of RUNTIME_OUTPUT_DIRECTORY_<CONFIG> may use +generator expressions.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..b804073b9beb618df00ecf49707aaf663465bc69 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_NAME.html @@ -0,0 +1,143 @@ + + + + + + + + + RUNTIME_OUTPUT_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

RUNTIME_OUTPUT_NAME

+

Output name for RUNTIME target files.

+

This property specifies the base name for runtime target files. It +overrides OUTPUT_NAME and OUTPUT_NAME_<CONFIG> +properties.

+

See also the RUNTIME_OUTPUT_NAME_<CONFIG> target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_NAME_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_NAME_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..796caa798b69b3465bab83016e77806ad0ab6225 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/RUNTIME_OUTPUT_NAME_CONFIG.html @@ -0,0 +1,142 @@ + + + + + + + + + RUNTIME_OUTPUT_NAME_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

RUNTIME_OUTPUT_NAME_<CONFIG>

+

Per-configuration output name for +RUNTIME target files.

+

This is the configuration-specific version of the +RUNTIME_OUTPUT_NAME target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SKIP_BUILD_RPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SKIP_BUILD_RPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..28b83bf31b939422e7cdf51577c58e3ba2069612 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SKIP_BUILD_RPATH.html @@ -0,0 +1,144 @@ + + + + + + + + + SKIP_BUILD_RPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

SKIP_BUILD_RPATH

+

Should rpaths be used for the build tree.

+

SKIP_BUILD_RPATH is a boolean specifying whether to skip automatic +generation of an rpath allowing the target to run from the build tree, +see also the BUILD_RPATH target property. +This property is initialized by the value of the variable +CMAKE_SKIP_BUILD_RPATH if it is set when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SOURCES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SOURCES.html new file mode 100644 index 0000000000000000000000000000000000000000..9b65a08173b9f18ab3c449e937c57e3ec6b8511f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SOURCES.html @@ -0,0 +1,170 @@ + + + + + + + + + SOURCES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

SOURCES

+

This specifies the list of paths to source files for the target. +The following commands all set or add to the SOURCES target property +and are the usual way to manipulate it:

+ +

Contents of SOURCES may use +generator expressions. +If a path starts with a generator expression, it is expected to +evaluate to an absolute path. Not doing so is considered undefined behavior.

+

Paths that are for files generated by the build will be treated +as relative to the build directory of the target, if the path is not +already specified as an absolute path. Note that whether a file is seen as +generated may be affected by policy CMP0118.

+

If a path does not start with a generator expression, is not an +absolute path and is not a generated file, it will be treated as relative to +the location selected by the first of the following that matches:

+
    +
  • If a file by the specified path exists relative to the target's source +directory, use that file.

  • +
  • If policy CMP0115 is not set to NEW, try appending each +known source file extension to the path and check if that exists +relative to the target's source directory.

  • +
  • Repeat the above two steps, this time relative to the target's binary +directory instead.

  • +
+

Note that the above decisions are made at generation time, not build time.

+

See the cmake-buildsystem(7) manual for more on defining +buildsystem properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SOURCE_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SOURCE_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..ebb3edd1422e88c3bcbc6803c09e6c11ca699c1a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SOURCE_DIR.html @@ -0,0 +1,144 @@ + + + + + + + + + SOURCE_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

SOURCE_DIR

+
+

New in version 3.4.

+
+

This read-only property reports the value of the +CMAKE_CURRENT_SOURCE_DIR variable in the directory in which +the target was defined.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SOVERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SOVERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..c911d0cf6fe9d65f16d9006493808607d9a81f23 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SOVERSION.html @@ -0,0 +1,178 @@ + + + + + + + + + SOVERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

SOVERSION

+

What version number is this target.

+

For shared libraries VERSION and SOVERSION can be used to +specify the build version and API version respectively. When building or +installing appropriate symlinks are created if the platform supports +symlinks and the linker supports so-names. If only one of both is +specified the missing is assumed to have the same version number. +SOVERSION is ignored if NO_SONAME property is set.

+
+

Windows Versions

+

For shared libraries and executables on Windows the VERSION +attribute is parsed to extract a <major>.<minor> version number. +These numbers are used as the image version of the binary.

+
+
+

Mach-O Versions

+

For shared libraries and executables on Mach-O systems (e.g. macOS, iOS), +the SOVERSION property corresponds to the compatibility version and +VERSION corresponds to the current version (unless Mach-O +specific overrides are provided, as discussed below). +See the FRAMEWORK target property for an example.

+

For shared libraries, the MACHO_COMPATIBILITY_VERSION and +MACHO_CURRENT_VERSION properties can be used to +override the compatibility version and current version respectively. +Note that SOVERSION will still be used to form the install_name +and both SOVERSION and VERSION may also affect the file +and symlink names.

+

Versions of Mach-O binaries may be checked with the otool -L <binary> +command.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/STATIC_LIBRARY_FLAGS_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/STATIC_LIBRARY_FLAGS_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..83f35a53484a180f8feeb0da515408b33d9ea16a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/STATIC_LIBRARY_FLAGS_CONFIG.html @@ -0,0 +1,146 @@ + + + + + + + + + STATIC_LIBRARY_FLAGS_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

STATIC_LIBRARY_FLAGS_<CONFIG>

+

Per-configuration archiver (or MSVC librarian) flags for a static library +target.

+

This is the configuration-specific version of STATIC_LIBRARY_FLAGS.

+
+

Note

+

This property has been superseded by STATIC_LIBRARY_OPTIONS +property.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/STATIC_LIBRARY_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/STATIC_LIBRARY_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..290ef688cfb702044a01fd72d61407f91b964f7e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/STATIC_LIBRARY_OPTIONS.html @@ -0,0 +1,181 @@ + + + + + + + + + STATIC_LIBRARY_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

STATIC_LIBRARY_OPTIONS

+
+

New in version 3.13.

+
+

Archiver (or MSVC librarian) flags for a static library target. +Targets that are shared libraries, modules, or executables need to use +the LINK_OPTIONS target property.

+

This property holds a semicolon-separated list of options +specified so far for its target. Use set_target_properties() or +set_property() commands to set its content.

+

Contents of STATIC_LIBRARY_OPTIONS may use "generator expressions" with the +syntax $<...>. See the cmake-generator-expressions(7) manual +for available expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+
+

Note

+

This property must be used in preference to STATIC_LIBRARY_FLAGS +property.

+
+
+

Option De-duplication

+

The final set of options used for a target is constructed by +accumulating options from the current target and the usage requirements of +its dependencies. The set of options is de-duplicated to avoid repetition.

+
+

New in version 3.12: While beneficial for individual options, the de-duplication step can break +up option groups. For example, -option A -option B becomes +-option A B. One may specify a group of options using shell-like +quoting along with a SHELL: prefix. The SHELL: prefix is dropped, +and the rest of the option string is parsed using the +separate_arguments() UNIX_COMMAND mode. For example, +"SHELL:-option A" "SHELL:-option B" becomes -option A -option B.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..93635720986d65b78cbbad6aab5a6f9d58817148 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SUFFIX.html @@ -0,0 +1,141 @@ + + + + + + + + + SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

SUFFIX

+

What comes after the target name.

+

A target property that can be set to override the suffix (such as +.so or .exe) on the name of a library, module or executable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SYSTEM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SYSTEM.html new file mode 100644 index 0000000000000000000000000000000000000000..8b5c9de886af039b2bb1bf7d050ae8618ee57add --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/SYSTEM.html @@ -0,0 +1,161 @@ + + + + + + + + + SYSTEM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

SYSTEM

+
+

New in version 3.25.

+
+

Specifies that a target is a system target. This has the following +effects:

+ +

For imported targets, this property defaults to true, which means +that their INTERFACE_INCLUDE_DIRECTORIES and, if the +FRAMEWORK target property is true, frameworks directory are +treated as system directories by default. If their SYSTEM property is +false, then their INTERFACE_INCLUDE_DIRECTORIES as well as +frameworks will not be treated as system. Use the EXPORT_NO_SYSTEM +property to change how a target's SYSTEM property is set when it is +installed.

+

For non-imported targets, this target property is initialized from +the SYSTEM directory property when the target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_DEPENDENCIES_FILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_DEPENDENCIES_FILE.html new file mode 100644 index 0000000000000000000000000000000000000000..035ec4fa4cfd079db6ea929c7c7caebd1ba8558b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_DEPENDENCIES_FILE.html @@ -0,0 +1,143 @@ + + + + + + + + + Swift_DEPENDENCIES_FILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

Swift_DEPENDENCIES_FILE

+
+

New in version 3.15.

+
+

This property sets the path for the Swift dependency file (swiftdep) for the +target. If one is not specified, it will default to <TARGET>.swiftdeps.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_LANGUAGE_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_LANGUAGE_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..c1df68819e8743f7ed80537bb98189b713ca01d0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_LANGUAGE_VERSION.html @@ -0,0 +1,144 @@ + + + + + + + + + Swift_LANGUAGE_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

Swift_LANGUAGE_VERSION

+
+

New in version 3.16.

+
+

This property sets the language version for the Swift sources in the target. If +one is not specified, it will default to <CMAKE_Swift_LANGUAGE_VERSION> if +specified, otherwise it is the latest version supported by the compiler.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_MODULE_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_MODULE_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..1ab3ecac25bcbc9a8ec1f287be82e58c9a769b39 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_MODULE_DIRECTORY.html @@ -0,0 +1,147 @@ + + + + + + + + + Swift_MODULE_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

Swift_MODULE_DIRECTORY

+
+

New in version 3.15.

+
+

Specify output directory for Swift modules provided by the target.

+

If the target contains Swift source files, this specifies the directory in which +the modules will be placed. When this property is not set, the modules will be +placed in the build directory corresponding to the target's source directory. +If the variable CMAKE_Swift_MODULE_DIRECTORY is set when a target is +created its value is used to initialize this property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_MODULE_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_MODULE_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..30a7653ec15b21b25dc36448ba57bea163ce3573 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/Swift_MODULE_NAME.html @@ -0,0 +1,143 @@ + + + + + + + + + Swift_MODULE_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

Swift_MODULE_NAME

+
+

New in version 3.15.

+
+

This property specifies the name of the Swift module. It is defaulted to the +name of the target.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/TYPE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/TYPE.html new file mode 100644 index 0000000000000000000000000000000000000000..fda7890d8a5a3b60d527126d6c1e83f363b7ee0e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/TYPE.html @@ -0,0 +1,143 @@ + + + + + + + + + TYPE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

TYPE

+

The type of the target.

+

This read-only property can be used to test the type of the given +target. It will be one of STATIC_LIBRARY, MODULE_LIBRARY, +SHARED_LIBRARY, OBJECT_LIBRARY, INTERFACE_LIBRARY, EXECUTABLE +or one of the internal target types.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/UNITY_BUILD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/UNITY_BUILD.html new file mode 100644 index 0000000000000000000000000000000000000000..ede9a4bb8a9a0b0af5eceea6edb7f4e77c197a97 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/UNITY_BUILD.html @@ -0,0 +1,225 @@ + + + + + + + + + UNITY_BUILD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

UNITY_BUILD

+
+

New in version 3.16.

+
+

When this property is set to true, the target source files will be combined +into batches for faster compilation. This is done by creating a (set of) +unity sources which #include the original sources, then compiling these +unity sources instead of the originals. This is known as a Unity or Jumbo +build.

+

CMake provides different algorithms for selecting which sources are grouped +together into a bucket. Algorithm selection is decided by the +UNITY_BUILD_MODE target property, which has the following acceptable +values:

+
    +
  • BATCH +When in this mode CMake determines which files are grouped together. +The UNITY_BUILD_BATCH_SIZE property controls the upper limit on +how many sources can be combined per unity source file.

  • +
  • GROUP +When in this mode each target explicitly specifies how to group +source files. Each source file that has the same +UNITY_GROUP value will be grouped together. Any sources +that don't have this property will be compiled individually. The +UNITY_BUILD_BATCH_SIZE property is ignored when using +this mode.

  • +
+

If no explicit UNITY_BUILD_MODE has been specified, CMake will +default to BATCH.

+

Unity builds are not currently supported for all languages. CMake version +3.27.9 supports combining C and CXX source files. For targets that +mix source files from more than one language, CMake will separate the languages +such that each generated unity source file only contains sources for a single +language.

+

This property is initialized by the value of the CMAKE_UNITY_BUILD +variable when a target is created.

+
+

Note

+

Projects should not directly set the UNITY_BUILD property or its +associated CMAKE_UNITY_BUILD variable to true. Depending +on the capabilities of the build machine and compiler used, it might or +might not be appropriate to enable unity builds. Therefore, this feature +should be under developer control, which would normally be through the +developer choosing whether or not to set the CMAKE_UNITY_BUILD +variable on the cmake(1) command line or some other equivalent +method. However, it IS recommended to set the UNITY_BUILD target +property to false if it is known that enabling unity builds for the +target can lead to problems.

+
+
+

ODR (One definition rule) errors

+

When multiple source files are included into one source file, as is done +for unity builds, it can potentially lead to ODR errors. CMake provides +a number of measures to help address such problems:

+ +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/UNITY_BUILD_BATCH_SIZE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/UNITY_BUILD_BATCH_SIZE.html new file mode 100644 index 0000000000000000000000000000000000000000..1ada340575a46a44a21679b50997d0f64b7fa693 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/UNITY_BUILD_BATCH_SIZE.html @@ -0,0 +1,158 @@ + + + + + + + + + UNITY_BUILD_BATCH_SIZE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

UNITY_BUILD_BATCH_SIZE

+
+

New in version 3.16.

+
+

Specifies the maximum number of source files that can be combined into any one +unity source file when unity builds are enabled by the UNITY_BUILD +target property. The original source files will be distributed across as many +unity source files as necessary to honor this limit.

+

The initial value for this property is taken from the +CMAKE_UNITY_BUILD_BATCH_SIZE variable when the target is created. +If that variable has not been set, the initial value will be 8.

+

The batch size needs to be selected carefully. If set too high, the size of +the combined source files could result in the compiler using excessive memory +or hitting other similar limits. In extreme cases, this can even result in +build failure. On the other hand, if the batch size is too low, there will be +little gain in build performance.

+

Although strongly discouraged, the batch size may be set to a value of 0 to +combine all the sources for the target into a single unity file, regardless of +how many sources are involved. This runs the risk of creating an excessively +large unity source file and negatively impacting the build performance, so +a value of 0 is not generally recommended.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/UNITY_BUILD_UNIQUE_ID.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/UNITY_BUILD_UNIQUE_ID.html new file mode 100644 index 0000000000000000000000000000000000000000..a43bb152db375b9ccd72b444b0cce77aa625a30c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/UNITY_BUILD_UNIQUE_ID.html @@ -0,0 +1,184 @@ + + + + + + + + + UNITY_BUILD_UNIQUE_ID — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

UNITY_BUILD_UNIQUE_ID

+
+

New in version 3.20.

+
+

The name of a valid C-identifier which is set to a unique per-file +value during unity builds.

+

When this property is populated and when UNITY_BUILD +is true, the property value is used to define a compiler definition +of the specified name. The value of the defined symbol is unspecified, +but it is unique per file path.

+

Given:

+
set_target_properties(myTarget PROPERTIES
+  UNITY_BUILD "ON"
+  UNITY_BUILD_UNIQUE_ID "MY_UNITY_ID"
+)
+
+
+

the MY_UNITY_ID symbol is defined to a unique per-file value.

+

One known use case for this identifier is to disambiguate the +variables in an anonymous namespace in a limited scope. +Anonymous namespaces present a problem for unity builds because +they are used to ensure that certain variables and declarations +are scoped to a translation unit which is approximated by a +single source file. When source files are combined in a unity +build file, those variables in different files are combined in +a single translation unit and the names clash. This property can +be used to avoid that with code like the following:

+
// Needed for when unity builds are disabled
+#ifndef MY_UNITY_ID
+#define MY_UNITY_ID
+#endif
+
+namespace { namespace MY_UNITY_ID {
+  // The name 'i' clashes (or could clash) with other
+  // variables in other anonymous namespaces
+  int i = 42;
+}}
+
+int use_var()
+{
+  return MY_UNITY_ID::i;
+}
+
+
+

The pseudonymous namespace is used within a truly anonymous namespace. +On many platforms, this maintains the invariant that the symbols within +do not get external linkage when performing a unity build.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..e171745b1d52f29aab467aa59696146fece06af9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VERSION.html @@ -0,0 +1,180 @@ + + + + + + + + + VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VERSION

+

What version number is this target.

+

For shared libraries VERSION and SOVERSION can be used +to specify the build version and API version respectively. When building or +installing appropriate symlinks are created if the platform supports +symlinks and the linker supports so-names. If only one of both is +specified the missing is assumed to have the same version number. For +executables VERSION can be used to specify the build version. When +building or installing appropriate symlinks are created if the +platform supports symlinks.

+
+

Windows Versions

+

For shared libraries and executables on Windows the VERSION +attribute is parsed to extract a <major>.<minor> version number. +These numbers are used as the image version of the binary.

+
+
+

Mach-O Versions

+

For shared libraries and executables on Mach-O systems (e.g. macOS, iOS), +the SOVERSION property corresponds to the compatibility version +and VERSION corresponds to the current version (unless Mach-O specific +overrides are provided, as discussed below). +See the FRAMEWORK target property for an example.

+

For shared libraries, the MACHO_COMPATIBILITY_VERSION and +MACHO_CURRENT_VERSION properties can be used to +override the compatibility version and current version respectively. +Note that SOVERSION will still be used to form the +install_name and both SOVERSION and VERSION may also +affect the file and symlink names.

+

Versions of Mach-O binaries may be checked with the otool -L <binary> +command.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VISIBILITY_INLINES_HIDDEN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VISIBILITY_INLINES_HIDDEN.html new file mode 100644 index 0000000000000000000000000000000000000000..474a63be30d39f6c6f18162fa95c1f3eaafc43d8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VISIBILITY_INLINES_HIDDEN.html @@ -0,0 +1,146 @@ + + + + + + + + + VISIBILITY_INLINES_HIDDEN — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VISIBILITY_INLINES_HIDDEN

+

Whether to add a compile flag to hide symbols of inline functions

+

The VISIBILITY_INLINES_HIDDEN property determines whether a flag for +hiding symbols for inline functions, such as -fvisibility-inlines-hidden, +should be used when invoking the compiler. This property affects compilation +in sources of all types of targets (subject to policy CMP0063).

+

This property is initialized by +the value of the CMAKE_VISIBILITY_INLINES_HIDDEN variable if it +is set when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_CONFIGURATION_TYPE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_CONFIGURATION_TYPE.html new file mode 100644 index 0000000000000000000000000000000000000000..a8e16d4b0b98afa713e726ee846abe696c7fd309 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_CONFIGURATION_TYPE.html @@ -0,0 +1,148 @@ + + + + + + + + + VS_CONFIGURATION_TYPE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_CONFIGURATION_TYPE

+
+

New in version 3.6.

+
+

Visual Studio project configuration type.

+

Sets the ConfigurationType attribute for a generated Visual Studio project. +The property value may use +generator expressions. +If this property is set, it overrides the default setting that is based on the +target type (e.g. StaticLibrary, Application, ...).

+

Supported on Visual Studio Generators for VS 2010 and higher.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DEBUGGER_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DEBUGGER_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..7e13ccffbceb72d15b6edbc730bb7cb8e3d4e335 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DEBUGGER_COMMAND.html @@ -0,0 +1,150 @@ + + + + + + + + + VS_DEBUGGER_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DEBUGGER_COMMAND

+
+

New in version 3.12.

+
+

Sets the local debugger command for Visual Studio C++ targets. +The property value may use +generator expressions. +This is defined in <LocalDebuggerCommand> in the Visual Studio +project file. This property is initialized by the value of the variable +CMAKE_VS_DEBUGGER_COMMAND if it is set when a target is +created.

+

This property only works for Visual Studio 11 2012 and above; +it is ignored on other generators.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DEBUGGER_COMMAND_ARGUMENTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DEBUGGER_COMMAND_ARGUMENTS.html new file mode 100644 index 0000000000000000000000000000000000000000..4175ba6c1e0d99c4f62a8e32680001f61ed9e850 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DEBUGGER_COMMAND_ARGUMENTS.html @@ -0,0 +1,150 @@ + + + + + + + + + VS_DEBUGGER_COMMAND_ARGUMENTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DEBUGGER_COMMAND_ARGUMENTS

+
+

New in version 3.13.

+
+

Sets the local debugger command line arguments for Visual Studio C++ targets. +The property value may use +generator expressions. +This is defined in <LocalDebuggerCommandArguments> in the Visual Studio +project file. This property is initialized by the value of the variable +CMAKE_VS_DEBUGGER_COMMAND_ARGUMENTS if it is set when a target is +created.

+

This property only works for Visual Studio 11 2012 and above; +it is ignored on other generators.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DEBUGGER_ENVIRONMENT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DEBUGGER_ENVIRONMENT.html new file mode 100644 index 0000000000000000000000000000000000000000..f7dcfc5a89f8ca20821e459d59aa482a545f1ea8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DEBUGGER_ENVIRONMENT.html @@ -0,0 +1,150 @@ + + + + + + + + + VS_DEBUGGER_ENVIRONMENT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DEBUGGER_ENVIRONMENT

+
+

New in version 3.13.

+
+

Sets the local debugger environment for Visual Studio C++ targets. +The property value may use +generator expressions. +This is defined in <LocalDebuggerEnvironment> in the Visual Studio +project file. This property is initialized by the value of the variable +CMAKE_VS_DEBUGGER_ENVIRONMENT if it is set when a target is +created.

+

This property only works for Visual Studio 11 2012 and above; +it is ignored on other generators.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DESKTOP_EXTENSIONS_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DESKTOP_EXTENSIONS_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..25a9946d6188ae2eeeed22c52df7b8832cafd311 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DESKTOP_EXTENSIONS_VERSION.html @@ -0,0 +1,147 @@ + + + + + + + + + VS_DESKTOP_EXTENSIONS_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DESKTOP_EXTENSIONS_VERSION

+
+

New in version 3.4.

+
+

Visual Studio Windows 10 Desktop Extensions Version

+

Specifies the version of the Desktop Extensions that should be included in the +target. For example 10.0.10240.0. If the value is not specified, the Desktop +Extensions will not be included. To use the same version of the extensions as +the Windows 10 SDK that is being used, you can use the +CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_DOCUMENTATION_FILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_DOCUMENTATION_FILE.html new file mode 100644 index 0000000000000000000000000000000000000000..b8e45d059cf9227d48f2fd7ef4d610b4136b0253 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_DOCUMENTATION_FILE.html @@ -0,0 +1,143 @@ + + + + + + + + + VS_DOTNET_DOCUMENTATION_FILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DOTNET_DOCUMENTATION_FILE

+
+

New in version 3.17.

+
+

Visual Studio managed project .NET documentation output

+

Sets the target XML documentation file output.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCEPROP_refname_TAG_tagname.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCEPROP_refname_TAG_tagname.html new file mode 100644 index 0000000000000000000000000000000000000000..6e1b470c60191065e8a4a151e86b11b882662734 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCEPROP_refname_TAG_tagname.html @@ -0,0 +1,150 @@ + + + + + + + + + VS_DOTNET_REFERENCEPROP_<refname>_TAG_<tagname> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DOTNET_REFERENCEPROP_<refname>_TAG_<tagname>

+
+

New in version 3.10.

+
+

Defines an XML property <tagname> for a .NET reference +<refname>.

+

Reference properties can be set for .NET references which are +defined by the target properties VS_DOTNET_REFERENCES, +VS_DOTNET_REFERENCE_<refname> +and also for project references to other C# targets which are +established by target_link_libraries().

+

This property is only applicable to C# targets and Visual Studio +generators 2010 and later.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCES.html new file mode 100644 index 0000000000000000000000000000000000000000..21aa43761349b7b4225d86697fab9782a7252660 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCES.html @@ -0,0 +1,141 @@ + + + + + + + + + VS_DOTNET_REFERENCES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DOTNET_REFERENCES

+

Visual Studio managed project .NET references

+

Adds one or more semicolon-delimited .NET references to a generated +Visual Studio project. For example, "System;System.Windows.Forms".

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCES_COPY_LOCAL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCES_COPY_LOCAL.html new file mode 100644 index 0000000000000000000000000000000000000000..7da53520bb683cfac415bf435cdd6c86cdc9a5c9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCES_COPY_LOCAL.html @@ -0,0 +1,144 @@ + + + + + + + + + VS_DOTNET_REFERENCES_COPY_LOCAL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DOTNET_REFERENCES_COPY_LOCAL

+
+

New in version 3.8.

+
+

Sets the Copy Local property for all .NET hint references in the target

+

Boolean property to enable/disable copying of .NET hint references to +output directory. The default is ON.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCE_refname.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCE_refname.html new file mode 100644 index 0000000000000000000000000000000000000000..c23e5f1b5be49ff376421e92caa7d4c971c7a22b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_REFERENCE_refname.html @@ -0,0 +1,148 @@ + + + + + + + + + VS_DOTNET_REFERENCE_<refname> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DOTNET_REFERENCE_<refname>

+
+

New in version 3.8.

+
+

Visual Studio managed project .NET reference with name <refname> +and hint path.

+

Adds one .NET reference to generated Visual Studio project. The +reference will have the name <refname> and will point to the +assembly given as value of the property.

+

See also VS_DOTNET_REFERENCES and +VS_DOTNET_REFERENCES_COPY_LOCAL

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_STARTUP_OBJECT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_STARTUP_OBJECT.html new file mode 100644 index 0000000000000000000000000000000000000000..c5125ee1bef5ca4b144a00a544a78fb5921d4cb5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_STARTUP_OBJECT.html @@ -0,0 +1,154 @@ + + + + + + + + + VS_DOTNET_STARTUP_OBJECT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DOTNET_STARTUP_OBJECT

+
+

New in version 3.24.

+
+

Sets the startup object property in Visual Studio .NET targets. +The property value defines a full qualified class name (including package +name), for example: MyCompany.Package.MyStarterClass.

+

If the property is unset, Visual Studio uses the first matching +static void Main(string[]) function signature by default. When more +than one Main() method is available in the current project, the property +becomes mandatory for building the project.

+

This property only works for Visual Studio 11 2012 and above; +it is ignored on other generators.

+
set_property(TARGET ${TARGET_NAME} PROPERTY
+  VS_DOTNET_STARTUP_OBJECT "MyCompany.Package.MyStarterClass")
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_TARGET_FRAMEWORK_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_TARGET_FRAMEWORK_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..df142a144244f36e058cf22e7ca4d5261992ea31 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DOTNET_TARGET_FRAMEWORK_VERSION.html @@ -0,0 +1,144 @@ + + + + + + + + + VS_DOTNET_TARGET_FRAMEWORK_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DOTNET_TARGET_FRAMEWORK_VERSION

+

Specify the .NET target framework version.

+

Used to specify the .NET target framework version for C++/CLI. For +example, "v4.5".

+

This property is deprecated and should not be used anymore. Use +DOTNET_TARGET_FRAMEWORK or +DOTNET_TARGET_FRAMEWORK_VERSION instead.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DPI_AWARE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DPI_AWARE.html new file mode 100644 index 0000000000000000000000000000000000000000..2b1f3182f98298f4ca3ca0849d94f3af58161b84 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_DPI_AWARE.html @@ -0,0 +1,149 @@ + + + + + + + + + VS_DPI_AWARE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_DPI_AWARE

+
+

New in version 3.16.

+
+

Set the Manifest Tool -> Input and Output -> DPI Awareness in the Visual Studio +target project properties.

+

Valid values are PerMonitor, ON, or OFF.

+

For example:

+
add_executable(myproject myproject.cpp)
+set_property(TARGET myproject PROPERTY VS_DPI_AWARE "PerMonitor")
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_KEYWORD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_KEYWORD.html new file mode 100644 index 0000000000000000000000000000000000000000..d965239cc160c01af2ee26c4241a3ae6afc88ab8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_KEYWORD.html @@ -0,0 +1,145 @@ + + + + + + + + + VS_GLOBAL_KEYWORD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_GLOBAL_KEYWORD

+

Visual Studio project keyword for VS 10 (2010) and newer.

+

Sets the "keyword" attribute for a generated Visual Studio project. +Defaults to "Win32Proj". You may wish to override this value with +"ManagedCProj", for example, in a Visual Studio managed C++ unit test +project.

+

Use the VS_KEYWORD target property to set the +keyword for Visual Studio 9 (2008) and older.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_PROJECT_TYPES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_PROJECT_TYPES.html new file mode 100644 index 0000000000000000000000000000000000000000..9beb47d2d4263fe99bffdfb5fb590b8740333f74 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_PROJECT_TYPES.html @@ -0,0 +1,147 @@ + + + + + + + + + VS_GLOBAL_PROJECT_TYPES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_GLOBAL_PROJECT_TYPES

+

Visual Studio project type(s).

+

Can be set to one or more UUIDs recognized by Visual Studio to +indicate the type of project. This value is copied verbatim into the +generated project file. Example for a managed C++ unit testing +project:

+
{3AC096D0-A1C2-E12C-1390-A8335801FDAB};{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}
+
+
+

UUIDs are semicolon-delimited.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_ROOTNAMESPACE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_ROOTNAMESPACE.html new file mode 100644 index 0000000000000000000000000000000000000000..0470da891a6c6a4ab9369303dddb463e14eddca9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_ROOTNAMESPACE.html @@ -0,0 +1,141 @@ + + + + + + + + + VS_GLOBAL_ROOTNAMESPACE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_GLOBAL_ROOTNAMESPACE

+

Visual Studio project root namespace.

+

Sets the "RootNamespace" attribute for a generated Visual Studio +project. The attribute will be generated only if this is set.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_variable.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_variable.html new file mode 100644 index 0000000000000000000000000000000000000000..38f853d9d5ae04ddbdb7953c320865999e560386 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_GLOBAL_variable.html @@ -0,0 +1,144 @@ + + + + + + + + + VS_GLOBAL_<variable> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_GLOBAL_<variable>

+

Visual Studio project-specific global variable.

+

Tell the Visual Studio generator to set the global variable +'<variable>' to a given value in the generated Visual Studio project. +Ignored on other generators. Qt integration works better if +VS_GLOBAL_QtVersion is set to the version FindQt4.cmake found. For +example, "4.7.3"

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_IOT_EXTENSIONS_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_IOT_EXTENSIONS_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..3f819ca9a2504377213e89cdd2aa3928f7da3760 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_IOT_EXTENSIONS_VERSION.html @@ -0,0 +1,147 @@ + + + + + + + + + VS_IOT_EXTENSIONS_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_IOT_EXTENSIONS_VERSION

+
+

New in version 3.4.

+
+

Visual Studio Windows 10 IoT Extensions Version

+

Specifies the version of the IoT Extensions that should be included in the +target. For example 10.0.10240.0. If the value is not specified, the IoT +Extensions will not be included. To use the same version of the extensions as +the Windows 10 SDK that is being used, you can use the +CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_IOT_STARTUP_TASK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_IOT_STARTUP_TASK.html new file mode 100644 index 0000000000000000000000000000000000000000..495a7aa0fa49c559697a82db090fa2210c53ce4a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_IOT_STARTUP_TASK.html @@ -0,0 +1,143 @@ + + + + + + + + + VS_IOT_STARTUP_TASK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_IOT_STARTUP_TASK

+
+

New in version 3.4.

+
+

Visual Studio Windows 10 IoT Continuous Background Task

+

Specifies that the target should be compiled as a Continuous Background Task library.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_JUST_MY_CODE_DEBUGGING.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_JUST_MY_CODE_DEBUGGING.html new file mode 100644 index 0000000000000000000000000000000000000000..da666d02dbb3955b6cb6454c5c0b937694a46846 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_JUST_MY_CODE_DEBUGGING.html @@ -0,0 +1,146 @@ + + + + + + + + + VS_JUST_MY_CODE_DEBUGGING — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_JUST_MY_CODE_DEBUGGING

+
+

New in version 3.15.

+
+

Enable Just My Code with Visual Studio debugger.

+

Supported on Visual Studio Generators for VS 2010 and higher, +Makefile Generators and the Ninja generators.

+

This property is initialized by the CMAKE_VS_JUST_MY_CODE_DEBUGGING +variable if it is set when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_KEYWORD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_KEYWORD.html new file mode 100644 index 0000000000000000000000000000000000000000..f48a23e61d0e73870368a46857c3eba1e0f3a0db --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_KEYWORD.html @@ -0,0 +1,143 @@ + + + + + + + + + VS_KEYWORD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_KEYWORD

+

Visual Studio project keyword for VS 9 (2008) and older.

+

Can be set to change the visual studio keyword, for example Qt +integration works better if this is set to Qt4VSv1.0.

+

Use the VS_GLOBAL_KEYWORD target property to set the +keyword for Visual Studio 11 (2012) and newer.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_MOBILE_EXTENSIONS_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_MOBILE_EXTENSIONS_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..a05138c94022f74d508e3477cff67e4a04bc62ff --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_MOBILE_EXTENSIONS_VERSION.html @@ -0,0 +1,147 @@ + + + + + + + + + VS_MOBILE_EXTENSIONS_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_MOBILE_EXTENSIONS_VERSION

+
+

New in version 3.4.

+
+

Visual Studio Windows 10 Mobile Extensions Version

+

Specifies the version of the Mobile Extensions that should be included in the +target. For example 10.0.10240.0. If the value is not specified, the Mobile +Extensions will not be included. To use the same version of the extensions as +the Windows 10 SDK that is being used, you can use the +CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_NO_COMPILE_BATCHING.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_NO_COMPILE_BATCHING.html new file mode 100644 index 0000000000000000000000000000000000000000..b14b9c49ef8f50b9f715c0ecbf89a723bbdb1494 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_NO_COMPILE_BATCHING.html @@ -0,0 +1,167 @@ + + + + + + + + + VS_NO_COMPILE_BATCHING — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_NO_COMPILE_BATCHING

+
+

New in version 3.24.

+
+

Turn off compile batching for the target. Usually MSBuild calls the compiler +with multiple c/cpp files and compiler starts subprocesses for each file to +make the build parallel. If you want compiler to be invoked with one file at +a time set VS_NO_COMPILE_BATCHING to ON. If this flag is set MSBuild will +call compiler with one c/cpp file at a time. Useful when you want to use tool +that replaces the compiler, for example some build caching tool.

+

This property is initialized by the CMAKE_VS_NO_COMPILE_BATCHING +variable if it is set when a target is created.

+
+

Example

+

This shows setting the property for the target foo.

+
add_library(foo SHARED foo.cpp)
+set_property(TARGET foo PROPERTY VS_NO_COMPILE_BATCHING ON)
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_NO_SOLUTION_DEPLOY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_NO_SOLUTION_DEPLOY.html new file mode 100644 index 0000000000000000000000000000000000000000..44d9e1df0365cdef61e6261047ad1a63728c053a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_NO_SOLUTION_DEPLOY.html @@ -0,0 +1,188 @@ + + + + + + + + + VS_NO_SOLUTION_DEPLOY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_NO_SOLUTION_DEPLOY

+
+

New in version 3.15.

+
+

Specify that the target should not be marked for deployment to a Windows CE +or Windows Phone device in the generated Visual Studio solution.

+

Be default, all EXE and shared library (DLL) targets are marked to deploy to +the target device in the generated Visual Studio solution.

+

Generator expressions are supported.

+

There are reasons one might want to exclude a target / generated project from +deployment:

+
    +
  • The library or executable may not be necessary in the primary deploy/debug +scenario, and excluding from deployment saves time in the +develop/download/debug cycle.

  • +
  • There may be insufficient space on the target device to accommodate all of +the build products.

  • +
  • Visual Studio 2013 requires a target device IP address be entered for each +target marked for deployment. For large numbers of targets, this can be +tedious. +NOTE: Visual Studio will deploy all project dependencies of a project +tagged for deployment to the IP address configured for that project even +if those dependencies are not tagged for deployment.

  • +
+
+

Example 1

+

This shows setting the variable for the target foo.

+
add_library(foo SHARED foo.cpp)
+set_property(TARGET foo PROPERTY VS_NO_SOLUTION_DEPLOY ON)
+
+
+
+
+

Example 2

+

This shows setting the variable for the Release configuration only.

+
add_library(foo SHARED foo.cpp)
+set_property(TARGET foo PROPERTY VS_NO_SOLUTION_DEPLOY "$<CONFIG:Release>")
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_PACKAGE_REFERENCES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_PACKAGE_REFERENCES.html new file mode 100644 index 0000000000000000000000000000000000000000..1c2617cdd11dd57318eadb2782ab9e3548b5a965 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_PACKAGE_REFERENCES.html @@ -0,0 +1,149 @@ + + + + + + + + + VS_PACKAGE_REFERENCES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_PACKAGE_REFERENCES

+
+

New in version 3.15.

+
+

Visual Studio package references for nuget.

+

Adds one or more semicolon-delimited package references to a generated +Visual Studio project. The version of the package will be +underscore delimited. For example, boost_1.7.0;nunit_3.12.*.

+
set_property(TARGET ${TARGET_NAME} PROPERTY
+  VS_PACKAGE_REFERENCES "boost_1.7.0")
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_PROJECT_IMPORT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_PROJECT_IMPORT.html new file mode 100644 index 0000000000000000000000000000000000000000..52457996d0fda7ba1f653908a27781fbc49a3f8f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_PROJECT_IMPORT.html @@ -0,0 +1,145 @@ + + + + + + + + + VS_PROJECT_IMPORT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_PROJECT_IMPORT

+
+

New in version 3.15.

+
+

Visual Studio managed project imports

+

Adds to a generated Visual Studio project one or more semicolon-delimited paths +to .props files needed when building projects from some NuGet packages. +For example, my_packages_path/MyPackage.1.0.0/build/MyPackage.props.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_AUXPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_AUXPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..90a10f8702e8a62411c47b894e652fa12af7811f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_AUXPATH.html @@ -0,0 +1,141 @@ + + + + + + + + + VS_SCC_AUXPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_SCC_AUXPATH

+

Visual Studio Source Code Control Aux Path.

+

Can be set to change the visual studio source code control auxpath +property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_LOCALPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_LOCALPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..4c8b84ccf805b85396de2ea7eeae94af71d6df37 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_LOCALPATH.html @@ -0,0 +1,141 @@ + + + + + + + + + VS_SCC_LOCALPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_SCC_LOCALPATH

+

Visual Studio Source Code Control Local Path.

+

Can be set to change the visual studio source code control local path +property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_PROJECTNAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_PROJECTNAME.html new file mode 100644 index 0000000000000000000000000000000000000000..6a1b2a8ebf523aab75defb17e55bcd45f3c7bcd3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_PROJECTNAME.html @@ -0,0 +1,141 @@ + + + + + + + + + VS_SCC_PROJECTNAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_SCC_PROJECTNAME

+

Visual Studio Source Code Control Project.

+

Can be set to change the visual studio source code control project +name property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_PROVIDER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_PROVIDER.html new file mode 100644 index 0000000000000000000000000000000000000000..aa20cdbd09b5c28e0abdf7fd5d232202f0644c27 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SCC_PROVIDER.html @@ -0,0 +1,141 @@ + + + + + + + + + VS_SCC_PROVIDER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_SCC_PROVIDER

+

Visual Studio Source Code Control Provider.

+

Can be set to change the visual studio source code control provider +property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SDK_REFERENCES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SDK_REFERENCES.html new file mode 100644 index 0000000000000000000000000000000000000000..49be0565fb1c4f2b1d3c15d0f2c00299ad634928 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SDK_REFERENCES.html @@ -0,0 +1,145 @@ + + + + + + + + + VS_SDK_REFERENCES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_SDK_REFERENCES

+
+

New in version 3.7.

+
+

Visual Studio project SDK references. +Specify a semicolon-separated list of SDK references +to be added to a generated Visual Studio project, e.g. +Microsoft.AdMediatorWindows81, Version=1.0.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SOLUTION_DEPLOY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SOLUTION_DEPLOY.html new file mode 100644 index 0000000000000000000000000000000000000000..68706e1fde6b7b1219d69d69c7460191c1111493 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SOLUTION_DEPLOY.html @@ -0,0 +1,169 @@ + + + + + + + + + VS_SOLUTION_DEPLOY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_SOLUTION_DEPLOY

+
+

New in version 3.18.

+
+

Specify that the target should be marked for deployment when not targeting +Windows CE, Windows Phone or a Windows Store application.

+

If the target platform doesn't support deployment, this property won't have +any effect.

+

Generator expressions are supported.

+
+

Examples

+

Always deploy target foo:

+
add_executable(foo SHARED foo.cpp)
+set_property(TARGET foo PROPERTY VS_SOLUTION_DEPLOY ON)
+
+
+

Deploy target foo for all configurations except Release:

+
add_executable(foo SHARED foo.cpp)
+set_property(TARGET foo PROPERTY VS_SOLUTION_DEPLOY "$<NOT:$<CONFIG:Release>>")
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SOURCE_SETTINGS_tool.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SOURCE_SETTINGS_tool.html new file mode 100644 index 0000000000000000000000000000000000000000..d4247b033d419cbf4967dcf7afb6bdfd71cfa87c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_SOURCE_SETTINGS_tool.html @@ -0,0 +1,152 @@ + + + + + + + + + VS_SOURCE_SETTINGS_<tool> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_SOURCE_SETTINGS_<tool>

+
+

New in version 3.18.

+
+

Set any item metadata on all non-built files that use <tool>.

+

Takes a list of Key=Value pairs. Tells the Visual Studio generator +to set Key to Value as item metadata on all non-built files +that use <tool>.

+

For example:

+
set_property(TARGET main PROPERTY VS_SOURCE_SETTINGS_FXCompile "Key=Value" "Key2=Value2")
+
+
+

will set Key to Value and Key2 to Value2 for all +non-built files that use FXCompile.

+

Generator expressions are supported.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_USER_PROPS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_USER_PROPS.html new file mode 100644 index 0000000000000000000000000000000000000000..0d5fb6de6d987b2c2436f91545ff2685d62a4c2d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_USER_PROPS.html @@ -0,0 +1,149 @@ + + + + + + + + + VS_USER_PROPS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_USER_PROPS

+
+

New in version 3.8.

+
+

Sets the user props file to be included in the visual studio +C++ project file. The standard path is +$(UserRootDir)\\Microsoft.Cpp.$(Platform).user.props, which is +in most cases the same as +%LOCALAPPDATA%\\Microsoft\\MSBuild\\v4.0\\Microsoft.Cpp.Win32.user.props +or %LOCALAPPDATA%\\Microsoft\\MSBuild\\v4.0\\Microsoft.Cpp.x64.user.props.

+

The *.user.props files can be used for Visual Studio wide +configuration which is independent from cmake.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..d712772db3d1f3e09495617f0351d5fb0d3eb789 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.html @@ -0,0 +1,152 @@ + + + + + + + + + VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION

+
+

New in version 3.4.

+
+

Visual Studio Windows Target Platform Minimum Version

+

For Windows 10. Specifies the minimum version of the OS that is being +targeted. For example 10.0.10240.0. If the value is not specified, the +value of the CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION variable +will be used on WindowsStore projects. Otherwise the target platform +minimum version will not be specified for the project.

+
+

New in version 3.27: This property is initialized by the value of the +CMAKE_VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION variable +if it is set when a target is created.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINRT_COMPONENT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINRT_COMPONENT.html new file mode 100644 index 0000000000000000000000000000000000000000..81b58d6ec8170c16dd1296f803f567a48ee0dcec --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINRT_COMPONENT.html @@ -0,0 +1,150 @@ + + + + + + + + + VS_WINRT_COMPONENT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_WINRT_COMPONENT

+
+

New in version 3.1.

+
+

Mark a target as a Windows Runtime component for the Visual Studio generator. +Compile the target with C++/CX language extensions for Windows Runtime. +For SHARED and MODULE libraries, this also defines the +_WINRT_DLL preprocessor macro.

+
+

Note

+

Currently this is implemented only by Visual Studio generators. +Support may be added to other generators in the future.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINRT_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINRT_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..080ce938faae107cf5e0871450fa27a9eb115767 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINRT_EXTENSIONS.html @@ -0,0 +1,140 @@ + + + + + + + + + VS_WINRT_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_WINRT_EXTENSIONS

+

Deprecated. Use VS_WINRT_COMPONENT instead. +This property was an experimental partial implementation of that one.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINRT_REFERENCES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINRT_REFERENCES.html new file mode 100644 index 0000000000000000000000000000000000000000..3c10a12ab39dca047f54311fa33715676604591d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/VS_WINRT_REFERENCES.html @@ -0,0 +1,141 @@ + + + + + + + + + VS_WINRT_REFERENCES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

VS_WINRT_REFERENCES

+

Visual Studio project Windows Runtime Metadata references

+

Adds one or more semicolon-delimited WinRT references to a generated +Visual Studio project. For example, "Windows;Windows.UI.Core".

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/WATCOM_RUNTIME_LIBRARY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/WATCOM_RUNTIME_LIBRARY.html new file mode 100644 index 0000000000000000000000000000000000000000..d0972ceabdd2eeaf8c0483e286d99de3e66cd338 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/WATCOM_RUNTIME_LIBRARY.html @@ -0,0 +1,182 @@ + + + + + + + + + WATCOM_RUNTIME_LIBRARY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

WATCOM_RUNTIME_LIBRARY

+
+

New in version 3.24.

+
+

Select the Watcom runtime library for use by compilers targeting the Watcom ABI.

+

The allowed values are:

+
+
SingleThreaded

Compile without additional flags to use a single-threaded +statically-linked runtime library.

+
+
SingleThreadedDLL

Compile with -br or equivalent flag(s) to use a single-threaded +dynamically-linked runtime library. This is not available for Linux +targets.

+
+
MultiThreaded

Compile with -bm or equivalent flag(s) to use a multi-threaded +statically-linked runtime library.

+
+
MultiThreadedDLL

Compile with -bm -br or equivalent flag(s) to use a multi-threaded +dynamically-linked runtime library. This is not available for Linux +targets.

+
+
+

The value is ignored on non-Watcom compilers but an unsupported value will +be rejected as an error when using a compiler targeting the Watcom ABI.

+

The value may also be the empty string ("") in which case no runtime +library selection flag will be added explicitly by CMake.

+

Use generator expressions to +support per-configuration specification.

+

For example, the code:

+
add_executable(foo foo.c)
+set_property(TARGET foo PROPERTY
+  WATCOM_RUNTIME_LIBRARY "MultiThreaded")
+
+
+

selects for the target foo a multi-threaded statically-linked runtime +library.

+

If this property is not set then CMake uses the default value +MultiThreadedDLL on Windows and SingleThreaded on other +platforms to select a Watcom runtime library.

+
+

Note

+

This property has effect only when policy CMP0136 is set to NEW +prior to the first project() or enable_language() command +that enables a language using a compiler targeting the Watcom ABI.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/WIN32_EXECUTABLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/WIN32_EXECUTABLE.html new file mode 100644 index 0000000000000000000000000000000000000000..e16b1b93ba420d7b46d25e64ca2f1e4b6591731d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/WIN32_EXECUTABLE.html @@ -0,0 +1,150 @@ + + + + + + + + + WIN32_EXECUTABLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

WIN32_EXECUTABLE

+

Build an executable with a WinMain entry point on windows.

+

When this property is set to true the executable when linked on +Windows will be created with a WinMain() entry point instead of just +main(). This makes it a GUI executable instead of a console application. +See the CMAKE_MFC_FLAG variable documentation to +configure use of the Microsoft Foundation Classes (MFC) for WinMain +executables. This property is initialized by the value of the +CMAKE_WIN32_EXECUTABLE variable if it is set when +a target is created.

+

This property supports +generator expressions, except if the +target is managed (contains C# code.)

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/WINDOWS_EXPORT_ALL_SYMBOLS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/WINDOWS_EXPORT_ALL_SYMBOLS.html new file mode 100644 index 0000000000000000000000000000000000000000..307799cc431ba0ca97e460eae7769f182fc598bd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/WINDOWS_EXPORT_ALL_SYMBOLS.html @@ -0,0 +1,161 @@ + + + + + + + + + WINDOWS_EXPORT_ALL_SYMBOLS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

WINDOWS_EXPORT_ALL_SYMBOLS

+
+

New in version 3.4.

+
+

This property is implemented only for MS-compatible tools on Windows.

+

Enable this boolean property to automatically create a module definition +(.def) file with all global symbols found in the input .obj files +for a SHARED library (or executable with ENABLE_EXPORTS) +on Windows. The module definition file will be passed to the linker +causing all symbols to be exported from the .dll. +For global data symbols, __declspec(dllimport) must still be used when +compiling against the code in the .dll. All other function symbols will +be automatically exported and imported by callers. This simplifies porting +projects to Windows by reducing the need for explicit dllexport markup, +even in C++ classes.

+

When this property is enabled, zero or more .def files may also be +specified as source files of the target. The exports named by these files +will be merged with those detected from the object files to generate a +single module definition file to be passed to the linker. This can be +used to export symbols from a .dll that are not in any of its object +files but are added by the linker from dependencies (e.g. msvcrt.lib).

+

This property is initialized by the value of +the CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS variable if it is set +when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_ATTRIBUTE_an-attribute.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_ATTRIBUTE_an-attribute.html new file mode 100644 index 0000000000000000000000000000000000000000..c7fbf21d4be31f93208fd9ef9477625fa6544f19 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_ATTRIBUTE_an-attribute.html @@ -0,0 +1,153 @@ + + + + + + + + + XCODE_ATTRIBUTE_<an-attribute> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_ATTRIBUTE_<an-attribute>

+

Set Xcode target attributes directly.

+

Tell the Xcode generator to set <an-attribute> to a given +value in the generated Xcode project. Ignored on other generators.

+

This offers low-level control over the generated Xcode project file. +It is meant as a last resort for specifying settings that CMake does +not otherwise have a way to control. Although this can override a +setting CMake normally produces on its own, doing so bypasses CMake's +model of the project and can break things.

+

See the CMAKE_XCODE_ATTRIBUTE_<an-attribute> variable +to set attributes on all targets in a directory tree.

+

Contents of XCODE_ATTRIBUTE_<an-attribute> may use +"generator expressions" with the syntax $<...>. See the +cmake-generator-expressions(7) manual for available +expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_FRAMEWORKS_CODE_SIGN_ON_COPY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_FRAMEWORKS_CODE_SIGN_ON_COPY.html new file mode 100644 index 0000000000000000000000000000000000000000..182acf0ba9abd10d5c92f8f0a9938e3cab0a6747 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_FRAMEWORKS_CODE_SIGN_ON_COPY.html @@ -0,0 +1,149 @@ + + + + + + + + + XCODE_EMBED_FRAMEWORKS_CODE_SIGN_ON_COPY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_EMBED_FRAMEWORKS_CODE_SIGN_ON_COPY

+
+

New in version 3.20.

+
+

Tell the Xcode generator to perform code signing for all the +frameworks and libraries that are embedded using the +XCODE_EMBED_FRAMEWORKS property.

+
+

New in version 3.21.

+
+

This property was generalized to other types of embedded items. See +XCODE_EMBED_<type>_CODE_SIGN_ON_COPY for the more general form.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_FRAMEWORKS_REMOVE_HEADERS_ON_COPY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_FRAMEWORKS_REMOVE_HEADERS_ON_COPY.html new file mode 100644 index 0000000000000000000000000000000000000000..803b2f5d41d11e9a432226f4e7529d6961f9297c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_FRAMEWORKS_REMOVE_HEADERS_ON_COPY.html @@ -0,0 +1,150 @@ + + + + + + + + + XCODE_EMBED_FRAMEWORKS_REMOVE_HEADERS_ON_COPY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_EMBED_FRAMEWORKS_REMOVE_HEADERS_ON_COPY

+
+

New in version 3.20.

+
+

Tell the Xcode generator to remove headers from all the +frameworks that are embedded using the +XCODE_EMBED_FRAMEWORKS property.

+
+

New in version 3.21.

+
+

This property was generalized to other types of embedded items. See +XCODE_EMBED_<type>_REMOVE_HEADERS_ON_COPY for the more +general form.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type.html new file mode 100644 index 0000000000000000000000000000000000000000..fb854b47fc655bbf7f81930d86392617cbfd1efb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type.html @@ -0,0 +1,177 @@ + + + + + + + + + XCODE_EMBED_<type> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_EMBED_<type>

+
+

New in version 3.20.

+
+

Tell the Xcode generator to embed the specified list of items into +the target bundle. <type> specifies the embed build phase to use. +See the Xcode documentation for the base location of each <type>.

+

The supported values for <type> are:

+
+
FRAMEWORKS

The specified items will be added to the Embed Frameworks build phase. +The items can be CMake target names or paths to frameworks or libraries.

+
+
APP_EXTENSIONS
+

New in version 3.21.

+
+

The specified items will be added to the Embed App Extensions build +phase, with Destination set to PlugIns and Foundation Extensions +They must be CMake target names.

+
+
EXTENSIONKIT_EXTENSIONS
+

New in version 3.26.

+
+

The specified items will be added to the Embed App Extensions build +phase, with Destination set to ExtensionKit Extensions +They must be CMake target names, and should likely have the +XCODE_PRODUCT_TYPE target property set to +com.apple.product-type.extensionkit-extension +as well as the XCODE_EXPLICIT_FILE_TYPE to +wrapper.extensionkit-extension

+
+
PLUGINS
+

New in version 3.23.

+
+

The specified items will be added to the Embed PlugIns build phase. +They must be CMake target names.

+
+
+

See also XCODE_EMBED_<type>_PATH, +XCODE_EMBED_<type>_REMOVE_HEADERS_ON_COPY and +XCODE_EMBED_<type>_CODE_SIGN_ON_COPY.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type_CODE_SIGN_ON_COPY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type_CODE_SIGN_ON_COPY.html new file mode 100644 index 0000000000000000000000000000000000000000..b0af6d78c59e5591bb186403995ca1c608bf3683 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type_CODE_SIGN_ON_COPY.html @@ -0,0 +1,162 @@ + + + + + + + + + XCODE_EMBED_<type>_CODE_SIGN_ON_COPY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_EMBED_<type>_CODE_SIGN_ON_COPY

+
+

New in version 3.20.

+
+

Boolean property used only by the Xcode generator. It specifies +whether to perform code signing for the items that are embedded using the +XCODE_EMBED_<type> property.

+

The supported values for <type> are:

+

FRAMEWORKS

+
+
APP_EXTENSIONS
+

New in version 3.21.

+
+
+
EXTENSIONKIT_EXTENSIONS
+

New in version 3.26.

+
+
+
PLUGINS
+

New in version 3.23.

+
+
+
+

If a XCODE_EMBED_<type>_CODE_SIGN_ON_COPY property is not defined on the +target, no code signing on copy will be performed for that <type>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..213ac54155265579e4d16f8767534119ed14826c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type_PATH.html @@ -0,0 +1,163 @@ + + + + + + + + + XCODE_EMBED_<type>_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_EMBED_<type>_PATH

+
+

New in version 3.20.

+
+

This property is used only by the Xcode generator. When defined, +it specifies the relative path to use when embedding the items specified by +XCODE_EMBED_<type>. The path is relative +to the base location of the Embed XXX build phase associated with +<type>. See the Xcode documentation for the base location of each +<type>.

+

The supported values for <type> are:

+

FRAMEWORKS

+
+
APP_EXTENSIONS
+

New in version 3.21.

+
+
+
EXTENSIONKIT_EXTENSIONS
+

New in version 3.26.

+
+
+
PLUGINS
+

New in version 3.23.

+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type_REMOVE_HEADERS_ON_COPY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type_REMOVE_HEADERS_ON_COPY.html new file mode 100644 index 0000000000000000000000000000000000000000..b070261858042b8ee3b3f878547c540fe3b0c7f6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_EMBED_type_REMOVE_HEADERS_ON_COPY.html @@ -0,0 +1,166 @@ + + + + + + + + + XCODE_EMBED_<type>_REMOVE_HEADERS_ON_COPY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_EMBED_<type>_REMOVE_HEADERS_ON_COPY

+
+

New in version 3.20.

+
+

Boolean property used only by the Xcode generator. It specifies +whether to remove headers from all the frameworks that are embedded using the +XCODE_EMBED_<type> property.

+

The supported values for <type> are:

+
+
FRAMEWORKS

If the XCODE_EMBED_FRAMEWORKS_REMOVE_HEADERS_ON_COPY property is not +defined, headers will not be removed on copy by default.

+
+
APP_EXTENSIONS
+

New in version 3.21.

+
+

If the XCODE_EMBED_APP_EXTENSIONS_REMOVE_HEADERS_ON_COPY property is not +defined, headers WILL be removed on copy by default.

+
+
EXTENSIONKIT_EXTENSIONS
+

New in version 3.26.

+
+

If the XCODE_EMBED_APP_EXTENSIONS_REMOVE_HEADERS_ON_COPY property is not +defined, headers WILL be removed on copy by default.

+
+
PLUGINS
+

New in version 3.23.

+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_LINK_BUILD_PHASE_MODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_LINK_BUILD_PHASE_MODE.html new file mode 100644 index 0000000000000000000000000000000000000000..7930fcafcd4a9f187e94c85c672368f51fd73ef4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_LINK_BUILD_PHASE_MODE.html @@ -0,0 +1,192 @@ + + + + + + + + + XCODE_LINK_BUILD_PHASE_MODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_PRODUCT_TYPE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_PRODUCT_TYPE.html new file mode 100644 index 0000000000000000000000000000000000000000..24c9aa9014595377d1745e3d87a25a1b01dc9282 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_PRODUCT_TYPE.html @@ -0,0 +1,145 @@ + + + + + + + + + XCODE_PRODUCT_TYPE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_PRODUCT_TYPE

+
+

New in version 3.8.

+
+

Set the Xcode productType attribute on its reference to a +target. CMake computes a default based on target type but +can be told explicitly with this property.

+

See also XCODE_EXPLICIT_FILE_TYPE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER.html new file mode 100644 index 0000000000000000000000000000000000000000..b5d65c4b00f415c1beebdbedaf1ad47ff1eaf0db --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ADDRESS_SANITIZER.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_ADDRESS_SANITIZER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_ADDRESS_SANITIZER

+
+

New in version 3.13.

+
+

Whether to enable Address Sanitizer in the Diagnostics +section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ARGUMENTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ARGUMENTS.html new file mode 100644 index 0000000000000000000000000000000000000000..8ac587123bc17fa856d7864aa6e75775cf34ddd9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ARGUMENTS.html @@ -0,0 +1,146 @@ + + + + + + + + + XCODE_SCHEME_ARGUMENTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_ARGUMENTS

+
+

New in version 3.13.

+
+

Specify command line arguments that should be added to the Arguments +section of the generated Xcode scheme.

+

If set to a list of arguments those will be added to the scheme.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DEBUG_AS_ROOT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DEBUG_AS_ROOT.html new file mode 100644 index 0000000000000000000000000000000000000000..a322c81d1517670fd0cbaa44467cd2f9cd6bab04 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DEBUG_AS_ROOT.html @@ -0,0 +1,144 @@ + + + + + + + + + XCODE_SCHEME_DEBUG_AS_ROOT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_DEBUG_AS_ROOT

+
+

New in version 3.15.

+
+

Whether to debug the target as 'root'.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.html new file mode 100644 index 0000000000000000000000000000000000000000..fe3366b06d4e134f1a9f35608e5e94b56320a954 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER

+
+

New in version 3.13.

+
+

Whether to disable the Main Thread Checker +in the Diagnostics section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER +if it is set when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.html new file mode 100644 index 0000000000000000000000000000000000000000..2b37e069190d56e013d6b38acb51c4b8938eb84c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS

+
+

New in version 3.13.

+
+

Whether to enable Dynamic Library Loads +in the Diagnostics section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.html new file mode 100644 index 0000000000000000000000000000000000000000..675a927703154edebf7e96f29712613f42e2efbf --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE

+
+

New in version 3.13.

+
+

Whether to enable Dynamic Linker API usage +in the Diagnostics section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ENABLE_GPU_API_VALIDATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ENABLE_GPU_API_VALIDATION.html new file mode 100644 index 0000000000000000000000000000000000000000..25ec29898c7bc3b478c65e35c366fa8dd028e63d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ENABLE_GPU_API_VALIDATION.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_ENABLE_GPU_API_VALIDATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_ENABLE_GPU_API_VALIDATION

+
+

New in version 3.25.

+
+

Property value for Metal: API Validation in the Options section of +the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_ENABLE_GPU_API_VALIDATION +if it is set when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ENABLE_GPU_SHADER_VALIDATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ENABLE_GPU_SHADER_VALIDATION.html new file mode 100644 index 0000000000000000000000000000000000000000..dfca6b4d73d5beb192c26fe57db53fe6562d47f3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ENABLE_GPU_SHADER_VALIDATION.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_ENABLE_GPU_SHADER_VALIDATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_ENABLE_GPU_SHADER_VALIDATION

+
+

New in version 3.25.

+
+

Property value for Metal: Shader Validation in the Options section of +the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_ENABLE_GPU_SHADER_VALIDATION +if it is set when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ENVIRONMENT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ENVIRONMENT.html new file mode 100644 index 0000000000000000000000000000000000000000..f6e9d748e99f865057b35cd6465359c293b19fa4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ENVIRONMENT.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_ENVIRONMENT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_ENVIRONMENT

+
+

New in version 3.13.

+
+

Specify environment variables that should be added to the Arguments +section of the generated Xcode scheme.

+

If set to a list of environment variables and values of the form +MYVAR=value those environment variables will be added to the +scheme.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_EXECUTABLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_EXECUTABLE.html new file mode 100644 index 0000000000000000000000000000000000000000..b9989b8402aad41684fb827c30d70ad448b547e9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_EXECUTABLE.html @@ -0,0 +1,146 @@ + + + + + + + + + XCODE_SCHEME_EXECUTABLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_EXECUTABLE

+
+

New in version 3.13.

+
+

Specify path to executable in the Info section of the generated +Xcode scheme. If not set the schema generator will select the +current target if it is actually executable.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_LAUNCH_CONFIGURATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_LAUNCH_CONFIGURATION.html new file mode 100644 index 0000000000000000000000000000000000000000..4606e32e594840da1b45b68935aa6f9942e6e473 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_LAUNCH_CONFIGURATION.html @@ -0,0 +1,147 @@ + + + + + + + + + XCODE_SCHEME_LAUNCH_CONFIGURATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_LAUNCH_CONFIGURATION

+
+

New in version 3.25.

+
+

Set the build configuration to run the target.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_LAUNCH_CONFIGURATION +if it is set when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_LAUNCH_MODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_LAUNCH_MODE.html new file mode 100644 index 0000000000000000000000000000000000000000..dc603edb01a7e99935ce8ac5508e752cf80c9d45 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_LAUNCH_MODE.html @@ -0,0 +1,155 @@ + + + + + + + + + XCODE_SCHEME_LAUNCH_MODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_LAUNCH_MODE

+
+

New in version 3.25.

+
+

Property value for Launch in the Info section of the generated Xcode +scheme.

+

Possible values are:

+
+
AUTO

Launch automatically. This is the default.

+
+
WAIT

Wait for the executable to be launched.

+
+
+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_LAUNCH_MODE if it is set when a target is +created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.html new file mode 100644 index 0000000000000000000000000000000000000000..eea6f32bae80a961a7b7657f7ea09f704fb24b0a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.html @@ -0,0 +1,149 @@ + + + + + + + + + XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP

+
+

New in version 3.13.

+
+

Whether to enable the Main Thread Checker option +Pause on issues +in the Diagnostics section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MALLOC_GUARD_EDGES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MALLOC_GUARD_EDGES.html new file mode 100644 index 0000000000000000000000000000000000000000..f379245ac2fec4a9022b8227c8e33f9c524a0875 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MALLOC_GUARD_EDGES.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_MALLOC_GUARD_EDGES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_MALLOC_GUARD_EDGES

+
+

New in version 3.13.

+
+

Whether to enable Malloc Guard Edges +in the Diagnostics section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_MALLOC_GUARD_EDGES if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MALLOC_SCRIBBLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MALLOC_SCRIBBLE.html new file mode 100644 index 0000000000000000000000000000000000000000..4cc60a037e6e0867b8590bdebaba901ce09bb276 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MALLOC_SCRIBBLE.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_MALLOC_SCRIBBLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_MALLOC_SCRIBBLE

+
+

New in version 3.13.

+
+

Whether to enable Malloc Scribble +in the Diagnostics section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MALLOC_STACK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MALLOC_STACK.html new file mode 100644 index 0000000000000000000000000000000000000000..302e18d3445f6252f895739ddd9d365e40af31d1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_MALLOC_STACK.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_MALLOC_STACK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_MALLOC_STACK

+
+

New in version 3.13.

+
+

Whether to enable Malloc Stack in the Diagnostics +section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_MALLOC_STACK if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER.html new file mode 100644 index 0000000000000000000000000000000000000000..af73f7984eda30492768f76d2214d1ced0f9960b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_THREAD_SANITIZER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_THREAD_SANITIZER

+
+

New in version 3.13.

+
+

Whether to enable Thread Sanitizer in the Diagnostics +section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_THREAD_SANITIZER if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER_STOP.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER_STOP.html new file mode 100644 index 0000000000000000000000000000000000000000..7e388056f84fd7befd36dd1add2fbabb648d638b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_THREAD_SANITIZER_STOP.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_THREAD_SANITIZER_STOP — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_THREAD_SANITIZER_STOP

+
+

New in version 3.13.

+
+

Whether to enable Thread Sanitizer - Pause on issues +in the Diagnostics section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_THREAD_SANITIZER_STOP if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER.html new file mode 100644 index 0000000000000000000000000000000000000000..cdf1e0cae9f6f96e7d8daec6624f2c8b88f108c9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER

+
+

New in version 3.13.

+
+

Whether to enable Undefined Behavior Sanitizer +in the Diagnostics section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER +if it is set when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.html new file mode 100644 index 0000000000000000000000000000000000000000..41a4db347bb2ee8b2a4590a3c5e66410f78e263b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.html @@ -0,0 +1,149 @@ + + + + + + + + + XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP

+
+

New in version 3.13.

+
+

Whether to enable Undefined Behavior Sanitizer option +Pause on issues +in the Diagnostics section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP +if it is set when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_WORKING_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_WORKING_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..c62c554ba4e2ea7d3f39a7ca72352ae0384c0c15 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_WORKING_DIRECTORY.html @@ -0,0 +1,149 @@ + + + + + + + + + XCODE_SCHEME_WORKING_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_WORKING_DIRECTORY

+
+

New in version 3.17.

+
+

Specify the Working Directory of the Run and Profile +actions in the generated Xcode scheme. In case the value contains +generator expressions those are evaluated.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_WORKING_DIRECTORY if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ZOMBIE_OBJECTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ZOMBIE_OBJECTS.html new file mode 100644 index 0000000000000000000000000000000000000000..afa438442bf8c8eed6dc6a6e501beaf3dd0857e0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_SCHEME_ZOMBIE_OBJECTS.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_SCHEME_ZOMBIE_OBJECTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_SCHEME_ZOMBIE_OBJECTS

+
+

New in version 3.13.

+
+

Whether to enable Zombie Objects +in the Diagnostics section of the generated Xcode scheme.

+

This property is initialized by the value of the variable +CMAKE_XCODE_SCHEME_ZOMBIE_OBJECTS if it is set +when a target is created.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_XCCONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_XCCONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..2c5237cf647a1098b868570ece28d98ff93f8b4e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCODE_XCCONFIG.html @@ -0,0 +1,148 @@ + + + + + + + + + XCODE_XCCONFIG — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_XCCONFIG

+
+

New in version 3.24.

+
+

If set, the Xcode generator will register the specified +file as a target-level XCConfig file. For global XCConfig files see +the CMAKE_XCODE_XCCONFIG variable.

+

This feature is intended to ease migration from native Xcode projects +to CMake projects.

+

Contents of XCODE_XCCONFIG may use +generator expressions.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCTEST.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCTEST.html new file mode 100644 index 0000000000000000000000000000000000000000..cd519d0b783ee78600af0e1cfe5b2018a611739a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/prop_tgt/XCTEST.html @@ -0,0 +1,148 @@ + + + + + + + + + XCTEST — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCTEST

+
+

New in version 3.3.

+
+

This target is a XCTest CFBundle on the Mac.

+

This property will usually get set via the xctest_add_bundle() +macro in FindXCTest module.

+

If a module library target has this property set to true it will be +built as a CFBundle when built on the Mac. It will have the directory +structure required for a CFBundle.

+

This property depends on BUNDLE to be effective.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/ANDROID.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/ANDROID.html new file mode 100644 index 0000000000000000000000000000000000000000..a3e38956ce0946542f321f0a7b2d7ac5d179887f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/ANDROID.html @@ -0,0 +1,143 @@ + + + + + + + + + ANDROID — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ANDROID

+
+

New in version 3.7.

+
+

Set to 1 when the target system (CMAKE_SYSTEM_NAME) is +Android.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/BORLAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/BORLAND.html new file mode 100644 index 0000000000000000000000000000000000000000..b43db8e06b7346aec12c110dfb63eac58bd49f07 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/BORLAND.html @@ -0,0 +1,140 @@ + + + + + + + + + BORLAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

BORLAND

+

True if the Borland compiler is being used.

+

This is set to true if the Borland compiler is being used.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/BSD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/BSD.html new file mode 100644 index 0000000000000000000000000000000000000000..f8c29b2de375b3c11a370dd3ed1a1cdb0aa242aa --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/BSD.html @@ -0,0 +1,143 @@ + + + + + + + + + BSD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

BSD

+
+

New in version 3.25.

+
+

Set to a string value when the target system is BSD. This value can be one of +the following: DragonFlyBSD, FreeBSD, OpenBSD, or NetBSD.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/BUILD_SHARED_LIBS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/BUILD_SHARED_LIBS.html new file mode 100644 index 0000000000000000000000000000000000000000..0f748832e99423497de944b81ffc222e938a4a0b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/BUILD_SHARED_LIBS.html @@ -0,0 +1,144 @@ + + + + + + + + + BUILD_SHARED_LIBS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

BUILD_SHARED_LIBS

+

Global flag to cause add_library() to create shared libraries if on.

+

If present and true, this will cause all libraries to be built shared +unless the library was explicitly added as a static library. This +variable is often added to projects as an option() so that each user +of a project can decide if they want to build the project using shared or +static libraries.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CACHE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CACHE.html new file mode 100644 index 0000000000000000000000000000000000000000..7644edeb6197350d84af6d1ca95328dd267d4e4c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CACHE.html @@ -0,0 +1,153 @@ + + + + + + + + + CACHE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CACHE

+
+

New in version 3.13.

+
+

Operator to read cache variables.

+

Use the syntax $CACHE{VAR} to read cache entry VAR. +See the cmake-language(7) variables +documentation for more complete documentation of the interaction of +normal variables and cache entries.

+

When evaluating Variable References of the form ${VAR}, +CMake first searches for a normal variable with that name, and if not +found CMake will search for a cache entry with that name. +The $CACHE{VAR} syntax can be used to do direct cache lookup and +ignore any existing normal variable.

+

See the set() and unset() commands to see how to +write or remove cache variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ABSOLUTE_DESTINATION_FILES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ABSOLUTE_DESTINATION_FILES.html new file mode 100644 index 0000000000000000000000000000000000000000..a56865ca0aa6b1d19e7e17e23ce9f488ec9fc785 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ABSOLUTE_DESTINATION_FILES.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ABSOLUTE_DESTINATION_FILES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ABSOLUTE_DESTINATION_FILES

+

List of files which have been installed using an ABSOLUTE DESTINATION path.

+

This variable is defined by CMake-generated cmake_install.cmake +scripts. It can be used (read-only) by programs or scripts that +source those install scripts. This is used by some CPack generators +(e.g. RPM).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ADD_CUSTOM_COMMAND_DEPENDS_EXPLICIT_ONLY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ADD_CUSTOM_COMMAND_DEPENDS_EXPLICIT_ONLY.html new file mode 100644 index 0000000000000000000000000000000000000000..a01b6b6080e6c233d14ef9cacc7c57a0d2acd98f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ADD_CUSTOM_COMMAND_DEPENDS_EXPLICIT_ONLY.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_ADD_CUSTOM_COMMAND_DEPENDS_EXPLICIT_ONLY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ADD_CUSTOM_COMMAND_DEPENDS_EXPLICIT_ONLY

+
+

New in version 3.27.

+
+

Whether to enable the DEPENDS_EXPLICIT_ONLY option by default in +add_custom_command().

+

This variable affects the default behavior of the add_custom_command() +command. Setting this variable to ON is equivalent to using the +DEPENDS_EXPLICIT_ONLY option in all uses of that command.

+

See also CMAKE_OPTIMIZE_DEPENDENCIES.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ADSP_ROOT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ADSP_ROOT.html new file mode 100644 index 0000000000000000000000000000000000000000..c122d3f72dec2dda9c753fbd2853dd0ff5aa2f22 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ADSP_ROOT.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_ADSP_ROOT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ADSP_ROOT

+
+

New in version 3.24.

+
+

When Cross Compiling for ADSP SHARC/Blackfin, +this variable holds the absolute path to the latest CCES or VDSP++ install. +The directory is expected to contain the cc21k.exe and ccblkfn.exe compilers. +This will be set automatically if a default install of CCES or VDSP++ can be found.

+

See also the ADSP_ROOT environment variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AIX_EXPORT_ALL_SYMBOLS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AIX_EXPORT_ALL_SYMBOLS.html new file mode 100644 index 0000000000000000000000000000000000000000..1a87b9ec4fa399697424c0d98ea8b030b5f82c00 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AIX_EXPORT_ALL_SYMBOLS.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_AIX_EXPORT_ALL_SYMBOLS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AIX_EXPORT_ALL_SYMBOLS

+
+

New in version 3.17.

+
+

Default value for AIX_EXPORT_ALL_SYMBOLS target property. +This variable is used to initialize the property on each target as it is +created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..930fe6b2022646783a05f8d20d032d04e63869de --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS

+
+

New in version 3.4.

+
+

Default value for the ANDROID_ANT_ADDITIONAL_OPTIONS target property. +See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_API.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_API.html new file mode 100644 index 0000000000000000000000000000000000000000..968556e903e6d6ed2e38a1f64904603caa1f9c1d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_API.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_ANDROID_API — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_API

+
+

New in version 3.1.

+
+

When Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition, this variable may be set to specify the default value for the +ANDROID_API target property. See that target property for +additional information.

+

When Cross Compiling for Android, the CMAKE_SYSTEM_VERSION +variable represents the Android API version number targeted. For historical +reasons, if a toolchain file sets CMAKE_ANDROID_API, but not +CMAKE_SYSTEM_VERSION, the latter will be initialized using the former.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_API_MIN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_API_MIN.html new file mode 100644 index 0000000000000000000000000000000000000000..ad967c910e024f9f86b1c4179abed257987c850c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_API_MIN.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ANDROID_API_MIN — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_API_MIN

+
+

New in version 3.2.

+
+

Default value for the ANDROID_API_MIN target property. +See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_ARCH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_ARCH.html new file mode 100644 index 0000000000000000000000000000000000000000..05f4794b5a2e76ea5ae5b3853deb5aa417cb76d8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_ARCH.html @@ -0,0 +1,156 @@ + + + + + + + + + CMAKE_ANDROID_ARCH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_ARCH

+
+

New in version 3.4.

+
+

When Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition, this variable may be set to specify the default value for the +ANDROID_ARCH target property. See that target property for +additional information.

+

Otherwise, when Cross Compiling for Android, this variable provides +the name of the Android architecture corresponding to the value of the +CMAKE_ANDROID_ARCH_ABI variable. The architecture name +may be one of:

+
    +
  • arm

  • +
  • arm64

  • +
  • mips

  • +
  • mips64

  • +
  • x86

  • +
  • x86_64

  • +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_ARM_MODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_ARM_MODE.html new file mode 100644 index 0000000000000000000000000000000000000000..c1fa1259f03d1bd7f17031f6d235f14db8ca061a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_ARM_MODE.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_ANDROID_ARM_MODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_ARM_MODE

+
+

New in version 3.7.

+
+

When Cross Compiling for Android and CMAKE_ANDROID_ARCH_ABI +is set to one of the armeabi architectures, set CMAKE_ANDROID_ARM_MODE +to ON to target 32-bit ARM processors (-marm). Otherwise, the +default is to target the 16-bit Thumb processors (-mthumb).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_EXCEPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_EXCEPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..5db7c34749476f98fe43f52e96bb405a67b7cda0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_EXCEPTIONS.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ANDROID_EXCEPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_EXCEPTIONS

+
+

New in version 3.20.

+
+

When Cross Compiling for Android with the NDK, this variable may be set +to specify whether exceptions are enabled.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_JAVA_SOURCE_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_JAVA_SOURCE_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..f0f5ed7584319bacf694d65fab981c6c435e4eac --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_JAVA_SOURCE_DIR.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ANDROID_JAVA_SOURCE_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_JAVA_SOURCE_DIR

+
+

New in version 3.4.

+
+

Default value for the ANDROID_JAVA_SOURCE_DIR target property. +See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES.html new file mode 100644 index 0000000000000000000000000000000000000000..a72887d07bcdc87a1581ae5037f5baa66de21993 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES

+
+

New in version 3.4.

+
+

Default value for the ANDROID_NATIVE_LIB_DEPENDENCIES target +property. See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..aeb4bec60b8985535606f865792d356d0a95326a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES

+
+

New in version 3.4.

+
+

Default value for the ANDROID_NATIVE_LIB_DIRECTORIES target +property. See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NDK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NDK.html new file mode 100644 index 0000000000000000000000000000000000000000..4234f173039c39bdbb6f99dca31c1f0afbcf9340 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NDK.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_ANDROID_NDK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_NDK

+
+

New in version 3.7.

+
+

When Cross Compiling for Android with the NDK, this variable holds +the absolute path to the root directory of the NDK. The directory must +contain a platforms subdirectory holding the android-<api> +directories.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NDK_DEPRECATED_HEADERS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NDK_DEPRECATED_HEADERS.html new file mode 100644 index 0000000000000000000000000000000000000000..94cdf1f3edbb8ea26b3bdf364031fbbae0d018dd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NDK_DEPRECATED_HEADERS.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_ANDROID_NDK_DEPRECATED_HEADERS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_NDK_DEPRECATED_HEADERS

+
+

New in version 3.9.

+
+

When Cross Compiling for Android with the NDK, this variable +may be set to specify whether to use the deprecated per-api-level +headers instead of the unified headers.

+

If not specified, the default will be false if using a NDK version +that provides the unified headers and true otherwise.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NDK_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NDK_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..d795427c5b65b3909f11c74817e53e075f62d28b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_NDK_VERSION.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_ANDROID_NDK_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_NDK_VERSION

+
+

New in version 3.20.

+
+

When Cross Compiling for Android with the NDK and using an +Android NDK version 11 or higher, this variable is provided by +CMake to report the NDK version number.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_PROGUARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_PROGUARD.html new file mode 100644 index 0000000000000000000000000000000000000000..2ed4d1b6f32769dba194b35cf0afb1437aa12111 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_PROGUARD.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ANDROID_PROGUARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_PROGUARD

+
+

New in version 3.4.

+
+

Default value for the ANDROID_PROGUARD target property. +See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_PROGUARD_CONFIG_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_PROGUARD_CONFIG_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..321c9588dc80d832ac79acb0d53f01934f4728ac --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_PROGUARD_CONFIG_PATH.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ANDROID_PROGUARD_CONFIG_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_PROGUARD_CONFIG_PATH

+
+

New in version 3.4.

+
+

Default value for the ANDROID_PROGUARD_CONFIG_PATH target property. +See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_SECURE_PROPS_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_SECURE_PROPS_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..8ae91308251649f3d62643772820a04e6be146a1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_SECURE_PROPS_PATH.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ANDROID_SECURE_PROPS_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_SECURE_PROPS_PATH

+
+

New in version 3.4.

+
+

Default value for the ANDROID_SECURE_PROPS_PATH target property. +See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_STANDALONE_TOOLCHAIN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_STANDALONE_TOOLCHAIN.html new file mode 100644 index 0000000000000000000000000000000000000000..65b826e69d6f7c6684c00cb478a29cee8852345a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_STANDALONE_TOOLCHAIN.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_ANDROID_STANDALONE_TOOLCHAIN — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_STANDALONE_TOOLCHAIN

+
+

New in version 3.7.

+
+

When Cross Compiling for Android with a Standalone Toolchain, this +variable holds the absolute path to the root directory of the toolchain. +The specified directory must contain a sysroot subdirectory.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_STL_TYPE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_STL_TYPE.html new file mode 100644 index 0000000000000000000000000000000000000000..82f5797f81b33bb4ae13859e42c2617264345d12 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ANDROID_STL_TYPE.html @@ -0,0 +1,173 @@ + + + + + + + + + CMAKE_ANDROID_STL_TYPE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ANDROID_STL_TYPE

+
+

New in version 3.4.

+
+

When Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition, this variable may be set to specify the default value for the +ANDROID_STL_TYPE target property. See that target property +for additional information.

+

When Cross Compiling for Android with the NDK, this variable may be +set to specify the STL variant to be used. The value may be one of:

+
+
none

No C++ Support

+
+
system

Minimal C++ without STL

+
+
gabi++_static

GAbi++ Static

+
+
gabi++_shared

GAbi++ Shared

+
+
gnustl_static

GNU libstdc++ Static

+
+
gnustl_shared

GNU libstdc++ Shared

+
+
c++_static

LLVM libc++ Static

+
+
c++_shared

LLVM libc++ Shared

+
+
stlport_static

STLport Static

+
+
stlport_shared

STLport Shared

+
+
+

The default value is gnustl_static on NDK versions that provide it +and otherwise c++_static. Note that this default differs from +the native NDK build system because CMake may be used to build projects for +Android that are not natively implemented for it and use the C++ standard +library.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_APPBUNDLE_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_APPBUNDLE_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..6e920af51fc7a8df1a75efc50b6e6fd2dd39f21c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_APPBUNDLE_PATH.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_APPBUNDLE_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_APPBUNDLE_PATH

+

Semicolon-separated list of directories specifying a search path +for macOS application bundles used by the find_program(), and +find_package() commands.

+

There is also an environment variable CMAKE_APPBUNDLE_PATH, which is used +as an additional list of search directories.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_APPLE_SILICON_PROCESSOR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_APPLE_SILICON_PROCESSOR.html new file mode 100644 index 0000000000000000000000000000000000000000..ff22c392c334b8b91d0ca3e85d6c153c15726738 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_APPLE_SILICON_PROCESSOR.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_APPLE_SILICON_PROCESSOR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_APPLE_SILICON_PROCESSOR

+
+

New in version 3.19.2.

+
+

On Apple Silicon hosts running macOS, set this variable to tell +CMake what architecture to use for CMAKE_HOST_SYSTEM_PROCESSOR. +The value must be either arm64 or x86_64.

+

The value of this variable should never be modified by project code. +It is meant to be set as a cache entry provided by the user, +e.g. via -DCMAKE_APPLE_SILICON_PROCESSOR=....

+

See also the CMAKE_APPLE_SILICON_PROCESSOR environment variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AR.html new file mode 100644 index 0000000000000000000000000000000000000000..6e2a1256af1511b930c20bd3c94da6c34ac54b42 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AR.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_AR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AR

+

Name of archiving tool for static libraries.

+

This specifies the name of the program that creates archive or static +libraries.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..56c997040227ccbada632438b848dc5fea0b54f9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ARCHIVE_OUTPUT_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ARCHIVE_OUTPUT_DIRECTORY

+

Where to put all the ARCHIVE +target files when built.

+

This variable is used to initialize the ARCHIVE_OUTPUT_DIRECTORY +property on all the targets. See that target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..3c11964aa1053e7abe939d5492fe88cd6e8c3ca4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARCHIVE_OUTPUT_DIRECTORY_CONFIG.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_ARCHIVE_OUTPUT_DIRECTORY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ARCHIVE_OUTPUT_DIRECTORY_<CONFIG>

+
+

New in version 3.3.

+
+

Where to put all the ARCHIVE +target files when built for a specific configuration.

+

This variable is used to initialize the +ARCHIVE_OUTPUT_DIRECTORY_<CONFIG> property on all the targets. +See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARGC.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARGC.html new file mode 100644 index 0000000000000000000000000000000000000000..aa4bfd2fe353db12f33a1ffe516e325f3d71ea9e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARGC.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_ARGC — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ARGC

+

Number of command line arguments passed to CMake in script mode.

+

When run in -P script mode, CMake sets this +variable to the number of command line arguments. See also +CMAKE_ARGV0, 1, 2 ...

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARGV0.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARGV0.html new file mode 100644 index 0000000000000000000000000000000000000000..e23b9c3bdd5e8917b41dec1f1d457ebfeb5fd265 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ARGV0.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_ARGV0 — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ARGV0

+

Command line argument passed to CMake in script mode.

+

When run in -P script mode, CMake sets this +variable to the first command line argument. It then also sets CMAKE_ARGV1, +CMAKE_ARGV2, ... and so on, up to the number of command line arguments +given. See also CMAKE_ARGC.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOGEN_PARALLEL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOGEN_PARALLEL.html new file mode 100644 index 0000000000000000000000000000000000000000..d6d229d1592a8ad0deec4558cf53e7b717fd68d2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOGEN_PARALLEL.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_AUTOGEN_PARALLEL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOGEN_PARALLEL

+
+

New in version 3.11.

+
+

Number of parallel moc or uic processes to start when using +AUTOMOC and AUTOUIC.

+

This variable is used to initialize the AUTOGEN_PARALLEL property +on all the targets. See that target property for additional information.

+

By default CMAKE_AUTOGEN_PARALLEL is unset.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOGEN_USE_SYSTEM_INCLUDE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOGEN_USE_SYSTEM_INCLUDE.html new file mode 100644 index 0000000000000000000000000000000000000000..65f74cd8e82e3dd3fcd3c33f157ee4e8933b93bd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOGEN_USE_SYSTEM_INCLUDE.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_AUTOGEN_USE_SYSTEM_INCLUDE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOGEN_USE_SYSTEM_INCLUDE

+
+

New in version 3.27.

+
+

This variable is used to initialize the AUTOGEN_USE_SYSTEM_INCLUDE +property on all targets as they are created. See that target property for +additional information.

+

By default CMAKE_AUTOGEN_USE_SYSTEM_INCLUDE is unset.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOGEN_VERBOSE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOGEN_VERBOSE.html new file mode 100644 index 0000000000000000000000000000000000000000..733d68d7169068a0b886c9a01e14bc41cb2e06fc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOGEN_VERBOSE.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_AUTOGEN_VERBOSE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOGEN_VERBOSE

+
+

New in version 3.13.

+
+

Sets the verbosity of AUTOMOC, AUTOUIC and +AUTORCC. A positive integer value or a true boolean value +lets the AUTO* generators output additional processing information.

+

Setting CMAKE_AUTOGEN_VERBOSE has the same effect +as setting the VERBOSE environment variable during +generation (e.g. by calling make VERBOSE=1). +The extra verbosity is limited to the AUTO* generators though.

+

By default CMAKE_AUTOGEN_VERBOSE is unset.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_COMPILER_PREDEFINES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_COMPILER_PREDEFINES.html new file mode 100644 index 0000000000000000000000000000000000000000..448695d1b1dfd6ceb1d4cb3d78fabc1c1b7a6d31 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_COMPILER_PREDEFINES.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_AUTOMOC_COMPILER_PREDEFINES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOMOC_COMPILER_PREDEFINES

+
+

New in version 3.10.

+
+

This variable is used to initialize the AUTOMOC_COMPILER_PREDEFINES +property on all the targets. See that target property for additional +information.

+

By default it is ON.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_EXECUTABLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_EXECUTABLE.html new file mode 100644 index 0000000000000000000000000000000000000000..7185ceefcfd44c75f9f35e0514677153ac835b22 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_EXECUTABLE.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_AUTOMOC_EXECUTABLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOMOC_EXECUTABLE

+
+

New in version 3.27.

+
+

This variable is used to initialize the AUTOMOC_EXECUTABLE +property on all the targets. See that target property for additional +information.

+

By default it is empty.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_MACRO_NAMES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_MACRO_NAMES.html new file mode 100644 index 0000000000000000000000000000000000000000..cc4fcfbcf0cc65bc81e607aa92ceb3293bedf675 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_MACRO_NAMES.html @@ -0,0 +1,167 @@ + + + + + + + + + CMAKE_AUTOMOC_MACRO_NAMES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOMOC_MACRO_NAMES

+
+

New in version 3.10.

+
+

Semicolon-separated list list of macro names used by +CMAKE_AUTOMOC to determine if a C++ file needs to be +processed by moc.

+

This variable is used to initialize the AUTOMOC_MACRO_NAMES +property on all the targets. See that target property for additional +information.

+

The default value is Q_OBJECT;Q_GADGET;Q_NAMESPACE;Q_NAMESPACE_EXPORT.

+
+

Example

+

Let CMake know that source files that contain CUSTOM_MACRO must be moc +processed as well:

+
set(CMAKE_AUTOMOC ON)
+list(APPEND CMAKE_AUTOMOC_MACRO_NAMES "CUSTOM_MACRO")
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_PATH_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_PATH_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..702cf54c76af5cc40f08b40f2a7e737e5d636a96 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_PATH_PREFIX.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_AUTOMOC_PATH_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOMOC_PATH_PREFIX

+
+

New in version 3.16.

+
+

Whether to generate the -p path prefix option for moc on +AUTOMOC enabled Qt targets.

+

This variable is used to initialize the AUTOMOC_PATH_PREFIX +property on all the targets. See that target property for additional +information.

+

The default value is OFF.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_RELAXED_MODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_RELAXED_MODE.html new file mode 100644 index 0000000000000000000000000000000000000000..80a99975f731a517c05d6f2d9af077aef1b2a687 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOMOC_RELAXED_MODE.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_AUTOMOC_RELAXED_MODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOMOC_RELAXED_MODE

+
+

Deprecated since version 3.15.

+
+

Switch between strict and relaxed automoc mode.

+

By default, AUTOMOC behaves exactly as described in the +documentation of the AUTOMOC target property. When set to +TRUE, it accepts more input and tries to find the correct input file for +moc even if it differs from the documented behavior. In this mode it +e.g. also checks whether a header file is intended to be processed by moc +when a "foo.moc" file has been included.

+

Relaxed mode has to be enabled for KDE4 compatibility.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTORCC.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTORCC.html new file mode 100644 index 0000000000000000000000000000000000000000..bdc50194fe55374dbf8371ad84b1e7eff0616165 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTORCC.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_AUTORCC — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTORCC

+

Whether to handle rcc automatically for Qt targets.

+

This variable is used to initialize the AUTORCC property on all +the targets. See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTORCC_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTORCC_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..6b41e2a016c675948c020007c576a8772b8cc930 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTORCC_OPTIONS.html @@ -0,0 +1,159 @@ + + + + + + + + + CMAKE_AUTORCC_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTORCC_OPTIONS

+

Additional options for rcc when using CMAKE_AUTORCC.

+

This variable is used to initialize the AUTORCC_OPTIONS property on +all the targets. See that target property for additional information.

+
+

EXAMPLE

+
# ...
+set(CMAKE_AUTORCC_OPTIONS "--compress;9")
+# ...
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOUIC.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOUIC.html new file mode 100644 index 0000000000000000000000000000000000000000..bc37bf22bcae8c368c34bbb8dd7bda00d16ddaf0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOUIC.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_AUTOUIC — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOUIC

+

Whether to handle uic automatically for Qt targets.

+

This variable is used to initialize the AUTOUIC property on all +the targets. See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOUIC_EXECUTABLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOUIC_EXECUTABLE.html new file mode 100644 index 0000000000000000000000000000000000000000..2d69d5a6ed69ab4ab7eb9202082e535395713779 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOUIC_EXECUTABLE.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_AUTOUIC_EXECUTABLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOUIC_EXECUTABLE

+
+

New in version 3.27.

+
+

This variable is used to initialize the AUTOUIC_EXECUTABLE +property on all the targets. See that target property for additional +information.

+

By default it is empty.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOUIC_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOUIC_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..93e7f06d817eca203a6d58b22e2ca60e1d3c30ae --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_AUTOUIC_OPTIONS.html @@ -0,0 +1,159 @@ + + + + + + + + + CMAKE_AUTOUIC_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_AUTOUIC_OPTIONS

+

Additional options for uic when using CMAKE_AUTOUIC.

+

This variable is used to initialize the AUTOUIC_OPTIONS property on +all the targets. See that target property for additional information.

+
+

EXAMPLE

+
# ...
+set_property(CMAKE_AUTOUIC_OPTIONS "--no-protection")
+# ...
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BACKWARDS_COMPATIBILITY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BACKWARDS_COMPATIBILITY.html new file mode 100644 index 0000000000000000000000000000000000000000..45239098db8702d51ac64166f15e79803fc5dccb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BACKWARDS_COMPATIBILITY.html @@ -0,0 +1,139 @@ + + + + + + + + + CMAKE_BACKWARDS_COMPATIBILITY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_BACKWARDS_COMPATIBILITY

+

Deprecated. See CMake Policy CMP0001 documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BINARY_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BINARY_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..0d731fe0f8d4d6bd987af222f989f4a23a418ee3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BINARY_DIR.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_BINARY_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_BINARY_DIR

+

The path to the top level of the build tree.

+

This is the full path to the top level of the current CMake build +tree. For an in-source build, this would be the same as +CMAKE_SOURCE_DIR.

+

When run in cmake -P script mode, CMake sets the variables +CMAKE_BINARY_DIR, CMAKE_SOURCE_DIR, +CMAKE_CURRENT_BINARY_DIR and +CMAKE_CURRENT_SOURCE_DIR to the current working directory.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_RPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_RPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..5220a1353eab6a29134fe0b386da703fe3086755 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_RPATH.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_BUILD_RPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_BUILD_RPATH

+
+

New in version 3.8.

+
+

Semicolon-separated list specifying runtime path (RPATH) +entries to add to binaries linked in the build tree (for platforms that +support it). The entries will not be used for binaries in the install +tree. See also the CMAKE_INSTALL_RPATH variable.

+

This is used to initialize the BUILD_RPATH target property +for all targets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_RPATH_USE_ORIGIN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_RPATH_USE_ORIGIN.html new file mode 100644 index 0000000000000000000000000000000000000000..3b84fa458bed6b51df9f123d9ca9a9b91d602587 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_RPATH_USE_ORIGIN.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_BUILD_RPATH_USE_ORIGIN — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_BUILD_RPATH_USE_ORIGIN

+
+

New in version 3.14.

+
+

Whether to use relative paths for the build RPATH.

+

This is used to initialize the BUILD_RPATH_USE_ORIGIN target +property for all targets, see that property for more details.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_TOOL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_TOOL.html new file mode 100644 index 0000000000000000000000000000000000000000..6ef52d9775a4d09baa914d646f12d1ef164b3b4f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_TOOL.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_BUILD_TOOL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_BUILD_TOOL

+

This variable exists only for backwards compatibility. +It contains the same value as CMAKE_MAKE_PROGRAM. +Use that variable instead.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_TYPE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_TYPE.html new file mode 100644 index 0000000000000000000000000000000000000000..702d92e78eb6538560fb627063da8b9eb2fbfe22 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_TYPE.html @@ -0,0 +1,153 @@ + + + + + + + + + CMAKE_BUILD_TYPE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_BUILD_TYPE

+

Specifies the build type on single-configuration generators (e.g. +Makefile Generators or Ninja). Typical values include +Debug, Release, RelWithDebInfo and MinSizeRel, but custom +build types can also be defined.

+

This variable is initialized by the first project() or +enable_language() command called in a project when a new build +tree is first created. If the CMAKE_BUILD_TYPE environment +variable is set, its value is used. Otherwise, a toolchain-specific +default is chosen when a language is enabled. The default value is often +an empty string, but this is usually not desirable and one of the other +standard build types is usually more appropriate.

+

Depending on the situation, the value of this variable may be treated +case-sensitively or case-insensitively. See Build Configurations +for discussion of this and other related topics.

+

For multi-config generators, see CMAKE_CONFIGURATION_TYPES.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_WITH_INSTALL_NAME_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_WITH_INSTALL_NAME_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..e04c6093a06d1ac7dd7b317951512d3a7e39bee3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_BUILD_WITH_INSTALL_NAME_DIR.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_BUILD_WITH_INSTALL_NAME_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_BUILD_WITH_INSTALL_NAME_DIR

+
+

New in version 3.9.

+
+

Whether to use INSTALL_NAME_DIR on targets in the build tree.

+

This variable is used to initialize the BUILD_WITH_INSTALL_NAME_DIR +property on all targets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CACHEFILE_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CACHEFILE_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..242fa18d7f2b7a81d978639ef61b96d6acec9e2e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CACHEFILE_DIR.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_CACHEFILE_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CACHEFILE_DIR

+

This variable is used internally by CMake, and may not be set during +the first configuration of a build tree. When it is set, it has the +same value as CMAKE_BINARY_DIR. Use that variable instead.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CACHE_MAJOR_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CACHE_MAJOR_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..06637b67e9f5dfd13d41ff001e96b5e078af1107 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CACHE_MAJOR_VERSION.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_CACHE_MAJOR_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CACHE_MAJOR_VERSION

+

Major version of CMake used to create the CMakeCache.txt file

+

This stores the major version of CMake used to write a CMake cache +file. It is only different when a different version of CMake is run +on a previously created cache file.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CACHE_PATCH_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CACHE_PATCH_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..a00f8594fc2ba08204a56bce696208d9493cdde1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CACHE_PATCH_VERSION.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_CACHE_PATCH_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CACHE_PATCH_VERSION

+

Patch version of CMake used to create the CMakeCache.txt file

+

This stores the patch version of CMake used to write a CMake cache +file. It is only different when a different version of CMake is run +on a previously created cache file.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CFG_INTDIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CFG_INTDIR.html new file mode 100644 index 0000000000000000000000000000000000000000..7f03634258859ebba2065170deeb82e248518e51 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CFG_INTDIR.html @@ -0,0 +1,181 @@ + + + + + + + + + CMAKE_CFG_INTDIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CFG_INTDIR

+
+

Deprecated since version 3.21: This variable has poor support on Ninja Multi-Config, and +predates the existence of the $<CONFIG> generator expression. Use +$<CONFIG> instead.

+
+

Build-time reference to per-configuration output subdirectory.

+

For native build systems supporting multiple configurations in the +build tree (such as Visual Studio Generators and Xcode), +the value is a reference to a build-time variable specifying the name +of the per-configuration output subdirectory. On Makefile Generators +this evaluates to . because there is only one configuration in a build tree. +Example values:

+
$(ConfigurationName) = Visual Studio 9
+$(Configuration)     = Visual Studio 11 and above
+$(CONFIGURATION)     = Xcode
+.                    = Make-based tools
+.                    = Ninja
+${CONFIGURATION}     = Ninja Multi-Config
+
+
+

Since these values are evaluated by the native build system, this +variable is suitable only for use in command lines that will be +evaluated at build time. Example of intended usage:

+
add_executable(mytool mytool.c)
+add_custom_command(
+  OUTPUT out.txt
+  COMMAND ${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}/mytool
+          ${CMAKE_CURRENT_SOURCE_DIR}/in.txt out.txt
+  DEPENDS mytool in.txt
+  )
+add_custom_target(drive ALL DEPENDS out.txt)
+
+
+

Note that CMAKE_CFG_INTDIR is no longer necessary for this purpose but +has been left for compatibility with existing projects. Instead +add_custom_command() recognizes executable target names in its +COMMAND option, so +${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}/mytool can be replaced +by just mytool.

+

This variable is read-only. Setting it is undefined behavior. In +multi-configuration build systems the value of this variable is passed +as the value of preprocessor symbol CMAKE_INTDIR to the compilation +of all source files.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CLANG_VFS_OVERLAY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CLANG_VFS_OVERLAY.html new file mode 100644 index 0000000000000000000000000000000000000000..c1174b69fb50408f312b6f7c423895d82aed24fd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CLANG_VFS_OVERLAY.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_CLANG_VFS_OVERLAY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CLANG_VFS_OVERLAY

+
+

New in version 3.19.

+
+

When cross compiling for windows with clang-cl, this variable can be an +absolute path pointing to a clang virtual file system yaml file, which +will enable clang-cl to resolve windows header names on a case sensitive +file system.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CL_64.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CL_64.html new file mode 100644 index 0000000000000000000000000000000000000000..7177955e77f158f884a071e7aeec42c1db0b652f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CL_64.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_CL_64 — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CL_64

+

Discouraged. Use CMAKE_SIZEOF_VOID_P instead.

+

Set to a true value when using a Microsoft Visual Studio cl compiler that +targets a 64-bit architecture.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES.html new file mode 100644 index 0000000000000000000000000000000000000000..88989671ebff79559c77d02d82acaaed62ee73dc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES

+
+

New in version 3.10.

+
+

Change the way the CodeBlocks generator creates project files.

+

If this variable evaluates to ON the generator excludes from +the project file any files that are located outside the project root.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CODELITE_USE_TARGETS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CODELITE_USE_TARGETS.html new file mode 100644 index 0000000000000000000000000000000000000000..f4547c321b6683ac8c4d8c6b7fbf02b6e7deee5b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CODELITE_USE_TARGETS.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_CODELITE_USE_TARGETS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CODELITE_USE_TARGETS

+
+

New in version 3.7.

+
+

Change the way the CodeLite generator creates projectfiles.

+

If this variable evaluates to ON at the end of the top-level +CMakeLists.txt file, the generator creates projectfiles based on targets +rather than projects.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COLOR_DIAGNOSTICS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COLOR_DIAGNOSTICS.html new file mode 100644 index 0000000000000000000000000000000000000000..1a0eebe7c3bfa6442ba8d88e96bd34e66e3f4dfc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COLOR_DIAGNOSTICS.html @@ -0,0 +1,168 @@ + + + + + + + + + CMAKE_COLOR_DIAGNOSTICS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_COLOR_DIAGNOSTICS

+
+

New in version 3.24.

+
+

Enable color diagnostics throughout.

+

This variable uses three states: ON, OFF and not defined.

+

When not defined:

+ +

When ON:

+
    +
  • Makefile Generators produce color buildsystem messages by default. +CMAKE_COLOR_MAKEFILE is not initialized, but may be +explicitly set to OFF to disable color buildsystem messages.

  • +
  • GNU/Clang compilers are invoked with a flag enabling color diagnostics +(-fcolor-diagnostics).

  • +
+

When OFF:

+
    +
  • Makefile Generators do not produce color buildsystem messages by +default. CMAKE_COLOR_MAKEFILE is not initialized, but may be +explicitly set to ON to enable color buildsystem messages.

  • +
  • GNU/Clang compilers are invoked with a flag disabling color diagnostics +(-fno-color-diagnostics).

  • +
+

If the CMAKE_COLOR_DIAGNOSTICS environment variable is set, its +value is used. Otherwise, CMAKE_COLOR_DIAGNOSTICS is not defined by +default.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COLOR_MAKEFILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COLOR_MAKEFILE.html new file mode 100644 index 0000000000000000000000000000000000000000..8a862e8e3915c6fae424531fd70982e0e61f8849 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COLOR_MAKEFILE.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_COLOR_MAKEFILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_COLOR_MAKEFILE

+

Enables color output when using the Makefile Generators.

+

When enabled, the generated Makefiles will produce colored output. +Default is ON.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..96b3200ac76b26650bc9fdd51bc8beea84c8dad4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMMAND.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_COMMAND

+

The full path to the cmake(1) executable.

+

This is the full path to the CMake executable cmake(1) which is +useful from custom commands that want to use the cmake -E option for +portable system commands. (e.g. /usr/local/bin/cmake)

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMPILER_IS_GNUCXX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMPILER_IS_GNUCXX.html new file mode 100644 index 0000000000000000000000000000000000000000..6959a3896012f1214b8f8815577b0501a4c36755 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMPILER_IS_GNUCXX.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_COMPILER_IS_GNUCXX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_COMPILER_IS_GNUCXX

+

True if the C++ (CXX) compiler is GNU.

+

This variable is deprecated. Use +CMAKE_CXX_COMPILER_ID instead.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMPILER_IS_GNUG77.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMPILER_IS_GNUG77.html new file mode 100644 index 0000000000000000000000000000000000000000..4421b3ebe6b47bbfba2b78c5c2053f99f03c9e92 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMPILER_IS_GNUG77.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_COMPILER_IS_GNUG77 — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_COMPILER_IS_GNUG77

+

True if the Fortran compiler is GNU.

+

This variable is deprecated. Use +CMAKE_Fortran_COMPILER_ID instead.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..995b4448868dc76cbac9756ae75ed829fe22af27 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_CONFIG.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG>

+
+

New in version 3.1.

+
+

Per-configuration output directory for MS debug symbol .pdb files +generated by the compiler while building source files.

+

This is a per-configuration version of +CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY. +This variable is used to initialize the +COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG> +property on all the targets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CONFIG_POSTFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CONFIG_POSTFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..6dc3c38680f7e544a66e90e2a98e89ed176474b5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CONFIG_POSTFIX.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_<CONFIG>_POSTFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<CONFIG>_POSTFIX

+

Default filename postfix for libraries under configuration <CONFIG>.

+

When a non-executable target is created its <CONFIG>_POSTFIX +target property is initialized with the value of this variable if it is set.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CPACK_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CPACK_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..adfc63fa1bcdf25dfc13cc278cbf5266a29365bc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CPACK_COMMAND.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_CPACK_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CPACK_COMMAND

+
+

New in version 3.13.

+
+

Full path to cpack(1) command installed with CMake.

+

This is the full path to the CPack executable cpack(1) +that can be used for custom commands or tests to invoke +CPack commands.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CROSSCOMPILING.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CROSSCOMPILING.html new file mode 100644 index 0000000000000000000000000000000000000000..5b329e8c2d853a341ba2fceaa8f5c00b08904ce2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CROSSCOMPILING.html @@ -0,0 +1,160 @@ + + + + + + + + + CMAKE_CROSSCOMPILING — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CROSSCOMPILING

+

This variable is set by CMake to indicate whether it is cross compiling, +but note limitations discussed below.

+

This variable will be set to true by CMake if the CMAKE_SYSTEM_NAME +variable has been set manually (i.e. in a toolchain file or as a cache entry +from the cmake command line). In most cases, manually +setting CMAKE_SYSTEM_NAME will only be done when cross compiling +since, if not manually set, it will be given the same value as +CMAKE_HOST_SYSTEM_NAME, which is correct for +the non-cross-compiling case. In the event that CMAKE_SYSTEM_NAME +is manually set to the same value as CMAKE_HOST_SYSTEM_NAME, then +CMAKE_CROSSCOMPILING will still be set to true.

+

Another case to be aware of is that builds targeting Apple platforms other than +macOS are handled differently to other cross compiling scenarios. Rather than +relying on CMAKE_SYSTEM_NAME to select the target platform, Apple +device builds use CMAKE_OSX_SYSROOT to select the appropriate SDK, +which indirectly determines the target platform. Furthermore, when using the +Xcode generator, developers can switch between device and +simulator builds at build time rather than having a single +choice at configure time, so the concept +of whether the build is cross compiling or not is more complex. Therefore, the +use of CMAKE_CROSSCOMPILING is not recommended for projects targeting Apple +devices.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CROSS_CONFIGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CROSS_CONFIGS.html new file mode 100644 index 0000000000000000000000000000000000000000..a3e40970f283c436a71a25eb436c3dd4be12faae --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CROSS_CONFIGS.html @@ -0,0 +1,152 @@ + + + + + + + + + CMAKE_CROSS_CONFIGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CROSS_CONFIGS

+
+

New in version 3.17.

+
+

Specifies a semicolon-separated list of +configurations available from all build-<Config>.ninja files in the +Ninja Multi-Config generator. This variable activates +cross-config mode. Targets from each config specified in this variable can be +built from any build-<Config>.ninja file. Custom commands will use the +configuration native to build-<Config>.ninja. If it is set to all, all +configurations from CMAKE_CONFIGURATION_TYPES are cross-configs. If +it is not specified, or empty, each build-<Config>.ninja file will only +contain build rules for its own configuration.

+

The value of this variable must be a subset of +CMAKE_CONFIGURATION_TYPES.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CTEST_ARGUMENTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CTEST_ARGUMENTS.html new file mode 100644 index 0000000000000000000000000000000000000000..cf4432c4d58bbe1aa7f05ccb58c7b1433280f85b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CTEST_ARGUMENTS.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_CTEST_ARGUMENTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CTEST_ARGUMENTS

+
+

New in version 3.17.

+
+

Set this to a semicolon-separated list of +command-line arguments to pass to ctest(1) when running tests +through the test (or RUN_TESTS) target of the generated build system.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CTEST_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CTEST_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..82b6e411babcbca049ebaadde00b8dffaad799ce --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CTEST_COMMAND.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_CTEST_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CTEST_COMMAND

+

Full path to ctest(1) command installed with CMake.

+

This is the full path to the CTest executable ctest(1) +that can be used for custom commands or tests to invoke +CTest commands.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_COMPILE_FEATURES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_COMPILE_FEATURES.html new file mode 100644 index 0000000000000000000000000000000000000000..27fd4e8d866d0e5f1adfd629dfe626aa4e4be9d9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_COMPILE_FEATURES.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_CUDA_COMPILE_FEATURES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CUDA_COMPILE_FEATURES

+
+

New in version 3.17.

+
+

List of features known to the CUDA compiler

+

These features are known to be available for use with the CUDA compiler. This +list is a subset of the features listed in the +CMAKE_CUDA_KNOWN_FEATURES global property.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..32a4ac76208bd48185240ef278340841ef02800a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_EXTENSIONS.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_CUDA_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CUDA_EXTENSIONS

+
+

New in version 3.8.

+
+

Default value for CUDA_EXTENSIONS target property if set when a +target is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_HOST_COMPILER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_HOST_COMPILER.html new file mode 100644 index 0000000000000000000000000000000000000000..dabe0de3612ec9644930350c6d85f185ae11d4a8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_HOST_COMPILER.html @@ -0,0 +1,163 @@ + + + + + + + + + CMAKE_CUDA_HOST_COMPILER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CUDA_HOST_COMPILER

+
+

New in version 3.10.

+
+

When CMAKE_CUDA_COMPILER_ID is +NVIDIA, CMAKE_CUDA_HOST_COMPILER selects the compiler executable to use +when compiling host code for CUDA language files. +This maps to the nvcc -ccbin option.

+

The CMAKE_CUDA_HOST_COMPILER variable may be set explicitly before CUDA is +first enabled by a project() or enable_language() command. +This can be done via -DCMAKE_CUDA_HOST_COMPILER=... on the command line +or in a toolchain file. Or, one may set +the CUDAHOSTCXX environment variable to provide a default value.

+

Once the CUDA language is enabled, the CMAKE_CUDA_HOST_COMPILER variable +is read-only and changes to it are undefined behavior.

+
+

Note

+

Since CMAKE_CUDA_HOST_COMPILER is meaningful only when the +CMAKE_CUDA_COMPILER_ID is NVIDIA, +it does not make sense to set CMAKE_CUDA_HOST_COMPILER without also +setting CMAKE_CUDA_COMPILER to NVCC.

+
+
+

Note

+

Ignored when using Visual Studio Generators.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_SEPARABLE_COMPILATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_SEPARABLE_COMPILATION.html new file mode 100644 index 0000000000000000000000000000000000000000..0afd3508e9a6c923f08a019a346c09bee413b53c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_SEPARABLE_COMPILATION.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_CUDA_SEPARABLE_COMPILATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CUDA_SEPARABLE_COMPILATION

+
+

New in version 3.11.

+
+

Default value for CUDA_SEPARABLE_COMPILATION target property. +This variable is used to initialize the property on each target as it is +created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_STANDARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_STANDARD.html new file mode 100644 index 0000000000000000000000000000000000000000..4bed29c22cf007a69658eb36cd7f12813fa615df --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_STANDARD.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_CUDA_STANDARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CUDA_STANDARD

+
+

New in version 3.8.

+
+

Default value for CUDA_STANDARD target property if set when a +target is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..748f7437f7dc807641701fa952bd7311f3f37aea --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CUDA_STANDARD_REQUIRED.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_CUDA_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CUDA_STANDARD_REQUIRED

+
+

New in version 3.8.

+
+

Default value for CUDA_STANDARD_REQUIRED target property if set +when a target is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_BINARY_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_BINARY_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..cb03f5b137f9d8462e04fc446148ba057c49c47d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_BINARY_DIR.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_CURRENT_BINARY_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CURRENT_BINARY_DIR

+

The path to the binary directory currently being processed.

+

This is the full path to the build directory that is currently being +processed by cmake. Each directory added by add_subdirectory() will +create a binary directory in the build tree, and as it is being +processed this variable will be set. For in-source builds this is the +current source directory being processed.

+

When run in cmake -P script mode, CMake sets the variables +CMAKE_BINARY_DIR, CMAKE_SOURCE_DIR, +CMAKE_CURRENT_BINARY_DIR and +CMAKE_CURRENT_SOURCE_DIR to the current working directory.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_FUNCTION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_FUNCTION.html new file mode 100644 index 0000000000000000000000000000000000000000..27becc26d00f9127224320fbc1f3a7594c103232 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_FUNCTION.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_CURRENT_FUNCTION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CURRENT_FUNCTION

+
+

New in version 3.17.

+
+

When executing code inside a function(), this variable +contains the name of the current function. It can be useful for +diagnostic or debug messages.

+

See also CMAKE_CURRENT_FUNCTION_LIST_DIR, +CMAKE_CURRENT_FUNCTION_LIST_FILE and +CMAKE_CURRENT_FUNCTION_LIST_LINE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_FUNCTION_LIST_FILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_FUNCTION_LIST_FILE.html new file mode 100644 index 0000000000000000000000000000000000000000..f22266e6ba3e42b929f748c8c1b5e0ed91ba7a75 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_FUNCTION_LIST_FILE.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_CURRENT_FUNCTION_LIST_FILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CURRENT_FUNCTION_LIST_FILE

+
+

New in version 3.17.

+
+

When executing code inside a function(), this variable +contains the full path to the listfile that defined the current function.

+

See also CMAKE_CURRENT_FUNCTION, +CMAKE_CURRENT_FUNCTION_LIST_DIR and +CMAKE_CURRENT_FUNCTION_LIST_LINE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_FUNCTION_LIST_LINE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_FUNCTION_LIST_LINE.html new file mode 100644 index 0000000000000000000000000000000000000000..a67aa95e8cbfefde5e0a0763d7b4a487612b1344 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_FUNCTION_LIST_LINE.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_CURRENT_FUNCTION_LIST_LINE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CURRENT_FUNCTION_LIST_LINE

+
+

New in version 3.17.

+
+

When executing code inside a function(), this variable +contains the line number in the listfile where the current function +was defined.

+

See also CMAKE_CURRENT_FUNCTION, +CMAKE_CURRENT_FUNCTION_LIST_DIR and +CMAKE_CURRENT_FUNCTION_LIST_FILE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_LIST_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_LIST_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..8ea2ebd714555dfac1b6c9c98cda67e90d2aeab6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_LIST_DIR.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_CURRENT_LIST_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CURRENT_LIST_DIR

+

Full directory of the listfile currently being processed.

+

As CMake processes the listfiles in your project this variable will +always be set to the directory where the listfile which is currently +being processed (CMAKE_CURRENT_LIST_FILE) is located. The value +has dynamic scope. When CMake starts processing commands in a source file +it sets this variable to the directory where this file is located. +When CMake finishes processing commands from the file it restores the +previous value. Therefore the value of the variable inside a macro or +function is the directory of the file invoking the bottom-most entry +on the call stack, not the directory of the file containing the macro +or function definition.

+

See also CMAKE_CURRENT_LIST_FILE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_LIST_FILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_LIST_FILE.html new file mode 100644 index 0000000000000000000000000000000000000000..4f70b5d565a26e4212b05d753f3744dde5929014 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_LIST_FILE.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_CURRENT_LIST_FILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CURRENT_LIST_FILE

+

Full path to the listfile currently being processed.

+

As CMake processes the listfiles in your project this variable will +always be set to the one currently being processed. The value has +dynamic scope. When CMake starts processing commands in a source file +it sets this variable to the location of the file. When CMake +finishes processing commands from the file it restores the previous +value. Therefore the value of the variable inside a macro or function +is the file invoking the bottom-most entry on the call stack, not the +file containing the macro or function definition.

+

See also CMAKE_PARENT_LIST_FILE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_LIST_LINE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_LIST_LINE.html new file mode 100644 index 0000000000000000000000000000000000000000..35032409d6827f72c7c3f827081d4b04a567ff2d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_LIST_LINE.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_CURRENT_LIST_LINE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CURRENT_LIST_LINE

+

The line number of the current file being processed.

+

This is the line number of the file currently being processed by +cmake.

+

If CMake is currently processing deferred calls scheduled by +the cmake_language(DEFER) command, this variable +evaluates to DEFERRED instead of a specific line number.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_SOURCE_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_SOURCE_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..6efcfc6857132507f79ebaa8d8cb2a59ba828eb2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CURRENT_SOURCE_DIR.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_CURRENT_SOURCE_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CURRENT_SOURCE_DIR

+

The path to the source directory currently being processed.

+

This is the full path to the source directory that is currently being +processed by cmake.

+

When run in cmake -P script mode, CMake sets the variables +CMAKE_BINARY_DIR, CMAKE_SOURCE_DIR, +CMAKE_CURRENT_BINARY_DIR and +CMAKE_CURRENT_SOURCE_DIR to the current working directory.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CXX_COMPILE_FEATURES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CXX_COMPILE_FEATURES.html new file mode 100644 index 0000000000000000000000000000000000000000..c418cb899dc117e1f7bf443e7d430fe7891639da --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CXX_COMPILE_FEATURES.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_CXX_COMPILE_FEATURES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CXX_COMPILE_FEATURES

+
+

New in version 3.1.

+
+

List of features known to the C++ compiler

+

These features are known to be available for use with the C++ compiler. This +list is a subset of the features listed in the +CMAKE_CXX_KNOWN_FEATURES global property.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CXX_STANDARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CXX_STANDARD.html new file mode 100644 index 0000000000000000000000000000000000000000..22ef1097d00053ccc7beeaf2e75dafebf66c61bf --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CXX_STANDARD.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_CXX_STANDARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CXX_STANDARD

+
+

New in version 3.1.

+
+

Default value for CXX_STANDARD target property if set when a target +is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CXX_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CXX_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..acf75f500c194ca17cb0ec0f84ab2bea34e4decb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_CXX_STANDARD_REQUIRED.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_CXX_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_CXX_STANDARD_REQUIRED

+
+

New in version 3.1.

+
+

Default value for CXX_STANDARD_REQUIRED target property if set when +a target is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_C_COMPILE_FEATURES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_C_COMPILE_FEATURES.html new file mode 100644 index 0000000000000000000000000000000000000000..5425d5d1de1b284a260c6893a4dff32f3f760ed7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_C_COMPILE_FEATURES.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_C_COMPILE_FEATURES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_C_COMPILE_FEATURES

+
+

New in version 3.1.

+
+

List of features known to the C compiler

+

These features are known to be available for use with the C compiler. This +list is a subset of the features listed in the +CMAKE_C_KNOWN_FEATURES global property.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_C_STANDARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_C_STANDARD.html new file mode 100644 index 0000000000000000000000000000000000000000..db5f08b40c0de206c881a99121a262db041f0a8b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_C_STANDARD.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_C_STANDARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_C_STANDARD

+
+

New in version 3.1.

+
+

Default value for C_STANDARD target property if set when a target +is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_C_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_C_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..7fdb5b90326c9351080a9bde004cccd32e189843 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_C_STANDARD_REQUIRED.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_C_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_C_STANDARD_REQUIRED

+
+

New in version 3.1.

+
+

Default value for C_STANDARD_REQUIRED target property if set when +a target is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEBUG_POSTFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEBUG_POSTFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..7744fcd85a12756e19c8a980537d72b9cb1b9f55 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEBUG_POSTFIX.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_DEBUG_POSTFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_DEBUG_POSTFIX

+

See variable CMAKE_<CONFIG>_POSTFIX.

+

This variable is a special case of the more-general +CMAKE_<CONFIG>_POSTFIX variable for the DEBUG configuration.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEBUG_TARGET_PROPERTIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEBUG_TARGET_PROPERTIES.html new file mode 100644 index 0000000000000000000000000000000000000000..7c6df924e99ab51fd6273ae0908de38fdd9b06b9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEBUG_TARGET_PROPERTIES.html @@ -0,0 +1,157 @@ + + + + + + + + + CMAKE_DEBUG_TARGET_PROPERTIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_DEBUG_TARGET_PROPERTIES

+

Enables tracing output for target properties.

+

This variable can be populated with a list of properties to generate +debug output for when evaluating target properties. Currently it can +only be used when evaluating:

+ +

target properties and any other property listed in +COMPATIBLE_INTERFACE_STRING and other +COMPATIBLE_INTERFACE_ properties. It outputs an origin for each entry +in the target property. Default is unset.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEFAULT_BUILD_TYPE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEFAULT_BUILD_TYPE.html new file mode 100644 index 0000000000000000000000000000000000000000..1a353ac4fbdb6738270c1be4ed22acce234aa8d4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEFAULT_BUILD_TYPE.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_DEFAULT_BUILD_TYPE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_DEFAULT_BUILD_TYPE

+
+

New in version 3.17.

+
+

Specifies the configuration to use by default in a build.ninja file in the +Ninja Multi-Config generator. If this variable is specified, +build.ninja uses build rules from build-<Config>.ninja by default. All +custom commands are executed with this configuration. If the variable is not +specified, the first item from CMAKE_CONFIGURATION_TYPES is used +instead.

+

The value of this variable must be one of the items from +CMAKE_CONFIGURATION_TYPES.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEFAULT_CONFIGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEFAULT_CONFIGS.html new file mode 100644 index 0000000000000000000000000000000000000000..b2ed8e38d1429a7575ec6d1c181c315a9ff30275 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEFAULT_CONFIGS.html @@ -0,0 +1,155 @@ + + + + + + + + + CMAKE_DEFAULT_CONFIGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_DEFAULT_CONFIGS

+
+

New in version 3.17.

+
+

Specifies a semicolon-separated list of configurations +to build for a target in build.ninja if no :<Config> suffix is specified in +the Ninja Multi-Config generator. If it is set to all, all +configurations from CMAKE_CROSS_CONFIGS are used. If it is not +specified, it defaults to CMAKE_DEFAULT_BUILD_TYPE.

+

For example, if you set CMAKE_DEFAULT_BUILD_TYPE to Release, +but set CMAKE_DEFAULT_CONFIGS to Debug or all, all +<target> aliases in build.ninja will resolve to <target>:Debug or +<target>:all, but custom commands will still use the Release +configuration.

+

The value of this variable must be a subset of CMAKE_CROSS_CONFIGS +or be the same as CMAKE_DEFAULT_BUILD_TYPE. It must not be +specified if CMAKE_DEFAULT_BUILD_TYPE or +CMAKE_CROSS_CONFIGS is not used.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEPENDS_USE_COMPILER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEPENDS_USE_COMPILER.html new file mode 100644 index 0000000000000000000000000000000000000000..4cd627a1b82287b58c026286f97e7e9a6a8f428e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DEPENDS_USE_COMPILER.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_DEPENDS_USE_COMPILER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_DEPENDS_USE_COMPILER

+
+

New in version 3.20.

+
+

For the Makefile Generators, source dependencies are now, for a +selection of compilers, generated by the compiler itself. By defining this +variable with value FALSE, you can restore the legacy behavior (i.e. using +CMake for dependencies discovery).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html new file mode 100644 index 0000000000000000000000000000000000000000..95eb1670b45869c67f8c3d2027e90b948004d35e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_DISABLE_FIND_PACKAGE_<PackageName> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_DISABLE_FIND_PACKAGE_<PackageName>

+

Variable for disabling find_package() calls.

+

Every non-REQUIRED find_package() call in a project can be +disabled by setting the variable +CMAKE_DISABLE_FIND_PACKAGE_<PackageName> to TRUE. +This can be used to build a project without an optional package, +although that package is installed.

+

This switch should be used during the initial CMake run. Otherwise if +the package has already been found in a previous CMake run, the +variables which have been stored in the cache will still be there. In +that case it is recommended to remove the cache variables for this +package from the cache using the cache editor or cmake -U.

+

See also the CMAKE_REQUIRE_FIND_PACKAGE_<PackageName> variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DLL_NAME_WITH_SOVERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DLL_NAME_WITH_SOVERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..bb2896a26152c4801d79080607bb9d7b29c31e95 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DLL_NAME_WITH_SOVERSION.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_DLL_NAME_WITH_SOVERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_DLL_NAME_WITH_SOVERSION

+
+

New in version 3.27.

+
+

This variable is used to initialize the DLL_NAME_WITH_SOVERSION +property on shared library targets for the Windows platform, which is selected +when the WIN32 variable is set.

+

See this target property for additional information.

+

Please note that setting this variable has no effect if versioned filenames +are globally disabled with the CMAKE_PLATFORM_NO_VERSIONED_SONAME +variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DL_LIBS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DL_LIBS.html new file mode 100644 index 0000000000000000000000000000000000000000..afc25197e32375e31177fc1ff6c25c19f406090e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DL_LIBS.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_DL_LIBS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_DL_LIBS

+

Name of library containing dlopen and dlclose.

+

The name of the library that has dlopen and dlclose in it, usually +-ldl on most UNIX machines.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DOTNET_SDK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DOTNET_SDK.html new file mode 100644 index 0000000000000000000000000000000000000000..690bd771a92f9ee86162391cb113fae5dfd8bda8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DOTNET_SDK.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_DOTNET_SDK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_DOTNET_SDK

+
+

New in version 3.23.

+
+

Default value for DOTNET_SDK property of targets.

+

This variable is used to initialize the DOTNET_SDK +property on all targets. See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..a96a889f68e732a02c56538e9d2b1681690f3478 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION.html @@ -0,0 +1,154 @@ + + + + + + + + + CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION

+
+

New in version 3.12.

+
+

Default value for DOTNET_TARGET_FRAMEWORK_VERSION +property of targets.

+

This variable is used to initialize the +DOTNET_TARGET_FRAMEWORK_VERSION property on all +targets. See that target property for additional information. When set, +CMAKE_DOTNET_TARGET_FRAMEWORK takes precednece over this +variable. See that variable or the associated target property +DOTNET_TARGET_FRAMEWORK for additional information.

+

Setting CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION may be necessary +when working with C# and newer .NET framework versions to +avoid referencing errors with the ALL_BUILD CMake target.

+

This variable is only evaluated for Visual Studio Generators +VS 2010 and above.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT.html new file mode 100644 index 0000000000000000000000000000000000000000..208c2b7bd51233595e598456aab42a64f5395b9b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT

+
+

New in version 3.6.

+
+

This cache variable is used by the Eclipse project generator. See +cmake-generators(7).

+

If this variable is set to TRUE, the Eclipse project generator will generate +an Eclipse project in CMAKE_SOURCE_DIR . This project can then +be used in Eclipse e.g. for the version control functionality. +CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT defaults to FALSE; so +nothing is written into the source directory.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ECLIPSE_MAKE_ARGUMENTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ECLIPSE_MAKE_ARGUMENTS.html new file mode 100644 index 0000000000000000000000000000000000000000..a65f364e5d39e0585b5999e62b406f11f5100cdb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ECLIPSE_MAKE_ARGUMENTS.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_ECLIPSE_MAKE_ARGUMENTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ECLIPSE_MAKE_ARGUMENTS

+
+

New in version 3.6.

+
+

This cache variable is used by the Eclipse project generator. See +cmake-generators(7).

+

This variable holds arguments which are used when Eclipse invokes the make +tool. By default it is initialized to hold flags to enable parallel builds +(using -j typically).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ECLIPSE_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ECLIPSE_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..ab51a3a1777a1e84a83dfd3baa09961219d444cf --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ECLIPSE_VERSION.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_ECLIPSE_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ECLIPSE_VERSION

+
+

New in version 3.6.

+
+

This cache variable is used by the Eclipse project generator. See +cmake-generators(7).

+

When using the Eclipse project generator, CMake tries to find the Eclipse +executable and detect the version of it. Depending on the version it finds, +some features are enabled or disabled. If CMake doesn't find +Eclipse, it assumes the oldest supported version, Eclipse Callisto (3.2).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION.html new file mode 100644 index 0000000000000000000000000000000000000000..83fe9c2f31fb3cea045f103b744e769c3dbd7ee1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION

+

Ask cmake_install.cmake script to error out as soon as a file with +absolute INSTALL DESTINATION is encountered.

+

The fatal error is emitted before the installation of the offending +file takes place. This variable is used by CMake-generated +cmake_install.cmake scripts. If one sets this variable to ON while +running the script, it may get fatal error messages from the script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXECUTABLE_SUFFIX_LANG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXECUTABLE_SUFFIX_LANG.html new file mode 100644 index 0000000000000000000000000000000000000000..0aa03342af4349ae58e2da49889b82247ec4982a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXECUTABLE_SUFFIX_LANG.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_EXECUTABLE_SUFFIX_<LANG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_EXECUTABLE_SUFFIX_<LANG>

+

The suffix to use for the end of an executable filename of <LANG> +compiler target architecture, if any.

+

It overrides CMAKE_EXECUTABLE_SUFFIX for language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXECUTE_PROCESS_COMMAND_ECHO.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXECUTE_PROCESS_COMMAND_ECHO.html new file mode 100644 index 0000000000000000000000000000000000000000..af5cd491bd6f559c772a220ea82f757bc9af35b8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXECUTE_PROCESS_COMMAND_ECHO.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_EXECUTE_PROCESS_COMMAND_ECHO — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_EXECUTE_PROCESS_COMMAND_ECHO

+
+

New in version 3.15.

+
+

If this variable is set to STDERR, STDOUT or NONE then commands +in execute_process() calls will be printed to either stderr or +stdout or not at all.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXE_LINKER_FLAGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXE_LINKER_FLAGS.html new file mode 100644 index 0000000000000000000000000000000000000000..475a5a1c84864ba0ee380d658ee153fe84a1231b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXE_LINKER_FLAGS.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_EXE_LINKER_FLAGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_EXE_LINKER_FLAGS

+

Linker flags to be used to create executables.

+

These flags will be used by the linker when creating an executable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..382fd9003738e9f7b9e9e37e0f295181d8435047 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_EXE_LINKER_FLAGS_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_EXE_LINKER_FLAGS_<CONFIG>

+

Flags to be used when linking an executable.

+

Same as CMAKE_C_FLAGS_* but used by the linker when creating +executables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG_INIT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG_INIT.html new file mode 100644 index 0000000000000000000000000000000000000000..0997a31355ad30b4271e0ea1ad2ab528f8565764 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXE_LINKER_FLAGS_CONFIG_INIT.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_EXE_LINKER_FLAGS_<CONFIG>_INIT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_EXE_LINKER_FLAGS_<CONFIG>_INIT

+
+

New in version 3.7.

+
+

Value used to initialize the CMAKE_EXE_LINKER_FLAGS_<CONFIG> +cache entry the first time a build tree is configured. +This variable is meant to be set by a toolchain file. CMake may prepend or append content to +the value based on the environment and target platform.

+

See also CMAKE_EXE_LINKER_FLAGS_INIT.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXPORT_COMPILE_COMMANDS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXPORT_COMPILE_COMMANDS.html new file mode 100644 index 0000000000000000000000000000000000000000..b1ce4963ff23cb7cb5fafd70c09ca011ca527b9f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXPORT_COMPILE_COMMANDS.html @@ -0,0 +1,173 @@ + + + + + + + + + CMAKE_EXPORT_COMPILE_COMMANDS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_EXPORT_COMPILE_COMMANDS

+
+

New in version 3.5.

+
+

Enable/Disable output of compile commands during generation.

+

If enabled, generates a compile_commands.json file containing the exact +compiler calls for all translation units of the project in machine-readable +form. The format of the JSON file looks like:

+
[
+  {
+    "directory": "/home/user/development/project",
+    "command": "/usr/bin/c++ ... -c ../foo/foo.cc",
+    "file": "../foo/foo.cc"
+  },
+
+  ...
+
+  {
+    "directory": "/home/user/development/project",
+    "command": "/usr/bin/c++ ... -c ../foo/bar.cc",
+    "file": "../foo/bar.cc"
+  }
+]
+
+
+

This is initialized by the CMAKE_EXPORT_COMPILE_COMMANDS environment +variable, and initializes the EXPORT_COMPILE_COMMANDS target +property for all targets.

+
+

Note

+

This option is implemented only by Makefile Generators +and Ninja Generators. It is ignored on other generators.

+

This option currently does not work well in combination with +the UNITY_BUILD target property or the +CMAKE_UNITY_BUILD variable.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXPORT_NO_PACKAGE_REGISTRY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXPORT_NO_PACKAGE_REGISTRY.html new file mode 100644 index 0000000000000000000000000000000000000000..8d9321ac61df51e38317da7cdc32e9caf3c0f07b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXPORT_NO_PACKAGE_REGISTRY.html @@ -0,0 +1,151 @@ + + + + + + + + + CMAKE_EXPORT_NO_PACKAGE_REGISTRY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_EXPORT_NO_PACKAGE_REGISTRY

+
+

New in version 3.1.

+
+

Disable the export(PACKAGE) command when CMP0090 +is not set to NEW.

+

In some cases, for example for packaging and for system wide +installations, it is not desirable to write the user package registry. +If the CMAKE_EXPORT_NO_PACKAGE_REGISTRY variable is enabled, +the export(PACKAGE) command will do nothing.

+

If CMP0090 is set to NEW this variable does nothing, and the +CMAKE_EXPORT_PACKAGE_REGISTRY variable controls the behavior +instead.

+

See also Disabling the Package Registry.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXPORT_PACKAGE_REGISTRY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXPORT_PACKAGE_REGISTRY.html new file mode 100644 index 0000000000000000000000000000000000000000..24598f652e9641e63dfd53febf7715fad7f90b54 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXPORT_PACKAGE_REGISTRY.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_EXPORT_PACKAGE_REGISTRY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_EXPORT_PACKAGE_REGISTRY

+
+

New in version 3.15.

+
+

Enables the export(PACKAGE) command when CMP0090 +is set to NEW.

+

The export(PACKAGE) command does nothing by default. In some cases +it is desirable to write to the user package registry, so the +CMAKE_EXPORT_PACKAGE_REGISTRY variable may be set to enable it.

+

If CMP0090 is not set to NEW this variable does nothing, and +the CMAKE_EXPORT_NO_PACKAGE_REGISTRY variable controls the behavior +instead.

+

See also Disabling the Package Registry.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXTRA_GENERATOR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXTRA_GENERATOR.html new file mode 100644 index 0000000000000000000000000000000000000000..6d792656f539adb456f977fff3291fb95c4a4ef4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXTRA_GENERATOR.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_EXTRA_GENERATOR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_EXTRA_GENERATOR

+
+

Deprecated since version 3.27: Support for Extra Generators is deprecated and will be removed from +a future version of CMake. IDEs may use the cmake-file-api(7) +to view CMake-generated project build trees.

+
+

The extra generator used to build the project. See +cmake-generators(7).

+

When using the Eclipse, CodeBlocks, CodeLite, Kate or Sublime generators, CMake +generates Makefiles (CMAKE_GENERATOR) and additionally project +files for the respective IDE. This IDE project file generator is stored in +CMAKE_EXTRA_GENERATOR (e.g. Eclipse CDT4).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXTRA_SHARED_LIBRARY_SUFFIXES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXTRA_SHARED_LIBRARY_SUFFIXES.html new file mode 100644 index 0000000000000000000000000000000000000000..e0d1a97de2ca7834761650e3541b6807dde7a5dd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_EXTRA_SHARED_LIBRARY_SUFFIXES.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_EXTRA_SHARED_LIBRARY_SUFFIXES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_EXTRA_SHARED_LIBRARY_SUFFIXES

+

Additional suffixes for shared libraries.

+

Extensions for shared libraries other than that specified by +CMAKE_SHARED_LIBRARY_SUFFIX, if any. CMake uses this to recognize +external shared library files during analysis of libraries linked by a +target.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_APPBUNDLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_APPBUNDLE.html new file mode 100644 index 0000000000000000000000000000000000000000..8d7a588fccf4e3cf1ae0e398ae91d5b048fa088e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_APPBUNDLE.html @@ -0,0 +1,157 @@ + + + + + + + + + CMAKE_FIND_APPBUNDLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_APPBUNDLE

+
+

New in version 3.4.

+
+

This variable affects how find_* commands choose between +macOS Application Bundles and unix-style package components.

+

On Darwin or systems supporting macOS Application Bundles, the +CMAKE_FIND_APPBUNDLE variable can be set to empty or +one of the following:

+
+
FIRST

Try to find application bundles before standard programs. +This is the default on Darwin.

+
+
LAST

Try to find application bundles after standard programs.

+
+
ONLY

Only try to find application bundles.

+
+
NEVER

Never try to find application bundles.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_DEBUG_MODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_DEBUG_MODE.html new file mode 100644 index 0000000000000000000000000000000000000000..b5026782db7b6854c66359f02e4ebeef87fc0513 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_DEBUG_MODE.html @@ -0,0 +1,159 @@ + + + + + + + + + CMAKE_FIND_DEBUG_MODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_DEBUG_MODE

+
+

New in version 3.17.

+
+

Print extra find call information for the following commands to standard +error:

+ +

Output is designed for human consumption and not for parsing. +Enabling this variable is equivalent to using cmake --debug-find +with the added ability to enable debugging for a subset of find calls.

+
set(CMAKE_FIND_DEBUG_MODE TRUE)
+find_program(...)
+set(CMAKE_FIND_DEBUG_MODE FALSE)
+
+
+

Default is unset.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_FRAMEWORK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_FRAMEWORK.html new file mode 100644 index 0000000000000000000000000000000000000000..7b8750a2792260ccc3113327ea5e7c68d7bd2340 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_FRAMEWORK.html @@ -0,0 +1,157 @@ + + + + + + + + + CMAKE_FIND_FRAMEWORK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_FRAMEWORK

+
+

New in version 3.4.

+
+

This variable affects how find_* commands choose between +macOS Frameworks and unix-style package components.

+

On Darwin or systems supporting macOS Frameworks, the +CMAKE_FIND_FRAMEWORK variable can be set to empty or +one of the following:

+
+
FIRST

Try to find frameworks before standard libraries or headers. +This is the default on Darwin.

+
+
LAST

Try to find frameworks after standard libraries or headers.

+
+
ONLY

Only try to find frameworks.

+
+
NEVER

Never try to find frameworks.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..a6278fc9d1fb819618571f325042c1d1587e7e62 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX

+
+

New in version 3.9.

+
+

Specify a <suffix> to tell the find_library() command to +search in a lib<suffix> directory before each lib directory that +would normally be searched.

+

This overrides the behavior of related global properties:

+ +
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_LIBRARY_PREFIXES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_LIBRARY_PREFIXES.html new file mode 100644 index 0000000000000000000000000000000000000000..9a6f75da45abc7b825c5938c468899665872cdb1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_LIBRARY_PREFIXES.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_FIND_LIBRARY_PREFIXES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_LIBRARY_PREFIXES

+

Prefixes to prepend when looking for libraries.

+

This specifies what prefixes to add to library names when the +find_library() command looks for libraries. On UNIX systems this is +typically lib, meaning that when trying to find the foo library it +will look for libfoo.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_LIBRARY_SUFFIXES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_LIBRARY_SUFFIXES.html new file mode 100644 index 0000000000000000000000000000000000000000..401532ef4eee566629133f97fefd47064968d878 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_LIBRARY_SUFFIXES.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_FIND_LIBRARY_SUFFIXES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_LIBRARY_SUFFIXES

+

Suffixes to append when looking for libraries.

+

This specifies what suffixes to add to library names when the +find_library() command looks for libraries. On Windows systems this +is typically .lib and, depending on the compiler, .dll.a, .a +(e.g. GCC and Clang), so when it tries to find the foo library, it will +look for [<prefix>]foo.lib and/or [<prefix>]foo[.dll].a, depending on +the compiler used and the <prefix> specified in the +CMAKE_FIND_LIBRARY_PREFIXES.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_NO_INSTALL_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_NO_INSTALL_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..bd339f3ef3a3bee6e334f4d1f5b8bd914efc93bc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_NO_INSTALL_PREFIX.html @@ -0,0 +1,152 @@ + + + + + + + + + CMAKE_FIND_NO_INSTALL_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_NO_INSTALL_PREFIX

+

Exclude the values of the CMAKE_INSTALL_PREFIX and +CMAKE_STAGING_PREFIX variables from +CMAKE_SYSTEM_PREFIX_PATH. CMake adds these project-destination +prefixes to CMAKE_SYSTEM_PREFIX_PATH by default in order to +support building a series of dependent packages and installing them into +a common prefix. Set CMAKE_FIND_NO_INSTALL_PREFIX to TRUE +to suppress this behavior.

+

The CMAKE_SYSTEM_PREFIX_PATH is initialized on the first call to a +project() or enable_language() command. Therefore one must +set CMAKE_FIND_NO_INSTALL_PREFIX before this in order to take effect. A +user may set the variable as a cache entry on the command line to achieve this.

+

Note that the prefix(es) may still be searched for other reasons, such as being +the same prefix as the CMake installation, or for being a built-in system +prefix.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..677d593493d541379dd490b56599c4419bc25d9c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_NAME.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_FIND_PACKAGE_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_PACKAGE_NAME

+
+

New in version 3.1.1.

+
+

Defined by the find_package() command while loading +a find module to record the caller-specified package name. +See command documentation for details.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY.html new file mode 100644 index 0000000000000000000000000000000000000000..c7616f82d15e3e1605f7ed19b3e2efa49cd41387 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY.html @@ -0,0 +1,158 @@ + + + + + + + + + CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY

+
+

New in version 3.1.

+
+
+

Deprecated since version 3.16: Use the CMAKE_FIND_USE_PACKAGE_REGISTRY variable instead.

+
+

By default this variable is not set. If neither +CMAKE_FIND_USE_PACKAGE_REGISTRY nor +CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY is set, then +find_package() will use the User Package Registry +unless the NO_CMAKE_PACKAGE_REGISTRY option is provided.

+

CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY is ignored if +CMAKE_FIND_USE_PACKAGE_REGISTRY is set.

+

In some cases, for example to locate only system wide installations, it +is not desirable to use the User Package Registry when searching +for packages. If the CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY +variable is TRUE, all the find_package() commands will skip +the User Package Registry as if they were called with the +NO_CMAKE_PACKAGE_REGISTRY argument.

+

See also Disabling the Package Registry.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_PREFER_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_PREFER_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..4c79782ca4826aabcc2fc4756b6ae4fbf9194499 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_PREFER_CONFIG.html @@ -0,0 +1,161 @@ + + + + + + + + + CMAKE_FIND_PACKAGE_PREFER_CONFIG — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_PACKAGE_PREFER_CONFIG

+
+

New in version 3.15.

+
+

Tell find_package() to try "Config" mode before "Module" mode if no +mode was specified.

+

The command find_package() operates without an explicit mode when +the reduced signature is used without the MODULE option. In this case, +by default, CMake first tries Module mode by searching for a +Find<pkg>.cmake module. If it fails, CMake then searches for the package +using Config mode.

+

Set CMAKE_FIND_PACKAGE_PREFER_CONFIG to TRUE to tell +find_package() to first search using Config mode before falling back +to Module mode.

+

This variable may be useful when a developer has compiled a custom version of +a common library and wishes to link it to a dependent project. If this +variable is set to TRUE, it would prevent a dependent project's call +to find_package() from selecting the default library located by the +system's Find<pkg>.cmake module before finding the developer's custom +built library.

+

Once this variable is set, it is the responsibility of the exported +<pkg>Config.cmake files to provide the same result variables as the +Find<pkg>.cmake modules so that dependent projects can use them +interchangeably.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_REDIRECTS_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_REDIRECTS_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..42dc08ab71a1e1596eb0190e0b544d82438132c9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_REDIRECTS_DIR.html @@ -0,0 +1,161 @@ + + + + + + + + + CMAKE_FIND_PACKAGE_REDIRECTS_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_PACKAGE_REDIRECTS_DIR

+
+

New in version 3.24.

+
+

This read-only variable specifies a directory that the find_package() +command will check first before searching anywhere else for a module or config +package file. A config package file in this directory will always be found in +preference to any other Find module file or config package file.

+

The primary purpose of this variable is to facilitate integration between +find_package() and FetchContent_MakeAvailable(). The latter +command may create files in the CMAKE_FIND_PACKAGE_REDIRECTS_DIR directory +when it populates a dependency. This allows subsequent calls to +find_package() for the same dependency to re-use the populated +contents instead of trying to satisfy the dependency from somewhere external +to the build. Projects may also want to write files into this directory in +some situations (see Integrating With find_package() +for examples).

+

The directory that CMAKE_FIND_PACKAGE_REDIRECTS_DIR points to will always +be erased and recreated empty at the start of every CMake run. Any files +written into this directory during the CMake run will be lost the next time +CMake configures the project.

+

CMAKE_FIND_PACKAGE_REDIRECTS_DIR is only set in CMake project mode. +It is not set when CMake is run in script mode +(i.e. cmake -P).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_TARGETS_GLOBAL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_TARGETS_GLOBAL.html new file mode 100644 index 0000000000000000000000000000000000000000..c431bb7dc05157b60a03d0a7816e5f12d1a90901 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_TARGETS_GLOBAL.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_FIND_PACKAGE_TARGETS_GLOBAL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_PACKAGE_TARGETS_GLOBAL

+
+

New in version 3.24.

+
+

Setting to TRUE promotes all IMPORTED targets discoverd +by find_package() to a GLOBAL scope.

+

Setting this to TRUE is akin to specifying GLOBAL +as an argument to find_package(). +Default value is OFF.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_WARN_NO_MODULE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_WARN_NO_MODULE.html new file mode 100644 index 0000000000000000000000000000000000000000..26a4036e58423b672aa854503528857131fbdd0e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_PACKAGE_WARN_NO_MODULE.html @@ -0,0 +1,154 @@ + + + + + + + + + CMAKE_FIND_PACKAGE_WARN_NO_MODULE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_PACKAGE_WARN_NO_MODULE

+

Tell find_package() to warn if called without an explicit mode.

+

If find_package() is called without an explicit mode option +(MODULE, CONFIG, or NO_MODULE) and no Find<pkg>.cmake module +is in CMAKE_MODULE_PATH then CMake implicitly assumes that the +caller intends to search for a package configuration file. If no package +configuration file is found then the wording of the failure message +must account for both the case that the package is really missing and +the case that the project has a bug and failed to provide the intended +Find module. If instead the caller specifies an explicit mode option +then the failure message can be more specific.

+

Set CMAKE_FIND_PACKAGE_WARN_NO_MODULE to TRUE to tell +find_package() to warn when it implicitly assumes Config mode. This +helps developers enforce use of an explicit mode in all calls to +find_package() within a project.

+

This variable has no effect if CMAKE_FIND_PACKAGE_PREFER_CONFIG is +set to TRUE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_ROOT_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_ROOT_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..f21fba7391d12c8dd34952aa3040b4d45abc6fa5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_ROOT_PATH.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_FIND_ROOT_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_ROOT_PATH

+

Semicolon-separated list of root paths to search on the filesystem.

+

This variable is most useful when cross-compiling. CMake uses the paths in +this list as alternative roots to find filesystem items with +find_package(), find_library() etc.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_ROOT_PATH_MODE_INCLUDE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_ROOT_PATH_MODE_INCLUDE.html new file mode 100644 index 0000000000000000000000000000000000000000..f186a32969a6c88c496e0208db78f3e158d2adf7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_ROOT_PATH_MODE_INCLUDE.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_FIND_ROOT_PATH_MODE_INCLUDE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_ROOT_PATH_MODE_INCLUDE

+

This variable controls whether the CMAKE_FIND_ROOT_PATH and +CMAKE_SYSROOT are used by find_file() and find_path().

+

If set to ONLY, then only the roots in CMAKE_FIND_ROOT_PATH +will be searched. If set to NEVER, then the roots in +CMAKE_FIND_ROOT_PATH will be ignored and only the host system +root will be used. If set to BOTH, then the host system paths and the +paths in CMAKE_FIND_ROOT_PATH will be searched.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_ROOT_PATH_MODE_PROGRAM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_ROOT_PATH_MODE_PROGRAM.html new file mode 100644 index 0000000000000000000000000000000000000000..ae4b0b1a956d584dd52f1ccf3944d9858ba7c312 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_ROOT_PATH_MODE_PROGRAM.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_FIND_ROOT_PATH_MODE_PROGRAM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_ROOT_PATH_MODE_PROGRAM

+

This variable controls whether the CMAKE_FIND_ROOT_PATH and +CMAKE_SYSROOT are used by find_program().

+

If set to ONLY, then only the roots in CMAKE_FIND_ROOT_PATH +will be searched. If set to NEVER, then the roots in +CMAKE_FIND_ROOT_PATH will be ignored and only the host system +root will be used. If set to BOTH, then the host system paths and the +paths in CMAKE_FIND_ROOT_PATH will be searched.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_CMAKE_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_CMAKE_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..3a542f4c6853835a187f25b22c36a0c7165919ca --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_CMAKE_PATH.html @@ -0,0 +1,160 @@ + + + + + + + + + CMAKE_FIND_USE_CMAKE_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_USE_CMAKE_PATH

+
+

New in version 3.16.

+
+

Controls the default behavior of the following commands for whether or not to +search paths provided by cmake-specific cache variables:

+ +

This is useful in cross-compiling environments.

+

By default this variable is not set, which is equivalent to it having +a value of TRUE. Explicit options given to the above commands +take precedence over this variable.

+

See also the CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH, +CMAKE_FIND_USE_CMAKE_SYSTEM_PATH, +CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH, +CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY, +CMAKE_FIND_USE_PACKAGE_REGISTRY, +and CMAKE_FIND_USE_PACKAGE_ROOT_PATH variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_CMAKE_SYSTEM_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_CMAKE_SYSTEM_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..e786edd63e1d2c3d784fff71b61d12a63e582f4a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_CMAKE_SYSTEM_PATH.html @@ -0,0 +1,161 @@ + + + + + + + + + CMAKE_FIND_USE_CMAKE_SYSTEM_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_USE_CMAKE_SYSTEM_PATH

+
+

New in version 3.16.

+
+

Controls the default behavior of the following commands for whether or not to +search paths provided by platform-specific cmake variables:

+ +

This is useful in cross-compiling environments.

+

By default this variable is not set, which is equivalent to it having +a value of TRUE. Explicit options given to the above commands +take precedence over this variable.

+

See also the CMAKE_FIND_USE_CMAKE_PATH, +CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH, +CMAKE_FIND_USE_INSTALL_PREFIX, +CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH, +CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY, +CMAKE_FIND_USE_PACKAGE_REGISTRY, +and CMAKE_FIND_USE_PACKAGE_ROOT_PATH variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_INSTALL_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_INSTALL_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..e2d3792f06fed740e7044edf9f4829b9212183d3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_INSTALL_PREFIX.html @@ -0,0 +1,196 @@ + + + + + + + + + CMAKE_FIND_USE_INSTALL_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_USE_INSTALL_PREFIX

+
+

New in version 3.24.

+
+

Controls the default behavior of the following commands for whether or not to +search the locations in the CMAKE_INSTALL_PREFIX and +CMAKE_STAGING_PREFIX variables.

+ +

This is useful in cross-compiling environments.

+

Due to backwards compatibility with CMAKE_FIND_NO_INSTALL_PREFIX, +the behavior of the find command change based on if this variable exists.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

CMAKE_FIND_USE_INSTALL_PREFIX

CMAKE_FIND_NO_INSTALL_PREFIX

Search

Not Defined

On

NO

Not Defined

Off || Not Defined

YES

Off

On

NO

Off

Off || Not Defined

NO

On

On

YES

On

Off || Not Defined

YES

+

By default this variable is not defined. Explicit options given to the above +commands take precedence over this variable.

+

See also the CMAKE_FIND_USE_CMAKE_PATH, +CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH, +CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH, +CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY, +CMAKE_FIND_USE_PACKAGE_REGISTRY, +and CMAKE_FIND_USE_PACKAGE_ROOT_PATH variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_PACKAGE_REGISTRY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_PACKAGE_REGISTRY.html new file mode 100644 index 0000000000000000000000000000000000000000..3aa8fabc8290128a83cdf6ca49a0625bec462187 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_PACKAGE_REGISTRY.html @@ -0,0 +1,165 @@ + + + + + + + + + CMAKE_FIND_USE_PACKAGE_REGISTRY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_USE_PACKAGE_REGISTRY

+
+

New in version 3.16.

+
+

Controls the default behavior of the find_package() command for +whether or not to search paths provided by the User Package Registry.

+

By default this variable is not set and the behavior will fall back +to that determined by the deprecated +CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY variable. If that is +also not set, then find_package() will use the +User Package Registry unless the NO_CMAKE_PACKAGE_REGISTRY option +is provided.

+

This variable takes precedence over +CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY when both are set.

+

In some cases, for example to locate only system wide installations, it +is not desirable to use the User Package Registry when searching +for packages. If the CMAKE_FIND_USE_PACKAGE_REGISTRY +variable is FALSE, all the find_package() commands will skip +the User Package Registry as if they were called with the +NO_CMAKE_PACKAGE_REGISTRY argument.

+

See also Disabling the Package Registry and the +CMAKE_FIND_USE_CMAKE_PATH, +CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH, +CMAKE_FIND_USE_INSTALL_PREFIX, +CMAKE_FIND_USE_CMAKE_SYSTEM_PATH, +CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH, +CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY, +and CMAKE_FIND_USE_PACKAGE_ROOT_PATH variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..30bb77484b969a7ee178acca98adb4f863000a75 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH.html @@ -0,0 +1,161 @@ + + + + + + + + + CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH

+
+

New in version 3.16.

+
+

Controls the default behavior of the following commands for whether or not to +search paths provided by standard system environment variables:

+ +

This is useful in cross-compiling environments.

+

By default this variable is not set, which is equivalent to it having +a value of TRUE. Explicit options given to the above commands +take precedence over this variable.

+

See also the CMAKE_FIND_USE_CMAKE_PATH, +CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH, +CMAKE_FIND_USE_INSTALL_PREFIX, +CMAKE_FIND_USE_CMAKE_SYSTEM_PATH, +CMAKE_FIND_USE_PACKAGE_REGISTRY, +CMAKE_FIND_USE_PACKAGE_ROOT_PATH, +and CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FOLDER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FOLDER.html new file mode 100644 index 0000000000000000000000000000000000000000..142f9d3f665c358cd236a99fc3d4ae2a6b3af894 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FOLDER.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_FOLDER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FOLDER

+
+

New in version 3.12.

+
+

Set the folder name. Use to organize targets in an IDE.

+

This variable is used to initialize the FOLDER property on all the +targets. See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..abc7dc83f3f9de368e17be36d399d88f17fa19c9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_CONFIG.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG>

+
+

New in version 3.18.

+
+

Default framework filename postfix under configuration <CONFIG> when +using a multi-config generator.

+

When a framework target is created its FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG> +target property is initialized with the value of this variable if it is set.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FRAMEWORK_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FRAMEWORK_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..85aa17d18214e8e1a7387a137d46071838f1cad9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_FRAMEWORK_PATH.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_FRAMEWORK_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_FRAMEWORK_PATH

+

Semicolon-separated list of directories specifying a search path +for macOS frameworks used by the find_library(), +find_package(), find_path(), and find_file() +commands.

+

There is also an environment variable CMAKE_FRAMEWORK_PATH, which is used +as an additional list of search directories.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODDIR_DEFAULT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODDIR_DEFAULT.html new file mode 100644 index 0000000000000000000000000000000000000000..e44d3e99efb4142a8e51667a59f0cca8c7b97802 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODDIR_DEFAULT.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_Fortran_MODDIR_DEFAULT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_Fortran_MODDIR_DEFAULT

+

Fortran default module output directory.

+

Most Fortran compilers write .mod files to the current working +directory. For those that do not, this is set to . and used when +the Fortran_MODULE_DIRECTORY target property is not set.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODDIR_FLAG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODDIR_FLAG.html new file mode 100644 index 0000000000000000000000000000000000000000..c9bfa3b764e789db71bad323161fbb00bbeb6ad1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODDIR_FLAG.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_Fortran_MODDIR_FLAG — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_Fortran_MODDIR_FLAG

+

Fortran flag for module output directory.

+

This stores the flag needed to pass the value of the +Fortran_MODULE_DIRECTORY target property to the compiler.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODOUT_FLAG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODOUT_FLAG.html new file mode 100644 index 0000000000000000000000000000000000000000..91325167b5d0d0c0c4a5094df243503077563a22 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODOUT_FLAG.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_Fortran_MODOUT_FLAG — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_Fortran_MODOUT_FLAG

+

Fortran flag to enable module output.

+

Most Fortran compilers write .mod files out by default. For others, +this stores the flag needed to enable module output.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODULE_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODULE_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..ef076609448bd4bd06d389a75cc2f99186729b71 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_MODULE_DIRECTORY.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_Fortran_MODULE_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_Fortran_MODULE_DIRECTORY

+

Fortran module output directory.

+

This variable is used to initialize the Fortran_MODULE_DIRECTORY +property on all the targets. See that target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_PREPROCESS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_PREPROCESS.html new file mode 100644 index 0000000000000000000000000000000000000000..0d9c4a53b9cfcb65591d4332708075f17e09b6d0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Fortran_PREPROCESS.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_Fortran_PREPROCESS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_Fortran_PREPROCESS

+
+

New in version 3.18.

+
+

Default value for Fortran_PREPROCESS of targets.

+

This variable is used to initialize the Fortran_PREPROCESS +property on all the targets. See that target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GENERATOR_INSTANCE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GENERATOR_INSTANCE.html new file mode 100644 index 0000000000000000000000000000000000000000..6fe060fdc054b725fef453749b49c62ad0221942 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GENERATOR_INSTANCE.html @@ -0,0 +1,219 @@ + + + + + + + + + CMAKE_GENERATOR_INSTANCE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_GENERATOR_INSTANCE

+
+

New in version 3.11.

+
+

Generator-specific instance specification provided by user.

+

Some CMake generators support selection of an instance of the native build +system when multiple instances are available. If the user specifies an +instance (e.g. by setting this cache entry or via the +CMAKE_GENERATOR_INSTANCE environment variable), or after a default +instance is chosen when a build tree is first configured, the value will be +available in this variable.

+

The value of this variable should never be modified by project code. +A toolchain file specified by the CMAKE_TOOLCHAIN_FILE +variable may initialize CMAKE_GENERATOR_INSTANCE as a cache entry. +Once a given build tree has been initialized with a particular value +for this variable, changing the value has undefined behavior.

+

Instance specification is supported only on specific generators.

+
+

Visual Studio Instance Selection

+

Visual Studio Generators support instance specification for +Visual Studio 2017 and above. The CMAKE_GENERATOR_INSTANCE variable +may be set as a cache entry selecting an instance of Visual Studio +via one of the following forms:

+
    +
  • location

  • +
  • location[,key=value]*

  • +
  • key=value[,key=value]*

  • +
+

The location specifies the absolute path to the top-level directory +of the VS installation.

+

The key=value pairs form a comma-separated list of options to +specify details of the instance selection. +Supported pairs are:

+
+
version=<major>.<minor>.<date>.<build>
+

New in version 3.23.

+
+

Specify the 4-component VS Build Version, a.k.a. Build Number.

+

The components are:

+

<major>.<minor>

+
+

The VS major and minor version numbers. +These are the same as the release version numbers.

+
+

<date>

+
+

A build date in the format MMMDD, where MMM is a month index +since an epoch used by Microsoft, and DD is a day in that month.

+
+

<build>

+
+

A build index on the day represented by <date>.

+
+

The build number is reported by vswhere as installationVersion. +For example, VS 16.11.10 has build number 16.11.32126.315.

+
+
+
+

New in version 3.23: A portable VS instance, which is not known to the Visual Studio Installer, +may be specified by providing both location and version=.

+
+

If the value of CMAKE_GENERATOR_INSTANCE is not specified explicitly +by the user or a toolchain file, CMake queries the Visual Studio Installer +to locate VS instances, chooses one, and sets the variable as a cache entry +to hold the value persistently. If an environment variable of the form +VS##0COMNTOOLS, where ## the Visual Studio major version number, +is set and points to the Common7/Tools directory within one of the +VS instances, that instance will be used. Otherwise, if more than one +VS instance is installed we do not define which one is chosen by default.

+

The VS version build number of the selected VS instance is provided in +the CMAKE_VS_VERSION_BUILD_NUMBER variable.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GENERATOR_PLATFORM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GENERATOR_PLATFORM.html new file mode 100644 index 0000000000000000000000000000000000000000..c8a9c0b8558d014cbde96fe9c52ee699645acc34 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GENERATOR_PLATFORM.html @@ -0,0 +1,212 @@ + + + + + + + + + CMAKE_GENERATOR_PLATFORM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_GENERATOR_PLATFORM

+
+

New in version 3.1.

+
+

Generator-specific target platform specification provided by user.

+

Some CMake generators support a target platform name to be given +to the native build system to choose a compiler toolchain. +If the user specifies a platform name (e.g. via the cmake -A +option or via the CMAKE_GENERATOR_PLATFORM environment variable) +the value will be available in this variable.

+

The value of this variable should never be modified by project code. +A toolchain file specified by the CMAKE_TOOLCHAIN_FILE +variable may initialize CMAKE_GENERATOR_PLATFORM. Once a given +build tree has been initialized with a particular value for this +variable, changing the value has undefined behavior.

+

Platform specification is supported only on specific generators:

+ +

See native build system documentation for allowed platform names.

+
+

Visual Studio Platform Selection

+

The Visual Studio Generators support platform specification +using one of these forms:

+
    +
  • platform

  • +
  • platform[,key=value]*

  • +
  • key=value[,key=value]*

  • +
+

The platform specifies the target platform (VS target architecture), +such as x64, ARM64, or Win32. The selected platform +name is provided in the CMAKE_VS_PLATFORM_NAME variable.

+

The key=value pairs form a comma-separated list of options to +specify generator-specific details of the platform selection. +Supported pairs are:

+
+
version=<version>
+

New in version 3.27.

+
+

Specify the Windows SDK version to use. This is supported by VS 2015 and +above when targeting Windows or Windows Store. CMake will set the +CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION variable to the +selected SDK version.

+

The <version> may be one of:

+
+
10.0

Specify that any 10.0 SDK version may be used, and let Visual Studio +pick one. This is supported by VS 2019 and above.

+
+
10.0.<build>.<increment>

Specify the exact 4-component SDK version, e.g., 10.0.19041.0. +The specified version of the SDK must be installed. It may not exceed +the value of CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM, +if that variable is set.

+
+
8.1

Specify the 8.1 SDK version. This is always supported by VS 2015. +On VS 2017 and above the 8.1 SDK must be installed.

+
+
+

If the version field is not specified, CMake selects a version as +described in the CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION +variable documentation.

+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GENERATOR_TOOLSET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GENERATOR_TOOLSET.html new file mode 100644 index 0000000000000000000000000000000000000000..b3a2acfa90722f9b941a9d0d0fec4d52f5435e63 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GENERATOR_TOOLSET.html @@ -0,0 +1,228 @@ + + + + + + + + + CMAKE_GENERATOR_TOOLSET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_GENERATOR_TOOLSET

+

Native build system toolset specification provided by user.

+

Some CMake generators support a toolset specification to tell the +native build system how to choose a compiler. If the user specifies +a toolset (e.g. via the cmake -T option or via +the CMAKE_GENERATOR_TOOLSET environment variable) the value +will be available in this variable.

+

The value of this variable should never be modified by project code. +A toolchain file specified by the CMAKE_TOOLCHAIN_FILE +variable may initialize CMAKE_GENERATOR_TOOLSET. Once a given +build tree has been initialized with a particular value for this +variable, changing the value has undefined behavior.

+

Toolset specification is supported only on specific generators:

+ +

See native build system documentation for allowed toolset names.

+
+

Visual Studio Toolset Selection

+

The Visual Studio Generators support toolset specification +using one of these forms:

+
    +
  • toolset

  • +
  • toolset[,key=value]*

  • +
  • key=value[,key=value]*

  • +
+

The toolset specifies the toolset name. The selected toolset name +is provided in the CMAKE_VS_PLATFORM_TOOLSET variable.

+

The key=value pairs form a comma-separated list of options to +specify generator-specific details of the toolset selection. +Supported pairs are:

+
+
cuda=<version>|<path>

Specify the CUDA toolkit version to use or the path to a +standalone CUDA toolkit directory. Supported by VS 2010 +and above. The version can only be used with the CUDA +toolkit VS integration globally installed. +See the CMAKE_VS_PLATFORM_TOOLSET_CUDA and +CMAKE_VS_PLATFORM_TOOLSET_CUDA_CUSTOM_DIR variables.

+
+
host=<arch>

Specify the host tools architecture as x64 or x86. +Supported by VS 2013 and above. +See the CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE +variable.

+
+
version=<version>

Specify the toolset version to use. Supported by VS 2017 +and above with the specified toolset installed. +See the CMAKE_VS_PLATFORM_TOOLSET_VERSION variable.

+
+
VCTargetsPath=<path>

Specify an alternative VCTargetsPath value for Visual Studio +project files. This allows use of VS platform extension configuration +files (.props and .targets) that are not installed with VS.

+
+
+
+
+

Visual Studio Toolset Customization

+

These are unstable interfaces with no compatibility guarantees +because they hook into undocumented internal CMake implementation details. +Institutions may use these to internally maintain support for non-public +Visual Studio platforms and toolsets, but must accept responsibility to +make updates as changes are made to CMake.

+

Additional key=value pairs are available:

+
+
customFlagTableDir=<path>
+

New in version 3.21.

+
+

Specify the absolute path to a directory from which to load custom +flag tables stored as JSON documents with file names of the form +<platform>_<toolset>_<tool>.json or <platform>_<tool>.json, +where <platform> is the CMAKE_VS_PLATFORM_NAME, +<toolset> is the CMAKE_VS_PLATFORM_TOOLSET, +and <tool> is the tool for which the flag table is meant. +This naming pattern is an internal CMake implementation detail. +The <tool> names are undocumented. The format of the .json +flag table files is undocumented.

+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GLOBAL_AUTOGEN_TARGET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GLOBAL_AUTOGEN_TARGET.html new file mode 100644 index 0000000000000000000000000000000000000000..f6324537de0abcdea0a572ba2cce21b9110cd4e9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GLOBAL_AUTOGEN_TARGET.html @@ -0,0 +1,169 @@ + + + + + + + + + CMAKE_GLOBAL_AUTOGEN_TARGET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_GLOBAL_AUTOGEN_TARGET

+
+

New in version 3.14.

+
+

Switch to enable generation of a global autogen target.

+

When CMAKE_GLOBAL_AUTOGEN_TARGET is enabled, a custom target +autogen is generated. This target depends on all AUTOMOC and +AUTOUIC generated <ORIGIN>_autogen targets in the project. +By building the global autogen target, all AUTOMOC and +AUTOUIC files in the project will be generated.

+

The name of the global autogen target can be changed by setting +CMAKE_GLOBAL_AUTOGEN_TARGET_NAME.

+

By default CMAKE_GLOBAL_AUTOGEN_TARGET is unset.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+

Note

+

<ORIGIN>_autogen targets by default inherit their origin target's +dependencies. This might result in unintended dependency target +builds when only <ORIGIN>_autogen targets are built. A solution is to +disable AUTOGEN_ORIGIN_DEPENDS on the respective origin targets.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GLOBAL_AUTORCC_TARGET_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GLOBAL_AUTORCC_TARGET_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..74c97e5396174713273c0ebac870bb5a5cc25b3f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GLOBAL_AUTORCC_TARGET_NAME.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_GLOBAL_AUTORCC_TARGET_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_GLOBAL_AUTORCC_TARGET_NAME

+
+

New in version 3.14.

+
+

Change the name of the global autorcc target.

+

When CMAKE_GLOBAL_AUTORCC_TARGET is enabled, a global custom target +named autorcc is created. CMAKE_GLOBAL_AUTORCC_TARGET_NAME +allows to set a different name for that target.

+

By default CMAKE_GLOBAL_AUTORCC_TARGET_NAME is unset.

+

See the cmake-qt(7) manual for more information on using CMake +with Qt.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GNUtoMS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GNUtoMS.html new file mode 100644 index 0000000000000000000000000000000000000000..8e940e10cbb1498be0932fdb54cbecf6e5d6ca49 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_GNUtoMS.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_GNUtoMS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_GNUtoMS

+

Convert GNU import libraries (.dll.a) to MS format (.lib).

+

This variable is used to initialize the GNUtoMS property on +targets when they are created. See that target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HIP_ARCHITECTURES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HIP_ARCHITECTURES.html new file mode 100644 index 0000000000000000000000000000000000000000..f909444fe6ee1d02c840f5dfdbe6fc4e3063ac09 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HIP_ARCHITECTURES.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_HIP_ARCHITECTURES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_HIP_ARCHITECTURES

+
+

New in version 3.21.

+
+

Default value for HIP_ARCHITECTURES property of targets.

+

This is initialized to the architectures reported by rocm_agent_enumerator, +if available, and otherwise to the default chosen by the compiler.

+

This variable is used to initialize the HIP_ARCHITECTURES property +on all targets. See the target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HIP_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HIP_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..abb52cb60a81ccb7e5aed77edcb6deeba4cfbdbe --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HIP_EXTENSIONS.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_HIP_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_HIP_EXTENSIONS

+
+

New in version 3.21.

+
+

Default value for HIP_EXTENSIONS target property if set when a +target is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOME_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOME_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..e67aae8a0710ef377035c4be99bc738fd125c7fd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOME_DIRECTORY.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_HOME_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_HOME_DIRECTORY

+

Path to top of source tree. Same as CMAKE_SOURCE_DIR.

+

This is an internal cache entry used to locate the source directory +when loading a CMakeCache.txt from a build tree. It should not +be used in project code. The variable CMAKE_SOURCE_DIR +has the same value and should be preferred.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_BSD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_BSD.html new file mode 100644 index 0000000000000000000000000000000000000000..4f7e502594dc8ad641b27cd28f7570c95e50cc8c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_BSD.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_HOST_BSD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_HOST_BSD

+
+

New in version 3.25.

+
+

Set to a string value when the host system is BSD. This value can be one of +the following: DragonFlyBSD, FreeBSD, OpenBSD, or NetBSD.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_LINUX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_LINUX.html new file mode 100644 index 0000000000000000000000000000000000000000..85b8c123b2616b377ec56aa801d1eaba775a5274 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_LINUX.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_HOST_LINUX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_HOST_LINUX

+
+

New in version 3.25.

+
+

Set to true when the host system is Linux.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_SYSTEM_PROCESSOR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_SYSTEM_PROCESSOR.html new file mode 100644 index 0000000000000000000000000000000000000000..5a8e8579a4f0e96efba33d95dc6d57709bfc20c8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_SYSTEM_PROCESSOR.html @@ -0,0 +1,187 @@ + + + + + + + + + CMAKE_HOST_SYSTEM_PROCESSOR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_HOST_SYSTEM_PROCESSOR

+

The name of the CPU CMake is running on.

+
+

Windows Platforms

+

On Windows, this variable is set to the value of the environment variable +PROCESSOR_ARCHITECTURE.

+
+
+

Unix Platforms

+

On systems that support uname, this variable is set to the output of:

+
    +
  • uname -m on GNU, Linux, Cygwin, Android, or

  • +
  • arch on OpenBSD, or

  • +
  • on other systems,

    +
      +
    • uname -p if its exit code is nonzero, or

    • +
    • uname -m otherwise.

    • +
    +
  • +
+
+
+

macOS Platforms

+

The value of uname -m is used by default.

+

On Apple Silicon hosts, the architecture printed by uname -m may vary +based on CMake's own architecture and that of the invoking process tree.

+
+

New in version 3.19.2: On Apple Silicon hosts:

+ +
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_SYSTEM_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_SYSTEM_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..014999dd4bd344d96cd771c10ff7e5abf434109f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_SYSTEM_VERSION.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_HOST_SYSTEM_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_HOST_SYSTEM_VERSION

+

The OS version CMake is running on.

+

A numeric version string for the system. On systems that support +uname, this variable is set to the output of uname -r. On other +systems this is set to major-minor version numbers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_UNIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_UNIX.html new file mode 100644 index 0000000000000000000000000000000000000000..c080a85832f3f403d230c2789c2138f9a742dfdc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_UNIX.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_HOST_UNIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_HOST_UNIX

+

True for UNIX and UNIX like operating systems.

+

Set to true when the host system is UNIX or UNIX like (i.e. APPLE and +CYGWIN).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_WIN32.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_WIN32.html new file mode 100644 index 0000000000000000000000000000000000000000..83d7d5750d749d5e0c5aa03682217e0ccfdb8d49 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_HOST_WIN32.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_HOST_WIN32 — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_HOST_WIN32

+

True if the host system is running Windows, including Windows 64-bit and MSYS.

+

Set to false on Cygwin.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IGNORE_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IGNORE_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..f118249031bc29cdc78f6a9dcb502b5175b270c1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IGNORE_PATH.html @@ -0,0 +1,170 @@ + + + + + + + + + CMAKE_IGNORE_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_IGNORE_PATH

+

Semicolon-separated list of directories +to be ignored by the various find...() commands.

+

For find_program(), find_library(), find_file(), +and find_path(), any file found in one of the listed directories +will be ignored. The listed directories do not apply recursively, so any +subdirectories to be ignored must also be explicitly listed. +CMAKE_IGNORE_PATH does not affect the search prefixes used by these +four commands. To ignore individual paths under a search prefix +(e.g. bin, include, lib, etc.), each path must be listed in +CMAKE_IGNORE_PATH as a full absolute path. CMAKE_IGNORE_PREFIX_PATH +provides a more appropriate way to ignore a whole search prefix.

+

find_package() is also affected by CMAKE_IGNORE_PATH, but only +for Config mode searches. Any <Name>Config.cmake or +<name>-config.cmake file found in one of the specified directories +will be ignored. In addition, any search prefix found in CMAKE_IGNORE_PATH +will be skipped for backward compatibility reasons, but new code should +prefer to use CMAKE_IGNORE_PREFIX_PATH to ignore prefixes instead.

+

Ignoring search locations can be useful in cross-compiling environments where +some system directories contain incompatible but possibly linkable libraries. +For example, on cross-compiled cluster environments, this allows a user to +ignore directories containing libraries meant for the front-end machine.

+

By default, CMAKE_IGNORE_PATH is empty. It is intended to be set by the +project or the end user.

+

See also the following variables:

+ +
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IMPORT_LIBRARY_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IMPORT_LIBRARY_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..566556e0cab76bbf89c89090af8d74319add34b7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IMPORT_LIBRARY_PREFIX.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_IMPORT_LIBRARY_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_IMPORT_LIBRARY_PREFIX

+

The prefix for import libraries that you link to.

+

The prefix to use for the name of an import library if used on this +platform.

+

CMAKE_IMPORT_LIBRARY_PREFIX_<LANG> overrides this for language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IMPORT_LIBRARY_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IMPORT_LIBRARY_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..3a0ef15b74d877cf19f7168f6ddc4c4a4c9eef13 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IMPORT_LIBRARY_SUFFIX.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_IMPORT_LIBRARY_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_IMPORT_LIBRARY_SUFFIX

+

The suffix for import libraries that you link to.

+

The suffix to use for the end of an import library filename if used on +this platform.

+

CMAKE_IMPORT_LIBRARY_SUFFIX_<LANG> overrides this for language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_CURRENT_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_CURRENT_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..6a0c54f1affedc977bcd06de7791ecc7c1eab389 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_CURRENT_DIR.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_INCLUDE_CURRENT_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_INCLUDE_CURRENT_DIR

+

Automatically add the current source and build directories to the include path.

+

If this variable is enabled, CMake automatically adds +CMAKE_CURRENT_SOURCE_DIR and CMAKE_CURRENT_BINARY_DIR +to the include path for each directory. These additional include +directories do not propagate down to subdirectories. This is useful +mainly for out-of-source builds, where files generated into the build +tree are included by files located in the source tree.

+

By default CMAKE_INCLUDE_CURRENT_DIR is OFF.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_DIRECTORIES_BEFORE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_DIRECTORIES_BEFORE.html new file mode 100644 index 0000000000000000000000000000000000000000..e365855e662a5fe3981353375ae2cd2adf6c4c7b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_DIRECTORIES_BEFORE.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_INCLUDE_DIRECTORIES_BEFORE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_INCLUDE_DIRECTORIES_BEFORE

+

Whether to append or prepend directories by default in +include_directories().

+

This variable affects the default behavior of the include_directories() +command. Setting this variable to ON is equivalent to using the BEFORE +option in all uses of that command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_DIRECTORIES_PROJECT_BEFORE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_DIRECTORIES_PROJECT_BEFORE.html new file mode 100644 index 0000000000000000000000000000000000000000..9ec03481891fc44875143bf7ab6e0c7b35c2af55 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_DIRECTORIES_PROJECT_BEFORE.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_INCLUDE_DIRECTORIES_PROJECT_BEFORE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_INCLUDE_DIRECTORIES_PROJECT_BEFORE

+

Whether to force prepending of project include directories.

+

This variable affects the order of include directories generated in compiler +command lines. If set to ON, it causes the CMAKE_SOURCE_DIR +and the CMAKE_BINARY_DIR to appear first.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..b6c6fe010f93ca5475233365ce8217a90b994f3a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INCLUDE_PATH.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_INCLUDE_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_INCLUDE_PATH

+

Semicolon-separated list of directories specifying a search path +for the find_file() and find_path() commands. By default it +is empty, it is intended to be set by the project.

+

There is also an environment variable CMAKE_INCLUDE_PATH, which is used +as an additional list of search directories.

+

See also CMAKE_SYSTEM_INCLUDE_PATH and CMAKE_PREFIX_PATH.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_DEFAULT_COMPONENT_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_DEFAULT_COMPONENT_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..c2f3334441e6633927d01a9fe0aac166a17dcd39 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_DEFAULT_COMPONENT_NAME.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_INSTALL_DEFAULT_COMPONENT_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_INSTALL_DEFAULT_COMPONENT_NAME

+

Default component used in install() commands.

+

If an install() command is used without the COMPONENT argument, +these files will be grouped into a default component. The name of this +default install component will be taken from this variable. It +defaults to Unspecified.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..d5270421ec1c695f30ab294ae46cec19026a8edf --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.html @@ -0,0 +1,162 @@ + + + + + + + + + CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS

+
+

New in version 3.11.

+
+

Default permissions for directories created implicitly during installation +of files by install() and file(INSTALL).

+

If make install is invoked and directories are implicitly created they +get permissions set by CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS +variable or platform specific default permissions if the variable is not set.

+

Implicitly created directories are created if they are not explicitly installed +by install() command but are needed to install a file on a certain +path. Example of such locations are directories created due to the setting of +CMAKE_INSTALL_PREFIX.

+

Expected content of the CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS +variable is a list of permissions that can be used by install() command +PERMISSIONS section.

+

Example usage:

+
set(CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS
+     OWNER_READ
+     OWNER_WRITE
+     OWNER_EXECUTE
+     GROUP_READ
+   )
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_MESSAGE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_MESSAGE.html new file mode 100644 index 0000000000000000000000000000000000000000..7f04ad7c09aae5ca6a88115588afb10de157a061 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_MESSAGE.html @@ -0,0 +1,165 @@ + + + + + + + + + CMAKE_INSTALL_MESSAGE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_INSTALL_MESSAGE

+
+

New in version 3.1.

+
+

Specify verbosity of installation script code generated by the +install() command (using the file(INSTALL) command). +For paths that are newly installed or updated, installation +may print lines like:

+
-- Installing: /some/destination/path
+
+
+

For paths that are already up to date, installation may print +lines like:

+
-- Up-to-date: /some/destination/path
+
+
+

The CMAKE_INSTALL_MESSAGE variable may be set to control +which messages are printed:

+
+
ALWAYS

Print both Installing and Up-to-date messages.

+
+
LAZY

Print Installing but not Up-to-date messages.

+
+
NEVER

Print neither Installing nor Up-to-date messages.

+
+
+

Other values have undefined behavior and may not be diagnosed.

+

If this variable is not set, the default behavior is ALWAYS.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_NAME_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_NAME_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..cf3baed4a2a805d9bdfebd8cfd8c86fee1986654 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_NAME_DIR.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_INSTALL_NAME_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_INSTALL_NAME_DIR

+

Directory name for installed targets on Apple platforms.

+

CMAKE_INSTALL_NAME_DIR is used to initialize the +INSTALL_NAME_DIR property on all targets. See that target +property for more information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT.html new file mode 100644 index 0000000000000000000000000000000000000000..4b320aa28a5cf01adb74c248839a0fe1ec984221 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT.html @@ -0,0 +1,151 @@ + + + + + + + + + CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT

+
+

New in version 3.7.1.

+
+

CMake sets this variable to a TRUE value when the +CMAKE_INSTALL_PREFIX has just been initialized to +its default value, typically on the first run of CMake within +a new build tree. This can be used by project code to change +the default without overriding a user-provided value:

+
if(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
+  set(CMAKE_INSTALL_PREFIX "/my/default" CACHE PATH "..." FORCE)
+endif()
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_RPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_RPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..76dc98a0d40d0c8dc778f811fdba9b245c5957d5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_RPATH.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_INSTALL_RPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_INSTALL_RPATH

+

The rpath to use for installed targets.

+

A semicolon-separated list specifying the rpath to use in installed +targets (for platforms that support it). This is used to initialize +the target property INSTALL_RPATH for all targets.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_RPATH_USE_LINK_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_RPATH_USE_LINK_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..259e3d117864fd1ad834c9cdb0b9f463725c8af3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_INSTALL_RPATH_USE_LINK_PATH.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_INSTALL_RPATH_USE_LINK_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IOS_INSTALL_COMBINED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IOS_INSTALL_COMBINED.html new file mode 100644 index 0000000000000000000000000000000000000000..75874553cc05299e4fa37290a74459604dfbdb20 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_IOS_INSTALL_COMBINED.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_IOS_INSTALL_COMBINED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_IOS_INSTALL_COMBINED

+
+

New in version 3.5.

+
+

Default value for IOS_INSTALL_COMBINED of targets.

+

This variable is used to initialize the IOS_INSTALL_COMBINED +property on all the targets. See that target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ISPC_HEADER_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ISPC_HEADER_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..f9bb2bebf9c040d62016c2e57e212b63c9cdc3e7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ISPC_HEADER_DIRECTORY.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_ISPC_HEADER_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ISPC_HEADER_DIRECTORY

+
+

New in version 3.19.

+
+

ISPC generated header output directory.

+

This variable is used to initialize the ISPC_HEADER_DIRECTORY +property on all the targets. See the target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ISPC_HEADER_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ISPC_HEADER_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..f6355ead4f50e4937d79322597732770fd891b97 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ISPC_HEADER_SUFFIX.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_ISPC_HEADER_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ISPC_HEADER_SUFFIX

+
+

New in version 3.19.2.

+
+

Output suffix to be used for ISPC generated headers.

+

This variable is used to initialize the ISPC_HEADER_SUFFIX +property on all the targets. See the target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ISPC_INSTRUCTION_SETS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ISPC_INSTRUCTION_SETS.html new file mode 100644 index 0000000000000000000000000000000000000000..24dd16f6ff33e90f33bdc56092361ff2b4615038 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_ISPC_INSTRUCTION_SETS.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_ISPC_INSTRUCTION_SETS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_ISPC_INSTRUCTION_SETS

+
+

New in version 3.19.

+
+

Default value for ISPC_INSTRUCTION_SETS property of targets.

+

This variable is used to initialize the ISPC_INSTRUCTION_SETS property +on all targets. See the target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_JOB_POOL_COMPILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_JOB_POOL_COMPILE.html new file mode 100644 index 0000000000000000000000000000000000000000..2dc1819b0f842c6b31bf9396371f03dcdb5fbc78 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_JOB_POOL_COMPILE.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_JOB_POOL_COMPILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_JOB_POOL_COMPILE

+

This variable is used to initialize the JOB_POOL_COMPILE +property on all the targets. See JOB_POOL_COMPILE +for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_JOB_POOL_LINK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_JOB_POOL_LINK.html new file mode 100644 index 0000000000000000000000000000000000000000..4e314431cb77195565a191529508aa75b470b737 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_JOB_POOL_LINK.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_JOB_POOL_LINK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_KATE_MAKE_ARGUMENTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_KATE_MAKE_ARGUMENTS.html new file mode 100644 index 0000000000000000000000000000000000000000..e62c54097d6adc26be2da8e6bddc2ba99e843e1c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_KATE_MAKE_ARGUMENTS.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_KATE_MAKE_ARGUMENTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_KATE_MAKE_ARGUMENTS

+
+

New in version 3.0.

+
+

This cache variable is used by the Kate project generator. See +cmake-generators(7).

+

This variable holds arguments which are used when Kate invokes the make +tool. By default it is initialized to hold flags to enable parallel builds +(using -j typically).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_MACHINE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_MACHINE.html new file mode 100644 index 0000000000000000000000000000000000000000..5a847a2bec1608fe944285bc746fb224935dce04 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_MACHINE.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINE

+
+

New in version 3.7.1.

+
+

When Cross Compiling for Android this variable contains the +toolchain binutils machine name (e.g. gcc -dumpmachine). The +binutils typically have a <machine>- prefix on their name.

+

See also CMAKE_<LANG>_ANDROID_TOOLCHAIN_PREFIX +and CMAKE_<LANG>_ANDROID_TOOLCHAIN_SUFFIX.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..5b0ca6f801ba59c99939bec8eb2ab67811f47650 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_PREFIX.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_<LANG>_ANDROID_TOOLCHAIN_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_ANDROID_TOOLCHAIN_PREFIX

+
+

New in version 3.7.

+
+

When Cross Compiling for Android this variable contains the absolute +path prefixing the toolchain GNU compiler and its binutils.

+

See also CMAKE_<LANG>_ANDROID_TOOLCHAIN_SUFFIX +and CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINE.

+

For example, the path to the linker is:

+
${CMAKE_CXX_ANDROID_TOOLCHAIN_PREFIX}ld${CMAKE_CXX_ANDROID_TOOLCHAIN_SUFFIX}
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..30624b3fdf5b61a22492c120228242bfde0d4222 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ANDROID_TOOLCHAIN_SUFFIX.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_<LANG>_ANDROID_TOOLCHAIN_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_ANDROID_TOOLCHAIN_SUFFIX

+
+

New in version 3.7.

+
+

When Cross Compiling for Android this variable contains the +host platform suffix of the toolchain GNU compiler and its binutils.

+

See also CMAKE_<LANG>_ANDROID_TOOLCHAIN_PREFIX +and CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ARCHIVE_APPEND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ARCHIVE_APPEND.html new file mode 100644 index 0000000000000000000000000000000000000000..ab19ff8834b83399154be3ffe3262d93f442042b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ARCHIVE_APPEND.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_<LANG>_ARCHIVE_APPEND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_ARCHIVE_APPEND

+

Rule variable to append to a static archive.

+

This is a rule variable that tells CMake how to append to a static +archive. It is used in place of CMAKE_<LANG>_CREATE_STATIC_LIBRARY +on some platforms in order to support large object counts. See also +CMAKE_<LANG>_ARCHIVE_CREATE and +CMAKE_<LANG>_ARCHIVE_FINISH.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ARCHIVE_FINISH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ARCHIVE_FINISH.html new file mode 100644 index 0000000000000000000000000000000000000000..accd954b0ef203c586b340c6224019394141eb25 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_ARCHIVE_FINISH.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_<LANG>_ARCHIVE_FINISH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_ARCHIVE_FINISH

+

Rule variable to finish an existing static archive.

+

This is a rule variable that tells CMake how to finish a static +archive. It is used in place of CMAKE_<LANG>_CREATE_STATIC_LIBRARY +on some platforms in order to support large object counts. See also +CMAKE_<LANG>_ARCHIVE_CREATE and +CMAKE_<LANG>_ARCHIVE_APPEND.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CLANG_TIDY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CLANG_TIDY.html new file mode 100644 index 0000000000000000000000000000000000000000..d12c5c8c89082ea70ad3dfb66cd26628d1c17919 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CLANG_TIDY.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_<LANG>_CLANG_TIDY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_CLANG_TIDY

+
+

New in version 3.6.

+
+

Default value for <LANG>_CLANG_TIDY target property +when <LANG> is C, CXX, OBJC or OBJCXX.

+

This variable is used to initialize the property on each target as it is +created. For example:

+
set(CMAKE_CXX_CLANG_TIDY clang-tidy -checks=-*,readability-*)
+add_executable(foo foo.cxx)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_ABI.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_ABI.html new file mode 100644 index 0000000000000000000000000000000000000000..09007b5b883447c913cbc288708db91a95aa6687 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_ABI.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_ABI — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_ABI

+

An internal variable subject to change.

+

This is used in determining the compiler ABI and is subject to change.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_AR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_AR.html new file mode 100644 index 0000000000000000000000000000000000000000..09f99a2b1fd1f48c84ecdcc67f3291b9d76fef10 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_AR.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_AR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_AR

+
+

New in version 3.9.

+
+

A wrapper around ar adding the appropriate --plugin option for the +compiler.

+

See also CMAKE_AR.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_ARCHITECTURE_ID.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_ARCHITECTURE_ID.html new file mode 100644 index 0000000000000000000000000000000000000000..5dc6524b0eba52742648c7b9b2b817072eecb2c3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_ARCHITECTURE_ID.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_ARCHITECTURE_ID — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_ARCHITECTURE_ID

+
+

New in version 3.10.

+
+

An internal variable subject to change.

+

This is used to identify the variant of a compiler based on its target +architecture. For some compilers this is needed to determine the correct +usage.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_FRONTEND_VARIANT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_FRONTEND_VARIANT.html new file mode 100644 index 0000000000000000000000000000000000000000..89f73627f1f083640e7635143b21629fcf9334af --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_FRONTEND_VARIANT.html @@ -0,0 +1,158 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_FRONTEND_VARIANT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_FRONTEND_VARIANT

+
+

New in version 3.14.

+
+

Identification string of the compiler frontend variant.

+

Some compilers have multiple, different frontends for accepting command +line options. (For example Clang originally only had a frontend +compatible with the GNU compiler but since its port to Windows +(Clang-Cl) it now also supports a frontend compatible with MSVC.) +When CMake detects such a compiler it sets this +variable to what would have been the CMAKE_<LANG>_COMPILER_ID for +the compiler whose frontend it resembles.

+
+

Note

+

In other words, this variable describes what command line options +and language extensions the compiler frontend expects.

+
+
+

Changed in version 3.26: This variable is set for GNU, MSVC, and AppleClang +compilers that have only one frontend variant.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_ID.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_ID.html new file mode 100644 index 0000000000000000000000000000000000000000..2c27710a932d987b9306df9929aec2d804f9ba2f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_ID.html @@ -0,0 +1,260 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_ID — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_ID

+

Compiler identification string.

+

A short string unique to the compiler vendor. Possible values +include:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Value

Name

Absoft

Absoft Fortran

ADSP

Analog VisualDSP++

AppleClang

Apple Clang

ARMCC

ARM Compiler

ARMClang

ARM Compiler based on Clang

Bruce

Bruce C Compiler

CCur

Concurrent Fortran

Clang

LLVM Clang

Cray

Cray Compiler

Embarcadero, Borland

Embarcadero

Flang

Classic Flang Fortran Compiler

LLVMFlang

LLVM Flang Fortran Compiler

Fujitsu

Fujitsu HPC compiler (Trad mode)

FujitsuClang

Fujitsu HPC compiler (Clang mode)

G95

G95 Fortran

GNU

GNU Compiler Collection

GHS

Green Hills Software

HP

Hewlett-Packard Compiler

IAR

IAR Systems

Intel

Intel Classic Compiler

IntelLLVM

Intel LLVM-Based Compiler

LCC

MCST Elbrus C/C++/Fortran Compiler

MSVC

Microsoft Visual Studio

NVHPC

NVIDIA HPC Compiler

NVIDIA

NVIDIA CUDA Compiler

OpenWatcom

Open Watcom

PGI

The Portland Group

PathScale

PathScale

SDCC

Small Device C Compiler

SunPro

Oracle Solaris Studio

Tasking

Tasking Compiler Toolsets

TI

Texas Instruments

TinyCC

Tiny C Compiler

XL, VisualAge, zOS

IBM XL

XLClang

IBM Clang-based XL

IBMClang

IBM LLVM-based Compiler

+

This variable is not guaranteed to be defined for all compilers or +languages.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_LAUNCHER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_LAUNCHER.html new file mode 100644 index 0000000000000000000000000000000000000000..1f664e10701b0074db361512a533ebdadc44bb82 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_LAUNCHER.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_LAUNCHER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_LAUNCHER

+
+

New in version 3.4.

+
+

Default value for <LANG>_COMPILER_LAUNCHER target property. +This variable is used to initialize the property on each target as it is +created. This is done only when <LANG> is C, CXX, Fortran, +HIP, ISPC, OBJC, OBJCXX, or CUDA.

+

This variable is initialized to the CMAKE_<LANG>_COMPILER_LAUNCHER +environment variable if it is set.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_LOADED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_LOADED.html new file mode 100644 index 0000000000000000000000000000000000000000..6386df18cc73cd197eddb2e9e465d9325ee008db --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_LOADED.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_LOADED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_LOADED

+

Defined to true if the language is enabled.

+

When language <LANG> is enabled by project() or +enable_language() this variable is defined to 1.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_PREDEFINES_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_PREDEFINES_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..ba3fd1401e149e2c91c9a1a9b491d6ec044d9cb4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_PREDEFINES_COMMAND.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_PREDEFINES_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_PREDEFINES_COMMAND

+
+

New in version 3.10.

+
+

Command that outputs the compiler pre definitions.

+

See AUTOMOC which uses +CMAKE_CXX_COMPILER_PREDEFINES_COMMAND +to generate the AUTOMOC_COMPILER_PREDEFINES.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_RANLIB.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_RANLIB.html new file mode 100644 index 0000000000000000000000000000000000000000..bc0c6c0095f7ed6ec9ba79a044697cb1da2357ba --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_RANLIB.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_RANLIB — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_RANLIB

+
+

New in version 3.9.

+
+

A wrapper around ranlib adding the appropriate --plugin option for the +compiler.

+

See also CMAKE_RANLIB.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_TARGET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_TARGET.html new file mode 100644 index 0000000000000000000000000000000000000000..9e6bcc6c68b5815d74273a0bd1a4263b0ee4d06e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_TARGET.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_TARGET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_TARGET

+

The target for cross-compiling, if supported.

+

Some compiler drivers are inherently cross-compilers, such as clang and +QNX qcc. These compiler drivers support a command-line argument to specify +the target to cross-compile for.

+

This variable may only be set in a toolchain file specified by +the CMAKE_TOOLCHAIN_FILE variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..7188ce784b36e3c5b13589d1f32df44985be6d59 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILER_VERSION.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_<LANG>_COMPILER_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILER_VERSION

+

Compiler version string.

+

Compiler version in major[.minor[.patch[.tweak]]] format. This +variable is not guaranteed to be defined for all compilers or +languages.

+

For example CMAKE_C_COMPILER_VERSION and +CMAKE_CXX_COMPILER_VERSION might indicate the respective C and C++ +compiler version.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILE_OBJECT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILE_OBJECT.html new file mode 100644 index 0000000000000000000000000000000000000000..01e95ae8c363fa4a66bff46f49a54fdb34aefc2a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_COMPILE_OBJECT.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_<LANG>_COMPILE_OBJECT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_COMPILE_OBJECT

+

Rule variable to compile a single object file.

+

This is a rule variable that tells CMake how to compile a single +object file for the language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CPPCHECK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CPPCHECK.html new file mode 100644 index 0000000000000000000000000000000000000000..71f2fe3d517846f5b8d5f19ce03ef7dbd478ebc3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CPPCHECK.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_<LANG>_CPPCHECK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_CPPCHECK

+
+

New in version 3.10.

+
+

Default value for <LANG>_CPPCHECK target property. This variable +is used to initialize the property on each target as it is created. This +is done only when <LANG> is C or CXX.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CPPLINT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CPPLINT.html new file mode 100644 index 0000000000000000000000000000000000000000..88f3d4e2f40987b19d7a03d424b1450e41ebdeff --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CPPLINT.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_<LANG>_CPPLINT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_CPPLINT

+
+

New in version 3.8.

+
+

Default value for <LANG>_CPPLINT target property. This variable +is used to initialize the property on each target as it is created. This +is done only when <LANG> is C or CXX.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CREATE_SHARED_LIBRARY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CREATE_SHARED_LIBRARY.html new file mode 100644 index 0000000000000000000000000000000000000000..cf38a16afa9fdf6bc559a3c40129c3d15308fac2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CREATE_SHARED_LIBRARY.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_<LANG>_CREATE_SHARED_LIBRARY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_CREATE_SHARED_LIBRARY

+

Rule variable to create a shared library.

+

This is a rule variable that tells CMake how to create a shared +library for the language <LANG>. This rule variable is a ; delimited +list of commands to run to perform the linking step.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CREATE_STATIC_LIBRARY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CREATE_STATIC_LIBRARY.html new file mode 100644 index 0000000000000000000000000000000000000000..eb28360b6264f01fa4253d1ab0e5ce09698f83e1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_CREATE_STATIC_LIBRARY.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_<LANG>_CREATE_STATIC_LIBRARY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_CREATE_STATIC_LIBRARY

+

Rule variable to create a static library.

+

This is a rule variable that tells CMake how to create a static +library for the language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..5983f9b7920725d215deb2de90964e53d673a70a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_EXTENSIONS.html @@ -0,0 +1,153 @@ + + + + + + + + + CMAKE_<LANG>_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_EXTENSIONS

+

The variations are:

+ +

Default values for <LANG>_EXTENSIONS target properties if set when +a target is created. For the compiler's default setting see +CMAKE_<LANG>_EXTENSIONS_DEFAULT.

+

For supported CMake versions see the respective pages.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_EXTENSIONS_DEFAULT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_EXTENSIONS_DEFAULT.html new file mode 100644 index 0000000000000000000000000000000000000000..fb3a13d87fdf92da262c8d4e4a3a6f87f94a306f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_EXTENSIONS_DEFAULT.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_<LANG>_EXTENSIONS_DEFAULT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_EXTENSIONS_DEFAULT

+
+

New in version 3.22.

+
+

Compiler's default extensions mode. Used as the default for the +<LANG>_EXTENSIONS target property when +CMAKE_<LANG>_EXTENSIONS is not set (see CMP0128).

+

This variable is read-only. Modifying it is undefined behavior.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS.html new file mode 100644 index 0000000000000000000000000000000000000000..ba0c1d6c058878bdcd7339e5211948131e7ec5fc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS.html @@ -0,0 +1,170 @@ + + + + + + + + + CMAKE_<LANG>_FLAGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_FLAGS

+

Language-wide flags for language <LANG> used when building for +all configurations. These flags will be passed to all invocations +of the compiler. This includes invocations that drive compiling +and those that drive linking.

+

For each language, if this variable is not defined, it is initialized +and stored in the cache using values from environment variables in +combination with CMake's builtin defaults for the toolchain:

+
    +
  • CMAKE_C_FLAGS: +Initialized by the CFLAGS environment variable.

  • +
  • CMAKE_CXX_FLAGS: +Initialized by the CXXFLAGS environment variable.

  • +
  • CMAKE_CUDA_FLAGS: +Initialized by the CUDAFLAGS environment variable.

  • +
  • CMAKE_Fortran_FLAGS: +Initialized by the FFLAGS environment variable.

  • +
  • CMAKE_CSharp_FLAGS: +Initialized by the CSFLAGS environment variable.

  • +
  • CMAKE_HIP_FLAGS: +Initialized by the HIPFLAGS environment variable.

  • +
  • CMAKE_ISPC_FLAGS: +Initialized by the ISPCFLAGS environment variable.

  • +
+

This value is a command-line string fragment. Therefore, multiple options +should be separated by spaces, and options with spaces should be quoted.

+

The flags in this variable will be passed before those in the +per-configuration CMAKE_<LANG>_FLAGS_<CONFIG> variable. +On invocations driving compiling, flags from both variables will be passed +before flags added by commands such as add_compile_options() and +target_compile_options(). On invocations driving linking, +they will be passed before flags added by commands such as +add_link_options() and target_link_options().

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..776af91dffe9b18611f58d83687c6e1521049478 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_CONFIG.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_<LANG>_FLAGS_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_FLAGS_<CONFIG>

+

Language-wide flags for language <LANG> used when building for +the <CONFIG> configuration. These flags will be passed to all +invocations of the compiler in the corresponding configuration. +This includes invocations that drive compiling and those that drive +linking.

+

The flags in this variable will be passed after those in the +CMAKE_<LANG>_FLAGS variable. On invocations driving compiling, +flags from both variables will be passed before flags added by commands +such as add_compile_options() and target_compile_options(). +On invocations driving linking, they will be passed before flags added by +commands such as add_link_options() and +target_link_options().

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_CONFIG_INIT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_CONFIG_INIT.html new file mode 100644 index 0000000000000000000000000000000000000000..789cc4e8c099d4bc1e7adbb681f4a2416edf5e7b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_CONFIG_INIT.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_<LANG>_FLAGS_<CONFIG>_INIT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_FLAGS_<CONFIG>_INIT

+
+

New in version 3.11.

+
+

Value used to initialize the CMAKE_<LANG>_FLAGS_<CONFIG> cache +entry the first time a build tree is configured for language <LANG>. +This variable is meant to be set by a toolchain file. CMake may prepend or append content to +the value based on the environment and target platform.

+

See also CMAKE_<LANG>_FLAGS_INIT.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_DEBUG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_DEBUG.html new file mode 100644 index 0000000000000000000000000000000000000000..744a73c01e94fead75c93a0f0e3732bd1bd2622c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_DEBUG.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_<LANG>_FLAGS_DEBUG — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_FLAGS_DEBUG

+

This variable is the Debug variant of the +CMAKE_<LANG>_FLAGS_<CONFIG> variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_DEBUG_INIT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_DEBUG_INIT.html new file mode 100644 index 0000000000000000000000000000000000000000..9c473150df97f4bd1cdc1c917df51d5b181ce1f7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_DEBUG_INIT.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_<LANG>_FLAGS_DEBUG_INIT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_FLAGS_DEBUG_INIT

+
+

New in version 3.7.

+
+

This variable is the Debug variant of the +CMAKE_<LANG>_FLAGS_<CONFIG>_INIT variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_MINSIZEREL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_MINSIZEREL.html new file mode 100644 index 0000000000000000000000000000000000000000..3f9f77abeba14133cce9e603b46257dcea20931b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_MINSIZEREL.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_<LANG>_FLAGS_MINSIZEREL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_FLAGS_MINSIZEREL

+

This variable is the MinSizeRel variant of the +CMAKE_<LANG>_FLAGS_<CONFIG> variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_RELEASE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_RELEASE.html new file mode 100644 index 0000000000000000000000000000000000000000..9649338b9a1f7b40253963b001265e6db70af1e8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_RELEASE.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_<LANG>_FLAGS_RELEASE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_FLAGS_RELEASE

+

This variable is the Release variant of the +CMAKE_<LANG>_FLAGS_<CONFIG> variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_RELEASE_INIT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_RELEASE_INIT.html new file mode 100644 index 0000000000000000000000000000000000000000..82dffff90be3a4f428e1b1e273761c4ebf8692d6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_RELEASE_INIT.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_<LANG>_FLAGS_RELEASE_INIT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_FLAGS_RELEASE_INIT

+
+

New in version 3.7.

+
+

This variable is the Release variant of the +CMAKE_<LANG>_FLAGS_<CONFIG>_INIT variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_RELWITHDEBINFO.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_RELWITHDEBINFO.html new file mode 100644 index 0000000000000000000000000000000000000000..644b484215371097820f0473a0948bbfa81214bd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_FLAGS_RELWITHDEBINFO.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_<LANG>_FLAGS_RELWITHDEBINFO — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_FLAGS_RELWITHDEBINFO

+

This variable is the RelWithDebInfo variant of the +CMAKE_<LANG>_FLAGS_<CONFIG> variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_INCLUDE_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_INCLUDE_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..6b7eb7cf0980bc17d406b6d197af9911d2bd06e1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_INCLUDE_DIRECTORIES.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_<LANG>_IMPLICIT_INCLUDE_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_IMPLICIT_INCLUDE_DIRECTORIES

+

Directories implicitly searched by the compiler for header files.

+

CMake does not explicitly specify these directories on compiler +command lines for language <LANG>. This prevents system include +directories from being treated as user include directories on some +compilers, which is important for C, CXX, and CUDA to +avoid overriding standard library headers.

+

This value is not used for Fortran because it has no standard +library headers and some compilers do not search their implicit +include directories for module .mod files.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_LINK_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_LINK_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..cda9209b08d7419366ff81bf56a6291009e25b9b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_LINK_DIRECTORIES.html @@ -0,0 +1,168 @@ + + + + + + + + + CMAKE_<LANG>_IMPLICIT_LINK_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..d061f17f988de799861fcdb8e32526303961b58e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_<LANG>_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_LINK_LIBRARIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_LINK_LIBRARIES.html new file mode 100644 index 0000000000000000000000000000000000000000..e760fb1b4927fa1d17b5acdd1771c9ed61a994ec --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_IMPLICIT_LINK_LIBRARIES.html @@ -0,0 +1,156 @@ + + + + + + + + + CMAKE_<LANG>_IMPLICIT_LINK_LIBRARIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_INCLUDE_WHAT_YOU_USE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_INCLUDE_WHAT_YOU_USE.html new file mode 100644 index 0000000000000000000000000000000000000000..2017040ab30e6539d22604985156a23289f8d5f9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_INCLUDE_WHAT_YOU_USE.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE

+
+

New in version 3.3.

+
+

Default value for <LANG>_INCLUDE_WHAT_YOU_USE target property. +This variable is used to initialize the property on each target as it is +created. This is done only when <LANG> is C or CXX.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LIBRARY_ARCHITECTURE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LIBRARY_ARCHITECTURE.html new file mode 100644 index 0000000000000000000000000000000000000000..654bf7c3d1ce1625fb5a189719d6c42bce99b3be --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LIBRARY_ARCHITECTURE.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_<LANG>_LIBRARY_ARCHITECTURE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_LIBRARY_ARCHITECTURE

+

Target architecture library directory name detected for <LANG>.

+

If the <LANG> compiler passes to the linker an architecture-specific +system library search directory such as <prefix>/lib/<arch> this +variable contains the <arch> name if/as detected by CMake.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_LAUNCHER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_LAUNCHER.html new file mode 100644 index 0000000000000000000000000000000000000000..fd02c77955ea64ae469387d08e38f3db94e6138e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_LAUNCHER.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_<LANG>_LINKER_LAUNCHER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_LINKER_LAUNCHER

+
+

New in version 3.21.

+
+

Default value for <LANG>_LINKER_LAUNCHER target property. This +variable is used to initialize the property on each target as it is created. +This is done only when <LANG> is C, CXX, OBJC, or OBJCXX.

+

This variable is initialized to the CMAKE_<LANG>_LINKER_LAUNCHER +environment variable if it is set.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_PREFERENCE_PROPAGATES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_PREFERENCE_PROPAGATES.html new file mode 100644 index 0000000000000000000000000000000000000000..4a689faaa40790be790aeb21d2b51dcf517045ad --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_PREFERENCE_PROPAGATES.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_<LANG>_LINKER_PREFERENCE_PROPAGATES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_LINKER_PREFERENCE_PROPAGATES

+

An internal variable subject to change.

+

True if CMAKE_<LANG>_LINKER_PREFERENCE propagates across targets.

+

This is used when CMake selects a linker language for a target. +Languages compiled directly into the target are always considered. A +language compiled into static libraries linked by the target is +considered if this variable is true.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG.html new file mode 100644 index 0000000000000000000000000000000000000000..ea8df50b88006baf03abebef309ebd78df5eb128 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG.html @@ -0,0 +1,167 @@ + + + + + + + + + CMAKE_<LANG>_LINKER_WRAPPER_FLAG — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_LINKER_WRAPPER_FLAG

+
+

New in version 3.13.

+
+

Defines the syntax of compiler driver option to pass options to the linker +tool. It will be used to translate the LINKER: prefix in the link options +(see add_link_options() and target_link_options()).

+

This variable holds a semicolon-separated list of tokens. +If a space (i.e. " ") is specified as last token, flag and LINKER: +arguments will be specified as separate arguments to the compiler driver. +The CMAKE_<LANG>_LINKER_WRAPPER_FLAG_SEP variable can be specified +to manage concatenation of arguments.

+

For example, for Clang we have:

+
set (CMAKE_C_LINKER_WRAPPER_FLAG "-Xlinker" " ")
+
+
+

Specifying "LINKER:-z,defs" will be transformed in +-Xlinker -z -Xlinker defs.

+

For GNU GCC:

+
set (CMAKE_C_LINKER_WRAPPER_FLAG "-Wl,")
+set (CMAKE_C_LINKER_WRAPPER_FLAG_SEP ",")
+
+
+

Specifying "LINKER:-z,defs" will be transformed in -Wl,-z,defs.

+

And for SunPro:

+
set (CMAKE_C_LINKER_WRAPPER_FLAG "-Qoption" "ld" " ")
+set (CMAKE_C_LINKER_WRAPPER_FLAG_SEP ",")
+
+
+

Specifying "LINKER:-z,defs" will be transformed in -Qoption ld -z,defs.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG_SEP.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG_SEP.html new file mode 100644 index 0000000000000000000000000000000000000000..9c5961a7242e87621857c9fc812133281a62f686 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINKER_WRAPPER_FLAG_SEP.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_<LANG>_LINKER_WRAPPER_FLAG_SEP — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_LINKER_WRAPPER_FLAG_SEP

+
+

New in version 3.13.

+
+

This variable is used with CMAKE_<LANG>_LINKER_WRAPPER_FLAG +variable to format LINKER: prefix in the link options +(see add_link_options() and target_link_options()).

+

When specified, arguments of the LINKER: prefix will be concatenated using +this value as separator.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_GROUP_USING_FEATURE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_GROUP_USING_FEATURE.html new file mode 100644 index 0000000000000000000000000000000000000000..15a17eecc9d0a05f061108050ae4d8aa47d90d97 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_GROUP_USING_FEATURE.html @@ -0,0 +1,268 @@ + + + + + + + + + CMAKE_<LANG>_LINK_GROUP_USING_<FEATURE> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_LIBRARY_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_LIBRARY_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..49f70a58150380cff2dbf4c8c4f8a276c40e4369 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_LIBRARY_SUFFIX.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_<LANG>_LINK_LIBRARY_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_LIBRARY_USING_FEATURE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_LIBRARY_USING_FEATURE.html new file mode 100644 index 0000000000000000000000000000000000000000..dcca19493f0300e02a4a2e98849c6c0edb9fd57e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_LIBRARY_USING_FEATURE.html @@ -0,0 +1,409 @@ + + + + + + + + + CMAKE_<LANG>_LINK_LIBRARY_USING_<FEATURE> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_WHAT_YOU_USE_FLAG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_WHAT_YOU_USE_FLAG.html new file mode 100644 index 0000000000000000000000000000000000000000..786bed64e6f350abc26a86fe3813f7631bc3b7b0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_LINK_WHAT_YOU_USE_FLAG.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_<LANG>_LINK_WHAT_YOU_USE_FLAG — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_OUTPUT_EXTENSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_OUTPUT_EXTENSION.html new file mode 100644 index 0000000000000000000000000000000000000000..81e0d93379c2f0f639025cc31aac5f4dd0f4ea70 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_OUTPUT_EXTENSION.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_<LANG>_OUTPUT_EXTENSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_OUTPUT_EXTENSION

+

Extension for the output of a compile for a single file.

+

This is the extension for an object file for the given <LANG>. For +example .obj for C on Windows.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_PLATFORM_ID.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_PLATFORM_ID.html new file mode 100644 index 0000000000000000000000000000000000000000..e5b6b67698898ca682c97e8df393839d9ae2947d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_PLATFORM_ID.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_<LANG>_PLATFORM_ID — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_PLATFORM_ID

+

An internal variable subject to change.

+

This is used in determining the platform and is subject to change.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_SIMULATE_ID.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_SIMULATE_ID.html new file mode 100644 index 0000000000000000000000000000000000000000..3bdb259979e59a465455cdacdd03dcf063ae7a78 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_SIMULATE_ID.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_<LANG>_SIMULATE_ID — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_SIMULATE_ID

+

Identification string of the "simulated" compiler.

+

Some compilers simulate other compilers to serve as drop-in +replacements. When CMake detects such a compiler it sets this +variable to what would have been the CMAKE_<LANG>_COMPILER_ID for +the simulated compiler.

+
+

Note

+

In other words, this variable describes the ABI compatibility +of the generated code.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_SIMULATE_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_SIMULATE_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..efc9dc79e5fb85cfc22f667ab8f78647979c8301 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_SIMULATE_VERSION.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_<LANG>_SIMULATE_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_SIMULATE_VERSION

+

Version string of "simulated" compiler.

+

Some compilers simulate other compilers to serve as drop-in +replacements. When CMake detects such a compiler it sets this +variable to what would have been the CMAKE_<LANG>_COMPILER_VERSION +for the simulated compiler.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_SOURCE_FILE_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_SOURCE_FILE_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..0dc5ddec4787c05a7a17bdd1bfb49683a9b6d4f4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_SOURCE_FILE_EXTENSIONS.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_<LANG>_SOURCE_FILE_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_SOURCE_FILE_EXTENSIONS

+

Extensions of source files for the given language.

+

This is the list of extensions for a given language's source files.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_DEFAULT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_DEFAULT.html new file mode 100644 index 0000000000000000000000000000000000000000..3cfc47e571be09bbbc5f70c9853cb28151d49990 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_DEFAULT.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_<LANG>_STANDARD_DEFAULT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_STANDARD_DEFAULT

+
+

New in version 3.9.

+
+

The compiler's default standard for the language <LANG>. Empty if the +compiler has no conception of standard levels.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_INCLUDE_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_INCLUDE_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..6a0e3b7f0f057c1d6769eb08979bc5d03a83f9e0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_INCLUDE_DIRECTORIES.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_<LANG>_STANDARD_INCLUDE_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_STANDARD_INCLUDE_DIRECTORIES

+
+

New in version 3.6.

+
+

Include directories to be used for every source file compiled with +the <LANG> compiler. This is meant for specification of system +include directories needed by the language for the current platform. +The directories always appear at the end of the include path passed +to the compiler.

+

This variable should not be set by project code. It is meant to be set by +CMake's platform information modules for the current toolchain, or by a +toolchain file when used with CMAKE_TOOLCHAIN_FILE.

+

See also CMAKE_<LANG>_STANDARD_LIBRARIES.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_LIBRARIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_LIBRARIES.html new file mode 100644 index 0000000000000000000000000000000000000000..fa3d20b5e22b52e3339c716b0824978b738ed507 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_LIBRARIES.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_<LANG>_STANDARD_LIBRARIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_STANDARD_LIBRARIES

+
+

New in version 3.6.

+
+

Libraries linked into every executable and shared library linked +for language <LANG>. This is meant for specification of system +libraries needed by the language for the current platform.

+

This variable should not be set by project code. It is meant to be set by +CMake's platform information modules for the current toolchain, or by a +toolchain file when used with CMAKE_TOOLCHAIN_FILE.

+

See also CMAKE_<LANG>_STANDARD_INCLUDE_DIRECTORIES.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..611a80baf810a60dd925632f1622954b86e384d6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_STANDARD_REQUIRED.html @@ -0,0 +1,152 @@ + + + + + + + + + CMAKE_<LANG>_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_STANDARD_REQUIRED

+

The variations are:

+ +

Default values for <LANG>_STANDARD_REQUIRED target properties if +set when a target is created.

+

For supported CMake versions see the respective pages.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_VISIBILITY_PRESET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_VISIBILITY_PRESET.html new file mode 100644 index 0000000000000000000000000000000000000000..3bf1ed05a14e39b64a4057182edd1d6cf54cfae0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LANG_VISIBILITY_PRESET.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_<LANG>_VISIBILITY_PRESET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_<LANG>_VISIBILITY_PRESET

+

Default value for the <LANG>_VISIBILITY_PRESET target +property when a target is created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_ARCHITECTURE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_ARCHITECTURE.html new file mode 100644 index 0000000000000000000000000000000000000000..eb6b0898893c9dca22a587d889e1566a16cee242 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_ARCHITECTURE.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_LIBRARY_ARCHITECTURE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_LIBRARY_ARCHITECTURE

+

Target architecture library directory name, if detected.

+

This is the value of CMAKE_<LANG>_LIBRARY_ARCHITECTURE as detected +for one of the enabled languages.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_ARCHITECTURE_REGEX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_ARCHITECTURE_REGEX.html new file mode 100644 index 0000000000000000000000000000000000000000..ec054e362808315714dc60687504566fa419f5d4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_ARCHITECTURE_REGEX.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_LIBRARY_ARCHITECTURE_REGEX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_LIBRARY_ARCHITECTURE_REGEX

+

Regex matching possible target architecture library directory names.

+

This is used to detect CMAKE_<LANG>_LIBRARY_ARCHITECTURE from the +implicit linker search path by matching the <arch> name.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..f2b527edf7a621d7c7b4399c03a6f2266d7edc9f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_LIBRARY_OUTPUT_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_LIBRARY_OUTPUT_DIRECTORY

+

Where to put all the LIBRARY +target files when built.

+

This variable is used to initialize the LIBRARY_OUTPUT_DIRECTORY +property on all the targets. See that target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..09f3787e983fa63774f22b0923ca697ab09e76c4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_OUTPUT_DIRECTORY_CONFIG.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_LIBRARY_OUTPUT_DIRECTORY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_LIBRARY_OUTPUT_DIRECTORY_<CONFIG>

+
+

New in version 3.3.

+
+

Where to put all the LIBRARY +target files when built for a specific configuration.

+

This variable is used to initialize the +LIBRARY_OUTPUT_DIRECTORY_<CONFIG> property on all the targets. +See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_PATH_FLAG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_PATH_FLAG.html new file mode 100644 index 0000000000000000000000000000000000000000..47841acf791e7014425b147a3ec62c0b902f5331 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LIBRARY_PATH_FLAG.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_LIBRARY_PATH_FLAG — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_LIBRARY_PATH_FLAG

+

The flag to be used to add a library search path to a compiler.

+

The flag will be used to specify a library directory to the compiler. +On most compilers this is -L.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_DEPENDS_USE_LINKER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_DEPENDS_USE_LINKER.html new file mode 100644 index 0000000000000000000000000000000000000000..5f89fa4ab0901d2812efe0465ad986ab013b4f6f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_DEPENDS_USE_LINKER.html @@ -0,0 +1,153 @@ + + + + + + + + + CMAKE_LINK_DEPENDS_USE_LINKER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_GROUP_USING_FEATURE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_GROUP_USING_FEATURE.html new file mode 100644 index 0000000000000000000000000000000000000000..9b24ba671e843bcc7e5b5004482c17fe2588e24d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_GROUP_USING_FEATURE.html @@ -0,0 +1,274 @@ + + + + + + + + + CMAKE_LINK_GROUP_USING_<FEATURE> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_GROUP_USING_FEATURE_SUPPORTED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_GROUP_USING_FEATURE_SUPPORTED.html new file mode 100644 index 0000000000000000000000000000000000000000..410fc98b5622fa02da6243e100d92ca9043e5b64 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_GROUP_USING_FEATURE_SUPPORTED.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_LINK_GROUP_USING_<FEATURE>_SUPPORTED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_INTERFACE_LIBRARIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_INTERFACE_LIBRARIES.html new file mode 100644 index 0000000000000000000000000000000000000000..d84810305718884a40d71d52f1c60d2e3e3ac33c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_INTERFACE_LIBRARIES.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_LINK_INTERFACE_LIBRARIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_LIBRARIES_ONLY_TARGETS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_LIBRARIES_ONLY_TARGETS.html new file mode 100644 index 0000000000000000000000000000000000000000..442c31a725f85771e9e17bfae4132d91fb8948e0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_LIBRARIES_ONLY_TARGETS.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_LINK_LIBRARIES_ONLY_TARGETS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_LIBRARY_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_LIBRARY_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..d61d2f99948aae50be6a50cf33f323b3dd3fa1a5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_LIBRARY_SUFFIX.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_LINK_LIBRARY_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_LIBRARY_USING_FEATURE_SUPPORTED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_LIBRARY_USING_FEATURE_SUPPORTED.html new file mode 100644 index 0000000000000000000000000000000000000000..bcd2ef26699f39fa27eb03a30402d4d6fe6d72ef --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_LINK_LIBRARY_USING_FEATURE_SUPPORTED.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_LINK_LIBRARY_USING_<FEATURE>_SUPPORTED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MACOSX_BUNDLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MACOSX_BUNDLE.html new file mode 100644 index 0000000000000000000000000000000000000000..3b01276c337e9f306bdf2e3764078e70edac0721 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MACOSX_BUNDLE.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_MACOSX_BUNDLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MACOSX_BUNDLE

+

Default value for MACOSX_BUNDLE of targets.

+

This variable is used to initialize the MACOSX_BUNDLE property on +all the targets. See that target property for additional information.

+

This variable is set to ON by default if CMAKE_SYSTEM_NAME +equals to iOS, tvOS or watchOS.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAJOR_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAJOR_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..8b24cff00292b864a9a7e3cdcac2541f71a3556a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAJOR_VERSION.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_MAJOR_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MAJOR_VERSION

+

First version number component of the CMAKE_VERSION +variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAKE_PROGRAM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAKE_PROGRAM.html new file mode 100644 index 0000000000000000000000000000000000000000..8b94f46994050f52b9c03c82197c87b46d34c21b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAKE_PROGRAM.html @@ -0,0 +1,192 @@ + + + + + + + + + CMAKE_MAKE_PROGRAM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MAKE_PROGRAM

+

Tool that can launch the native build system. +The value may be the full path to an executable or just the tool +name if it is expected to be in the PATH.

+

The tool selected depends on the CMAKE_GENERATOR used +to configure the project:

+
    +
  • The Makefile Generators set this to make, gmake, or +a generator-specific tool (e.g. nmake for NMake Makefiles).

    +

    These generators store CMAKE_MAKE_PROGRAM in the CMake cache +so that it may be edited by the user.

    +
  • +
  • The Ninja generator sets this to ninja.

    +

    This generator stores CMAKE_MAKE_PROGRAM in the CMake cache +so that it may be edited by the user.

    +
  • +
  • The Xcode generator sets this to xcodebuild.

    +

    This generator prefers to lookup the build tool at build time +rather than to store CMAKE_MAKE_PROGRAM in the CMake cache +ahead of time. This is because xcodebuild is easy to find.

    +

    For compatibility with versions of CMake prior to 3.2, if +a user or project explicitly adds CMAKE_MAKE_PROGRAM to +the CMake cache then CMake will use the specified value.

    +
  • +
  • The Visual Studio Generators set this to the full path to +MSBuild.exe (VS >= 10), devenv.com (VS 7,8,9), or +VCExpress.exe (VS Express 8,9). +(See also variables +CMAKE_VS_MSBUILD_COMMAND and +CMAKE_VS_DEVENV_COMMAND.

    +

    These generators prefer to lookup the build tool at build time +rather than to store CMAKE_MAKE_PROGRAM in the CMake cache +ahead of time. This is because the tools are version-specific +and can be located using the Windows Registry. It is also +necessary because the proper build tool may depend on the +project content (e.g. the Intel Fortran plugin to VS 10 and 11 +requires devenv.com to build its .vfproj project files +even though MSBuild.exe is normally preferred to support +the CMAKE_GENERATOR_TOOLSET).

    +

    For compatibility with versions of CMake prior to 3.0, if +a user or project explicitly adds CMAKE_MAKE_PROGRAM to +the CMake cache then CMake will use the specified value if +possible.

    +
  • +
  • The Green Hills MULTI generator sets this to the full +path to gbuild.exe(Windows) or gbuild(Linux) based upon +the toolset being used.

    +

    Once the generator has initialized a particular value for this +variable, changing the value has undefined behavior.

    +
  • +
+

The CMAKE_MAKE_PROGRAM variable is set for use by project code. +The value is also used by the cmake --build and +ctest --build-and-test tools to launch the native +build process.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAP_IMPORTED_CONFIG_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAP_IMPORTED_CONFIG_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..13cb6f9a051d54c286db29973e5c8604c5690482 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAP_IMPORTED_CONFIG_CONFIG.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_MAP_IMPORTED_CONFIG_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MAP_IMPORTED_CONFIG_<CONFIG>

+

Default value for MAP_IMPORTED_CONFIG_<CONFIG> of targets.

+

This variable is used to initialize the +MAP_IMPORTED_CONFIG_<CONFIG> property on all the targets. See +that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MATCH_COUNT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MATCH_COUNT.html new file mode 100644 index 0000000000000000000000000000000000000000..ec800ce619a03e2c4c14cc9ef52b9fe1dfcfd2ee --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MATCH_COUNT.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_MATCH_COUNT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MATCH_COUNT

+
+

New in version 3.2.

+
+

The number of matches with the last regular expression.

+

When a regular expression match is used, CMake fills in +CMAKE_MATCH_<n> variables with the match contents. +The CMAKE_MATCH_COUNT variable holds the number of match +expressions when these are filled.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MATCH_n.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MATCH_n.html new file mode 100644 index 0000000000000000000000000000000000000000..96474df885757fc8fe30b93a329440f46a41a1e5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MATCH_n.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_MATCH_<n> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MATCH_<n>

+
+

New in version 3.9.

+
+

Capture group <n> matched by the last regular expression, for groups +0 through 9. Group 0 is the entire match. Groups 1 through 9 are the +subexpressions captured by () syntax.

+

When a regular expression match is used, CMake fills in CMAKE_MATCH_<n> +variables with the match contents. The CMAKE_MATCH_COUNT +variable holds the number of match expressions when these are filled.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAXIMUM_RECURSION_DEPTH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAXIMUM_RECURSION_DEPTH.html new file mode 100644 index 0000000000000000000000000000000000000000..a6c29255e5d7c513cfac0387c521d1e54baa149a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MAXIMUM_RECURSION_DEPTH.html @@ -0,0 +1,170 @@ + + + + + + + + + CMAKE_MAXIMUM_RECURSION_DEPTH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MAXIMUM_RECURSION_DEPTH

+
+

New in version 3.14.

+
+

Maximum recursion depth for CMake scripts. It is intended to be set on the +command line with -DCMAKE_MAXIMUM_RECURSION_DEPTH=<x>, or within +CMakeLists.txt by projects that require a large recursion depth. Projects +that set this variable should provide the user with a way to override it. For +example:

+
# About to perform deeply recursive actions
+if(NOT CMAKE_MAXIMUM_RECURSION_DEPTH)
+  set(CMAKE_MAXIMUM_RECURSION_DEPTH 2000)
+endif()
+
+
+

If it is not set, or is set to a non-integer value, a sensible default limit is +used. If the recursion limit is reached, the script terminates immediately with +a fatal error.

+

Calling any of the following commands increases the recursion depth:

+ +

See also the CMAKE_MAXIMUM_RECURSION_DEPTH environment variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MESSAGE_CONTEXT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MESSAGE_CONTEXT.html new file mode 100644 index 0000000000000000000000000000000000000000..c1cff7526ff4bfbed008424db115257191c45d47 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MESSAGE_CONTEXT.html @@ -0,0 +1,194 @@ + + + + + + + + + CMAKE_MESSAGE_CONTEXT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MESSAGE_CONTEXT

+
+

New in version 3.17.

+
+

When enabled by the cmake --log-context command line +option or the CMAKE_MESSAGE_CONTEXT_SHOW variable, the +message() command converts the CMAKE_MESSAGE_CONTEXT list into a +dot-separated string surrounded by square brackets and prepends it to each line +for messages of log levels NOTICE and below.

+

For logging contexts to work effectively, projects should generally +APPEND and POP_BACK an item to the current value of +CMAKE_MESSAGE_CONTEXT rather than replace it. +Projects should not assume the message context at the top of the source tree +is empty, as there are scenarios where the context might have already been set +(e.g. hierarchical projects).

+
+

Warning

+

Valid context names are restricted to anything that could be used +as a CMake variable name. All names that begin with an underscore +or the string cmake_ are also reserved for use by CMake and +should not be used by projects.

+
+

Example:

+
function(bar)
+  list(APPEND CMAKE_MESSAGE_CONTEXT "bar")
+  message(VERBOSE "bar VERBOSE message")
+endfunction()
+
+function(baz)
+  list(APPEND CMAKE_MESSAGE_CONTEXT "baz")
+  message(DEBUG "baz DEBUG message")
+endfunction()
+
+function(foo)
+  list(APPEND CMAKE_MESSAGE_CONTEXT "foo")
+  bar()
+  message(TRACE "foo TRACE message")
+  baz()
+endfunction()
+
+list(APPEND CMAKE_MESSAGE_CONTEXT "top")
+
+message(VERBOSE "Before `foo`")
+foo()
+message(VERBOSE "After `foo`")
+
+list(POP_BACK CMAKE_MESSAGE_CONTEXT)
+
+
+

Which results in the following output:

+
-- [top] Before `foo`
+-- [top.foo.bar] bar VERBOSE message
+-- [top.foo] foo TRACE message
+-- [top.foo.baz] baz DEBUG message
+-- [top] After `foo`
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MESSAGE_CONTEXT_SHOW.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MESSAGE_CONTEXT_SHOW.html new file mode 100644 index 0000000000000000000000000000000000000000..052aa07751559be3ea9d2ae6bf4163f4fb8ddb74 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MESSAGE_CONTEXT_SHOW.html @@ -0,0 +1,151 @@ + + + + + + + + + CMAKE_MESSAGE_CONTEXT_SHOW — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MESSAGE_CONTEXT_SHOW

+
+

New in version 3.17.

+
+

Setting this variable to true enables showing a context with each line +logged by the message() command (see CMAKE_MESSAGE_CONTEXT +for how the context itself is specified).

+

This variable is an alternative to providing the --log-context option +on the cmake command line. Whereas the command line +option will apply only to that one CMake run, setting +CMAKE_MESSAGE_CONTEXT_SHOW to true as a cache variable will ensure that +subsequent CMake runs will continue to show the message context.

+

Projects should not set CMAKE_MESSAGE_CONTEXT_SHOW. It is intended for +users so that they may control whether or not to include context with messages.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MESSAGE_LOG_LEVEL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MESSAGE_LOG_LEVEL.html new file mode 100644 index 0000000000000000000000000000000000000000..bcf672ddbee54b8fab6c307cc7b5ff029e9ab821 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MESSAGE_LOG_LEVEL.html @@ -0,0 +1,157 @@ + + + + + + + + + CMAKE_MESSAGE_LOG_LEVEL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MESSAGE_LOG_LEVEL

+
+

New in version 3.17.

+
+

When set, this variable specifies the logging level used by the +message() command. Valid values are the same as those for the +--log-level command line option of the +cmake(1) program. If this variable is set and the +--log-level command line option is +given, the command line option takes precedence.

+

The main advantage to using this variable is to make a log level persist +between CMake runs. Setting it as a cache variable will ensure that +subsequent CMake runs will continue to use the chosen log level.

+

Projects should not set this variable, it is intended for users so that +they may control the log level according to their own needs.

+
+

New in version 3.25: See the cmake_language() +cmake_language command for a way to query +the current message logging level.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MFC_FLAG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MFC_FLAG.html new file mode 100644 index 0000000000000000000000000000000000000000..898e76487d92ae83f9771a7b6015401a16535f33 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MFC_FLAG.html @@ -0,0 +1,151 @@ + + + + + + + + + CMAKE_MFC_FLAG — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MFC_FLAG

+

Use the MFC library for an executable or dll.

+

Enables the use of the Microsoft Foundation Classes (MFC). +It should be set to 1 for the static MFC library, and +2 for the shared MFC library. This is used in Visual Studio +project files.

+

Usage example:

+
add_definitions(-D_AFXDLL)
+set(CMAKE_MFC_FLAG 2)
+add_executable(CMakeSetup WIN32 ${SRCS})
+
+
+

Contents of CMAKE_MFC_FLAG may use +generator expressions.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MINIMUM_REQUIRED_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MINIMUM_REQUIRED_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..30ae5c166ed396b15d2642befda24d0b1c848317 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MINIMUM_REQUIRED_VERSION.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_MINIMUM_REQUIRED_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MINIMUM_REQUIRED_VERSION

+

The <min> version of CMake given to the most recent call to the +cmake_minimum_required(VERSION) command in the current +variable scope or any parent variable scope.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS.html new file mode 100644 index 0000000000000000000000000000000000000000..13ab46abbb23fd7b9795fd103556cefd6255fee5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_MODULE_LINKER_FLAGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MODULE_LINKER_FLAGS

+

Linker flags to be used to create modules.

+

These flags will be used by the linker when creating a module.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..30e3e11c286b9ff2e09e39eb08821be97fd5e20c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_MODULE_LINKER_FLAGS_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MODULE_LINKER_FLAGS_<CONFIG>

+

Flags to be used when linking a module.

+

Same as CMAKE_C_FLAGS_* but used by the linker when creating modules.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG_INIT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG_INIT.html new file mode 100644 index 0000000000000000000000000000000000000000..59b52824933889365f4db2c9978199dbe5236879 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS_CONFIG_INIT.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_MODULE_LINKER_FLAGS_<CONFIG>_INIT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MODULE_LINKER_FLAGS_<CONFIG>_INIT

+
+

New in version 3.7.

+
+

Value used to initialize the CMAKE_MODULE_LINKER_FLAGS_<CONFIG> +cache entry the first time a build tree is configured. +This variable is meant to be set by a toolchain file. CMake may prepend or append content to +the value based on the environment and target platform.

+

See also CMAKE_MODULE_LINKER_FLAGS_INIT.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS_INIT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS_INIT.html new file mode 100644 index 0000000000000000000000000000000000000000..af397af97bc401ce4079289274836002049160fb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MODULE_LINKER_FLAGS_INIT.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_MODULE_LINKER_FLAGS_INIT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MODULE_LINKER_FLAGS_INIT

+
+

New in version 3.7.

+
+

Value used to initialize the CMAKE_MODULE_LINKER_FLAGS +cache entry the first time a build tree is configured. +This variable is meant to be set by a toolchain file. CMake may prepend or append content to +the value based on the environment and target platform.

+

See also the configuration-specific variable +CMAKE_MODULE_LINKER_FLAGS_<CONFIG>_INIT.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MSVCIDE_RUN_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MSVCIDE_RUN_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..90c6cf70b6bb517dd5458f74eab0e6ff8e660c81 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_MSVCIDE_RUN_PATH.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_MSVCIDE_RUN_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_MSVCIDE_RUN_PATH

+
+

New in version 3.10.

+
+

Extra PATH locations that should be used when executing +add_custom_command() or add_custom_target() when using the +Visual Studio 9 2008 (or above) generator. This allows +for running commands and using dll's that the IDE environment is not aware of.

+

If not set explicitly the value is initialized by the CMAKE_MSVCIDE_RUN_PATH +environment variable, if set, and otherwise left empty.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NETRC.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NETRC.html new file mode 100644 index 0000000000000000000000000000000000000000..1e4a2234d920f9430105cb5d0107dede5ad162b2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NETRC.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_NETRC — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_NETRC

+
+

New in version 3.11.

+
+

This variable is used to initialize the NETRC option for the +file(DOWNLOAD) and file(UPLOAD) commands. +See those commands for additional information.

+

This variable is also used by the ExternalProject and +FetchContent modules for internal calls to file(DOWNLOAD).

+

The local option takes precedence over this variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NETRC_FILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NETRC_FILE.html new file mode 100644 index 0000000000000000000000000000000000000000..6b1e8e315fb7a1ee7b7f33e4c11a4dde17f7bd0b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NETRC_FILE.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_NETRC_FILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_NETRC_FILE

+
+

New in version 3.11.

+
+

This variable is used to initialize the NETRC_FILE option for the +file(DOWNLOAD) and file(UPLOAD) commands. +See those commands for additional information.

+

This variable is also used by the ExternalProject and +FetchContent modules for internal calls to file(DOWNLOAD).

+

The local option takes precedence over this variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NINJA_OUTPUT_PATH_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NINJA_OUTPUT_PATH_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..d7ee493da49a656820d3a774e7d2b23ed40919de --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NINJA_OUTPUT_PATH_PREFIX.html @@ -0,0 +1,172 @@ + + + + + + + + + CMAKE_NINJA_OUTPUT_PATH_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_NINJA_OUTPUT_PATH_PREFIX

+
+

New in version 3.6.

+
+

Tell the Ninja Generators to add a prefix to every output path in +build.ninja. A trailing slash is appended to the prefix, if missing.

+

This is useful when the generated ninja file is meant to be embedded as a +subninja file into a super ninja project. For example, the command:

+
cd super-build-dir &&
+cmake -G Ninja -S /path/to/src -B sub -DCMAKE_NINJA_OUTPUT_PATH_PREFIX=sub/
+#                                 ^^^---------- these match -----------^^^
+
+
+

generates a build directory with its top-level (CMAKE_BINARY_DIR) +in super-build-dir/sub. The path to the build directory ends in the +output path prefix. This makes it suitable for use in a separately-written +super-build-dir/build.ninja file with a directive like this:

+
subninja sub/build.ninja
+
+
+

The auto-regeneration rule in super-build-dir/build.ninja must +have an order-only dependency on sub/build.ninja.

+
+

New in version 3.27: The Ninja Multi-Config generator supports this variable.

+
+
+

Note

+

When CMAKE_NINJA_OUTPUT_PATH_PREFIX is set, the project generated +by CMake cannot be used as a standalone project. No default targets +are specified.

+

The value of CMAKE_NINJA_OUTPUT_PATH_PREFIX must match one or more +path components at the end of CMAKE_BINARY_DIR, or the +behavior is undefined. However, this requirement is not checked +automatically.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NOT_USING_CONFIG_FLAGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NOT_USING_CONFIG_FLAGS.html new file mode 100644 index 0000000000000000000000000000000000000000..3cb1d250d172416d4d11f62ab5ece68fed1d0bbb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NOT_USING_CONFIG_FLAGS.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_NOT_USING_CONFIG_FLAGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_NOT_USING_CONFIG_FLAGS

+

Skip _BUILD_TYPE flags if true.

+

This is an internal flag used by the generators in CMake to tell CMake +to skip the _BUILD_TYPE flags.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NO_BUILTIN_CHRPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NO_BUILTIN_CHRPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..7a0d90b66f51a0a54d5623fbe4df56685ffdc1a4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NO_BUILTIN_CHRPATH.html @@ -0,0 +1,152 @@ + + + + + + + + + CMAKE_NO_BUILTIN_CHRPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_NO_BUILTIN_CHRPATH

+

Do not use the builtin binary editor to fix runtime library search +paths on installation.

+

When an ELF or XCOFF binary needs to have a different runtime library +search path after installation than it does in the build tree, CMake uses +a builtin editor to change the runtime search path in the installed copy. +If this variable is set to true then CMake will relink the binary before +installation instead of using its builtin editor.

+

For more information on RPATH handling see +the INSTALL_RPATH and BUILD_RPATH target properties.

+
+

New in version 3.20: This variable also applies to XCOFF binaries' LIBPATH. Prior to the +addition of the XCOFF editor in CMake 3.20, this variable applied only +to ELF binaries' RPATH/RUNPATH.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NO_SYSTEM_FROM_IMPORTED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NO_SYSTEM_FROM_IMPORTED.html new file mode 100644 index 0000000000000000000000000000000000000000..132a7217aa736cb5c9f188b542dd66afceea2cf2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_NO_SYSTEM_FROM_IMPORTED.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_NO_SYSTEM_FROM_IMPORTED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_NO_SYSTEM_FROM_IMPORTED

+

Default value for NO_SYSTEM_FROM_IMPORTED of targets.

+

This variable is used to initialize the NO_SYSTEM_FROM_IMPORTED +property on all the targets. See that target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJCXX_STANDARD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJCXX_STANDARD.html new file mode 100644 index 0000000000000000000000000000000000000000..aedf27f67f78fe6064a5ecf3ce5e4dd6bb8a27f4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJCXX_STANDARD.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_OBJCXX_STANDARD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_OBJCXX_STANDARD

+
+

New in version 3.16.

+
+

Default value for OBJCXX_STANDARD target property if set when a +target is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJCXX_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJCXX_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..db94ba628bac80a2c14f6551d918ffe02fec8171 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJCXX_STANDARD_REQUIRED.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_OBJCXX_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_OBJCXX_STANDARD_REQUIRED

+
+

New in version 3.16.

+
+

Default value for OBJCXX_STANDARD_REQUIRED target property if set +when a target is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJC_EXTENSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJC_EXTENSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..68f5d2caf971f629e1a6a5d564c9b82fa41acfdd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJC_EXTENSIONS.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_OBJC_EXTENSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_OBJC_EXTENSIONS

+
+

New in version 3.16.

+
+

Default value for OBJC_EXTENSIONS target property if set when a +target is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJC_STANDARD_REQUIRED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJC_STANDARD_REQUIRED.html new file mode 100644 index 0000000000000000000000000000000000000000..1f3b4584214632659f5f07397beaf792def362cb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJC_STANDARD_REQUIRED.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_OBJC_STANDARD_REQUIRED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_OBJC_STANDARD_REQUIRED

+
+

New in version 3.16.

+
+

Default value for OBJC_STANDARD_REQUIRED target property if set +when a target is created.

+

See the cmake-compile-features(7) manual for information on +compile features and a list of supported compilers.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJECT_PATH_MAX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJECT_PATH_MAX.html new file mode 100644 index 0000000000000000000000000000000000000000..b434978b4e865b4e0170bf920f9cf678afcc5497 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OBJECT_PATH_MAX.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_OBJECT_PATH_MAX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_OBJECT_PATH_MAX

+

Maximum object file full-path length allowed by native build tools.

+

CMake computes for every source file an object file name that is +unique to the source file and deterministic with respect to the full +path to the source file. This allows multiple source files in a +target to share the same name if they lie in different directories +without rebuilding when one is added or removed. However, it can +produce long full paths in a few cases, so CMake shortens the path +using a hashing scheme when the full path to an object file exceeds a +limit. CMake has a built-in limit for each platform that is +sufficient for common tools, but some native tools may have a lower +limit. This variable may be set to specify the limit explicitly. The +value must be an integer no less than 128.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OPTIMIZE_DEPENDENCIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OPTIMIZE_DEPENDENCIES.html new file mode 100644 index 0000000000000000000000000000000000000000..2f70be98b6eeefe8b2a018c047a21f3c434902b1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OPTIMIZE_DEPENDENCIES.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_OPTIMIZE_DEPENDENCIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_OPTIMIZE_DEPENDENCIES

+
+

New in version 3.19.

+
+

Initializes the OPTIMIZE_DEPENDENCIES target property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OSX_ARCHITECTURES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OSX_ARCHITECTURES.html new file mode 100644 index 0000000000000000000000000000000000000000..3b689fbbe5c4167732ae39af49c674813db35130 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OSX_ARCHITECTURES.html @@ -0,0 +1,152 @@ + + + + + + + + + CMAKE_OSX_ARCHITECTURES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_OSX_ARCHITECTURES

+

Target specific architectures for macOS and iOS.

+

This variable is used to initialize the OSX_ARCHITECTURES +property on each target as it is created. See that target property +for additional information.

+

The value of this variable should be set prior to the first +project() or enable_language() command invocation +because it may influence configuration of the toolchain and flags. +It is intended to be set locally by the user creating a build tree. +This variable should be set as a CACHE entry (or else CMake may +remove it while initializing a cache entry of the same name) unless +policy CMP0126 is set to NEW.

+

Despite the OSX part in the variable name(s) they apply also to +other SDKs than macOS like iOS, tvOS, or watchOS.

+

This variable is ignored on platforms other than Apple.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OSX_DEPLOYMENT_TARGET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OSX_DEPLOYMENT_TARGET.html new file mode 100644 index 0000000000000000000000000000000000000000..2ed2acb8f43da21f2f5012339fcacaaa8fac2d32 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OSX_DEPLOYMENT_TARGET.html @@ -0,0 +1,157 @@ + + + + + + + + + CMAKE_OSX_DEPLOYMENT_TARGET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_OSX_DEPLOYMENT_TARGET

+

Specify the minimum version of the target platform (e.g. macOS or iOS) +on which the target binaries are to be deployed. CMake uses this +variable value for the -mmacosx-version-min flag or their respective +target platform equivalents. For older Xcode versions that shipped +multiple macOS SDKs this variable also helps to choose the SDK in case +CMAKE_OSX_SYSROOT is unset.

+

If not set explicitly the value is initialized by the +MACOSX_DEPLOYMENT_TARGET environment variable, if set, +and otherwise computed based on the host platform.

+

The value of this variable should be set prior to the first +project() or enable_language() command invocation +because it may influence configuration of the toolchain and flags. +It is intended to be set locally by the user creating a build tree. +This variable should be set as a CACHE entry (or else CMake may +remove it while initializing a cache entry of the same name) unless +policy CMP0126 is set to NEW.

+

Despite the OSX part in the variable name(s) they apply also to +other SDKs than macOS like iOS, tvOS, or watchOS.

+

This variable is ignored on platforms other than Apple.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OSX_SYSROOT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OSX_SYSROOT.html new file mode 100644 index 0000000000000000000000000000000000000000..f6ebdb1aeee8ae9ba1f2046de19863454ccb8127 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_OSX_SYSROOT.html @@ -0,0 +1,155 @@ + + + + + + + + + CMAKE_OSX_SYSROOT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_OSX_SYSROOT

+

Specify the location or name of the macOS platform SDK to be used. +CMake uses this value to compute the value of the -isysroot flag +or equivalent and to help the find_* commands locate files in +the SDK.

+

If not set explicitly the value is initialized by the SDKROOT +environment variable, if set, and otherwise computed based on the +CMAKE_OSX_DEPLOYMENT_TARGET or the host platform.

+

The value of this variable should be set prior to the first +project() or enable_language() command invocation +because it may influence configuration of the toolchain and flags. +It is intended to be set locally by the user creating a build tree. +This variable should be set as a CACHE entry (or else CMake may +remove it while initializing a cache entry of the same name) unless +policy CMP0126 is set to NEW.

+

Despite the OSX part in the variable name(s) they apply also to +other SDKs than macOS like iOS, tvOS, or watchOS.

+

This variable is ignored on platforms other than Apple.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PARENT_LIST_FILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PARENT_LIST_FILE.html new file mode 100644 index 0000000000000000000000000000000000000000..af0bd3260f30b97e2a24a4581fd37525380b269b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PARENT_LIST_FILE.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_PARENT_LIST_FILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PARENT_LIST_FILE

+

Full path to the CMake file that included the current one.

+

While processing a CMake file loaded by include() or +find_package() this variable contains the full path to the file +including it. The top of the include stack is always the CMakeLists.txt +for the current directory. See also CMAKE_CURRENT_LIST_FILE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PATCH_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PATCH_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..c00db19eb3d017c4978f76aec6a065d23970fe75 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PATCH_VERSION.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_PATCH_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PATCH_VERSION

+

Third version number component of the CMAKE_VERSION +variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PCH_WARN_INVALID.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PCH_WARN_INVALID.html new file mode 100644 index 0000000000000000000000000000000000000000..a70d8dbfdfb5e63000a03e285b54aa5dada4bdf6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PCH_WARN_INVALID.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_PCH_WARN_INVALID — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PCH_WARN_INVALID

+
+

New in version 3.18.

+
+

This variable is used to initialize the PCH_WARN_INVALID +property of targets when they are created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PDB_OUTPUT_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PDB_OUTPUT_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..8944c301ad29e6d2ee62cda3cdb596e3fff3ebb6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PDB_OUTPUT_DIRECTORY.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_PDB_OUTPUT_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PDB_OUTPUT_DIRECTORY

+

Output directory for MS debug symbol .pdb files generated by the +linker for executable and shared library targets.

+

This variable is used to initialize the PDB_OUTPUT_DIRECTORY +property on all the targets. See that target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PDB_OUTPUT_DIRECTORY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PDB_OUTPUT_DIRECTORY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..1394cb8541ad0ec11ba3fe57b1d8d98948393c9b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PDB_OUTPUT_DIRECTORY_CONFIG.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_PDB_OUTPUT_DIRECTORY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PDB_OUTPUT_DIRECTORY_<CONFIG>

+

Per-configuration output directory for MS debug symbol .pdb files +generated by the linker for executable and shared library targets.

+

This is a per-configuration version of CMAKE_PDB_OUTPUT_DIRECTORY. +This variable is used to initialize the +PDB_OUTPUT_DIRECTORY_<CONFIG> +property on all the targets. See that target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PLATFORM_NO_VERSIONED_SONAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PLATFORM_NO_VERSIONED_SONAME.html new file mode 100644 index 0000000000000000000000000000000000000000..1b63fcc7d21e283ce7b66d64dd61be9b75743655 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PLATFORM_NO_VERSIONED_SONAME.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_PLATFORM_NO_VERSIONED_SONAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PLATFORM_NO_VERSIONED_SONAME

+
+

New in version 3.1.

+
+

This variable is used to globally control whether the +VERSION and SOVERSION target +properties should be used for shared libraries. +When set to true, adding version information to each +shared library target is disabled.

+

By default this variable is set only on platforms where +CMake knows it is needed. On other platforms, the +specified properties will be used for shared libraries.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_POLICY_DEFAULT_CMPNNNN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_POLICY_DEFAULT_CMPNNNN.html new file mode 100644 index 0000000000000000000000000000000000000000..c8fe895f1726007201b8022d02679d71178255f0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_POLICY_DEFAULT_CMPNNNN.html @@ -0,0 +1,157 @@ + + + + + + + + + CMAKE_POLICY_DEFAULT_CMP<NNNN> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_POLICY_DEFAULT_CMP<NNNN>

+

Default for CMake Policy CMP<NNNN> when it is otherwise left unset.

+

Commands cmake_minimum_required(VERSION) and +cmake_policy(VERSION) by default leave policies introduced after +the given version unset. Set CMAKE_POLICY_DEFAULT_CMP<NNNN> to OLD +or NEW to specify the default for policy CMP<NNNN>, where <NNNN> +is the policy number.

+

This variable should not be set by a project in CMake code as a way to +set its own policies; use cmake_policy(SET) instead. This +variable is meant to externally set policies for which a project has +not itself been updated:

+
    +
  • Users running CMake may set this variable in the cache +(e.g. -DCMAKE_POLICY_DEFAULT_CMP<NNNN>=<OLD|NEW>). Set it to OLD +to quiet a policy warning while using old behavior or to NEW to +try building the project with new behavior.

  • +
  • Projects may set this variable before a call to add_subdirectory() +that adds a third-party project in order to set its policies without +modifying third-party code.

  • +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_POLICY_WARNING_CMPNNNN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_POLICY_WARNING_CMPNNNN.html new file mode 100644 index 0000000000000000000000000000000000000000..ab3b4de03354761511547274580c4bb65c7e78ea --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_POLICY_WARNING_CMPNNNN.html @@ -0,0 +1,184 @@ + + + + + + + + + CMAKE_POLICY_WARNING_CMP<NNNN> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_POLICY_WARNING_CMP<NNNN>

+

Explicitly enable or disable the warning when CMake Policy CMP<NNNN> +has not been set explicitly by cmake_policy() or implicitly +by cmake_minimum_required(). This is meaningful +only for the policies that do not warn by default:

+
    +
  • CMAKE_POLICY_WARNING_CMP0025 controls the warning for +policy CMP0025.

  • +
  • CMAKE_POLICY_WARNING_CMP0047 controls the warning for +policy CMP0047.

  • +
  • CMAKE_POLICY_WARNING_CMP0056 controls the warning for +policy CMP0056.

  • +
  • CMAKE_POLICY_WARNING_CMP0060 controls the warning for +policy CMP0060.

  • +
  • CMAKE_POLICY_WARNING_CMP0065 controls the warning for +policy CMP0065.

  • +
  • CMAKE_POLICY_WARNING_CMP0066 controls the warning for +policy CMP0066.

  • +
  • CMAKE_POLICY_WARNING_CMP0067 controls the warning for +policy CMP0067.

  • +
  • CMAKE_POLICY_WARNING_CMP0082 controls the warning for +policy CMP0082.

  • +
  • CMAKE_POLICY_WARNING_CMP0089 controls the warning for +policy CMP0089.

  • +
  • CMAKE_POLICY_WARNING_CMP0102 controls the warning for +policy CMP0102.

  • +
  • CMAKE_POLICY_WARNING_CMP0112 controls the warning for +policy CMP0112.

  • +
  • CMAKE_POLICY_WARNING_CMP0116 controls the warning for +policy CMP0116.

  • +
  • CMAKE_POLICY_WARNING_CMP0126 controls the warning for +policy CMP0126.

  • +
  • CMAKE_POLICY_WARNING_CMP0128 controls the warning for +policy CMP0128.

  • +
  • CMAKE_POLICY_WARNING_CMP0129 controls the warning for +policy CMP0129.

  • +
  • CMAKE_POLICY_WARNING_CMP0133 controls the warning for +policy CMP0133.

  • +
+

This variable should not be set by a project in CMake code. Project +developers running CMake may set this variable in their cache to +enable the warning (e.g. -DCMAKE_POLICY_WARNING_CMP<NNNN>=ON). +Alternatively, running cmake(1) with the +--debug-output, +--trace, or +--trace-expand option will also +enable the warning.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_POSITION_INDEPENDENT_CODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_POSITION_INDEPENDENT_CODE.html new file mode 100644 index 0000000000000000000000000000000000000000..1bad0ca8f50ccc979cbf3dfc45bd40e490c2765f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_POSITION_INDEPENDENT_CODE.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_POSITION_INDEPENDENT_CODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_POSITION_INDEPENDENT_CODE

+

Default value for POSITION_INDEPENDENT_CODE of targets.

+

This variable is used to initialize the +POSITION_INDEPENDENT_CODE property on all the targets. +See that target property for additional information. If set, its +value is also used by the try_compile() command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROGRAM_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROGRAM_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..f55cefcf5d5d54915a1604f4dfe952ea923eb82e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROGRAM_PATH.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_PROGRAM_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROGRAM_PATH

+

Semicolon-separated list of directories specifying a search path +for the find_program() command. By default it is empty, it is +intended to be set by the project.

+

There is also an environment variable CMAKE_PROGRAM_PATH, which is used +as an additional list of search directories.

+

See also CMAKE_SYSTEM_PROGRAM_PATH and CMAKE_PREFIX_PATH.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_DESCRIPTION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_DESCRIPTION.html new file mode 100644 index 0000000000000000000000000000000000000000..188fa59f3e3cbaacebe3b7ee7650068b70735293 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_DESCRIPTION.html @@ -0,0 +1,168 @@ + + + + + + + + + CMAKE_PROJECT_DESCRIPTION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_DESCRIPTION

+
+

New in version 3.9.

+
+

The description of the top level project.

+

This variable holds the description of the project as specified in the top +level CMakeLists.txt file by a project() command. In the event that +the top level CMakeLists.txt contains multiple project() calls, +the most recently called one from that top level CMakeLists.txt will determine +the value that CMAKE_PROJECT_DESCRIPTION contains. For example, consider +the following top level CMakeLists.txt:

+
cmake_minimum_required(VERSION 3.0)
+project(First DESCRIPTION "I am First")
+project(Second DESCRIPTION "I am Second")
+add_subdirectory(sub)
+project(Third DESCRIPTION "I am Third")
+
+
+

And sub/CMakeLists.txt with the following contents:

+
project(SubProj DESCRIPTION "I am SubProj")
+message("CMAKE_PROJECT_DESCRIPTION = ${CMAKE_PROJECT_DESCRIPTION}")
+
+
+

The most recently seen project() command from the top level +CMakeLists.txt would be project(Second ...), so this will print:

+
CMAKE_PROJECT_DESCRIPTION = I am Second
+
+
+

To obtain the description from the most recent call to project() in +the current directory scope or above, see the PROJECT_DESCRIPTION +variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_INCLUDE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_INCLUDE.html new file mode 100644 index 0000000000000000000000000000000000000000..848b1aae05a92862132604b813b21ffdb43aa2ec --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_INCLUDE.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_PROJECT_INCLUDE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_INCLUDE

+
+

New in version 3.15.

+
+

A CMake language file or module to be included as the last step of all +project() command calls. This is intended for injecting custom code +into project builds without modifying their source. See Code Injection +for a more detailed discussion of files potentially included during a +project() call.

+

See also the CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE, +CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE, +CMAKE_PROJECT_INCLUDE_BEFORE, and +CMAKE_PROJECT_TOP_LEVEL_INCLUDES variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_INCLUDE_BEFORE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_INCLUDE_BEFORE.html new file mode 100644 index 0000000000000000000000000000000000000000..7aedcc4ff6ad91b232def7763e9a8997b61afffc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_INCLUDE_BEFORE.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_PROJECT_INCLUDE_BEFORE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_INCLUDE_BEFORE

+
+

New in version 3.15.

+
+

A CMake language file or module to be included as the first step of all +project() command calls. This is intended for injecting custom code +into project builds without modifying their source. See Code Injection +for a more detailed discussion of files potentially included during a +project() call.

+

See also the CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE, +CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE, +CMAKE_PROJECT_INCLUDE, and +CMAKE_PROJECT_TOP_LEVEL_INCLUDES variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..f6421f912580bffc4d03f95c92a50b11ca911b30 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_NAME.html @@ -0,0 +1,165 @@ + + + + + + + + + CMAKE_PROJECT_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_NAME

+

The name of the top level project.

+

This variable holds the name of the project as specified in the top +level CMakeLists.txt file by a project() command. In the event that +the top level CMakeLists.txt contains multiple project() calls, +the most recently called one from that top level CMakeLists.txt will determine +the name that CMAKE_PROJECT_NAME contains. For example, consider +the following top level CMakeLists.txt:

+
cmake_minimum_required(VERSION 3.0)
+project(First)
+project(Second)
+add_subdirectory(sub)
+project(Third)
+
+
+

And sub/CMakeLists.txt with the following contents:

+
project(SubProj)
+message("CMAKE_PROJECT_NAME = ${CMAKE_PROJECT_NAME}")
+
+
+

The most recently seen project() command from the top level +CMakeLists.txt would be project(Second), so this will print:

+
CMAKE_PROJECT_NAME = Second
+
+
+

To obtain the name from the most recent call to project() in +the current directory scope or above, see the PROJECT_NAME +variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE.html new file mode 100644 index 0000000000000000000000000000000000000000..c7e1dda87d1d72eb52080ecae6fe4a322455b397 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE

+

A CMake language file or module to be included as the last step of any +project() command calls that specify <PROJECT-NAME> as the project +name. This is intended for injecting custom code into project builds without +modifying their source. See Code Injection for a more detailed +discussion of files potentially included during a project() call.

+

See also the CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE, +CMAKE_PROJECT_INCLUDE, CMAKE_PROJECT_INCLUDE_BEFORE, +and CMAKE_PROJECT_TOP_LEVEL_INCLUDES variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE_BEFORE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE_BEFORE.html new file mode 100644 index 0000000000000000000000000000000000000000..6907acc2547bf34e0b4f6c303b5a5e0179d1406c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_PROJECT-NAME_INCLUDE_BEFORE.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE

+
+

New in version 3.17.

+
+

A CMake language file or module to be included as the first step of any +project() command calls that specify <PROJECT-NAME> as the project +name. This is intended for injecting custom code into project builds without +modifying their source. See Code Injection for a more detailed +discussion of files potentially included during a project() call.

+

See also the CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE, +CMAKE_PROJECT_INCLUDE, CMAKE_PROJECT_INCLUDE_BEFORE, +and CMAKE_PROJECT_TOP_LEVEL_INCLUDES variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_TOP_LEVEL_INCLUDES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_TOP_LEVEL_INCLUDES.html new file mode 100644 index 0000000000000000000000000000000000000000..933ee6b6db0b49d8772a60d8dc78c7f698b343e4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_TOP_LEVEL_INCLUDES.html @@ -0,0 +1,160 @@ + + + + + + + + + CMAKE_PROJECT_TOP_LEVEL_INCLUDES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_TOP_LEVEL_INCLUDES

+
+

New in version 3.24.

+
+

Semicolon-separated list of CMake language +files to include as part of the very first project() call. +The files will be included immediately after the toolchain file has been read +(if one is specified) and platform variables have been set, but before any +languages have been enabled. Therefore, language-specific variables, +including things like CMAKE_<LANG>_COMPILER, might not be set. +See Code Injection for a more detailed discussion of files potentially +included during a project() call.

+

This variable is intended for specifying files that perform one-time setup +for the build. It provides an injection point for things like configuring +package managers, adding logic the user shares between projects (e.g. defining +their own custom build types), and so on. It is primarily for users to add +things specific to their environment, but not for specifying the toolchain +details (use CMAKE_TOOLCHAIN_FILE for that).

+

By default, this variable is empty. It is intended to be set by the user.

+

See also the CMAKE_PROJECT_INCLUDE, +CMAKE_PROJECT_INCLUDE_BEFORE, +CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE, and +CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..518aae069f9c2dae47cdcdd047cafcf8d8be4c12 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION.html @@ -0,0 +1,168 @@ + + + + + + + + + CMAKE_PROJECT_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_VERSION

+
+

New in version 3.12.

+
+

The version of the top level project.

+

This variable holds the version of the project as specified in the top +level CMakeLists.txt file by a project() command. In the event that +the top level CMakeLists.txt contains multiple project() calls, +the most recently called one from that top level CMakeLists.txt will determine +the value that CMAKE_PROJECT_VERSION contains. For example, consider +the following top level CMakeLists.txt:

+
cmake_minimum_required(VERSION 3.0)
+project(First VERSION 1.2.3)
+project(Second VERSION 3.4.5)
+add_subdirectory(sub)
+project(Third VERSION 6.7.8)
+
+
+

And sub/CMakeLists.txt with the following contents:

+
project(SubProj VERSION 1)
+message("CMAKE_PROJECT_VERSION = ${CMAKE_PROJECT_VERSION}")
+
+
+

The most recently seen project() command from the top level +CMakeLists.txt would be project(Second ...), so this will print:

+
CMAKE_PROJECT_VERSION = 3.4.5
+
+
+

To obtain the version from the most recent call to project() in +the current directory scope or above, see the PROJECT_VERSION +variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_MAJOR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_MAJOR.html new file mode 100644 index 0000000000000000000000000000000000000000..fee5633e80dce96efcbec45d0220671a281042a6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_MAJOR.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_PROJECT_VERSION_MAJOR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_VERSION_MAJOR

+
+

New in version 3.12.

+
+

The major version of the top level project.

+

This variable holds the major version of the project as specified in the top +level CMakeLists.txt file by a project() command. Please see +CMAKE_PROJECT_VERSION documentation for the behavior when +multiple project() commands are used in the sources.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_MINOR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_MINOR.html new file mode 100644 index 0000000000000000000000000000000000000000..feda0740c6290e5671a3e5e1b525bf887420d341 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_MINOR.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_PROJECT_VERSION_MINOR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_VERSION_MINOR

+
+

New in version 3.12.

+
+

The minor version of the top level project.

+

This variable holds the minor version of the project as specified in the top +level CMakeLists.txt file by a project() command. Please see +CMAKE_PROJECT_VERSION documentation for the behavior when +multiple project() commands are used in the sources.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_PATCH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_PATCH.html new file mode 100644 index 0000000000000000000000000000000000000000..d3f64595010da12809a7894717722b303a053d11 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_PATCH.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_PROJECT_VERSION_PATCH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_VERSION_PATCH

+
+

New in version 3.12.

+
+

The patch version of the top level project.

+

This variable holds the patch version of the project as specified in the top +level CMakeLists.txt file by a project() command. Please see +CMAKE_PROJECT_VERSION documentation for the behavior when +multiple project() commands are used in the sources.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_TWEAK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_TWEAK.html new file mode 100644 index 0000000000000000000000000000000000000000..bf9b165ea0fccce6c7f25f630d89e02a93877dfd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_PROJECT_VERSION_TWEAK.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_PROJECT_VERSION_TWEAK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_PROJECT_VERSION_TWEAK

+
+

New in version 3.12.

+
+

The tweak version of the top level project.

+

This variable holds the tweak version of the project as specified in the top +level CMakeLists.txt file by a project() command. Please see +CMAKE_PROJECT_VERSION documentation for the behavior when +multiple project() commands are used in the sources.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RANLIB.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RANLIB.html new file mode 100644 index 0000000000000000000000000000000000000000..f3d0ec3b9aebf7ced23598141eb91b1215f7f107 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RANLIB.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_RANLIB — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_RANLIB

+

Name of randomizing tool for static libraries.

+

This specifies name of the program that randomizes libraries on UNIX, +not used on Windows, but may be present.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RULE_MESSAGES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RULE_MESSAGES.html new file mode 100644 index 0000000000000000000000000000000000000000..a5f88a1d5869673e0748f74d1cfb1aa77835cfff --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RULE_MESSAGES.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_RULE_MESSAGES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_RULE_MESSAGES

+
+

New in version 3.13.

+
+

Specify whether to report a message for each make rule.

+

If set in the cache it is used to initialize the value of the RULE_MESSAGES property. +Users may disable the option in their local build tree to disable granular messages +and report only as each target completes in Makefile builds.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..ed2817241e3b6f0994514f51c3fa7a8590c59f06 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_RUNTIME_OUTPUT_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_RUNTIME_OUTPUT_DIRECTORY

+

Where to put all the RUNTIME +target files when built.

+

This variable is used to initialize the RUNTIME_OUTPUT_DIRECTORY +property on all the targets. See that target property for additional +information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY_CONFIG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY_CONFIG.html new file mode 100644 index 0000000000000000000000000000000000000000..8f20ec71dd6ae814bde0cf4036fcf1d7b518e7a6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_RUNTIME_OUTPUT_DIRECTORY_CONFIG.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_RUNTIME_OUTPUT_DIRECTORY_<CONFIG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_RUNTIME_OUTPUT_DIRECTORY_<CONFIG>

+
+

New in version 3.3.

+
+

Where to put all the RUNTIME +target files when built for a specific configuration.

+

This variable is used to initialize the +RUNTIME_OUTPUT_DIRECTORY_<CONFIG> property on all the targets. +See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SCRIPT_MODE_FILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SCRIPT_MODE_FILE.html new file mode 100644 index 0000000000000000000000000000000000000000..478d3547130e973711a0e18a75d07412d0b2b2b2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SCRIPT_MODE_FILE.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_SCRIPT_MODE_FILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SCRIPT_MODE_FILE

+

Full path to the cmake -P script file currently being +processed.

+

When run in cmake -P script mode, CMake sets this variable to +the full path of the script file. When run to configure a CMakeLists.txt +file, this variable is not set.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LIBRARY_ENABLE_EXPORTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LIBRARY_ENABLE_EXPORTS.html new file mode 100644 index 0000000000000000000000000000000000000000..346d91aa193f2fdc4e2ea56a7819825652565e63 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LIBRARY_ENABLE_EXPORTS.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_SHARED_LIBRARY_ENABLE_EXPORTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SHARED_LIBRARY_ENABLE_EXPORTS

+
+

New in version 3.27.

+
+

Specify whether shared library generates an import file.

+

This variable is used to initialize the ENABLE_EXPORTS target +property for shared library targets when they are created by calls to the +add_library() command. See the property documentation for details.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LIBRARY_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LIBRARY_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..5331e51dcf32b0423a96ccee299a937590c1bea6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LIBRARY_PREFIX.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_SHARED_LIBRARY_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SHARED_LIBRARY_PREFIX

+

The prefix for shared libraries that you link to.

+

The prefix to use for the name of a shared library, lib on UNIX.

+

CMAKE_SHARED_LIBRARY_PREFIX_<LANG> overrides this for language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LIBRARY_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LIBRARY_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..51d0841862c99581e4ba778c465e366f990ea4e3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LIBRARY_SUFFIX.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_SHARED_LIBRARY_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SHARED_LIBRARY_SUFFIX

+

The suffix for shared libraries that you link to.

+

The suffix to use for the end of a shared library filename, .dll on +Windows.

+

CMAKE_SHARED_LIBRARY_SUFFIX_<LANG> overrides this for language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LINKER_FLAGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LINKER_FLAGS.html new file mode 100644 index 0000000000000000000000000000000000000000..f8b167a6eaeb65b707fb6b629475a26348ff0a8b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LINKER_FLAGS.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_SHARED_LINKER_FLAGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SHARED_LINKER_FLAGS

+

Linker flags to be used to create shared libraries.

+

These flags will be used by the linker when creating a shared library.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LINKER_FLAGS_CONFIG_INIT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LINKER_FLAGS_CONFIG_INIT.html new file mode 100644 index 0000000000000000000000000000000000000000..c59283d5e1a95e658174391575688ae1f5ce3272 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LINKER_FLAGS_CONFIG_INIT.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_SHARED_LINKER_FLAGS_<CONFIG>_INIT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SHARED_LINKER_FLAGS_<CONFIG>_INIT

+
+

New in version 3.7.

+
+

Value used to initialize the CMAKE_SHARED_LINKER_FLAGS_<CONFIG> +cache entry the first time a build tree is configured. +This variable is meant to be set by a toolchain file. CMake may prepend or append content to +the value based on the environment and target platform.

+

See also CMAKE_SHARED_LINKER_FLAGS_INIT.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LINKER_FLAGS_INIT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LINKER_FLAGS_INIT.html new file mode 100644 index 0000000000000000000000000000000000000000..d6973f46e531d8b1f24ca5d6c5716601e23aac2b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_LINKER_FLAGS_INIT.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_SHARED_LINKER_FLAGS_INIT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SHARED_LINKER_FLAGS_INIT

+
+

New in version 3.7.

+
+

Value used to initialize the CMAKE_SHARED_LINKER_FLAGS +cache entry the first time a build tree is configured. +This variable is meant to be set by a toolchain file. CMake may prepend or append content to +the value based on the environment and target platform.

+

See also the configuration-specific variable +CMAKE_SHARED_LINKER_FLAGS_<CONFIG>_INIT.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_MODULE_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_MODULE_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..d33022cf6791a6f946448383768a8e2a9edc43c0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_MODULE_PREFIX.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_SHARED_MODULE_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SHARED_MODULE_PREFIX

+

The prefix for loadable modules that you link to.

+

The prefix to use for the name of a loadable module on this platform.

+

CMAKE_SHARED_MODULE_PREFIX_<LANG> overrides this for language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_MODULE_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_MODULE_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..1909c439a6d961a18c8be82405d61913cc639320 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SHARED_MODULE_SUFFIX.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_SHARED_MODULE_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SHARED_MODULE_SUFFIX

+

The suffix for shared libraries that you link to.

+

The suffix to use for the end of a loadable module filename on this +platform

+

CMAKE_SHARED_MODULE_SUFFIX_<LANG> overrides this for language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SIZEOF_VOID_P.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SIZEOF_VOID_P.html new file mode 100644 index 0000000000000000000000000000000000000000..343ec7d2a060bd2f2b5c589bd2d6568aac0e89c6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SIZEOF_VOID_P.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_SIZEOF_VOID_P — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SIZEOF_VOID_P

+

Size of a void pointer.

+

This is set to the size of a pointer on the target machine, and is determined +by a try compile. If a 64-bit size is found, then the library search +path is modified to look for 64-bit libraries first.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_BUILD_RPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_BUILD_RPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..b9d20c53d52dd2ca4d53dd4ffbd024c3b9674c86 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_BUILD_RPATH.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_SKIP_BUILD_RPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SKIP_BUILD_RPATH

+

Do not include RPATHs in the build tree.

+

Normally CMake uses the build tree for the RPATH when building +executables etc on systems that use RPATH. When the software is +installed the executables etc are relinked by CMake to have the +install RPATH. If this variable is set to TRUE then the software is +always built with no RPATH.

+

This is used to initialize the SKIP_BUILD_RPATH target property +for all targets. For more information on RPATH handling see +the INSTALL_RPATH and BUILD_RPATH target properties.

+

See also the CMAKE_SKIP_INSTALL_RPATH variable. +To omit RPATH in both the build and install steps, use +CMAKE_SKIP_RPATH instead.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_INSTALL_ALL_DEPENDENCY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_INSTALL_ALL_DEPENDENCY.html new file mode 100644 index 0000000000000000000000000000000000000000..5402b26e9abf57ec16359299d6eae652260409d8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_INSTALL_ALL_DEPENDENCY.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_SKIP_INSTALL_ALL_DEPENDENCY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SKIP_INSTALL_ALL_DEPENDENCY

+

Don't make the install target depend on the all target.

+

By default, the install target depends on the all target. This +has the effect, that when make install is invoked or INSTALL is +built, first the all target is built, then the installation starts. +If CMAKE_SKIP_INSTALL_ALL_DEPENDENCY is set to TRUE, this +dependency is not created, so the installation process will start immediately, +independent from whether the project has been completely built or not.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_INSTALL_RULES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_INSTALL_RULES.html new file mode 100644 index 0000000000000000000000000000000000000000..d13c3a1b7a826e64989306e520f735f701a39c85 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_INSTALL_RULES.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_SKIP_INSTALL_RULES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SKIP_INSTALL_RULES

+

Whether to disable generation of installation rules.

+

If TRUE, CMake will neither generate installation rules nor +will it generate cmake_install.cmake files. This variable is FALSE by +default.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_RPATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_RPATH.html new file mode 100644 index 0000000000000000000000000000000000000000..45f2ee91b3452be3aa97c1478e26ed8f26fbf0e8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SKIP_RPATH.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_SKIP_RPATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SKIP_RPATH

+

If true, do not add run time path information.

+

If this is set to TRUE, then the rpath information is not added to +compiled executables. The default is to add rpath information if the +platform supports it. This allows for easy running from the build +tree. To omit RPATH in the install step, but not the build step, use +CMAKE_SKIP_INSTALL_RPATH instead. To omit RPATH in the build step, +use CMAKE_SKIP_BUILD_RPATH.

+

For more information on RPATH handling see the INSTALL_RPATH +and BUILD_RPATH target properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SOURCE_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SOURCE_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..61cb8f1af1ce25d4f15faf8c2cf94f07fd6fbccd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SOURCE_DIR.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_SOURCE_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SOURCE_DIR

+

The path to the top level of the source tree.

+

This is the full path to the top level of the current CMake source +tree. For an in-source build, this would be the same as +CMAKE_BINARY_DIR.

+

When run in cmake -P script mode, CMake sets the variables +CMAKE_BINARY_DIR, CMAKE_SOURCE_DIR, +CMAKE_CURRENT_BINARY_DIR and +CMAKE_CURRENT_SOURCE_DIR to the current working directory.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STAGING_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STAGING_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..a703b35417db0d7d8c9bfe54447c03f87290bd1d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STAGING_PREFIX.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_STAGING_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_STAGING_PREFIX

+

This variable may be set to a path to install to when cross-compiling. This can +be useful if the path in CMAKE_SYSROOT is read-only, or otherwise +should remain pristine.

+

The CMAKE_STAGING_PREFIX location is also used as a search prefix +by the find_* commands. This can be controlled by setting the +CMAKE_FIND_NO_INSTALL_PREFIX variable.

+

If any RPATH/RUNPATH entries passed to the linker contain the +CMAKE_STAGING_PREFIX, the matching path fragments are replaced +with the CMAKE_INSTALL_PREFIX.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LIBRARY_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LIBRARY_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..7553d226c37ab2edfde3caa1014c19132352869f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LIBRARY_PREFIX.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_STATIC_LIBRARY_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_STATIC_LIBRARY_PREFIX

+

The prefix for static libraries that you link to.

+

The prefix to use for the name of a static library, lib on UNIX.

+

CMAKE_STATIC_LIBRARY_PREFIX_<LANG> overrides this for language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LIBRARY_SUFFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LIBRARY_SUFFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..3f186480c20497286e6571f491b397a990c0434d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LIBRARY_SUFFIX.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_STATIC_LIBRARY_SUFFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_STATIC_LIBRARY_SUFFIX

+

The suffix for static libraries that you link to.

+

The suffix to use for the end of a static library filename, .lib on +Windows.

+

CMAKE_STATIC_LIBRARY_SUFFIX_<LANG> overrides this for language <LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LINKER_FLAGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LINKER_FLAGS.html new file mode 100644 index 0000000000000000000000000000000000000000..de46a25b5d9498e94a21433ae1595764e0a1c77b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LINKER_FLAGS.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_STATIC_LINKER_FLAGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_STATIC_LINKER_FLAGS

+

Flags to be used to create static libraries. These flags will be passed +to the archiver when creating a static library.

+

See also CMAKE_STATIC_LINKER_FLAGS_<CONFIG>.

+
+

Note

+

Static libraries do not actually link. They are essentially archives +of object files. The use of the name "linker" in the name of this +variable is kept for compatibility.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LINKER_FLAGS_CONFIG_INIT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LINKER_FLAGS_CONFIG_INIT.html new file mode 100644 index 0000000000000000000000000000000000000000..7325b173d376ab40426137f0aed2b6fdc6da759d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LINKER_FLAGS_CONFIG_INIT.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_STATIC_LINKER_FLAGS_<CONFIG>_INIT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_STATIC_LINKER_FLAGS_<CONFIG>_INIT

+
+

New in version 3.7.

+
+

Value used to initialize the CMAKE_STATIC_LINKER_FLAGS_<CONFIG> +cache entry the first time a build tree is configured. +This variable is meant to be set by a toolchain file. CMake may prepend or append content to +the value based on the environment and target platform.

+

See also CMAKE_STATIC_LINKER_FLAGS_INIT.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LINKER_FLAGS_INIT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LINKER_FLAGS_INIT.html new file mode 100644 index 0000000000000000000000000000000000000000..6bcb3059cdfa3d5416f37d1b92959ef069192d6f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_STATIC_LINKER_FLAGS_INIT.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_STATIC_LINKER_FLAGS_INIT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_STATIC_LINKER_FLAGS_INIT

+
+

New in version 3.7.

+
+

Value used to initialize the CMAKE_STATIC_LINKER_FLAGS +cache entry the first time a build tree is configured. +This variable is meant to be set by a toolchain file. CMake may prepend or append content to +the value based on the environment and target platform.

+

See also the configuration-specific variable +CMAKE_STATIC_LINKER_FLAGS_<CONFIG>_INIT.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS.html new file mode 100644 index 0000000000000000000000000000000000000000..6574e3863e7668424407027bb4677186e408f620 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS.html @@ -0,0 +1,159 @@ + + + + + + + + + CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS

+
+

New in version 3.8.

+
+

This variable contains a list of env vars as a list of tokens with the +syntax var=value.

+

Example:

+
set(CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS
+   "FOO=FOO1\;FOO2\;FOON"
+   "BAR=BAR1\;BAR2\;BARN"
+   "BAZ=BAZ1\;BAZ2\;BAZN"
+   "FOOBAR=FOOBAR1\;FOOBAR2\;FOOBARN"
+   "VALID="
+   )
+
+
+

In case of malformed variables CMake will fail:

+
set(CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS
+    "THIS_IS_NOT_VALID"
+    )
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SUPPRESS_REGENERATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SUPPRESS_REGENERATION.html new file mode 100644 index 0000000000000000000000000000000000000000..2dfbd1ae12afa2c371bdf75cbf303d17d1ff54d3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SUPPRESS_REGENERATION.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_SUPPRESS_REGENERATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SUPPRESS_REGENERATION

+
+

New in version 3.12.

+
+

If CMAKE_SUPPRESS_REGENERATION is OFF, which is default, then CMake +adds a special target on which all other targets depend that checks the build +system and optionally re-runs CMake to regenerate the build system when +the target specification source changes.

+

If this variable evaluates to ON at the end of the top-level +CMakeLists.txt file, CMake will not add the regeneration target to the +build system or perform any build system checks.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSROOT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSROOT.html new file mode 100644 index 0000000000000000000000000000000000000000..d4640f6dc438e8db4bf2f45033919c3ab6118007 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSROOT.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_SYSROOT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSROOT

+

Path to pass to the compiler in the --sysroot flag.

+

The CMAKE_SYSROOT content is passed to the compiler in the --sysroot +flag, if supported. The path is also stripped from the RPATH/RUNPATH +if necessary on installation. The CMAKE_SYSROOT is also used to prefix +paths searched by the find_* commands.

+

This variable may only be set in a toolchain file specified by +the CMAKE_TOOLCHAIN_FILE variable.

+

See also the CMAKE_SYSROOT_COMPILE and +CMAKE_SYSROOT_LINK variables.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSROOT_COMPILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSROOT_COMPILE.html new file mode 100644 index 0000000000000000000000000000000000000000..bbef47628278a7c88b2cf52525e3decd278ccfb8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSROOT_COMPILE.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_SYSROOT_COMPILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSROOT_COMPILE

+
+

New in version 3.9.

+
+

Path to pass to the compiler in the --sysroot flag when compiling source +files. This is the same as CMAKE_SYSROOT but is used only for +compiling sources and not linking.

+

This variable may only be set in a toolchain file specified by +the CMAKE_TOOLCHAIN_FILE variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSROOT_LINK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSROOT_LINK.html new file mode 100644 index 0000000000000000000000000000000000000000..2326bb074bc9ce0cf5dc827bc85ae7f2fa6d71c8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSROOT_LINK.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_SYSROOT_LINK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM.html new file mode 100644 index 0000000000000000000000000000000000000000..f535ea6f3ac405b2277f483ba70295bc95a179b0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_SYSTEM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM

+

Composite name of operating system CMake is compiling for.

+

This variable is the composite of CMAKE_SYSTEM_NAME and +CMAKE_SYSTEM_VERSION, e.g. +${CMAKE_SYSTEM_NAME}-${CMAKE_SYSTEM_VERSION}. If +CMAKE_SYSTEM_VERSION is not set, then this variable is +the same as CMAKE_SYSTEM_NAME.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_APPBUNDLE_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_APPBUNDLE_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..ef19d92683a10f11fae1aceb7a3395e7993c81ed --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_APPBUNDLE_PATH.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_SYSTEM_APPBUNDLE_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_APPBUNDLE_PATH

+
+

New in version 3.4.

+
+

Search path for macOS application bundles used by the find_program(), +and find_package() commands. By default it contains the standard +directories for the current system. It is not intended to be modified by +the project, use CMAKE_APPBUNDLE_PATH for this.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_FRAMEWORK_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_FRAMEWORK_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..6dcd82ee633515e379ac8101977b54cbd0ceb852 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_FRAMEWORK_PATH.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_SYSTEM_FRAMEWORK_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_FRAMEWORK_PATH

+
+

New in version 3.4.

+
+

Search path for macOS frameworks used by the find_library(), +find_package(), find_path(), and find_file() +commands. By default it contains the standard directories for the +current system. It is not intended to be modified by the project, +use CMAKE_FRAMEWORK_PATH for this.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_IGNORE_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_IGNORE_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..835f876ec6b08c1dd029a4658f8dfc774b152f89 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_IGNORE_PATH.html @@ -0,0 +1,172 @@ + + + + + + + + + CMAKE_SYSTEM_IGNORE_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_IGNORE_PATH

+

Semicolon-separated list of directories +to be ignored by the various find...() commands.

+

For find_program(), find_library(), find_file(), +and find_path(), any file found in one of the listed directories +will be ignored. The listed directories do not apply recursively, so any +subdirectories to be ignored must also be explicitly listed. +CMAKE_SYSTEM_IGNORE_PATH does not affect the search prefixes used by these +four commands. To ignore individual paths under a search prefix +(e.g. bin, include, lib, etc.), each path must be listed in +CMAKE_SYSTEM_IGNORE_PATH as a full absolute path. CMAKE_SYSTEM_IGNORE_PREFIX_PATH +provides a more appropriate way to ignore a whole search prefix.

+

find_package() is also affected by CMAKE_SYSTEM_IGNORE_PATH, but only +for Config mode searches. Any <Name>Config.cmake or +<name>-config.cmake file found in one of the specified directories +will be ignored. In addition, any search prefix found in CMAKE_SYSTEM_IGNORE_PATH +will be skipped for backward compatibility reasons, but new code should +prefer to use CMAKE_SYSTEM_IGNORE_PREFIX_PATH to ignore prefixes instead.

+

Ignoring search locations can be useful in cross-compiling environments where +some system directories contain incompatible but possibly linkable libraries. +For example, on cross-compiled cluster environments, this allows a user to +ignore directories containing libraries meant for the front-end machine.

+

CMAKE_SYSTEM_IGNORE_PATH is populated by CMake as part of its platform +and toolchain setup. Its purpose is to ignore locations containing +incompatible binaries meant for the host rather than the target platform. +The project or end user should not modify this variable, they should use +CMAKE_IGNORE_PATH instead.

+

See also the following variables:

+ +
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_IGNORE_PREFIX_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_IGNORE_PREFIX_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..1cbbcfb40593a72d1d4c1cdbad4869b93033179b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_IGNORE_PREFIX_PATH.html @@ -0,0 +1,164 @@ + + + + + + + + + CMAKE_SYSTEM_IGNORE_PREFIX_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_IGNORE_PREFIX_PATH

+
+

New in version 3.23.

+
+

Semicolon-separated list of search prefixes +to be ignored by the find_program(), find_library(), +find_file(), and find_path() commands. +The prefixes are also ignored by the Config mode of the +find_package() command (Module mode is unaffected). +To ignore specific directories instead, see CMAKE_SYSTEM_IGNORE_PATH.

+

Ignoring search locations can be useful in cross-compiling environments where +some system directories contain incompatible but possibly linkable libraries. +For example, on cross-compiled cluster environments, this allows a user to +ignore directories containing libraries meant for the front-end machine.

+

CMAKE_SYSTEM_IGNORE_PREFIX_PATH is populated by CMake as part of its platform +and toolchain setup. Its purpose is to ignore locations containing +incompatible binaries meant for the host rather than the target platform. +The project or end user should not modify this variable, they should use +CMAKE_IGNORE_PREFIX_PATH instead.

+

See also the following variables:

+ +
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_INCLUDE_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_INCLUDE_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..340a5a0c7329ed66d3ee2a6b76d1b71ddd036391 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_INCLUDE_PATH.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_SYSTEM_INCLUDE_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_INCLUDE_PATH

+

Semicolon-separated list of directories specifying a search path +for the find_file() and find_path() commands. By default +this contains the standard directories for the current system. It is not +intended to be modified by the project; use CMAKE_INCLUDE_PATH for +this. See also CMAKE_SYSTEM_PREFIX_PATH.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_LIBRARY_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_LIBRARY_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..806b3996f163e6373de91b825edea20a9475d7d7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_LIBRARY_PATH.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_SYSTEM_LIBRARY_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_LIBRARY_PATH

+

Semicolon-separated list of directories specifying a search path +for the find_library() command. By default this contains the +standard directories for the current system. It is not intended to be +modified by the project; use CMAKE_LIBRARY_PATH for this. +See also CMAKE_SYSTEM_PREFIX_PATH.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..0a770c860aba286d3fd06177b5399abfe9ee4e6a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_NAME.html @@ -0,0 +1,166 @@ + + + + + + + + + CMAKE_SYSTEM_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_NAME

+

The name of the operating system for which CMake is to build. +See the CMAKE_SYSTEM_VERSION variable for the OS version.

+

Note that CMAKE_SYSTEM_NAME is not set to anything by default when running +in script mode, since it's not building anything.

+
+

System Name for Host Builds

+

CMAKE_SYSTEM_NAME is by default set to the same value as the +CMAKE_HOST_SYSTEM_NAME variable so that the build +targets the host system.

+
+
+

System Name for Cross Compiling

+

CMAKE_SYSTEM_NAME may be set explicitly when first configuring a new build +tree in order to enable cross compiling. +In this case the CMAKE_SYSTEM_VERSION variable must also be +set explicitly.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_PREFIX_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_PREFIX_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..fab5f40ef89599600ce1404bce5c5a5de7e5bf8a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_PREFIX_PATH.html @@ -0,0 +1,190 @@ + + + + + + + + + CMAKE_SYSTEM_PREFIX_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_PREFIX_PATH

+

Semicolon-separated list of directories specifying installation +prefixes to be searched by the find_package(), +find_program(), find_library(), find_file(), and +find_path() commands. Each command will add appropriate +subdirectories (like bin, lib, or include) as specified in its own +documentation.

+

By default this contains the system directories for the current system, the +CMAKE_INSTALL_PREFIX, and the CMAKE_STAGING_PREFIX. +The installation and staging prefixes may be excluded by setting +the CMAKE_FIND_NO_INSTALL_PREFIX variable before the +first project() invocation.

+

The system directories that are contained in CMAKE_SYSTEM_PREFIX_PATH are +locations that typically include installed software. An example being +/usr/local for UNIX based platforms. In addition to standard platform +locations, CMake will also add values to CMAKE_SYSTEM_PREFIX_PATH based on +environment variables. The environment variables and search locations that +CMake uses may evolve over time, as platforms and their conventions also +evolve. The following provides an indicative list of environment variables +and locations that CMake searches, but they are subject to change:

+
+
CrayLinuxEnvironment:
    +
  • ENV{SYSROOT_DIR}/

  • +
  • ENV{SYSROOT_DIR}/usr

  • +
  • ENV{SYSROOT_DIR}/usr/local

  • +
+
+
Darwin:
    +
  • ENV{SDKROOT}/usr When CMAKE_OSX_SYSROOT is not explicitly specified.

  • +
+
+
OpenBSD:
    +
  • ENV{LOCALBASE}

  • +
+
+
Unix:
    +
  • ENV{CONDA_PREFIX} when using a conda compiler

  • +
+
+
Windows:
    +
  • ENV{ProgramW6432}

  • +
  • ENV{ProgramFiles}

  • +
  • ENV{ProgramFiles(x86)}

  • +
  • ENV{SystemDrive}/Program Files

  • +
  • ENV{SystemDrive}/Program Files (x86)

  • +
+
+
+

CMAKE_SYSTEM_PREFIX_PATH is not intended to be modified by the project; +use CMAKE_PREFIX_PATH for this.

+

See also CMAKE_SYSTEM_INCLUDE_PATH, +CMAKE_SYSTEM_LIBRARY_PATH, CMAKE_SYSTEM_PROGRAM_PATH, +and CMAKE_SYSTEM_IGNORE_PATH.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_PROCESSOR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_PROCESSOR.html new file mode 100644 index 0000000000000000000000000000000000000000..130003c6b688b59574a60cfa4bddb069459b7050 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_PROCESSOR.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_SYSTEM_PROCESSOR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_PROCESSOR

+

When not cross-compiling, this variable has the same value as the +CMAKE_HOST_SYSTEM_PROCESSOR variable. In many cases, +this will correspond to the target architecture for the build, but +this is not guaranteed. (E.g. on Windows, the host may be AMD64 +even when using a MSVC cl compiler with a 32-bit target.)

+

When cross-compiling, a CMAKE_TOOLCHAIN_FILE should set +the CMAKE_SYSTEM_PROCESSOR variable to match target architecture +that it specifies (via CMAKE_<LANG>_COMPILER and perhaps +CMAKE_<LANG>_COMPILER_TARGET).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_PROGRAM_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_PROGRAM_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..d5af801c78aead2ccbe9099fdda056eadf40d72c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_PROGRAM_PATH.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_SYSTEM_PROGRAM_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_PROGRAM_PATH

+

Semicolon-separated list of directories specifying a search path +for the find_program() command. By default this contains the +standard directories for the current system. It is not intended to be +modified by the project; use CMAKE_PROGRAM_PATH for this. +See also CMAKE_SYSTEM_PREFIX_PATH.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..da7f87ece60ad2da7a3878ce645dffb2dd4357e1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_SYSTEM_VERSION.html @@ -0,0 +1,171 @@ + + + + + + + + + CMAKE_SYSTEM_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_SYSTEM_VERSION

+

The version of the operating system for which CMake is to build. +See the CMAKE_SYSTEM_NAME variable for the OS name.

+
+

System Version for Host Builds

+

When the CMAKE_SYSTEM_NAME variable takes its default value +then CMAKE_SYSTEM_VERSION is by default set to the same value as the +CMAKE_HOST_SYSTEM_VERSION variable so that the build targets +the host system version.

+

In the case of a host build then CMAKE_SYSTEM_VERSION may be set +explicitly when first configuring a new build tree in order to enable +targeting the build for a different version of the host operating system +than is actually running on the host. This is allowed and not considered +cross compiling so long as the binaries built for the specified OS version +can still run on the host.

+
+
+

System Version for Cross Compiling

+

When the CMAKE_SYSTEM_NAME variable is set explicitly to +enable cross compiling then the +value of CMAKE_SYSTEM_VERSION must also be set explicitly to specify +the target system version.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Swift_LANGUAGE_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Swift_LANGUAGE_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..93eaabf9dfe60670327f842965c5be73f955bc89 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Swift_LANGUAGE_VERSION.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_Swift_LANGUAGE_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_Swift_LANGUAGE_VERSION

+
+

New in version 3.7.

+
+

Set to the Swift language version number. If not set, the oldest legacy +version known to be available in the host Xcode version is assumed:

+
    +
  • Swift 4.0 for Xcode 10.2 and above.

  • +
  • Swift 3.0 for Xcode 8.3 and above.

  • +
  • Swift 2.3 for Xcode 8.2 and below.

  • +
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Swift_NUM_THREADS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Swift_NUM_THREADS.html new file mode 100644 index 0000000000000000000000000000000000000000..4626b080dba25ea8303d6ccbf0974768c07b80e3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_Swift_NUM_THREADS.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_Swift_NUM_THREADS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_Swift_NUM_THREADS

+
+

New in version 3.15.1.

+
+

Number of threads for parallel compilation for Swift targets.

+

This variable controls the number of parallel jobs that the swift driver creates +for building targets. If not specified, it will default to the number of +logical CPUs on the host.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TASKING_TOOLSET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TASKING_TOOLSET.html new file mode 100644 index 0000000000000000000000000000000000000000..4781399b6d54b128db1fafa691524f6f8d509b24 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TASKING_TOOLSET.html @@ -0,0 +1,167 @@ + + + + + + + + + CMAKE_TASKING_TOOLSET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_TASKING_TOOLSET

+
+

New in version 3.25.

+
+

Select the Tasking toolset which provides the compiler

+

Architecture compilers are provided by different toolchains with +incompatible versioning schemes. Set this variable in a +toolchain file so CMake can detect +the compiler features correctly. If no toolset is specified, +Standalone is assumed.

+

Due to the different versioning schemes, the compiler version +(CMAKE_<LANG>_COMPILER_VERSION) depends on the toolset and +architecture in use. If projects can be built with multiple toolsets or +architectures, the specified CMAKE_TASKING_TOOLSET and the +automatically determined CMAKE_<LANG>_COMPILER_ARCHITECTURE_ID +must be taken into account when comparing against the +CMAKE_<LANG>_COMPILER_VERSION.

+
+
TriCore

Compilers are provided by the TriCore toolset.

+
+
SmartCode

Compilers are provided by the SmartCode toolset.

+
+
Standalone

Compilers are provided by the standalone toolsets.

+
+

Note

+

For the TriCore architecture, the compiler from the TriCore toolset is +selected as standalone compiler.

+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TLS_VERIFY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TLS_VERIFY.html new file mode 100644 index 0000000000000000000000000000000000000000..ec199388e6f72bdc53737be982931054338c91a9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TLS_VERIFY.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_TLS_VERIFY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_TLS_VERIFY

+

Specify the default value for the file(DOWNLOAD) and +file(UPLOAD) commands' TLS_VERIFY options. +If not set, the default is off.

+

This variable is also used by the ExternalProject and +FetchContent modules for internal calls to file(DOWNLOAD).

+

TLS verification can help provide confidence that one is connecting +to the desired server. When downloading known content, one should +also use file hashes to verify it.

+
set(CMAKE_TLS_VERIFY TRUE)
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TOOLCHAIN_FILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TOOLCHAIN_FILE.html new file mode 100644 index 0000000000000000000000000000000000000000..19073f24f47696c8c2f575ebf5b4c9c2690acae3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TOOLCHAIN_FILE.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_TOOLCHAIN_FILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_TOOLCHAIN_FILE

+

Path to toolchain file supplied to cmake(1).

+

This variable is specified on the command line when cross-compiling with CMake. +It is the path to a file which is read early in the CMake run and which +specifies locations for compilers and toolchain utilities, and other target +platform and compiler related information.

+

Relative paths are allowed and are interpreted first as relative to the +build directory, and if not found, relative to the source directory.

+

This is initialized by the CMAKE_TOOLCHAIN_FILE environment +variable if it is set when a new build tree is first created.

+

See the CMAKE_PROJECT_TOP_LEVEL_INCLUDES variable for setting +other things not directly related to the toolchain.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TRY_COMPILE_NO_PLATFORM_VARIABLES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TRY_COMPILE_NO_PLATFORM_VARIABLES.html new file mode 100644 index 0000000000000000000000000000000000000000..4924786ac184268f1d95d8cf1d832735b6358c3e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TRY_COMPILE_NO_PLATFORM_VARIABLES.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_TRY_COMPILE_NO_PLATFORM_VARIABLES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_TRY_COMPILE_NO_PLATFORM_VARIABLES

+
+

New in version 3.24.

+
+

Set to a true value to tell the try_compile() command not +to propagate any platform variables into the test project.

+

The try_compile() command normally passes some CMake variables +that configure the platform and toolchain behavior into test projects. +See policy CMP0137. This variable may be set to disable +that behavior.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TRY_COMPILE_PLATFORM_VARIABLES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TRY_COMPILE_PLATFORM_VARIABLES.html new file mode 100644 index 0000000000000000000000000000000000000000..e1ecf76271ffa95992d510bbd3bfd9ecd00b9685 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TRY_COMPILE_PLATFORM_VARIABLES.html @@ -0,0 +1,169 @@ + + + + + + + + + CMAKE_TRY_COMPILE_PLATFORM_VARIABLES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_TRY_COMPILE_PLATFORM_VARIABLES

+
+

New in version 3.6.

+
+

List of variables that the try_compile() command source file signature +must propagate into the test project in order to target the same platform as +the host project.

+

This variable should not be set by project code. It is meant to be set by +CMake's platform information modules for the current toolchain, or by a +toolchain file when used with CMAKE_TOOLCHAIN_FILE.

+

Variables meaningful to CMake, such as CMAKE_<LANG>_FLAGS, are +propagated automatically. The CMAKE_TRY_COMPILE_PLATFORM_VARIABLES +variable may be set to pass custom variables meaningful to a toolchain file. +For example, a toolchain file may contain:

+
set(CMAKE_SYSTEM_NAME ...)
+set(CMAKE_TRY_COMPILE_PLATFORM_VARIABLES MY_CUSTOM_VARIABLE)
+# ... use MY_CUSTOM_VARIABLE ...
+
+
+

If a user passes -DMY_CUSTOM_VARIABLE=SomeValue to CMake then this +setting will be made visible to the toolchain file both for the main +project and for test projects generated by the try_compile() +command source file signature.

+
+

Changed in version 3.24: Listed variables are propagated to the try_compile() +whole-project signature too. +See CMP0137.

+
+
+

New in version 3.24: The CMAKE_TRY_COMPILE_NO_PLATFORM_VARIABLES variable may be +set to disable passing platform variables into the test project.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TRY_COMPILE_TARGET_TYPE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TRY_COMPILE_TARGET_TYPE.html new file mode 100644 index 0000000000000000000000000000000000000000..e3e006630f3f542ebe729874c1e388582ed42562 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TRY_COMPILE_TARGET_TYPE.html @@ -0,0 +1,153 @@ + + + + + + + + + CMAKE_TRY_COMPILE_TARGET_TYPE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_TRY_COMPILE_TARGET_TYPE

+
+

New in version 3.6.

+
+

Type of target generated for try_compile() calls using the +source file signature. Valid values are:

+
+
EXECUTABLE

Use add_executable() to name the source file in the +generated project. This is the default if no value is given.

+
+
STATIC_LIBRARY

Use add_library() with the STATIC option to name the +source file in the generated project. This avoids running the +linker and is intended for use with cross-compiling toolchains +that cannot link without custom flags or linker scripts.

+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TWEAK_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TWEAK_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..d05ce113e23985812802990843852cf29d130331 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_TWEAK_VERSION.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_TWEAK_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_TWEAK_VERSION

+

Defined to 0 for compatibility with code written for older +CMake versions that may have defined higher values.

+
+

Note

+

In CMake versions 2.8.2 through 2.8.12, this variable holds +the fourth version number component of the +CMAKE_VERSION variable.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_UNITY_BUILD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_UNITY_BUILD.html new file mode 100644 index 0000000000000000000000000000000000000000..87430fdd4867ca5e76de9cd79e40f4a0136f3281 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_UNITY_BUILD.html @@ -0,0 +1,157 @@ + + + + + + + + + CMAKE_UNITY_BUILD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_UNITY_BUILD

+
+

New in version 3.16.

+
+

This variable is used to initialize the UNITY_BUILD +property of targets when they are created. Setting it to true +enables batch compilation of multiple sources within each target. +This feature is known as a Unity or Jumbo build.

+

Projects should not set this variable, it is intended as a developer +control to be set on the cmake(1) command line or other +equivalent methods. The developer must have the ability to enable or +disable unity builds according to the capabilities of their own machine +and compiler.

+

By default, this variable is not set, which will result in unity builds +being disabled.

+
+

Note

+

This option currently does not work well in combination with +the CMAKE_EXPORT_COMPILE_COMMANDS variable.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_UNITY_BUILD_BATCH_SIZE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_UNITY_BUILD_BATCH_SIZE.html new file mode 100644 index 0000000000000000000000000000000000000000..4b65242c30245aeb4f5e7123ba5e140f1886d370 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_UNITY_BUILD_BATCH_SIZE.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_UNITY_BUILD_BATCH_SIZE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_UNITY_BUILD_BATCH_SIZE

+
+

New in version 3.16.

+
+

This variable is used to initialize the UNITY_BUILD_BATCH_SIZE +property of targets when they are created. It specifies the default upper +limit on the number of source files that may be combined in any one unity +source file when unity builds are enabled for a target.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_UNITY_BUILD_UNIQUE_ID.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_UNITY_BUILD_UNIQUE_ID.html new file mode 100644 index 0000000000000000000000000000000000000000..e99813b7bb04ef5389325a58a2576d6cf9028c54 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_UNITY_BUILD_UNIQUE_ID.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_UNITY_BUILD_UNIQUE_ID — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_UNITY_BUILD_UNIQUE_ID

+
+

New in version 3.20.

+
+

This variable is used to initialize the UNITY_BUILD_UNIQUE_ID +property of targets when they are created. It specifies the name of the +unique identifier generated per file in a unity build.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_USER_MAKE_RULES_OVERRIDE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_USER_MAKE_RULES_OVERRIDE.html new file mode 100644 index 0000000000000000000000000000000000000000..015f7b7a0b15fc6f5de9040517cf4bcbebe86a84 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_USER_MAKE_RULES_OVERRIDE.html @@ -0,0 +1,160 @@ + + + + + + + + + CMAKE_USER_MAKE_RULES_OVERRIDE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_USER_MAKE_RULES_OVERRIDE

+

Specify a CMake file that overrides platform information.

+

CMake loads the specified file while enabling support for each +language from either the project() or enable_language() +commands. It is loaded after CMake's builtin compiler and platform information +modules have been loaded but before the information is used. The file +may set platform information variables to override CMake's defaults. +See CMAKE_USER_MAKE_RULES_OVERRIDE_<LANG> for the language-specific +version of this variable.

+

This feature is intended for use only in overriding information +variables that must be set before CMake builds its first test project +to check that the compiler for a language works. It should not be +used to load a file in cases that a normal include() will work. Use +it only as a last resort for behavior that cannot be achieved any +other way. For example, one may set the +CMAKE_C_FLAGS_INIT variable +to change the default value used to initialize the +CMAKE_C_FLAGS variable +before it is cached. The override file should NOT be used to set anything +that could be set after languages are enabled, such as variables like +CMAKE_RUNTIME_OUTPUT_DIRECTORY that affect the placement of +binaries. Information set in the file will be used for try_compile() +and try_run() builds too.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_USER_MAKE_RULES_OVERRIDE_LANG.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_USER_MAKE_RULES_OVERRIDE_LANG.html new file mode 100644 index 0000000000000000000000000000000000000000..afb8bdb83aa8cf6727bdc3bc865c6402547d71f6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_USER_MAKE_RULES_OVERRIDE_LANG.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_USER_MAKE_RULES_OVERRIDE_<LANG> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_USER_MAKE_RULES_OVERRIDE_<LANG>

+

Specify a CMake file that overrides platform information for <LANG>.

+

This is a language-specific version of +CMAKE_USER_MAKE_RULES_OVERRIDE loaded only when enabling language +<LANG>.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_USE_RELATIVE_PATHS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_USE_RELATIVE_PATHS.html new file mode 100644 index 0000000000000000000000000000000000000000..80f289650b49b7699d579ef9553936d3e0832d57 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_USE_RELATIVE_PATHS.html @@ -0,0 +1,140 @@ + + + + + + + + + CMAKE_USE_RELATIVE_PATHS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_USE_RELATIVE_PATHS

+

This variable has no effect. The partially implemented effect it +had in previous releases was removed in CMake 3.4.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VERBOSE_MAKEFILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VERBOSE_MAKEFILE.html new file mode 100644 index 0000000000000000000000000000000000000000..51b2a294778b8ba0de893cd9b72da2adf6290dbc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VERBOSE_MAKEFILE.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_VERBOSE_MAKEFILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VERBOSE_MAKEFILE

+

Enable verbose output from Makefile builds.

+

This variable is a cache entry initialized (to FALSE) by +the project() command. Users may enable the option +in their local build tree to get more verbose output from +Makefile builds and show each command line as it is launched.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VERIFY_INTERFACE_HEADER_SETS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VERIFY_INTERFACE_HEADER_SETS.html new file mode 100644 index 0000000000000000000000000000000000000000..429877e2c2eb085a028694146607a78ba84068bc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VERIFY_INTERFACE_HEADER_SETS.html @@ -0,0 +1,171 @@ + + + + + + + + + CMAKE_VERIFY_INTERFACE_HEADER_SETS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VERIFY_INTERFACE_HEADER_SETS

+
+

New in version 3.24.

+
+

This variable is used to initialize the +VERIFY_INTERFACE_HEADER_SETS property of targets when they are +created. Setting it to true enables header set verification.

+

Projects should not normally set this variable, it is intended as a developer +control to be set on the cmake(1) command line or other +equivalent methods. The developer must have the ability to enable or +disable header set verification according to the capabilities of their own +machine and compiler.

+

Verification of a dependency's header sets is not typically of interest +to developers. Therefore, FetchContent_MakeAvailable() explicitly +sets CMAKE_VERIFY_INTERFACE_HEADER_SETS to false for the duration of its +call, but restores its original value before returning. If a project brings +a dependency directly into the main build (e.g. calling +add_subdirectory() on a vendored project from a git submodule), it +should also do likewise. For example:

+
# Save original setting so we can restore it later
+set(want_header_set_verification ${CMAKE_VERIFY_INTERFACE_HEADER_SETS})
+
+# Include the vendored dependency with header set verification disabled
+set(CMAKE_VERIFY_INTERFACE_HEADER_SETS OFF)
+add_subdirectory(...)   # Vendored sources, e.g. from git submodules
+
+# Add the project's own sources. Restore the developer's original choice
+# for whether to enable header set verification.
+set(CMAKE_VERIFY_INTERFACE_HEADER_SETS ${want_header_set_verification})
+add_subdirectory(src)
+
+
+

By default, this variable is not set, which will result in header set +verification being disabled.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..05ef0b5a3d4cef448947f4b35631d5e9e61d03a4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_COMMAND.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_VS_DEBUGGER_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_DEBUGGER_COMMAND

+
+

New in version 3.27.

+
+

This variable is used to initialize the VS_DEBUGGER_COMMAND +property on each target as it is created. See that target property +for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_COMMAND_ARGUMENTS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_COMMAND_ARGUMENTS.html new file mode 100644 index 0000000000000000000000000000000000000000..16a3ecf0e88ab4dfc0d636a864c2ddbc318b3f7b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_COMMAND_ARGUMENTS.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_VS_DEBUGGER_COMMAND_ARGUMENTS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_DEBUGGER_COMMAND_ARGUMENTS

+
+

New in version 3.27.

+
+

This variable is used to initialize the VS_DEBUGGER_COMMAND_ARGUMENTS +property on each target as it is created. See that target property +for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_ENVIRONMENT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_ENVIRONMENT.html new file mode 100644 index 0000000000000000000000000000000000000000..4252ae685370f123671b928e8547fe9db300f65d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_ENVIRONMENT.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_VS_DEBUGGER_ENVIRONMENT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_DEBUGGER_ENVIRONMENT

+
+

New in version 3.27.

+
+

This variable is used to initialize the VS_DEBUGGER_ENVIRONMENT +property on each target as it is created. See that target property +for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_WORKING_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_WORKING_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..efa9038899ebb18cbb22418a6219736e64475b0f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEBUGGER_WORKING_DIRECTORY.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_VS_DEBUGGER_WORKING_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_DEBUGGER_WORKING_DIRECTORY

+
+

New in version 3.27.

+
+

This variable is used to initialize the VS_DEBUGGER_WORKING_DIRECTORY +property on each target as it is created. See that target property +for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEVENV_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEVENV_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..d621bf0473045ddbdd280bc363b79cceb88940f0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_DEVENV_COMMAND.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_VS_DEVENV_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_DEVENV_COMMAND

+

The generators for Visual Studio 9 2008 and above set this +variable to the devenv.com command installed with the corresponding +Visual Studio version. Note that this variable may be empty on +Visual Studio Express editions because they do not provide this tool.

+

This variable is not defined by other generators even if devenv.com +is installed on the computer.

+

The CMAKE_VS_MSBUILD_COMMAND is also provided for +Visual Studio 11 2012 and above. +See also the CMAKE_MAKE_PROGRAM variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD.html new file mode 100644 index 0000000000000000000000000000000000000000..e6d7be917d4a2e466166232385b7cce8fd37ff5c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD

+
+

New in version 3.3.

+
+

Include INSTALL target to default build.

+

In Visual Studio solution, by default the INSTALL target will not be part +of the default build. Setting this variable will enable the INSTALL target +to be part of the default build.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_INTEL_Fortran_PROJECT_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_INTEL_Fortran_PROJECT_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..0278a2ad42cb7d907e5cf8be0111b0731f224099 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_INTEL_Fortran_PROJECT_VERSION.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_VS_INTEL_Fortran_PROJECT_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_INTEL_Fortran_PROJECT_VERSION

+

When generating for Visual Studio 9 2008 or greater with the Intel +Fortran plugin installed, this specifies the .vfproj project file format +version. This is intended for internal use by CMake and should not be +used by project code.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_JUST_MY_CODE_DEBUGGING.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_JUST_MY_CODE_DEBUGGING.html new file mode 100644 index 0000000000000000000000000000000000000000..0ce62edfcdfacb33b8ef6e13152c6f1f1cbe0aec --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_JUST_MY_CODE_DEBUGGING.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_VS_JUST_MY_CODE_DEBUGGING — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_JUST_MY_CODE_DEBUGGING

+
+

New in version 3.15.

+
+

Enable Just My Code with Visual Studio debugger.

+

This variable is used to initialize the VS_JUST_MY_CODE_DEBUGGING +property on all targets when they are created. See that target property for +additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_MSBUILD_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_MSBUILD_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..5dc15615337e2331f65714d8945d01119e4f5ab0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_MSBUILD_COMMAND.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_VS_MSBUILD_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_MSBUILD_COMMAND

+

The generators for Visual Studio 11 2012 and above set this +variable to the MSBuild.exe command installed with the corresponding +Visual Studio version.

+

This variable is not defined by other generators even if MSBuild.exe +is installed on the computer.

+

The CMAKE_VS_DEVENV_COMMAND is also provided for the +non-Express editions of Visual Studio. +See also the CMAKE_MAKE_PROGRAM variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_NO_COMPILE_BATCHING.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_NO_COMPILE_BATCHING.html new file mode 100644 index 0000000000000000000000000000000000000000..076f2a87d40eac431c3ff6c434dd59412049ff19 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_NO_COMPILE_BATCHING.html @@ -0,0 +1,163 @@ + + + + + + + + + CMAKE_VS_NO_COMPILE_BATCHING — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_NO_COMPILE_BATCHING

+
+

New in version 3.24.

+
+

Turn off compile batching when using Visual Studio Generators.

+

This variable is used to initialize the VS_NO_COMPILE_BATCHING +property on all targets when they are created. See that target property for +additional information.

+
+

Example

+

This shows setting the property for the target foo using the variable.

+
set(CMAKE_VS_NO_COMPILE_BATCHING ON)
+add_library(foo SHARED foo.cpp)
+
+
+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_NUGET_PACKAGE_RESTORE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_NUGET_PACKAGE_RESTORE.html new file mode 100644 index 0000000000000000000000000000000000000000..0bacbd74ea7fbb1fcc04985d970418175a952394 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_NUGET_PACKAGE_RESTORE.html @@ -0,0 +1,154 @@ + + + + + + + + + CMAKE_VS_NUGET_PACKAGE_RESTORE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_NUGET_PACKAGE_RESTORE

+
+

New in version 3.23.

+
+

When using a Visual Studio generator, this cache variable controls +if msbuild should automatically attempt to restore NuGet packages +prior to a build. NuGet packages can be defined using the +VS_PACKAGE_REFERENCES property on a target. If no +package references are defined, this setting will do nothing.

+

The command line option --resolve-package-references can be used +alternatively to control the resolve behavior globally. This option +will take precedence over the cache variable.

+

Targets that use the DOTNET_SDK are required to run a +restore before building. Disabling this option may cause the build +to fail in such projects.

+

This setting is stored as a cache entry. Default value is ON.

+

See also the VS_PACKAGE_REFERENCES property.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_PLATFORM_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_PLATFORM_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..e95aef438f13fa1f065dcbc46862f75c27826f9c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_PLATFORM_NAME.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_VS_PLATFORM_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_PLATFORM_NAME

+
+

New in version 3.1.

+
+

Visual Studio target platform name used by the current generator.

+

VS 8 and above allow project files to specify a target platform. +CMake provides the name of the chosen platform in this variable. +See the CMAKE_GENERATOR_PLATFORM variable for details.

+

See also the CMAKE_VS_PLATFORM_NAME_DEFAULT variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_PLATFORM_TOOLSET.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_PLATFORM_TOOLSET.html new file mode 100644 index 0000000000000000000000000000000000000000..a2d7c6cbf964f2c6f82b1afe17a3ab676a6efb56 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_PLATFORM_TOOLSET.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_VS_PLATFORM_TOOLSET — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_PLATFORM_TOOLSET

+

Visual Studio Platform Toolset name.

+

VS 10 and above use MSBuild under the hood and support multiple +compiler toolchains. CMake may specify a toolset explicitly, such as +v110 for VS 11 or Windows7.1SDK for 64-bit support in VS 10 +Express. CMake provides the name of the chosen toolset in this +variable.

+

See the CMAKE_GENERATOR_TOOLSET variable for details.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE.html new file mode 100644 index 0000000000000000000000000000000000000000..c477be1e999661eec0bc92aaf8c56a84c685017e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE

+
+

New in version 3.8.

+
+

Visual Studio preferred tool architecture.

+

The Visual Studio Generators for VS 2013 and above support using +either the 32-bit or 64-bit host toolchains by specifying a host=x86 +or host=x64 value in the CMAKE_GENERATOR_TOOLSET option. +CMake provides the selected toolchain architecture preference in this +variable (x86, x64, ARM64 or empty).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_SDK_INCLUDE_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_SDK_INCLUDE_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..af358b69cf291f2486a6abd6a793666eaec50011 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_SDK_INCLUDE_DIRECTORIES.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_VS_SDK_INCLUDE_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_SDK_INCLUDE_DIRECTORIES

+
+

New in version 3.12.

+
+

This variable allows to override Visual Studio default Include Directories.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_SDK_LIBRARY_WINRT_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_SDK_LIBRARY_WINRT_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..57e3c70e4d4aec9ee420cc58a5d24f727b381d4c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_SDK_LIBRARY_WINRT_DIRECTORIES.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_VS_SDK_LIBRARY_WINRT_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_SDK_LIBRARY_WINRT_DIRECTORIES

+
+

New in version 3.12.

+
+

This variable allows to override Visual Studio default Library WinRT +Directories.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_SDK_REFERENCE_DIRECTORIES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_SDK_REFERENCE_DIRECTORIES.html new file mode 100644 index 0000000000000000000000000000000000000000..388e66df578797dce23ab0af2acf2e2ff3505589 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_SDK_REFERENCE_DIRECTORIES.html @@ -0,0 +1,142 @@ + + + + + + + + + CMAKE_VS_SDK_REFERENCE_DIRECTORIES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_SDK_REFERENCE_DIRECTORIES

+
+

New in version 3.12.

+
+

This variable allows to override Visual Studio default Reference Directories.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_TARGET_FRAMEWORK_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_TARGET_FRAMEWORK_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..5ac190c11e323f36b5f19f7d7451ec90b470f106 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_TARGET_FRAMEWORK_VERSION.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_VS_TARGET_FRAMEWORK_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_TARGET_FRAMEWORK_VERSION

+
+

New in version 3.22.

+
+

Visual Studio target framework version.

+

In some cases, the Visual Studio Generators may use an explicit value +for the MSBuild TargetFrameworkVersion setting in .csproj files. +CMake provides the chosen value in this variable.

+

See the CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION variable +and DOTNET_TARGET_FRAMEWORK_VERSION target property to +specify custom TargetFrameworkVersion values for project targets.

+

See also CMAKE_VS_TARGET_FRAMEWORK_IDENTIFIER and +CMAKE_VS_TARGET_FRAMEWORK_TARGETS_VERSION.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_VERSION_BUILD_NUMBER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_VERSION_BUILD_NUMBER.html new file mode 100644 index 0000000000000000000000000000000000000000..ff0f4efc9fb950297990ec2c4d3292e37e535998 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_VERSION_BUILD_NUMBER.html @@ -0,0 +1,163 @@ + + + + + + + + + CMAKE_VS_VERSION_BUILD_NUMBER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_VERSION_BUILD_NUMBER

+
+

New in version 3.26.

+
+

Visual Studio version.

+

Visual Studio Generators for VS 2017 and above set this +variable to the Visual Studio version build number in the format +<major>.<minor>.<date>.<build>.

+

The components are:

+

<major>.<minor>

+
+

The VS major and minor version numbers. +These are the same as the release version numbers.

+
+

<date>

+
+

A build date in the format MMMDD, where MMM is a month index +since an epoch used by Microsoft, and DD is a day in that month.

+
+

<build>

+
+

A build index on the day represented by <date>.

+
+

The build number is reported by vswhere as installationVersion. +For example, VS 16.11.10 has build number 16.11.32126.315.

+

See also the CMAKE_GENERATOR_INSTANCE variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..bea84738655f58399fc4417e672be497b9c5d429 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION

+
+

New in version 3.27.

+
+

Tell Visual Studio Generators to use the given +Windows Target Platform Minimum Version.

+

This variable is used to initialize the +VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION property on all +targets when they are created. See that target property for +additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..975aae32950fa7f84d04d8ebe5361429e0e5850c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION.html @@ -0,0 +1,172 @@ + + + + + + + + + CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION

+
+

New in version 3.4.

+
+

Visual Studio Windows Target Platform Version.

+

When targeting Windows 10 and above, Visual Studio Generators for +VS 2015 and above support specification of a Windows SDK version:

+
    +
  • If CMAKE_GENERATOR_PLATFORM specifies a version= field, +as documented by Visual Studio Platform Selection, that SDK +version is selected.

  • +
  • Otherwise, if the WindowsSDKVersion environment variable +is set to an available SDK version, that version is selected. +This is intended for use in environments established by vcvarsall.bat +or similar scripts.

    +
    +

    New in version 3.27: This is enabled by policy CMP0149.

    +
    +
  • +
  • Otherwise, if CMAKE_SYSTEM_VERSION is set to an available +SDK version, that version is selected.

    +
    +

    Changed in version 3.27: This is disabled by policy CMP0149.

    +
    +
  • +
  • Otherwise, CMake uses the latest Windows SDK version available.

  • +
+

The chosen Windows target version number is provided +in CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION. If no Windows 10 SDK +is available this value will be empty.

+

One may set a CMAKE_WINDOWS_KITS_10_DIR environment variable +to an absolute path to tell CMake to look for Windows 10 SDKs in +a custom location. The specified directory is expected to contain +Include/10.0.* directories.

+

See also CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM.html new file mode 100644 index 0000000000000000000000000000000000000000..31b6b7315c31a28b08494040d33ee91cbf2a0fb3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM

+
+

New in version 3.19.

+
+

Override the Windows 10 SDK Maximum Version for VS 2015 and beyond.

+

The CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM variable may +be set to a false value (e.g. OFF, FALSE, or 0) or the SDK version +to use as the maximum (e.g. 10.0.14393.0). If unset, the default depends +on which version of Visual Studio is targeted by the current generator.

+

This can be used to exclude Windows SDK versions from consideration for +CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINRT_BY_DEFAULT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINRT_BY_DEFAULT.html new file mode 100644 index 0000000000000000000000000000000000000000..2d032d9468c289691c0c5a8a018229a5d5c1e00c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_VS_WINRT_BY_DEFAULT.html @@ -0,0 +1,153 @@ + + + + + + + + + CMAKE_VS_WINRT_BY_DEFAULT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_VS_WINRT_BY_DEFAULT

+
+

New in version 3.13.

+
+

Inform Visual Studio Generators for VS 2010 and above that the +target platform enables WinRT compilation by default and it needs to +be explicitly disabled if /ZW or VS_WINRT_COMPONENT is +omitted (as opposed to enabling it when either of those options is +present)

+

This makes cmake configuration consistent in terms of WinRT among +platforms - if you did not enable the WinRT compilation explicitly, it +will be disabled (by either not enabling it or explicitly disabling it)

+

Note: WinRT compilation is always explicitly disabled for C language +source files, even if it is expliclty enabled for a project

+

This variable is meant to be set by a +toolchain file for such platforms.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WARN_DEPRECATED.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WARN_DEPRECATED.html new file mode 100644 index 0000000000000000000000000000000000000000..af5dbcdcf8f4ce4aa033a19f5404036cac876514 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WARN_DEPRECATED.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_WARN_DEPRECATED — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_WARN_DEPRECATED

+

Whether to issue warnings for deprecated functionality.

+

If not FALSE, use of deprecated functionality will issue warnings. +If this variable is not set, CMake behaves as if it were set to TRUE.

+

When running cmake(1), this option can be enabled with the +-Wdeprecated option, or disabled with the +-Wno-deprecated option.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WARN_ON_ABSOLUTE_INSTALL_DESTINATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WARN_ON_ABSOLUTE_INSTALL_DESTINATION.html new file mode 100644 index 0000000000000000000000000000000000000000..3ec5676aae2ba7a57207d1f4cd145da0d1fffe64 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WARN_ON_ABSOLUTE_INSTALL_DESTINATION.html @@ -0,0 +1,143 @@ + + + + + + + + + CMAKE_WARN_ON_ABSOLUTE_INSTALL_DESTINATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_WARN_ON_ABSOLUTE_INSTALL_DESTINATION

+

Ask cmake_install.cmake script to warn each time a file with absolute +INSTALL DESTINATION is encountered.

+

This variable is used by CMake-generated cmake_install.cmake scripts. +If one sets this variable to ON while running the script, it may get +warning messages from the script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WATCOM_RUNTIME_LIBRARY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WATCOM_RUNTIME_LIBRARY.html new file mode 100644 index 0000000000000000000000000000000000000000..ac6d2cabd2b07f6c8a6137129329c13db1d37bb7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WATCOM_RUNTIME_LIBRARY.html @@ -0,0 +1,184 @@ + + + + + + + + + CMAKE_WATCOM_RUNTIME_LIBRARY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_WATCOM_RUNTIME_LIBRARY

+
+

New in version 3.24.

+
+

Select the Watcom runtime library for use by compilers targeting the Watcom ABI. +This variable is used to initialize the WATCOM_RUNTIME_LIBRARY +property on all targets as they are created. It is also propagated by +calls to the try_compile() command into the test project.

+

The allowed values are:

+
+
SingleThreaded

Compile without additional flags to use a single-threaded +statically-linked runtime library.

+
+
SingleThreadedDLL

Compile with -br or equivalent flag(s) to use a single-threaded +dynamically-linked runtime library. This is not available for Linux +targets.

+
+
MultiThreaded

Compile with -bm or equivalent flag(s) to use a multi-threaded +statically-linked runtime library.

+
+
MultiThreadedDLL

Compile with -bm -br or equivalent flag(s) to use a multi-threaded +dynamically-linked runtime library. This is not available for Linux +targets.

+
+
+

The value is ignored on non-Watcom compilers but an unsupported value will +be rejected as an error when using a compiler targeting the Watcom ABI.

+

The value may also be the empty string ("") in which case no runtime +library selection flag will be added explicitly by CMake.

+

Use generator expressions to +support per-configuration specification.

+

For example, the code:

+
set(CMAKE_WATCOM_RUNTIME_LIBRARY "MultiThreaded")
+
+
+

selects for all following targets a multi-threaded statically-linked runtime +library.

+

If this variable is not set then the WATCOM_RUNTIME_LIBRARY target +property will not be set automatically. If that property is not set then +CMake uses the default value MultiThreadedDLL on Windows and +SingleThreaded on other platforms to select a Watcom runtime library.

+
+

Note

+

This variable has effect only when policy CMP0136 is set to NEW +prior to the first project() or enable_language() command +that enables a language using a compiler targeting the Watcom ABI.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WIN32_EXECUTABLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WIN32_EXECUTABLE.html new file mode 100644 index 0000000000000000000000000000000000000000..bbe3e4f0e07b791b6eda8c49bfb0e215b632184f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WIN32_EXECUTABLE.html @@ -0,0 +1,141 @@ + + + + + + + + + CMAKE_WIN32_EXECUTABLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_WIN32_EXECUTABLE

+

Default value for WIN32_EXECUTABLE of targets.

+

This variable is used to initialize the WIN32_EXECUTABLE property +on all the targets. See that target property for additional information.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS.html new file mode 100644 index 0000000000000000000000000000000000000000..9084b5f92a35e7cdeded7a87bc943dc573c4bc4a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS.html @@ -0,0 +1,144 @@ + + + + + + + + + CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS

+
+

New in version 3.4.

+
+

Default value for WINDOWS_EXPORT_ALL_SYMBOLS target property. +This variable is used to initialize the property on each target as it is +created.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_ATTRIBUTE_an-attribute.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_ATTRIBUTE_an-attribute.html new file mode 100644 index 0000000000000000000000000000000000000000..a46c52724ad65458fb6d0acb5cf4dd81a3792557 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_ATTRIBUTE_an-attribute.html @@ -0,0 +1,156 @@ + + + + + + + + + CMAKE_XCODE_ATTRIBUTE_<an-attribute> — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_ATTRIBUTE_<an-attribute>

+
+

New in version 3.1.

+
+

Set Xcode target attributes directly.

+

Tell the Xcode generator to set <an-attribute> to a given +value in the generated Xcode project. Ignored on other generators.

+

This offers low-level control over the generated Xcode project file. +It is meant as a last resort for specifying settings that CMake does +not otherwise have a way to control. Although this can override a +setting CMake normally produces on its own, doing so bypasses CMake's +model of the project and can break things.

+

See the XCODE_ATTRIBUTE_<an-attribute> target property +to set attributes on a specific target.

+

Contents of CMAKE_XCODE_ATTRIBUTE_<an-attribute> may use +"generator expressions" with the syntax $<...>. See the +cmake-generator-expressions(7) manual for available +expressions. See the cmake-buildsystem(7) manual +for more on defining buildsystem properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_BUILD_SYSTEM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_BUILD_SYSTEM.html new file mode 100644 index 0000000000000000000000000000000000000000..8d2078d1e532ff5805731ba0f92158f99b18fb18 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_BUILD_SYSTEM.html @@ -0,0 +1,158 @@ + + + + + + + + + CMAKE_XCODE_BUILD_SYSTEM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_BUILD_SYSTEM

+
+

New in version 3.19.

+
+

Xcode build system selection.

+

The Xcode generator defines this variable to indicate which +variant of the Xcode build system will be used. The value is the +version of Xcode in which the corresponding build system first became +mature enough for use by CMake. The possible values are:

+
+
1

The original Xcode build system. +This is the default when using Xcode 11.x or below.

+
+
12

The Xcode "new build system" introduced by Xcode 10. +It became mature enough for use by CMake in Xcode 12. +This is the default when using Xcode 12.x or above.

+
+
+

The CMAKE_XCODE_BUILD_SYSTEM variable is informational and should not +be modified by project code. See the Toolset and Build System Selection +documentation section to select the Xcode build system.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY.html new file mode 100644 index 0000000000000000000000000000000000000000..9c844fa355cc9da9ee2bde24b56ad5f47255781b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY

+
+

New in version 3.11.

+
+

If enabled, the Xcode generator will generate only a +single Xcode project file for the topmost project() command +instead of generating one for every project() command.

+

This could be useful to speed up the CMake generation step for +large projects and to work-around a bug in the ZERO_CHECK logic.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_LINK_BUILD_PHASE_MODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_LINK_BUILD_PHASE_MODE.html new file mode 100644 index 0000000000000000000000000000000000000000..eec8718d017a8bc6111f65a6af846fb661449c88 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_LINK_BUILD_PHASE_MODE.html @@ -0,0 +1,145 @@ + + + + + + + + + CMAKE_XCODE_LINK_BUILD_PHASE_MODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER.html new file mode 100644 index 0000000000000000000000000000000000000000..3b47462cc0c68b965b8332f6e0f89c6abf3b6acd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER

+
+

New in version 3.13.

+
+

Whether to enable Address Sanitizer in the Diagnostics +section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_ADDRESS_SANITIZER +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN.html new file mode 100644 index 0000000000000000000000000000000000000000..73784b6762a4689c0bc6b0ac4f4f66c69facbce4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN

+
+

New in version 3.13.

+
+

Whether to enable Detect use of stack after return +in the Diagnostics section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING.html new file mode 100644 index 0000000000000000000000000000000000000000..c298e4986efb4bc031790ca03b6f9fa302f7e4f1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING

+
+

New in version 3.16.

+
+

Whether to enable +Allow debugging when using document Versions Browser +in the Options section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.html new file mode 100644 index 0000000000000000000000000000000000000000..97e957958ab810392f82511261ff3da18a50d376 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER

+
+

New in version 3.13.

+
+

Whether to disable the Main Thread Checker +in the Diagnostics section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.html new file mode 100644 index 0000000000000000000000000000000000000000..f7e1716212f118f666d3e820ea82ab6b109750ca --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS

+
+

New in version 3.13.

+
+

Whether to enable Dynamic Library Loads +in the Diagnostics section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.html new file mode 100644 index 0000000000000000000000000000000000000000..9a68b78abd4e113bd8b49ff58f50be3cd2955220 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE

+
+

New in version 3.13.

+
+

Whether to enable Dynamic Linker API usage +in the Diagnostics section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ENABLE_GPU_API_VALIDATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ENABLE_GPU_API_VALIDATION.html new file mode 100644 index 0000000000000000000000000000000000000000..f26fc8c408730796e08c4b40229dc0cc8ce1364f --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ENABLE_GPU_API_VALIDATION.html @@ -0,0 +1,147 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_ENABLE_GPU_API_VALIDATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_ENABLE_GPU_API_VALIDATION

+
+

New in version 3.25.

+
+

Property value for Metal: API Validation in the Options section of +the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_ENABLE_GPU_API_VALIDATION property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ENABLE_GPU_FRAME_CAPTURE_MODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ENABLE_GPU_FRAME_CAPTURE_MODE.html new file mode 100644 index 0000000000000000000000000000000000000000..6c5729920ad758ae7b057d37103bac1572a5b9b0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ENABLE_GPU_FRAME_CAPTURE_MODE.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_ENABLE_GPU_FRAME_CAPTURE_MODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_ENABLE_GPU_FRAME_CAPTURE_MODE

+
+

New in version 3.23.

+
+

Property value for GPU Frame Capture in the Options section of +the generated Xcode scheme. Example values are Metal and +Disabled.

+

This variable initializes the +XCODE_SCHEME_ENABLE_GPU_FRAME_CAPTURE_MODE +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ENVIRONMENT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ENVIRONMENT.html new file mode 100644 index 0000000000000000000000000000000000000000..974292479e14558f0361bcdffb14a6a8396659b8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_ENVIRONMENT.html @@ -0,0 +1,150 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_ENVIRONMENT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_ENVIRONMENT

+
+

New in version 3.17.

+
+

Specify environment variables that should be added to the Arguments +section of the generated Xcode scheme.

+

If set to a list of environment variables and values of the form +MYVAR=value those environment variables will be added to the +scheme.

+

This variable initializes the XCODE_SCHEME_ENVIRONMENT +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_GUARD_MALLOC.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_GUARD_MALLOC.html new file mode 100644 index 0000000000000000000000000000000000000000..cda0756a0a9318400202042ec368b029098cec60 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_GUARD_MALLOC.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_GUARD_MALLOC — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_GUARD_MALLOC

+
+

New in version 3.13.

+
+

Whether to enable Guard Malloc +in the Diagnostics section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_GUARD_MALLOC +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_LAUNCH_CONFIGURATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_LAUNCH_CONFIGURATION.html new file mode 100644 index 0000000000000000000000000000000000000000..fd9374f8a3f1a701b6f565cbdf08846b2f9eb899 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_LAUNCH_CONFIGURATION.html @@ -0,0 +1,146 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_LAUNCH_CONFIGURATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_LAUNCH_CONFIGURATION

+
+

New in version 3.25.

+
+

Set the build configuration to run the target.

+

This variable initializes the XCODE_SCHEME_LAUNCH_CONFIGURATION +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.html new file mode 100644 index 0000000000000000000000000000000000000000..de9e59a71ebe3474c4d627244fe33ded1c88d7d9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP

+
+

New in version 3.13.

+
+

Whether to enable the Main Thread Checker option +Pause on issues +in the Diagnostics section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE.html new file mode 100644 index 0000000000000000000000000000000000000000..ed265bf5ee5503b5e6ae6becb5c9296558333559 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE

+
+

New in version 3.13.

+
+

Whether to enable Malloc Scribble +in the Diagnostics section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_MALLOC_SCRIBBLE +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_MALLOC_STACK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_MALLOC_STACK.html new file mode 100644 index 0000000000000000000000000000000000000000..dd081cdaf7ec7910dcecab648760c663c68d1c8c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_MALLOC_STACK.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_MALLOC_STACK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_MALLOC_STACK

+
+

New in version 3.13.

+
+

Whether to enable Malloc Stack in the Diagnostics +section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_MALLOC_STACK +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER.html new file mode 100644 index 0000000000000000000000000000000000000000..a37ba9fe6281df0869d42194179ea0fc6ed3da8d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_THREAD_SANITIZER.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_THREAD_SANITIZER — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_THREAD_SANITIZER

+
+

New in version 3.13.

+
+

Whether to enable Thread Sanitizer in the Diagnostics +section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_THREAD_SANITIZER +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.html new file mode 100644 index 0000000000000000000000000000000000000000..fdcb6311a8ac41d98f3ff04af03be45a99534e31 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP.html @@ -0,0 +1,149 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP

+
+

New in version 3.13.

+
+

Whether to enable Undefined Behavior Sanitizer option +Pause on issues +in the Diagnostics section of the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_WORKING_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_WORKING_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..51a52b5c1433283450e3c9253a242cf064f6af84 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CMAKE_XCODE_SCHEME_WORKING_DIRECTORY.html @@ -0,0 +1,148 @@ + + + + + + + + + CMAKE_XCODE_SCHEME_WORKING_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CMAKE_XCODE_SCHEME_WORKING_DIRECTORY

+
+

New in version 3.17.

+
+

Specify the Working Directory of the Run and Profile +actions in the generated Xcode scheme.

+

This variable initializes the +XCODE_SCHEME_WORKING_DIRECTORY +property on all targets.

+

Please refer to the XCODE_GENERATE_SCHEME target property +documentation to see all Xcode schema related properties.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_ABSOLUTE_DESTINATION_FILES.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_ABSOLUTE_DESTINATION_FILES.html new file mode 100644 index 0000000000000000000000000000000000000000..50d12f254643e28213248ced655652dafa25d862 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_ABSOLUTE_DESTINATION_FILES.html @@ -0,0 +1,144 @@ + + + + + + + + + CPACK_ABSOLUTE_DESTINATION_FILES — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_ABSOLUTE_DESTINATION_FILES

+

List of files which have been installed using an ABSOLUTE DESTINATION path.

+

This variable is a Read-Only variable which is set internally by CPack +during installation and before packaging using +CMAKE_ABSOLUTE_DESTINATION_FILES defined in cmake_install.cmake +scripts. The value can be used within CPack project configuration +file and/or CPack<GEN>.cmake file of <GEN> generator.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION.html new file mode 100644 index 0000000000000000000000000000000000000000..ccecec61368ef574dd64d2ac90e4691f4219b8dc --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION.html @@ -0,0 +1,145 @@ + + + + + + + + + CPACK_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION

+

Ask CPack to error out as soon as a file with absolute INSTALL DESTINATION +is encountered.

+

The fatal error is emitted before the installation of the offending +file takes place. Some CPack generators, like NSIS, enforce this +internally. This variable triggers the definition +of CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION when CPack +runs.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_INCLUDE_TOPLEVEL_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_INCLUDE_TOPLEVEL_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..98ccec79b187d085327e64595611c2ee7b584ba5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_INCLUDE_TOPLEVEL_DIRECTORY.html @@ -0,0 +1,152 @@ + + + + + + + + + CPACK_INCLUDE_TOPLEVEL_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_INCLUDE_TOPLEVEL_DIRECTORY

+

Boolean toggle to include/exclude top level directory.

+

When preparing a package CPack installs the item under the so-called +top level directory. The purpose of is to include (set to 1 or ON or +TRUE) the top level directory in the package or not (set to 0 or +OFF or FALSE).

+

Each CPack generator has a built-in default value for this variable. +E.g. Archive generators (ZIP, TGZ, ...) includes the top level +whereas RPM or DEB don't. The user may override the default value by +setting this variable.

+

There is a similar variable +CPACK_COMPONENT_INCLUDE_TOPLEVEL_DIRECTORY which may be used +to override the behavior for the component packaging +case which may have different default value for historical (now +backward compatibility) reason.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..7b5a029d480af89401b9f04c05ca90a5d36a4821 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.html @@ -0,0 +1,147 @@ + + + + + + + + + CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS

+
+

New in version 3.11.

+
+

Default permissions for implicitly created directories during packaging.

+

This variable serves the same purpose during packaging as the +CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS variable +serves during installation (e.g. make install).

+

If include(CPack) is used then by default this variable is set to the content +of CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_PACKAGING_INSTALL_PREFIX.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_PACKAGING_INSTALL_PREFIX.html new file mode 100644 index 0000000000000000000000000000000000000000..3e3dc7a7e362835b8496ca4146b149b081e9da8b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_PACKAGING_INSTALL_PREFIX.html @@ -0,0 +1,147 @@ + + + + + + + + + CPACK_PACKAGING_INSTALL_PREFIX — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_PACKAGING_INSTALL_PREFIX

+

The prefix used in the built package.

+

Each CPack generator has a default value (like /usr). This default +value may be overwritten from the CMakeLists.txt or the cpack(1) +command line by setting an alternative value. Example:

+
set(CPACK_PACKAGING_INSTALL_PREFIX "/opt")
+
+
+

This is not the same purpose as CMAKE_INSTALL_PREFIX which is used +when installing from the build tree without building a package.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_SET_DESTDIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_SET_DESTDIR.html new file mode 100644 index 0000000000000000000000000000000000000000..44a59cb34b873fbee249f5db94e8ee834e8b484e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_SET_DESTDIR.html @@ -0,0 +1,162 @@ + + + + + + + + + CPACK_SET_DESTDIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_SET_DESTDIR

+

Boolean toggle to make CPack use DESTDIR mechanism when packaging.

+

DESTDIR means DESTination DIRectory. It is commonly used by makefile +users in order to install software at non-default location. It is a +basic relocation mechanism that should not be used on Windows (see +CMAKE_INSTALL_PREFIX documentation). It is usually invoked like +this:

+
make DESTDIR=/home/john install
+
+
+

which will install the concerned software using the installation +prefix, e.g. /usr/local prepended with the DESTDIR value which +finally gives /home/john/usr/local. When preparing a package, CPack +first installs the items to be packaged in a local (to the build tree) +directory by using the same DESTDIR mechanism. Nevertheless, if +CPACK_SET_DESTDIR is set then CPack will set DESTDIR before doing the +local install. The most noticeable difference is that without +CPACK_SET_DESTDIR, CPack uses CPACK_PACKAGING_INSTALL_PREFIX +as a prefix whereas with CPACK_SET_DESTDIR set, CPack will use +CMAKE_INSTALL_PREFIX as a prefix.

+

Manually setting CPACK_SET_DESTDIR may help (or simply be necessary) +if some install rules uses absolute DESTINATION (see CMake +install() command). However, starting with CPack/CMake 2.8.3 RPM +and DEB installers tries to handle DESTDIR automatically so that it is +seldom necessary for the user to set it.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_WARN_ON_ABSOLUTE_INSTALL_DESTINATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_WARN_ON_ABSOLUTE_INSTALL_DESTINATION.html new file mode 100644 index 0000000000000000000000000000000000000000..426bb33219eae38c35494196a7c87afc0fccafb3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CPACK_WARN_ON_ABSOLUTE_INSTALL_DESTINATION.html @@ -0,0 +1,143 @@ + + + + + + + + + CPACK_WARN_ON_ABSOLUTE_INSTALL_DESTINATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CPACK_WARN_ON_ABSOLUTE_INSTALL_DESTINATION

+

Ask CPack to warn each time a file with absolute INSTALL DESTINATION is +encountered.

+

This variable triggers the definition of +CMAKE_WARN_ON_ABSOLUTE_INSTALL_DESTINATION when CPack runs +cmake_install.cmake scripts.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_BUILD_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_BUILD_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..7ece1e4ac6463654b64c8306a552c75e58b8a9a8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_BUILD_COMMAND.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_BUILD_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_BUILD_COMMAND

+
+

New in version 3.1.

+
+

Specify the CTest MakeCommand setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_BUILD_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_BUILD_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..4bcb3bd52d76668bea2663f25cf5b35ea98d1d3e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_BUILD_NAME.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_BUILD_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_BUILD_NAME

+
+

New in version 3.1.

+
+

Specify the CTest BuildName setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_BZR_UPDATE_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_BZR_UPDATE_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..7c48080f6f80a98d65bfce843e56a29579aca1c2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_BZR_UPDATE_OPTIONS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_BZR_UPDATE_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_BZR_UPDATE_OPTIONS

+
+

New in version 3.1.

+
+

Specify the CTest BZRUpdateOptions setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CHANGE_ID.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CHANGE_ID.html new file mode 100644 index 0000000000000000000000000000000000000000..2e746b1c826c3250813f5c4a741ce62e8d8d082b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CHANGE_ID.html @@ -0,0 +1,146 @@ + + + + + + + + + CTEST_CHANGE_ID — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CHANGE_ID

+
+

New in version 3.4.

+
+

Specify the CTest ChangeId setting +in a ctest(1) dashboard client script.

+

This setting allows CTest to pass arbitrary information about this +build up to CDash. One use of this feature is to allow CDash to +post comments on your pull request if anything goes wrong with your build.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CHECKOUT_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CHECKOUT_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..2386077679d432904f9a3408f07d3b42293e2921 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CHECKOUT_COMMAND.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_CHECKOUT_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CHECKOUT_COMMAND

+
+

New in version 3.1.

+
+

Tell the ctest_start() command how to checkout or initialize +the source directory in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CONFIGURATION_TYPE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CONFIGURATION_TYPE.html new file mode 100644 index 0000000000000000000000000000000000000000..7ecb37324d6adc4769bf3eff4385b52d55eada58 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CONFIGURATION_TYPE.html @@ -0,0 +1,145 @@ + + + + + + + + + CTEST_CONFIGURATION_TYPE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CONFIGURATION_TYPE

+
+

New in version 3.1.

+
+

Specify the CTest DefaultCTestConfigurationType setting +in a ctest(1) dashboard client script.

+

If the configuration type is set via -C <cfg> from the command line +then this variable is populated accordingly.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CONFIGURE_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CONFIGURE_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..d83e75ce56352e08e0b1e0422ad366f869ffaf9e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CONFIGURE_COMMAND.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_CONFIGURE_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CONFIGURE_COMMAND

+
+

New in version 3.1.

+
+

Specify the CTest ConfigureCommand setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_COVERAGE_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_COVERAGE_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..465c00b2e0ca39e2e7349ed8b892ed9bf6254b70 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_COVERAGE_COMMAND.html @@ -0,0 +1,197 @@ + + + + + + + + + CTEST_COVERAGE_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_COVERAGE_COMMAND

+
+

New in version 3.1.

+
+

Specify the CTest CoverageCommand setting +in a ctest(1) dashboard client script.

+
+

Cobertura

+

Using Cobertura as the coverage generation within your multi-module +Java project can generate a series of XML files.

+

The Cobertura Coverage parser expects to read the coverage data from a +single XML file which contains the coverage data for all modules. +Cobertura has a program with the ability to merge given cobertura.ser files +and then another program to generate a combined XML file from the previous +merged file. For command line testing, this can be done by hand prior to +CTest looking for the coverage files. For script builds, +set the CTEST_COVERAGE_COMMAND variable to point to a file which will +perform these same steps, such as a .sh or .bat file.

+
set(CTEST_COVERAGE_COMMAND .../run-coverage-and-consolidate.sh)
+
+
+

where the run-coverage-and-consolidate.sh script is perhaps created by +the configure_file() command and might contain the following code:

+
#!/usr/bin/env bash
+CoberturaFiles="$(find "/path/to/source" -name "cobertura.ser")"
+SourceDirs="$(find "/path/to/source" -name "java" -type d)"
+cobertura-merge --datafile coberturamerge.ser $CoberturaFiles
+cobertura-report --datafile coberturamerge.ser --destination . \
+                 --format xml $SourceDirs
+
+
+

The script uses find to capture the paths to all of the cobertura.ser +files found below the project's source directory. It keeps the list of files +and supplies it as an argument to the cobertura-merge program. The +--datafile argument signifies where the result of the merge will be kept.

+

The combined coberturamerge.ser file is then used to generate the XML report +using the cobertura-report program. The call to the cobertura-report +program requires some named arguments.

+
+
--datafila

path to the merged .ser file

+
+
--destination

path to put the output files(s)

+
+
--format

file format to write output in: xml or html

+
+
+

The rest of the supplied arguments consist of the full paths to the +/src/main/java directories of each module within the source tree. These +directories are needed and should not be forgotten.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_COVERAGE_EXTRA_FLAGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_COVERAGE_EXTRA_FLAGS.html new file mode 100644 index 0000000000000000000000000000000000000000..7ad1adddaba34b1621d18f419fca82bb2c52706e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_COVERAGE_EXTRA_FLAGS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_COVERAGE_EXTRA_FLAGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_COVERAGE_EXTRA_FLAGS

+
+

New in version 3.1.

+
+

Specify the CTest CoverageExtraFlags setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_ERROR_EXCEPTION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_ERROR_EXCEPTION.html new file mode 100644 index 0000000000000000000000000000000000000000..fb02916c3f75a54316788d9fe4a7cef09597218d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_ERROR_EXCEPTION.html @@ -0,0 +1,142 @@ + + + + + + + + + CTEST_CUSTOM_ERROR_EXCEPTION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_ERROR_EXCEPTION

+

A list of regular expressions which will be used to exclude when detecting +error messages in build outputs by the ctest_build() command.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_ERROR_POST_CONTEXT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_ERROR_POST_CONTEXT.html new file mode 100644 index 0000000000000000000000000000000000000000..ef8775dfb399087b52b7fd3dffefe3a71f7c5a05 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_ERROR_POST_CONTEXT.html @@ -0,0 +1,142 @@ + + + + + + + + + CTEST_CUSTOM_ERROR_POST_CONTEXT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_ERROR_POST_CONTEXT

+

The number of lines to include as context which follow an error message by the +ctest_build() command. The default is 10.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_ERROR_PRE_CONTEXT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_ERROR_PRE_CONTEXT.html new file mode 100644 index 0000000000000000000000000000000000000000..9cbb96391917290f1093454f9eb635422360d7c5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_ERROR_PRE_CONTEXT.html @@ -0,0 +1,142 @@ + + + + + + + + + CTEST_CUSTOM_ERROR_PRE_CONTEXT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_ERROR_PRE_CONTEXT

+

The number of lines to include as context which precede an error message by +the ctest_build() command. The default is 10.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.html new file mode 100644 index 0000000000000000000000000000000000000000..ed64a9a5d7b6e08d8657eecf8559a053e2885d53 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.html @@ -0,0 +1,148 @@ + + + + + + + + + CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE

+

When saving a failing test's output, this is the maximum size, in bytes, that +will be collected by the ctest_test() command. Defaults to 307200 +(300 KiB). See CTEST_CUSTOM_TEST_OUTPUT_TRUNCATION for possible +truncation modes.

+

If a test's output contains the literal string "CTEST_FULL_OUTPUT", +the output will not be truncated and may exceed the maximum size.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+

For controlling the output collection of passing tests, see +CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MAXIMUM_NUMBER_OF_WARNINGS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MAXIMUM_NUMBER_OF_WARNINGS.html new file mode 100644 index 0000000000000000000000000000000000000000..95dee06d924670838c90230975c8d41609567d9d --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MAXIMUM_NUMBER_OF_WARNINGS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_CUSTOM_MAXIMUM_NUMBER_OF_WARNINGS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_MAXIMUM_NUMBER_OF_WARNINGS

+

The maximum number of warnings in a single build step which will be detected. +After this, the ctest_test() command will truncate the output. +Defaults to 50.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE.html new file mode 100644 index 0000000000000000000000000000000000000000..36adcb845f346f33fee541e02a320cfbd335657c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE.html @@ -0,0 +1,148 @@ + + + + + + + + + CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE

+

When saving a passing test's output, this is the maximum size, in bytes, that +will be collected by the ctest_test() command. Defaults to 1024 +(1 KiB). See CTEST_CUSTOM_TEST_OUTPUT_TRUNCATION for possible +truncation modes.

+

If a test's output contains the literal string "CTEST_FULL_OUTPUT", +the output will not be truncated and may exceed the maximum size.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+

For controlling the output collection of failing tests, see +CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MEMCHECK_IGNORE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MEMCHECK_IGNORE.html new file mode 100644 index 0000000000000000000000000000000000000000..ae8210f9daec83e4720069e87002254d8dd0045e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_MEMCHECK_IGNORE.html @@ -0,0 +1,142 @@ + + + + + + + + + CTEST_CUSTOM_MEMCHECK_IGNORE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_MEMCHECK_IGNORE

+

A list of regular expressions to use to exclude tests during the +ctest_memcheck() command.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_POST_TEST.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_POST_TEST.html new file mode 100644 index 0000000000000000000000000000000000000000..2bdf5cfc71d7e21976a23bc1e73595dad1864ed4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_POST_TEST.html @@ -0,0 +1,141 @@ + + + + + + + + + CTEST_CUSTOM_POST_TEST — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_POST_TEST

+

A list of commands to run at the end of the ctest_test() command.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_PRE_TEST.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_PRE_TEST.html new file mode 100644 index 0000000000000000000000000000000000000000..2605f0acafdd804850ae37dd66c4b8251eeacb73 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_PRE_TEST.html @@ -0,0 +1,141 @@ + + + + + + + + + CTEST_CUSTOM_PRE_TEST — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_PRE_TEST

+

A list of commands to run at the start of the ctest_test() command.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_TEST_OUTPUT_TRUNCATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_TEST_OUTPUT_TRUNCATION.html new file mode 100644 index 0000000000000000000000000000000000000000..bb9894d58a916732accb03a2c1f1316b2cc79851 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_TEST_OUTPUT_TRUNCATION.html @@ -0,0 +1,148 @@ + + + + + + + + + CTEST_CUSTOM_TEST_OUTPUT_TRUNCATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_TEST_OUTPUT_TRUNCATION

+
+

New in version 3.24.

+
+

Set the test output truncation mode in case a maximum size is configured +via the CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE or +CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE variables. +By default the tail of the output will be truncated. Other possible +values are middle and head.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_WARNING_EXCEPTION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_WARNING_EXCEPTION.html new file mode 100644 index 0000000000000000000000000000000000000000..0eb9f0e224bfcf1a8c469a851335d8ba2493e749 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_WARNING_EXCEPTION.html @@ -0,0 +1,142 @@ + + + + + + + + + CTEST_CUSTOM_WARNING_EXCEPTION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_WARNING_EXCEPTION

+

A list of regular expressions which will be used to exclude when detecting +warning messages in build outputs by the ctest_build() command.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_WARNING_MATCH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_WARNING_MATCH.html new file mode 100644 index 0000000000000000000000000000000000000000..9622d1ad519fe040c675291250785dc3c2d2c30e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CUSTOM_WARNING_MATCH.html @@ -0,0 +1,142 @@ + + + + + + + + + CTEST_CUSTOM_WARNING_MATCH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CUSTOM_WARNING_MATCH

+

A list of regular expressions which will be used to detect warning messages in +build outputs by the ctest_build() command.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CVS_CHECKOUT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CVS_CHECKOUT.html new file mode 100644 index 0000000000000000000000000000000000000000..7d9768a5881ad74c461b74508cf0536114f7fa5e --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CVS_CHECKOUT.html @@ -0,0 +1,142 @@ + + + + + + + + + CTEST_CVS_CHECKOUT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CVS_CHECKOUT

+
+

New in version 3.1.

+
+

Deprecated. Use CTEST_CHECKOUT_COMMAND instead.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CVS_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CVS_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..0a70b976afe0e1c66ce723fd22ef78c7ac257a8a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CVS_COMMAND.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_CVS_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CVS_COMMAND

+
+

New in version 3.1.

+
+

Specify the CTest CVSCommand setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CVS_UPDATE_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CVS_UPDATE_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..f2fd8fd5e6ae791dbada2d439affd9f9d95a33db --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_CVS_UPDATE_OPTIONS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_CVS_UPDATE_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_CVS_UPDATE_OPTIONS

+
+

New in version 3.1.

+
+

Specify the CTest CVSUpdateOptions setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_LOCATION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_LOCATION.html new file mode 100644 index 0000000000000000000000000000000000000000..fc0f3872555ca48e7aa96b79fbfb3e8098faf210 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_LOCATION.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_DROP_LOCATION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_DROP_LOCATION

+
+

New in version 3.1.

+
+

Specify the CTest DropLocation setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_METHOD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_METHOD.html new file mode 100644 index 0000000000000000000000000000000000000000..5be42d445ac061864bacdb0331766ac121f2cccf --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_METHOD.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_DROP_METHOD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_DROP_METHOD

+
+

New in version 3.1.

+
+

Specify the CTest DropMethod setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_SITE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_SITE.html new file mode 100644 index 0000000000000000000000000000000000000000..4400a355e6ccd008d46da223185a1b6ad5281d43 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_SITE.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_DROP_SITE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_DROP_SITE

+
+

New in version 3.1.

+
+

Specify the CTest DropSite setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_SITE_CDASH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_SITE_CDASH.html new file mode 100644 index 0000000000000000000000000000000000000000..a39e3995339a9a9098a8bf7fff9d3b81bf21298b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_SITE_CDASH.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_DROP_SITE_CDASH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_DROP_SITE_CDASH

+
+

New in version 3.1.

+
+

Specify the CTest IsCDash setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_SITE_PASSWORD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_SITE_PASSWORD.html new file mode 100644 index 0000000000000000000000000000000000000000..665716a040ae060269166975068a795bab416cf7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_DROP_SITE_PASSWORD.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_DROP_SITE_PASSWORD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_DROP_SITE_PASSWORD

+
+

New in version 3.1.

+
+

Specify the CTest DropSitePassword setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_EXTRA_COVERAGE_GLOB.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_EXTRA_COVERAGE_GLOB.html new file mode 100644 index 0000000000000000000000000000000000000000..d5d8b943248627fcc6e11a2c8604a485a28a8d72 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_EXTRA_COVERAGE_GLOB.html @@ -0,0 +1,145 @@ + + + + + + + + + CTEST_EXTRA_COVERAGE_GLOB — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_EXTRA_COVERAGE_GLOB

+
+

New in version 3.4.

+
+

A list of regular expressions which will be used to find files which should be +covered by the ctest_coverage() command.

+

It is initialized by ctest(1), but may be edited in a CTestCustom +file. See ctest_read_custom_files() documentation.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_GIT_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_GIT_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..f68a31400e3f2e5147ec98cbc2bc7fefd1c259d5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_GIT_COMMAND.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_GIT_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_GIT_COMMAND

+
+

New in version 3.1.

+
+

Specify the CTest GITCommand setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_GIT_UPDATE_CUSTOM.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_GIT_UPDATE_CUSTOM.html new file mode 100644 index 0000000000000000000000000000000000000000..1a023a7bd91c28ef3a8d4134bb6012a46576434b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_GIT_UPDATE_CUSTOM.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_GIT_UPDATE_CUSTOM — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_GIT_UPDATE_CUSTOM

+
+

New in version 3.1.

+
+

Specify the CTest GITUpdateCustom setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_HG_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_HG_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..7a45c5acd0e18723df8b0310f7027da145c06485 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_HG_COMMAND.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_HG_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_HG_COMMAND

+
+

New in version 3.1.

+
+

Specify the CTest HGCommand setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_HG_UPDATE_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_HG_UPDATE_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..2f6e08d079b32ba63274e70d12716d6e2e0e0a1b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_HG_UPDATE_OPTIONS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_HG_UPDATE_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_HG_UPDATE_OPTIONS

+
+

New in version 3.1.

+
+

Specify the CTest HGUpdateOptions setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_MEMORYCHECK_COMMAND_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_MEMORYCHECK_COMMAND_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..d3bdef880c80d98601a82a314ef5e2de8da3b4a6 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_MEMORYCHECK_COMMAND_OPTIONS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_MEMORYCHECK_COMMAND_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_MEMORYCHECK_COMMAND_OPTIONS

+
+

New in version 3.1.

+
+

Specify the CTest MemoryCheckCommandOptions setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_MEMORYCHECK_SUPPRESSIONS_FILE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_MEMORYCHECK_SUPPRESSIONS_FILE.html new file mode 100644 index 0000000000000000000000000000000000000000..2fcfccff25af575e7495584a1cfcbd603af6492c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_MEMORYCHECK_SUPPRESSIONS_FILE.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_MEMORYCHECK_SUPPRESSIONS_FILE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_MEMORYCHECK_SUPPRESSIONS_FILE

+
+

New in version 3.1.

+
+

Specify the CTest MemoryCheckSuppressionFile setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_MEMORYCHECK_TYPE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_MEMORYCHECK_TYPE.html new file mode 100644 index 0000000000000000000000000000000000000000..05c6f13223f61fc0daedcf4b42e603155b980cb2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_MEMORYCHECK_TYPE.html @@ -0,0 +1,146 @@ + + + + + + + + + CTEST_MEMORYCHECK_TYPE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_MEMORYCHECK_TYPE

+
+

New in version 3.1.

+
+

Specify the CTest MemoryCheckType setting +in a ctest(1) dashboard client script. +Valid values are Valgrind, Purify, BoundsChecker, DrMemory, +CudaSanitizer, ThreadSanitizer, AddressSanitizer, LeakSanitizer, +MemorySanitizer and UndefinedBehaviorSanitizer.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_NIGHTLY_START_TIME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_NIGHTLY_START_TIME.html new file mode 100644 index 0000000000000000000000000000000000000000..0da22e87dcdc4655a8c092c0da0bcf3fc2b4c140 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_NIGHTLY_START_TIME.html @@ -0,0 +1,146 @@ + + + + + + + + + CTEST_NIGHTLY_START_TIME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_NIGHTLY_START_TIME

+
+

New in version 3.1.

+
+

Specify the CTest NightlyStartTime setting in a ctest(1) +dashboard client script.

+

Note that this variable must always be set for a nightly build in a +dashboard script. It is needed so that nightly builds can be properly grouped +together in CDash.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_P4_CLIENT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_P4_CLIENT.html new file mode 100644 index 0000000000000000000000000000000000000000..30675ee4fa9da98e36da4142cad52fb45d900630 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_P4_CLIENT.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_P4_CLIENT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_P4_CLIENT

+
+

New in version 3.1.

+
+

Specify the CTest P4Client setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_P4_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_P4_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..94e54b47c5620eb8333ba9686560e012110ded88 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_P4_OPTIONS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_P4_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_P4_OPTIONS

+
+

New in version 3.1.

+
+

Specify the CTest P4Options setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_P4_UPDATE_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_P4_UPDATE_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..37a1c12289b2e78b7f4c6fd5cb81a0189c8f05ea --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_P4_UPDATE_OPTIONS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_P4_UPDATE_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_P4_UPDATE_OPTIONS

+
+

New in version 3.1.

+
+

Specify the CTest P4UpdateOptions setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_RUN_CURRENT_SCRIPT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_RUN_CURRENT_SCRIPT.html new file mode 100644 index 0000000000000000000000000000000000000000..1c7d0f4db83b2b53f7b7ab7db967ddefa2b18a76 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_RUN_CURRENT_SCRIPT.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_RUN_CURRENT_SCRIPT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_RUN_CURRENT_SCRIPT

+
+

New in version 3.11.

+
+

Setting this to 0 prevents ctest(1) from being run again when it +reaches the end of a script run by calling ctest -S.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SCP_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SCP_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..5e7442077b93bc0cb3ea907b46d57411ce601a4c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SCP_COMMAND.html @@ -0,0 +1,142 @@ + + + + + + + + + CTEST_SCP_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_SCP_COMMAND

+
+

New in version 3.1.

+
+

Legacy option. Not used.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SCRIPT_DIRECTORY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SCRIPT_DIRECTORY.html new file mode 100644 index 0000000000000000000000000000000000000000..f0e08fc2791cf1adb6a266e2e894b9da0d02f8cb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SCRIPT_DIRECTORY.html @@ -0,0 +1,140 @@ + + + + + + + + + CTEST_SCRIPT_DIRECTORY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_SCRIPT_DIRECTORY

+

The directory containing the top-level CTest script. +The concept is similar to CMAKE_SOURCE_DIR.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SITE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SITE.html new file mode 100644 index 0000000000000000000000000000000000000000..794f39afc2f8cf22deee56525744efe513212ca5 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SITE.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_SITE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_SITE

+
+

New in version 3.1.

+
+

Specify the CTest Site setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SUBMIT_INACTIVITY_TIMEOUT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SUBMIT_INACTIVITY_TIMEOUT.html new file mode 100644 index 0000000000000000000000000000000000000000..341918be4de0bf1c1f439dbbd68673468d1ed592 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SUBMIT_INACTIVITY_TIMEOUT.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_SUBMIT_INACTIVITY_TIMEOUT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_SUBMIT_INACTIVITY_TIMEOUT

+
+

New in version 3.23.

+
+

Specify the CTest SubmitInactivityTimeout setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SUBMIT_URL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SUBMIT_URL.html new file mode 100644 index 0000000000000000000000000000000000000000..c5cf31f20e5178cfc09d76e63937eb17ef2efe6c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SUBMIT_URL.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_SUBMIT_URL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_SUBMIT_URL

+
+

New in version 3.14.

+
+

Specify the CTest SubmitURL setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SVN_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SVN_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..8a18ad8b0fb76206f7419058465662f4baba06da --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SVN_COMMAND.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_SVN_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_SVN_COMMAND

+
+

New in version 3.1.

+
+

Specify the CTest SVNCommand setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SVN_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SVN_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..c24f0c04701884da75a4cc490d643c08acfe605a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_SVN_OPTIONS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_SVN_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_SVN_OPTIONS

+
+

New in version 3.1.

+
+

Specify the CTest SVNOptions setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_TEST_LOAD.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_TEST_LOAD.html new file mode 100644 index 0000000000000000000000000000000000000000..2c68b4ac60fc55705b2e767d569f77f893fd6a96 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_TEST_LOAD.html @@ -0,0 +1,145 @@ + + + + + + + + + CTEST_TEST_LOAD — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_TEST_LOAD

+
+

New in version 3.4.

+
+

Specify the TestLoad setting in the CTest Test Step +of a ctest(1) dashboard client script. This sets the +default value for the TEST_LOAD option of the ctest_test() +command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_TEST_TIMEOUT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_TEST_TIMEOUT.html new file mode 100644 index 0000000000000000000000000000000000000000..e6cdc35c553409363f04e40df2826a92f2aff2e0 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_TEST_TIMEOUT.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_TEST_TIMEOUT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_TEST_TIMEOUT

+
+

New in version 3.1.

+
+

Specify the CTest TimeOut setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_TRIGGER_SITE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_TRIGGER_SITE.html new file mode 100644 index 0000000000000000000000000000000000000000..41df2fa75e1022512e3cd356e9b59c2da0c5bdcd --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_TRIGGER_SITE.html @@ -0,0 +1,142 @@ + + + + + + + + + CTEST_TRIGGER_SITE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_TRIGGER_SITE

+
+

New in version 3.1.

+
+

Legacy option. Not used.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_COMMAND.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_COMMAND.html new file mode 100644 index 0000000000000000000000000000000000000000..563bca57758ffef4d7b16d3c7aa96ef73082fa39 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_COMMAND.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_UPDATE_COMMAND — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_UPDATE_COMMAND

+
+

New in version 3.1.

+
+

Specify the CTest UpdateCommand setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_OPTIONS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_OPTIONS.html new file mode 100644 index 0000000000000000000000000000000000000000..90acced8834743e1d0aacd10200d4f3bfca6d9f9 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_OPTIONS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_UPDATE_OPTIONS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_UPDATE_OPTIONS

+
+

New in version 3.1.

+
+

Specify the CTest UpdateOptions setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_VERSION_ONLY.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_VERSION_ONLY.html new file mode 100644 index 0000000000000000000000000000000000000000..4f98195fa4891d765a9c6733aa886bd9391d9708 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_VERSION_ONLY.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_UPDATE_VERSION_ONLY — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_UPDATE_VERSION_ONLY

+
+

New in version 3.1.

+
+

Specify the CTest UpdateVersionOnly setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_VERSION_OVERRIDE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_VERSION_OVERRIDE.html new file mode 100644 index 0000000000000000000000000000000000000000..3fd6af1478ee5bda57fc36be5d30c08a7161efb7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_UPDATE_VERSION_OVERRIDE.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_UPDATE_VERSION_OVERRIDE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_UPDATE_VERSION_OVERRIDE

+
+

New in version 3.15.

+
+

Specify the CTest UpdateVersionOverride setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_USE_LAUNCHERS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_USE_LAUNCHERS.html new file mode 100644 index 0000000000000000000000000000000000000000..1255d931b8b603073495597166987ce3281a6016 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CTEST_USE_LAUNCHERS.html @@ -0,0 +1,143 @@ + + + + + + + + + CTEST_USE_LAUNCHERS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CTEST_USE_LAUNCHERS

+
+

New in version 3.1.

+
+

Specify the CTest UseLaunchers setting +in a ctest(1) dashboard client script.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CYGWIN.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CYGWIN.html new file mode 100644 index 0000000000000000000000000000000000000000..e9b614090f334747a0a453fe55efb089a808ffef --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/CYGWIN.html @@ -0,0 +1,140 @@ + + + + + + + + + CYGWIN — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

CYGWIN

+

True for Cygwin.

+

Set to true when using Cygwin.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/ENV.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/ENV.html new file mode 100644 index 0000000000000000000000000000000000000000..c824fca98ce3cb6003d4c354bbc8f4092b42a225 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/ENV.html @@ -0,0 +1,145 @@ + + + + + + + + + ENV — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

ENV

+

Operator to read environment variables.

+

Use the syntax $ENV{VAR} to read environment variable VAR.

+

To test whether an environment variable is defined, use the signature +if(DEFINED ENV{<name>}) of the if() command.

+

For general information on environment variables, see the +Environment Variables +section in the cmake-language(7) manual.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/EXECUTABLE_OUTPUT_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/EXECUTABLE_OUTPUT_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..f9b0833dbe7a7e2e458df97734b1aea8feda89b1 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/EXECUTABLE_OUTPUT_PATH.html @@ -0,0 +1,142 @@ + + + + + + + + + EXECUTABLE_OUTPUT_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

EXECUTABLE_OUTPUT_PATH

+

Old executable location variable.

+

The target property RUNTIME_OUTPUT_DIRECTORY supersedes this +variable for a target if it is set. Executable targets are otherwise placed in +this directory.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/LIBRARY_OUTPUT_PATH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/LIBRARY_OUTPUT_PATH.html new file mode 100644 index 0000000000000000000000000000000000000000..d99c00b49e767a489071b5ed3f1907d67dbe35ed --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/LIBRARY_OUTPUT_PATH.html @@ -0,0 +1,143 @@ + + + + + + + + + LIBRARY_OUTPUT_PATH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

LIBRARY_OUTPUT_PATH

+

Old library location variable.

+

The target properties ARCHIVE_OUTPUT_DIRECTORY, +LIBRARY_OUTPUT_DIRECTORY, and RUNTIME_OUTPUT_DIRECTORY +supersede this variable for a target if they are set. Library targets are +otherwise placed in this directory.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC.html new file mode 100644 index 0000000000000000000000000000000000000000..50ae4b7cdd3b9765da5b868d1032b0793db4b8ff --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC.html @@ -0,0 +1,141 @@ + + + + + + + + + MSVC — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MSVC

+

Set to true when the compiler is some version of Microsoft Visual C++ +or another compiler simulating the Visual C++ cl command-line syntax.

+

See also the MSVC_VERSION variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC10.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC10.html new file mode 100644 index 0000000000000000000000000000000000000000..0d5148a242ac7c7d28fd05c8dbdd66bc3d250cd8 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC10.html @@ -0,0 +1,141 @@ + + + + + + + + + MSVC10 — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MSVC10

+

Discouraged. Use the MSVC_VERSION variable instead.

+

True when using the Microsoft Visual Studio v100 toolset +(cl version 16) or another compiler that simulates it.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC12.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC12.html new file mode 100644 index 0000000000000000000000000000000000000000..2c7dfb8daa29dd621f33c4f8ec11982f0e6f0165 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC12.html @@ -0,0 +1,141 @@ + + + + + + + + + MSVC12 — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MSVC12

+

Discouraged. Use the MSVC_VERSION variable instead.

+

True when using the Microsoft Visual Studio v120 toolset +(cl version 18) or another compiler that simulates it.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC14.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC14.html new file mode 100644 index 0000000000000000000000000000000000000000..40064681aa91e31ab3234100d28cff3251fcc52b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC14.html @@ -0,0 +1,144 @@ + + + + + + + + + MSVC14 — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MSVC14

+
+

New in version 3.1.

+
+

Discouraged. Use the MSVC_VERSION variable instead.

+

True when using the Microsoft Visual Studio v140 or v141 +toolset (cl version 19) or another compiler that simulates it.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC71.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC71.html new file mode 100644 index 0000000000000000000000000000000000000000..be9d3cb066e02fdd366e7972d6445058669cd5f3 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC71.html @@ -0,0 +1,141 @@ + + + + + + + + + MSVC71 — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MSVC71

+

Discouraged. Use the MSVC_VERSION variable instead.

+

True when using Microsoft Visual C++ 7.1.

+

Set to true when the compiler is version 7.1 of Microsoft Visual C++.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC90.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC90.html new file mode 100644 index 0000000000000000000000000000000000000000..3b67f52cb56ea2f6d127ed6e50e1c52686c01f83 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC90.html @@ -0,0 +1,141 @@ + + + + + + + + + MSVC90 — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MSVC90

+

Discouraged. Use the MSVC_VERSION variable instead.

+

True when using the Microsoft Visual Studio v90 toolset +(cl version 15) or another compiler that simulates it.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC_IDE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC_IDE.html new file mode 100644 index 0000000000000000000000000000000000000000..d334ccc194da891e7a2c24dd2f4289e21f03e1eb --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC_IDE.html @@ -0,0 +1,148 @@ + + + + + + + + + MSVC_IDE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MSVC_IDE

+

True when using the Microsoft Visual C++ IDE.

+

Set to true when the target platform is the Microsoft Visual C++ IDE, as +opposed to the command line compiler.

+
+

Note

+

This variable is only available after compiler detection has been performed, +so it is not available to toolchain files or before the first +project() or enable_language() call which uses an +MSVC-like compiler.

+
+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC_TOOLSET_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC_TOOLSET_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..82b18c9c9fc58fe5f90c7e8d46568272945d08c2 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSVC_TOOLSET_VERSION.html @@ -0,0 +1,159 @@ + + + + + + + + + MSVC_TOOLSET_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MSVC_TOOLSET_VERSION

+
+

New in version 3.12.

+
+

The toolset version of Microsoft Visual C/C++ being used if any. +If MSVC-like is being used, this variable is set based on the version +of the compiler as given by the MSVC_VERSION variable.

+

Known toolset version numbers are:

+
80        = VS 2005 (8.0)
+90        = VS 2008 (9.0)
+100       = VS 2010 (10.0)
+110       = VS 2012 (11.0)
+120       = VS 2013 (12.0)
+140       = VS 2015 (14.0)
+141       = VS 2017 (15.0)
+142       = VS 2019 (16.0)
+143       = VS 2022 (17.0)
+
+
+

Compiler versions newer than those known to CMake will be reported +as the latest known toolset version.

+

See also the MSVC_VERSION variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSYS.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSYS.html new file mode 100644 index 0000000000000000000000000000000000000000..aebe2524d5c02b6c9a473880cbc580694923f3ce --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/MSYS.html @@ -0,0 +1,142 @@ + + + + + + + + + MSYS — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

MSYS

+
+

New in version 3.14.

+
+

True when using the MSYS Makefiles generator.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_BINARY_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_BINARY_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..c89be1747b29aeb99eb7744f884a79ee17c1ee7c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_BINARY_DIR.html @@ -0,0 +1,142 @@ + + + + + + + + + <PROJECT-NAME>_BINARY_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<PROJECT-NAME>_BINARY_DIR

+

Top level binary directory for the named project.

+

A variable is created with the name used in the project() command, +and is the binary directory for the project. This can be useful when +add_subdirectory() is used to connect several projects.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_HOMEPAGE_URL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_HOMEPAGE_URL.html new file mode 100644 index 0000000000000000000000000000000000000000..d4c76bfd58a67e9ebec49e3d1fbfb557574ad6b7 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_HOMEPAGE_URL.html @@ -0,0 +1,143 @@ + + + + + + + + + <PROJECT-NAME>_HOMEPAGE_URL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<PROJECT-NAME>_HOMEPAGE_URL

+
+

New in version 3.12.

+
+

Value given to the HOMEPAGE_URL option of the most recent call to the +project() command with project name <PROJECT-NAME>, if any.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_IS_TOP_LEVEL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_IS_TOP_LEVEL.html new file mode 100644 index 0000000000000000000000000000000000000000..8ce84a71a26657b49b8ce7a21a3f10bb3b0a04a4 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_IS_TOP_LEVEL.html @@ -0,0 +1,163 @@ + + + + + + + + + <PROJECT-NAME>_IS_TOP_LEVEL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<PROJECT-NAME>_IS_TOP_LEVEL

+
+

New in version 3.21.

+
+

A boolean variable indicating whether the named project was called in a top +level CMakeLists.txt file.

+

To obtain the value from the most recent call to project() in +the current directory scope or above, see the +PROJECT_IS_TOP_LEVEL variable.

+

The variable value will be true in:

+ +

The variable value will be false in:

+ +
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_SOURCE_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_SOURCE_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..e40265e7242d0ce354a48fb1f74d8052a6106813 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_SOURCE_DIR.html @@ -0,0 +1,142 @@ + + + + + + + + + <PROJECT-NAME>_SOURCE_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<PROJECT-NAME>_SOURCE_DIR

+

Top level source directory for the named project.

+

A variable is created with the name used in the project() command, +and is the source directory for the project. This can be useful when +add_subdirectory() is used to connect several projects.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_VERSION_MAJOR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_VERSION_MAJOR.html new file mode 100644 index 0000000000000000000000000000000000000000..1447295926f7665a284acee034e66d4194496346 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_VERSION_MAJOR.html @@ -0,0 +1,140 @@ + + + + + + + + + <PROJECT-NAME>_VERSION_MAJOR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<PROJECT-NAME>_VERSION_MAJOR

+

First version number component of the <PROJECT-NAME>_VERSION +variable as set by the project() command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_VERSION_PATCH.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_VERSION_PATCH.html new file mode 100644 index 0000000000000000000000000000000000000000..eb2010a5dd0c1217595f491c7f4fec2fa60e6031 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_VERSION_PATCH.html @@ -0,0 +1,140 @@ + + + + + + + + + <PROJECT-NAME>_VERSION_PATCH — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<PROJECT-NAME>_VERSION_PATCH

+

Third version number component of the <PROJECT-NAME>_VERSION +variable as set by the project() command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_VERSION_TWEAK.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_VERSION_TWEAK.html new file mode 100644 index 0000000000000000000000000000000000000000..2aa1486b96b79bf139cb04f31ef9fd31ce22a476 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT-NAME_VERSION_TWEAK.html @@ -0,0 +1,140 @@ + + + + + + + + + <PROJECT-NAME>_VERSION_TWEAK — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<PROJECT-NAME>_VERSION_TWEAK

+

Fourth version number component of the <PROJECT-NAME>_VERSION +variable as set by the project() command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_DESCRIPTION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_DESCRIPTION.html new file mode 100644 index 0000000000000000000000000000000000000000..ce07fdb7d12fb1e40ef9967b233d78e328b0295b --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_DESCRIPTION.html @@ -0,0 +1,146 @@ + + + + + + + + + PROJECT_DESCRIPTION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PROJECT_DESCRIPTION

+
+

New in version 3.9.

+
+

Short project description given to the project command.

+

This is the description given to the most recently called project() +command in the current directory scope or above. To obtain the description +of the top level project, see the CMAKE_PROJECT_DESCRIPTION +variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_IS_TOP_LEVEL.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_IS_TOP_LEVEL.html new file mode 100644 index 0000000000000000000000000000000000000000..932d2418cb6ebb25cc5b9e8e484de795dac2d04c --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_IS_TOP_LEVEL.html @@ -0,0 +1,173 @@ + + + + + + + + + PROJECT_IS_TOP_LEVEL — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PROJECT_IS_TOP_LEVEL

+
+

New in version 3.21.

+
+

A boolean variable indicating whether the most recently called +project() command in the current scope or above was in the top +level CMakeLists.txt file.

+

Some modules should only be included as part of the top level +CMakeLists.txt file to not cause unintended side effects in the build +tree, and this variable can be used to conditionally execute such code. For +example, consider the CTest module, which creates targets and +options:

+
project(MyProject)
+...
+if(PROJECT_IS_TOP_LEVEL)
+  include(CTest)
+endif()
+
+
+

The variable value will be true in:

+ +

The variable value will be false in:

+ +
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_NAME.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_NAME.html new file mode 100644 index 0000000000000000000000000000000000000000..94976e4075d4ce24feb99a1e6effc868518acb77 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_NAME.html @@ -0,0 +1,142 @@ + + + + + + + + + PROJECT_NAME — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PROJECT_NAME

+

Name of the project given to the project command.

+

This is the name given to the most recently called project() +command in the current directory scope or above. To obtain the name of +the top level project, see the CMAKE_PROJECT_NAME variable.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_SOURCE_DIR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_SOURCE_DIR.html new file mode 100644 index 0000000000000000000000000000000000000000..bdd6b043dfbf66d366b4a96a948a233407c9d456 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_SOURCE_DIR.html @@ -0,0 +1,143 @@ + + + + + + + + + PROJECT_SOURCE_DIR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PROJECT_SOURCE_DIR

+

This is the source directory of the last call to the +project() command made in the current directory scope or one +of its parents. Note, it is not affected by calls to +project() made within a child directory scope (i.e. from +within a call to add_subdirectory() from the current scope).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..f78be7380dff6b7ae6fa686b0f56e6db57b58605 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_VERSION.html @@ -0,0 +1,145 @@ + + + + + + + + + PROJECT_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PROJECT_VERSION

+

Value given to the VERSION option of the most recent call to the +project() command, if any.

+

See also the component-wise version variables +PROJECT_VERSION_MAJOR, +PROJECT_VERSION_MINOR, +PROJECT_VERSION_PATCH, and +PROJECT_VERSION_TWEAK.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_VERSION_MAJOR.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_VERSION_MAJOR.html new file mode 100644 index 0000000000000000000000000000000000000000..f1732a92015efe04c73da55ec36612ddc9187841 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PROJECT_VERSION_MAJOR.html @@ -0,0 +1,140 @@ + + + + + + + + + PROJECT_VERSION_MAJOR — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

PROJECT_VERSION_MAJOR

+

First version number component of the PROJECT_VERSION +variable as set by the project() command.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PackageName_ROOT.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PackageName_ROOT.html new file mode 100644 index 0000000000000000000000000000000000000000..8a72b11be88c8d0d3194fe03e6ed2ddded1d20ed --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/PackageName_ROOT.html @@ -0,0 +1,161 @@ + + + + + + + + + <PackageName>_ROOT — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

<PackageName>_ROOT

+
+

New in version 3.12.

+
+

Calls to find_package(<PackageName>) will search in prefixes +specified by the <PackageName>_ROOT CMake variable, where +<PackageName> is the (case-preserved) name given to the +find_package() call and _ROOT is literal. +For example, find_package(Foo) will search prefixes specified in the +Foo_ROOT CMake variable (if set). See policy CMP0074.

+

This variable may hold a single prefix or a +semicolon-separated list of multiple prefixes.

+

See also the <PackageName>_ROOT environment variable.

+
+
+<PACKAGENAME>_ROOT
+
+

New in version 3.27.

+
+

Calls to find_package(<PackageName>) will also search in +prefixes specified by the upper-case <PACKAGENAME>_ROOT CMake +variable. See policy CMP0144.

+
+ +
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/WIN32.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/WIN32.html new file mode 100644 index 0000000000000000000000000000000000000000..56a0f5922352702c2c62dc8c17559d9aa74f5f88 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/WIN32.html @@ -0,0 +1,139 @@ + + + + + + + + + WIN32 — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

WIN32

+

Set to True when the target system is Windows, including Win64.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/WINCE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/WINCE.html new file mode 100644 index 0000000000000000000000000000000000000000..cb92321a4209c3343f6ebd257a9db98e0a17140a --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/WINCE.html @@ -0,0 +1,143 @@ + + + + + + + + + WINCE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

WINCE

+
+

New in version 3.1.

+
+

True when the CMAKE_SYSTEM_NAME variable is set +to WindowsCE.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/XCODE.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/XCODE.html new file mode 100644 index 0000000000000000000000000000000000000000..ec9ad8925f582e3d4a48154a6152bd69928af852 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/XCODE.html @@ -0,0 +1,142 @@ + + + + + + + + + XCODE — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE

+
+

New in version 3.7.

+
+

True when using Xcode generator.

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file diff --git a/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/XCODE_VERSION.html b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/XCODE_VERSION.html new file mode 100644 index 0000000000000000000000000000000000000000..b51337a7b401c5ee2bce27d65e66d835bad19f29 --- /dev/null +++ b/toolchain/cmake-3.27.9-linux-x86_64/doc/cmake/html/variable/XCODE_VERSION.html @@ -0,0 +1,141 @@ + + + + + + + + + XCODE_VERSION — CMake 3.27.9 Documentation + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

XCODE_VERSION

+

Version of Xcode (Xcode generator only).

+

Under the Xcode generator, this is the version of Xcode +as specified in Xcode.app/Contents/version.plist (such as 3.1.2).

+
+ + +
+
+
+
+ +
+
+ + + + + \ No newline at end of file