text:
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta charset="UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<meta name="generator" content="Asciidoctor 2.0.10"/>
<title>gitsubmodules(7)</title>
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400italic,600,600italic%7CNoto+Serif:400,400italic,700,700italic%7CDroid+Sans+Mono:400,700"/>
<style>
/* Asciidoctor default stylesheet | MIT License | https://asciidoctor.org */
/* Uncomment @import statement to use as custom stylesheet */
/*@import "https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400italic,600,600italic%7CNoto+Serif:400,400italic,700,700italic%7CDroid+Sans+Mono:400,700";*/
article,aside,details,figcaption,figure,footer,header,hgroup,main,nav,section{display:block}
audio,video{display:inline-block}
audio:not([controls]){display:none;height:0}
html{font-family:sans-serif;-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%}
a{background:none}
a:focus{outline:thin dotted}
a:active,a:hover{outline:0}
h1{font-size:2em;margin:.67em 0}
abbr[title]{border-bottom:1px dotted}
b,strong{font-weight:bold}
dfn{font-style:italic}
hr{-moz-box-sizing:content-box;box-sizing:content-box;height:0}
mark{background:#ff0;color:#000}
code,kbd,pre,samp{font-family:monospace;font-size:1em}
pre{white-space:pre-wrap}
q{quotes:"\201C" "\201D" "\2018" "\2019"}
small{font-size:80%}
sub,sup{font-size:75%;line-height:0;position:relative;vertical-align:baseline}
sup{top:-.5em}
sub{bottom:-.25em}
img{border:0}
svg:not(:root){overflow:hidden}
figure{margin:0}
fieldset{border:1px solid silver;margin:0 2px;padding:.35em .625em .75em}
legend{border:0;padding:0}
button,input,select,textarea{font-family:inherit;font-size:100%;margin:0}
button,input{line-height:normal}
button,select{text-transform:none}
button,html input[type="button"],input[type="reset"],input[type="submit"]{-webkit-appearance:button;cursor:pointer}
button[disabled],html input[disabled]{cursor:default}
input[type="checkbox"],input[type="radio"]{box-sizing:border-box;padding:0}
button::-moz-focus-inner,input::-moz-focus-inner{border:0;padding:0}
textarea{overflow:auto;vertical-align:top}
table{border-collapse:collapse;border-spacing:0}
*,*::before,*::after{-moz-box-sizing:border-box;-webkit-box-sizing:border-box;box-sizing:border-box}
html,body{font-size:100%}
body{background:#fff;color:rgba(0,0,0,.8);padding:0;margin:0;font-family:"Noto Serif","DejaVu Serif",serif;font-weight:400;font-style:normal;line-height:1;position:relative;cursor:auto;tab-size:4;-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased}
a:hover{cursor:pointer}
img,object,embed{max-width:100%;height:auto}
object,embed{height:100%}
img{-ms-interpolation-mode:bicubic}
.left{float:left!important}
.right{float:right!important}
.text-left{text-align:left!important}
.text-right{text-align:right!important}
.text-center{text-align:center!important}
.text-justify{text-align:justify!important}
.hide{display:none}
img,object,svg{display:inline-block;vertical-align:middle}
textarea{height:auto;min-height:50px}
select{width:100%}
.center{margin-left:auto;margin-right:auto}
.stretch{width:100%}
.subheader,.admonitionblock td.content>.title,.audioblock>.title,.exampleblock>.title,.imageblock>.title,.listingblock>.title,.literalblock>.title,.stemblock>.title,.openblock>.title,.paragraph>.title,.quoteblock>.title,table.tableblock>.title,.verseblock>.title,.videoblock>.title,.dlist>.title,.olist>.title,.ulist>.title,.qlist>.title,.hdlist>.title{line-height:1.45;color:#7a2518;font-weight:400;margin-top:0;margin-bottom:.25em}
div,dl,dt,dd,ul,ol,li,h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6,pre,form,p,blockquote,th,td{margin:0;padding:0;direction:ltr}
a{color:#2156a5;text-decoration:underline;line-height:inherit}
a:hover,a:focus{color:#1d4b8f}
a img{border:0}
p{font-family:inherit;font-weight:400;font-size:1em;line-height:1.6;margin-bottom:1.25em;text-rendering:optimizeLegibility}
p aside{font-size:.875em;line-height:1.35;font-style:italic}
h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6{font-family:"Open Sans","DejaVu Sans",sans-serif;font-weight:300;font-style:normal;color:#ba3925;text-rendering:optimizeLegibility;margin-top:1em;margin-bottom:.5em;line-height:1.0125em}
h1 small,h2 small,h3 small,#toctitle small,.sidebarblock>.content>.title small,h4 small,h5 small,h6 small{font-size:60%;color:#e99b8f;line-height:0}
h1{font-size:2.125em}
h2{font-size:1.6875em}
h3,#toctitle,.sidebarblock>.content>.title{font-size:1.375em}
h4,h5{font-size:1.125em}
h6{font-size:1em}
hr{border:solid #dddddf;border-width:1px 0 0;clear:both;margin:1.25em 0 1.1875em;height:0}
em,i{font-style:italic;line-height:inherit}
strong,b{font-weight:bold;line-height:inherit}
small{font-size:60%;line-height:inherit}
code{font-family:"Droid Sans Mono","DejaVu Sans Mono",monospace;font-weight:400;color:rgba(0,0,0,.9)}
ul,ol,dl{font-size:1em;line-height:1.6;margin-bottom:1.25em;list-style-position:outside;font-family:inherit}
ul,ol{margin-left:1.5em}
ul li ul,ul li ol{margin-left:1.25em;margin-bottom:0;font-size:1em}
ul.square li ul,ul.circle li ul,ul.disc li ul{list-style:inherit}
ul.square{list-style-type:square}
ul.circle{list-style-type:circle}
ul.disc{list-style-type:disc}
ol li ul,ol li ol{margin-left:1.25em;margin-bottom:0}
dl dt{margin-bottom:.3125em;font-weight:bold}
dl dd{margin-bottom:1.25em}
abbr,acronym{text-transform:uppercase;font-size:90%;color:rgba(0,0,0,.8);border-bottom:1px dotted #ddd;cursor:help}
abbr{text-transform:none}
blockquote{margin:0 0 1.25em;padding:.5625em 1.25em 0 1.1875em;border-left:1px solid #ddd}
blockquote cite{display:block;font-size:.9375em;color:rgba(0,0,0,.6)}
blockquote cite::before{content:"\2014 \0020"}
blockquote cite a,blockquote cite a:visited{color:rgba(0,0,0,.6)}
blockquote,blockquote p{line-height:1.6;color:rgba(0,0,0,.85)}
@media screen and (min-width:768px){h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6{line-height:1.2}
h1{font-size:2.75em}
h2{font-size:2.3125em}
h3,#toctitle,.sidebarblock>.content>.title{font-size:1.6875em}
h4{font-size:1.4375em}}
table{background:#fff;margin-bottom:1.25em;border:solid 1px #dedede}
table thead,table tfoot{background:#f7f8f7}
table thead tr th,table thead tr td,table tfoot tr th,table tfoot tr td{padding:.5em .625em .625em;font-size:inherit;color:rgba(0,0,0,.8);text-align:left}
table tr th,table tr td{padding:.5625em .625em;font-size:inherit;color:rgba(0,0,0,.8)}
table tr.even,table tr.alt{background:#f8f8f7}
table thead tr th,table tfoot tr th,table tbody tr td,table tr td,table tfoot tr td{display:table-cell;line-height:1.6}
h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6{line-height:1.2;word-spacing:-.05em}
h1 strong,h2 strong,h3 strong,#toctitle strong,.sidebarblock>.content>.title strong,h4 strong,h5 strong,h6 strong{font-weight:400}
.clearfix::before,.clearfix::after,.float-group::before,.float-group::after{content:" ";display:table}
.clearfix::after,.float-group::after{clear:both}
:not(pre):not([class^=L])>code{font-size:.9375em;font-style:normal!important;letter-spacing:0;padding:.1em .5ex;word-spacing:-.15em;background:#f7f7f8;-webkit-border-radius:4px;border-radius:4px;line-height:1.45;text-rendering:optimizeSpeed;word-wrap:break-word}
:not(pre)>code.nobreak{word-wrap:normal}
:not(pre)>code.nowrap{white-space:nowrap}
pre{color:rgba(0,0,0,.9);font-family:"Droid Sans Mono","DejaVu Sans Mono",monospace;line-height:1.45;text-rendering:optimizeSpeed}
pre code,pre pre{color:inherit;font-size:inherit;line-height:inherit}
pre>code{display:block}
pre.nowrap,pre.nowrap pre{white-space:pre;word-wrap:normal}
em em{font-style:normal}
strong strong{font-weight:400}
.keyseq{color:rgba(51,51,51,.8)}
kbd{font-family:"Droid Sans Mono","DejaVu Sans Mono",monospace;display:inline-block;color:rgba(0,0,0,.8);font-size:.65em;line-height:1.45;background:#f7f7f7;border:1px solid #ccc;-webkit-border-radius:3px;border-radius:3px;-webkit-box-shadow:0 1px 0 rgba(0,0,0,.2),0 0 0 .1em white inset;box-shadow:0 1px 0 rgba(0,0,0,.2),0 0 0 .1em #fff inset;margin:0 .15em;padding:.2em .5em;vertical-align:middle;position:relative;top:-.1em;white-space:nowrap}
.keyseq kbd:first-child{margin-left:0}
.keyseq kbd:last-child{margin-right:0}
.menuseq,.menuref{color:#000}
.menuseq b:not(.caret),.menuref{font-weight:inherit}
.menuseq{word-spacing:-.02em}
.menuseq b.caret{font-size:1.25em;line-height:.8}
.menuseq i.caret{font-weight:bold;text-align:center;width:.45em}
b.button::before,b.button::after{position:relative;top:-1px;font-weight:400}
b.button::before{content:"[";padding:0 3px 0 2px}
b.button::after{content:"]";padding:0 2px 0 3px}
p a>code:hover{color:rgba(0,0,0,.9)}
#header,#content,#footnotes,#footer{width:100%;margin-left:auto;margin-right:auto;margin-top:0;margin-bottom:0;max-width:62.5em;*zoom:1;position:relative;padding-left:.9375em;padding-right:.9375em}
#header::before,#header::after,#content::before,#content::after,#footnotes::before,#footnotes::after,#footer::before,#footer::after{content:" ";display:table}
#header::after,#content::after,#footnotes::after,#footer::after{clear:both}
#content{margin-top:1.25em}
#content::before{content:none}
#header>h1:first-child{color:rgba(0,0,0,.85);margin-top:2.25rem;margin-bottom:0}
#header>h1:first-child+#toc{margin-top:8px;border-top:1px solid #dddddf}
#header>h1:only-child,body.toc2 #header>h1:nth-last-child(2){border-bottom:1px solid #dddddf;padding-bottom:8px}
#header .details{border-bottom:1px solid #dddddf;line-height:1.45;padding-top:.25em;padding-bottom:.25em;padding-left:.25em;color:rgba(0,0,0,.6);display:-ms-flexbox;display:-webkit-flex;display:flex;-ms-flex-flow:row wrap;-webkit-flex-flow:row wrap;flex-flow:row wrap}
#header .details span:first-child{margin-left:-.125em}
#header .details span.email a{color:rgba(0,0,0,.85)}
#header .details br{display:none}
#header .details br+span::before{content:"\00a0\2013\00a0"}
#header .details br+span.author::before{content:"\00a0\22c5\00a0";color:rgba(0,0,0,.85)}
#header .details br+span#revremark::before{content:"\00a0|\00a0"}
#header #revnumber{text-transform:capitalize}
#header #revnumber::after{content:"\00a0"}
#content>h1:first-child:not([class]){color:rgba(0,0,0,.85);border-bottom:1px solid #dddddf;padding-bottom:8px;margin-top:0;padding-top:1rem;margin-bottom:1.25rem}
#toc{border-bottom:1px solid #e7e7e9;padding-bottom:.5em}
#toc>ul{margin-left:.125em}
#toc ul.sectlevel0>li>a{font-style:italic}
#toc ul.sectlevel0 ul.sectlevel1{margin:.5em 0}
#toc ul{font-family:"Open Sans","DejaVu Sans",sans-serif;list-style-type:none}
#toc li{line-height:1.3334;margin-top:.3334em}
#toc a{text-decoration:none}
#toc a:active{text-decoration:underline}
#toctitle{color:#7a2518;font-size:1.2em}
@media screen and (min-width:768px){#toctitle{font-size:1.375em}
body.toc2{padding-left:15em;padding-right:0}
#toc.toc2{margin-top:0!important;background:#f8f8f7;position:fixed;width:15em;left:0;top:0;border-right:1px solid #e7e7e9;border-top-width:0!important;border-bottom-width:0!important;z-index:1000;padding:1.25em 1em;height:100%;overflow:auto}
#toc.toc2 #toctitle{margin-top:0;margin-bottom:.8rem;font-size:1.2em}
#toc.toc2>ul{font-size:.9em;margin-bottom:0}
#toc.toc2 ul ul{margin-left:0;padding-left:1em}
#toc.toc2 ul.sectlevel0 ul.sectlevel1{padding-left:0;margin-top:.5em;margin-bottom:.5em}
body.toc2.toc-right{padding-left:0;padding-right:15em}
body.toc2.toc-right #toc.toc2{border-right-width:0;border-left:1px solid #e7e7e9;left:auto;right:0}}
@media screen and (min-width:1280px){body.toc2{padding-left:20em;padding-right:0}
#toc.toc2{width:20em}
#toc.toc2 #toctitle{font-size:1.375em}
#toc.toc2>ul{font-size:.95em}
#toc.toc2 ul ul{padding-left:1.25em}
body.toc2.toc-right{padding-left:0;padding-right:20em}}
#content #toc{border-style:solid;border-width:1px;border-color:#e0e0dc;margin-bottom:1.25em;padding:1.25em;background:#f8f8f7;-webkit-border-radius:4px;border-radius:4px}
#content #toc>:first-child{margin-top:0}
#content #toc>:last-child{margin-bottom:0}
#footer{max-width:100%;background:rgba(0,0,0,.8);padding:1.25em}
#footer-text{color:rgba(255,255,255,.8);line-height:1.44}
#content{margin-bottom:.625em}
.sect1{padding-bottom:.625em}
@media screen and (min-width:768px){#content{margin-bottom:1.25em}
.sect1{padding-bottom:1.25em}}
.sect1:last-child{padding-bottom:0}
.sect1+.sect1{border-top:1px solid #e7e7e9}
#content h1>a.anchor,h2>a.anchor,h3>a.anchor,#toctitle>a.anchor,.sidebarblock>.content>.title>a.anchor,h4>a.anchor,h5>a.anchor,h6>a.anchor{position:absolute;z-index:1001;width:1.5ex;margin-left:-1.5ex;display:block;text-decoration:none!important;visibility:hidden;text-align:center;font-weight:400}
#content h1>a.anchor::before,h2>a.anchor::before,h3>a.anchor::before,#toctitle>a.anchor::before,.sidebarblock>.content>.title>a.anchor::before,h4>a.anchor::before,h5>a.anchor::before,h6>a.anchor::before{content:"\00A7";font-size:.85em;display:block;padding-top:.1em}
#content h1:hover>a.anchor,#content h1>a.anchor:hover,h2:hover>a.anchor,h2>a.anchor:hover,h3:hover>a.anchor,#toctitle:hover>a.anchor,.sidebarblock>.content>.title:hover>a.anchor,h3>a.anchor:hover,#toctitle>a.anchor:hover,.sidebarblock>.content>.title>a.anchor:hover,h4:hover>a.anchor,h4>a.anchor:hover,h5:hover>a.anchor,h5>a.anchor:hover,h6:hover>a.anchor,h6>a.anchor:hover{visibility:visible}
#content h1>a.link,h2>a.link,h3>a.link,#toctitle>a.link,.sidebarblock>.content>.title>a.link,h4>a.link,h5>a.link,h6>a.link{color:#ba3925;text-decoration:none}
#content h1>a.link:hover,h2>a.link:hover,h3>a.link:hover,#toctitle>a.link:hover,.sidebarblock>.content>.title>a.link:hover,h4>a.link:hover,h5>a.link:hover,h6>a.link:hover{color:#a53221}
details,.audioblock,.imageblock,.literalblock,.listingblock,.stemblock,.videoblock{margin-bottom:1.25em}
details>summary:first-of-type{cursor:pointer;display:list-item;outline:none;margin-bottom:.75em}
.admonitionblock td.content>.title,.audioblock>.title,.exampleblock>.title,.imageblock>.title,.listingblock>.title,.literalblock>.title,.stemblock>.title,.openblock>.title,.paragraph>.title,.quoteblock>.title,table.tableblock>.title,.verseblock>.title,.videoblock>.title,.dlist>.title,.olist>.title,.ulist>.title,.qlist>.title,.hdlist>.title{text-rendering:optimizeLegibility;text-align:left;font-family:"Noto Serif","DejaVu Serif",serif;font-size:1rem;font-style:italic}
table.tableblock.fit-content>caption.title{white-space:nowrap;width:0}
.paragraph.lead>p,#preamble>.sectionbody>[class="paragraph"]:first-of-type p{font-size:1.21875em;line-height:1.6;color:rgba(0,0,0,.85)}
table.tableblock #preamble>.sectionbody>[class="paragraph"]:first-of-type p{font-size:inherit}
.admonitionblock>table{border-collapse:separate;border:0;background:none;width:100%}
.admonitionblock>table td.icon{text-align:center;width:80px}
.admonitionblock>table td.icon img{max-width:none}
.admonitionblock>table td.icon .title{font-weight:bold;font-family:"Open Sans","DejaVu Sans",sans-serif;text-transform:uppercase}
.admonitionblock>table td.content{padding-left:1.125em;padding-right:1.25em;border-left:1px solid #dddddf;color:rgba(0,0,0,.6)}
.admonitionblock>table td.content>:last-child>:last-child{margin-bottom:0}
.exampleblock>.content{border-style:solid;border-width:1px;border-color:#e6e6e6;margin-bottom:1.25em;padding:1.25em;background:#fff;-webkit-border-radius:4px;border-radius:4px}
.exampleblock>.content>:first-child{margin-top:0}
.exampleblock>.content>:last-child{margin-bottom:0}
.sidebarblock{border-style:solid;border-width:1px;border-color:#dbdbd6;margin-bottom:1.25em;padding:1.25em;background:#f3f3f2;-webkit-border-radius:4px;border-radius:4px}
.sidebarblock>:first-child{margin-top:0}
.sidebarblock>:last-child{margin-bottom:0}
.sidebarblock>.content>.title{color:#7a2518;margin-top:0;text-align:center}
.exampleblock>.content>:last-child>:last-child,.exampleblock>.content .olist>ol>li:last-child>:last-child,.exampleblock>.content .ulist>ul>li:last-child>:last-child,.exampleblock>.content .qlist>ol>li:last-child>:last-child,.sidebarblock>.content>:last-child>:last-child,.sidebarblock>.content .olist>ol>li:last-child>:last-child,.sidebarblock>.content .ulist>ul>li:last-child>:last-child,.sidebarblock>.content .qlist>ol>li:last-child>:last-child{margin-bottom:0}
.literalblock pre,.listingblock>.content>pre{-webkit-border-radius:4px;border-radius:4px;word-wrap:break-word;overflow-x:auto;padding:1em;font-size:.8125em}
@media screen and (min-width:768px){.literalblock pre,.listingblock>.content>pre{font-size:.90625em}}
@media screen and (min-width:1280px){.literalblock pre,.listingblock>.content>pre{font-size:1em}}
.literalblock pre,.listingblock>.content>pre:not(.highlight),.listingblock>.content>pre[class="highlight"],.listingblock>.content>pre[class^="highlight "]{background:#f7f7f8}
.literalblock.output pre{color:#f7f7f8;background:rgba(0,0,0,.9)}
.listingblock>.content{position:relative}
.listingblock code[data-lang]::before{display:none;content:attr(data-lang);position:absolute;font-size:.75em;top:.425rem;right:.5rem;line-height:1;text-transform:uppercase;color:inherit;opacity:.5}
.listingblock:hover code[data-lang]::before{display:block}
.listingblock.terminal pre .command::before{content:attr(data-prompt);padding-right:.5em;color:inherit;opacity:.5}
.listingblock.terminal pre .command:not([data-prompt])::before{content:"$"}
.listingblock pre.highlightjs{padding:0}
.listingblock pre.highlightjs>code{padding:1em;-webkit-border-radius:4px;border-radius:4px}
.listingblock pre.prettyprint{border-width:0}
.prettyprint{background:#f7f7f8}
pre.prettyprint .linenums{line-height:1.45;margin-left:2em}
pre.prettyprint li{background:none;list-style-type:inherit;padding-left:0}
pre.prettyprint li code[data-lang]::before{opacity:1}
pre.prettyprint li:not(:first-child) code[data-lang]::before{display:none}
table.linenotable{border-collapse:separate;border:0;margin-bottom:0;background:none}
table.linenotable td[class]{color:inherit;vertical-align:top;padding:0;line-height:inherit;white-space:normal}
table.linenotable td.code{padding-left:.75em}
table.linenotable td.linenos{border-right:1px solid currentColor;opacity:.35;padding-right:.5em}
pre.pygments .lineno{border-right:1px solid currentColor;opacity:.35;display:inline-block;margin-right:.75em}
pre.pygments .lineno::before{content:"";margin-right:-.125em}
.quoteblock{margin:0 1em 1.25em 1.5em;display:table}
.quoteblock:not(.excerpt)>.title{margin-left:-1.5em;margin-bottom:.75em}
.quoteblock blockquote,.quoteblock p{color:rgba(0,0,0,.85);font-size:1.15rem;line-height:1.75;word-spacing:.1em;letter-spacing:0;font-style:italic;text-align:justify}
.quoteblock blockquote{margin:0;padding:0;border:0}
.quoteblock blockquote::before{content:"\201c";float:left;font-size:2.75em;font-weight:bold;line-height:.6em;margin-left:-.6em;color:#7a2518;text-shadow:0 1px 2px rgba(0,0,0,.1)}
.quoteblock blockquote>.paragraph:last-child p{margin-bottom:0}
.quoteblock .attribution{margin-top:.75em;margin-right:.5ex;text-align:right}
.verseblock{margin:0 1em 1.25em}
.verseblock pre{font-family:"Open Sans","DejaVu Sans",sans;font-size:1.15rem;color:rgba(0,0,0,.85);font-weight:300;text-rendering:optimizeLegibility}
.verseblock pre strong{font-weight:400}
.verseblock .attribution{margin-top:1.25rem;margin-left:.5ex}
.quoteblock .attribution,.verseblock .attribution{font-size:.9375em;line-height:1.45;font-style:italic}
.quoteblock .attribution br,.verseblock .attribution br{display:none}
.quoteblock .attribution cite,.verseblock .attribution cite{display:block;letter-spacing:-.025em;color:rgba(0,0,0,.6)}
.quoteblock.abstract blockquote::before,.quoteblock.excerpt blockquote::before,.quoteblock .quoteblock blockquote::before{display:none}
.quoteblock.abstract blockquote,.quoteblock.abstract p,.quoteblock.excerpt blockquote,.quoteblock.excerpt p,.quoteblock .quoteblock blockquote,.quoteblock .quoteblock p{line-height:1.6;word-spacing:0}
.quoteblock.abstract{margin:0 1em 1.25em;display:block}
.quoteblock.abstract>.title{margin:0 0 .375em;font-size:1.15em;text-align:center}
.quoteblock.excerpt>blockquote,.quoteblock .quoteblock{padding:0 0 .25em 1em;border-left:.25em solid #dddddf}
.quoteblock.excerpt,.quoteblock .quoteblock{margin-left:0}
.quoteblock.excerpt blockquote,.quoteblock.excerpt p,.quoteblock .quoteblock blockquote,.quoteblock .quoteblock p{color:inherit;font-size:1.0625rem}
.quoteblock.excerpt .attribution,.quoteblock .quoteblock .attribution{color:inherit;text-align:left;margin-right:0}
table.tableblock{max-width:100%;border-collapse:separate}
p.tableblock:last-child{margin-bottom:0}
td.tableblock>.content>:last-child{margin-bottom:-1.25em}
td.tableblock>.content>:last-child.sidebarblock{margin-bottom:0}
table.tableblock,th.tableblock,td.tableblock{border:0 solid #dedede}
table.grid-all>thead>tr>.tableblock,table.grid-all>tbody>tr>.tableblock{border-width:0 1px 1px 0}
table.grid-all>tfoot>tr>.tableblock{border-width:1px 1px 0 0}
table.grid-cols>*>tr>.tableblock{border-width:0 1px 0 0}
table.grid-rows>thead>tr>.tableblock,table.grid-rows>tbody>tr>.tableblock{border-width:0 0 1px}
table.grid-rows>tfoot>tr>.tableblock{border-width:1px 0 0}
table.grid-all>*>tr>.tableblock:last-child,table.grid-cols>*>tr>.tableblock:last-child{border-right-width:0}
table.grid-all>tbody>tr:last-child>.tableblock,table.grid-all>thead:last-child>tr>.tableblock,table.grid-rows>tbody>tr:last-child>.tableblock,table.grid-rows>thead:last-child>tr>.tableblock{border-bottom-width:0}
table.frame-all{border-width:1px}
table.frame-sides{border-width:0 1px}
table.frame-topbot,table.frame-ends{border-width:1px 0}
table.stripes-all tr,table.stripes-odd tr:nth-of-type(odd),table.stripes-even tr:nth-of-type(even),table.stripes-hover tr:hover{background:#f8f8f7}
th.halign-left,td.halign-left{text-align:left}
th.halign-right,td.halign-right{text-align:right}
th.halign-center,td.halign-center{text-align:center}
th.valign-top,td.valign-top{vertical-align:top}
th.valign-bottom,td.valign-bottom{vertical-align:bottom}
th.valign-middle,td.valign-middle{vertical-align:middle}
table thead th,table tfoot th{font-weight:bold}
tbody tr th{display:table-cell;line-height:1.6;background:#f7f8f7}
tbody tr th,tbody tr th p,tfoot tr th,tfoot tr th p{color:rgba(0,0,0,.8);font-weight:bold}
p.tableblock>code:only-child{background:none;padding:0}
p.tableblock{font-size:1em}
ol{margin-left:1.75em}
ul li ol{margin-left:1.5em}
dl dd{margin-left:1.125em}
dl dd:last-child,dl dd:last-child>:last-child{margin-bottom:0}
ol>li p,ul>li p,ul dd,ol dd,.olist .olist,.ulist .ulist,.ulist .olist,.olist .ulist{margin-bottom:.625em}
ul.checklist,ul.none,ol.none,ul.no-bullet,ol.no-bullet,ol.unnumbered,ul.unstyled,ol.unstyled{list-style-type:none}
ul.no-bullet,ol.no-bullet,ol.unnumbered{margin-left:.625em}
ul.unstyled,ol.unstyled{margin-left:0}
ul.checklist{margin-left:.625em}
ul.checklist li>p:first-child>.fa-square-o:first-child,ul.checklist li>p:first-child>.fa-check-square-o:first-child{width:1.25em;font-size:.8em;position:relative;bottom:.125em}
ul.checklist li>p:first-child>input[type="checkbox"]:first-child{margin-right:.25em}
ul.inline{display:-ms-flexbox;display:-webkit-box;display:flex;-ms-flex-flow:row wrap;-webkit-flex-flow:row wrap;flex-flow:row wrap;list-style:none;margin:0 0 .625em -1.25em}
ul.inline>li{margin-left:1.25em}
.unstyled dl dt{font-weight:400;font-style:normal}
ol.arabic{list-style-type:decimal}
ol.decimal{list-style-type:decimal-leading-zero}
ol.loweralpha{list-style-type:lower-alpha}
ol.upperalpha{list-style-type:upper-alpha}
ol.lowerroman{list-style-type:lower-roman}
ol.upperroman{list-style-type:upper-roman}
ol.lowergreek{list-style-type:lower-greek}
.hdlist>table,.colist>table{border:0;background:none}
.hdlist>table>tbody>tr,.colist>table>tbody>tr{background:none}
td.hdlist1,td.hdlist2{vertical-align:top;padding:0 .625em}
td.hdlist1{font-weight:bold;padding-bottom:1.25em}
.literalblock+.colist,.listingblock+.colist{margin-top:-.5em}
.colist td:not([class]):first-child{padding:.4em .75em 0;line-height:1;vertical-align:top}
.colist td:not([class]):first-child img{max-width:none}
.colist td:not([class]):last-child{padding:.25em 0}
.thumb,.th{line-height:0;display:inline-block;border:solid 4px #fff;-webkit-box-shadow:0 0 0 1px #ddd;box-shadow:0 0 0 1px #ddd}
.imageblock.left{margin:.25em .625em 1.25em 0}
.imageblock.right{margin:.25em 0 1.25em .625em}
.imageblock>.title{margin-bottom:0}
.imageblock.thumb,.imageblock.th{border-width:6px}
.imageblock.thumb>.title,.imageblock.th>.title{padding:0 .125em}
.image.left,.image.right{margin-top:.25em;margin-bottom:.25em;display:inline-block;line-height:0}
.image.left{margin-right:.625em}
.image.right{margin-left:.625em}
a.image{text-decoration:none;display:inline-block}
a.image object{pointer-events:none}
sup.footnote,sup.footnoteref{font-size:.875em;position:static;vertical-align:super}
sup.footnote a,sup.footnoteref a{text-decoration:none}
sup.footnote a:active,sup.footnoteref a:active{text-decoration:underline}
#footnotes{padding-top:.75em;padding-bottom:.75em;margin-bottom:.625em}
#footnotes hr{width:20%;min-width:6.25em;margin:-.25em 0 .75em;border-width:1px 0 0}
#footnotes .footnote{padding:0 .375em 0 .225em;line-height:1.3334;font-size:.875em;margin-left:1.2em;margin-bottom:.2em}
#footnotes .footnote a:first-of-type{font-weight:bold;text-decoration:none;margin-left:-1.05em}
#footnotes .footnote:last-of-type{margin-bottom:0}
#content #footnotes{margin-top:-.625em;margin-bottom:0;padding:.75em 0}
.gist .file-data>table{border:0;background:#fff;width:100%;margin-bottom:0}
.gist .file-data>table td.line-data{width:99%}
div.unbreakable{page-break-inside:avoid}
.big{font-size:larger}
.small{font-size:smaller}
.underline{text-decoration:underline}
.overline{text-decoration:overline}
.line-through{text-decoration:line-through}
.aqua{color:#00bfbf}
.aqua-background{background:#00fafa}
.black{color:#000}
.black-background{background:#000}
.blue{color:#0000bf}
.blue-background{background:#0000fa}
.fuchsia{color:#bf00bf}
.fuchsia-background{background:#fa00fa}
.gray{color:#606060}
.gray-background{background:#7d7d7d}
.green{color:#006000}
.green-background{background:#007d00}
.lime{color:#00bf00}
.lime-background{background:#00fa00}
.maroon{color:#600000}
.maroon-background{background:#7d0000}
.navy{color:#000060}
.navy-background{background:#00007d}
.olive{color:#606000}
.olive-background{background:#7d7d00}
.purple{color:#600060}
.purple-background{background:#7d007d}
.red{color:#bf0000}
.red-background{background:#fa0000}
.silver{color:#909090}
.silver-background{background:#bcbcbc}
.teal{color:#006060}
.teal-background{background:#007d7d}
.white{color:#bfbfbf}
.white-background{background:#fafafa}
.yellow{color:#bfbf00}
.yellow-background{background:#fafa00}
span.icon>.fa{cursor:default}
a span.icon>.fa{cursor:inherit}
.admonitionblock td.icon [class^="fa icon-"]{font-size:2.5em;text-shadow:1px 1px 2px rgba(0,0,0,.5);cursor:default}
.admonitionblock td.icon .icon-note::before{content:"\f05a";color:#19407c}
.admonitionblock td.icon .icon-tip::before{content:"\f0eb";text-shadow:1px 1px 2px rgba(155,155,0,.8);color:#111}
.admonitionblock td.icon .icon-warning::before{content:"\f071";color:#bf6900}
.admonitionblock td.icon .icon-caution::before{content:"\f06d";color:#bf3400}
.admonitionblock td.icon .icon-important::before{content:"\f06a";color:#bf0000}
.conum[data-value]{display:inline-block;color:#fff!important;background:rgba(0,0,0,.8);-webkit-border-radius:100px;border-radius:100px;text-align:center;font-size:.75em;width:1.67em;height:1.67em;line-height:1.67em;font-family:"Open Sans","DejaVu Sans",sans-serif;font-style:normal;font-weight:bold}
.conum[data-value] *{color:#fff!important}
.conum[data-value]+b{display:none}
.conum[data-value]::after{content:attr(data-value)}
pre .conum[data-value]{position:relative;top:-.125em}
b.conum *{color:inherit!important}
.conum:not([data-value]):empty{display:none}
dt,th.tableblock,td.content,div.footnote{text-rendering:optimizeLegibility}
h1,h2,p,td.content,span.alt{letter-spacing:-.01em}
p strong,td.content strong,div.footnote strong{letter-spacing:-.005em}
p,blockquote,dt,td.content,span.alt{font-size:1.0625rem}
p{margin-bottom:1.25rem}
.sidebarblock p,.sidebarblock dt,.sidebarblock td.content,p.tableblock{font-size:1em}
.exampleblock>.content{background:#fffef7;border-color:#e0e0dc;-webkit-box-shadow:0 1px 4px #e0e0dc;box-shadow:0 1px 4px #e0e0dc}
.print-only{display:none!important}
@page{margin:1.25cm .75cm}
@media print{*{-webkit-box-shadow:none!important;box-shadow:none!important;text-shadow:none!important}
html{font-size:80%}
a{color:inherit!important;text-decoration:underline!important}
a.bare,a[href^="#"],a[href^="mailto:"]{text-decoration:none!important}
a[href^="http:"]:not(.bare)::after,a[href^="https:"]:not(.bare)::after{content:"(" attr(href) ")";display:inline-block;font-size:.875em;padding-left:.25em}
abbr[title]::after{content:" (" attr(title) ")"}
pre,blockquote,tr,img,object,svg{page-break-inside:avoid}
thead{display:table-header-group}
svg{max-width:100%}
p,blockquote,dt,td.content{font-size:1em;orphans:3;widows:3}
h2,h3,#toctitle,.sidebarblock>.content>.title{page-break-after:avoid}
#toc,.sidebarblock,.exampleblock>.content{background:none!important}
#toc{border-bottom:1px solid #dddddf!important;padding-bottom:0!important}
body.book #header{text-align:center}
body.book #header>h1:first-child{border:0!important;margin:2.5em 0 1em}
body.book #header .details{border:0!important;display:block;padding:0!important}
body.book #header .details span:first-child{margin-left:0!important}
body.book #header .details br{display:block}
body.book #header .details br+span::before{content:none!important}
body.book #toc{border:0!important;text-align:left!important;padding:0!important;margin:0!important}
body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-break-before:always}
.listingblock code[data-lang]::before{display:block}
#footer{padding:0 .9375em}
.hide-on-print{display:none!important}
.print-only{display:block!important}
.hide-for-print{display:none!important}
.show-for-print{display:inherit!important}}
@media print,amzn-kf8{#header>h1:first-child{margin-top:1.25rem}
.sect1{padding:0!important}
.sect1+.sect1{border:0}
#footer{background:none}
#footer-text{color:rgba(0,0,0,.6);font-size:.9em}}
@media amzn-kf8{#header,#content,#footnotes,#footer{padding:0}}
</style>
</head>
<body class="manpage">
<div id="header">
<h1>gitsubmodules(7) Manual Page</h1>
<h2 id="_name">NAME</h2>
<div class="sectionbody">
<p>gitsubmodules - Mounting one repository inside another</p>
</div>
</div>
<div id="content">
<div class="sect1">
<h2 id="_synopsis">SYNOPSIS</h2>
<div class="sectionbody">
<div class="literalblock">
<div class="content">
<pre>.gitmodules, $GIT_DIR/config</pre>
</div>
</div>
<div class="listingblock">
<div class="content">
<pre>git submodule
git <command> --recurse-submodules</pre>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
<div class="paragraph">
<p>A submodule is a repository embedded inside another repository.
The submodule has its own history; the repository it is embedded
in is called a superproject.</p>
</div>
<div class="paragraph">
<p>On the filesystem, a submodule usually (but not always - see FORMS below)
consists of (i) a Git directory located under the <code>$GIT_DIR/modules/</code>
directory of its superproject, (ii) a working directory inside the
superproject’s working directory, and a <code>.git</code> file at the root of
the submodule’s working directory pointing to (i).</p>
</div>
<div class="paragraph">
<p>Assuming the submodule has a Git directory at <code>$GIT_DIR/modules/foo/</code>
and a working directory at <code>path/to/bar/</code>, the superproject tracks the
submodule via a <code>gitlink</code> entry in the tree at <code>path/to/bar</code> and an entry
in its <code>.gitmodules</code> file (see <a href="gitmodules.html">gitmodules(5)</a>) of the form
<code>submodule.foo.path = path/to/bar</code>.</p>
</div>
<div class="paragraph">
<p>The <code>gitlink</code> entry contains the object name of the commit that the
superproject expects the submodule’s working directory to be at.</p>
</div>
<div class="paragraph">
<p>The section <code>submodule.foo.*</code> in the <code>.gitmodules</code> file gives additional
hints to Git’s porcelain layer. For example, the <code>submodule.foo.url</code>
setting specifies where to obtain the submodule.</p>
</div>
<div class="paragraph">
<p>Submodules can be used for at least two different use cases:</p>
</div>
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Using another project while maintaining independent history.
Submodules allow you to contain the working tree of another project
within your own working tree while keeping the history of both
projects separate. Also, since submodules are fixed to an arbitrary
version, the other project can be independently developed without
affecting the superproject, allowing the superproject project to
fix itself to new versions only when desired.</p>
</li>
<li>
<p>Splitting a (logically single) project into multiple
repositories and tying them back together. This can be used to
overcome current limitations of Git’s implementation to have
finer grained access:</p>
<div class="ulist">
<ul>
<li>
<p>Size of the Git repository:
In its current form Git scales up poorly for large repositories containing
content that is not compressed by delta computation between trees.
For example, you can use submodules to hold large binary assets
and these repositories can be shallowly cloned such that you do not
have a large history locally.</p>
</li>
<li>
<p>Transfer size:
In its current form Git requires the whole working tree present. It
does not allow partial trees to be transferred in fetch or clone.
If the project you work on consists of multiple repositories tied
together as submodules in a superproject, you can avoid fetching the
working trees of the repositories you are not interested in.</p>
</li>
<li>
<p>Access control:
By restricting user access to submodules, this can be used to implement
read/write policies for different users.</p>
</li>
</ul>
</div>
</li>
</ol>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_the_configuration_of_submodules">The configuration of submodules</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Submodule operations can be configured using the following mechanisms
(from highest to lowest precedence):</p>
</div>
<div class="ulist">
<ul>
<li>
<p>The command line for those commands that support taking submodules
as part of their pathspecs. Most commands have a boolean flag
<code>--recurse-submodules</code> which specify whether to recurse into submodules.
Examples are <code>grep</code> and <code>checkout</code>.
Some commands take enums, such as <code>fetch</code> and <code>push</code>, where you can
specify how submodules are affected.</p>
</li>
<li>
<p>The configuration inside the submodule. This includes <code>$GIT_DIR/config</code>
in the submodule, but also settings in the tree such as a <code>.gitattributes</code>
or <code>.gitignore</code> files that specify behavior of commands inside the
submodule.</p>
<div class="paragraph">
<p>For example an effect from the submodule’s <code>.gitignore</code> file
would be observed when you run <code>git status --ignore-submodules=none</code> in
the superproject. This collects information from the submodule’s working
directory by running <code>status</code> in the submodule while paying attention
to the <code>.gitignore</code> file of the submodule.</p>
</div>
<div class="paragraph">
<p>The submodule’s <code>$GIT_DIR/config</code> file would come into play when running
<code>git push --recurse-submodules=check</code> in the superproject, as this would
check if the submodule has any changes not published to any remote. The
remotes are configured in the submodule as usual in the <code>$GIT_DIR/config</code>
file.</p>
</div>
</li>
<li>
<p>The configuration file <code>$GIT_DIR/config</code> in the superproject.
Git only recurses into active submodules (see "ACTIVE SUBMODULES"
section below).</p>
<div class="paragraph">
<p>If the submodule is not yet initialized, then the configuration
inside the submodule does not exist yet, so where to
obtain the submodule from is configured here for example.</p>
</div>
</li>
<li>
<p>The <code>.gitmodules</code> file inside the superproject. A project usually
uses this file to suggest defaults for the upstream collection
of repositories for the mapping that is required between a
submodule’s name and its path.</p>
<div class="paragraph">
<p>This file mainly serves as the mapping between the name and path of submodules
in the superproject, such that the submodule’s Git directory can be
located.</p>
</div>
<div class="paragraph">
<p>If the submodule has never been initialized, this is the only place
where submodule configuration is found. It serves as the last fallback
to specify where to obtain the submodule from.</p>
</div>
</li>
</ul>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_forms">FORMS</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Submodules can take the following forms:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>The basic form described in DESCRIPTION with a Git directory,
a working directory, a <code>gitlink</code>, and a <code>.gitmodules</code> entry.</p>
</li>
<li>
<p>"Old-form" submodule: A working directory with an embedded
<code>.git</code> directory, and the tracking <code>gitlink</code> and <code>.gitmodules</code> entry in
the superproject. This is typically found in repositories generated
using older versions of Git.</p>
<div class="paragraph">
<p>It is possible to construct these old form repositories manually.</p>
</div>
<div class="paragraph">
<p>When deinitialized or deleted (see below), the submodule’s Git
directory is automatically moved to <code>$GIT_DIR/modules/<name>/</code>
of the superproject.</p>
</div>
</li>
<li>
<p>Deinitialized submodule: A <code>gitlink</code>, and a <code>.gitmodules</code> entry,
but no submodule working directory. The submodule’s Git directory
may be there as after deinitializing the Git directory is kept around.
The directory which is supposed to be the working directory is empty instead.</p>
<div class="paragraph">
<p>A submodule can be deinitialized by running <code>git submodule deinit</code>.
Besides emptying the working directory, this command only modifies
the superproject’s <code>$GIT_DIR/config</code> file, so the superproject’s history
is not affected. This can be undone using <code>git submodule init</code>.</p>
</div>
</li>
<li>
<p>Deleted submodule: A submodule can be deleted by running
<code>git rm <submodule path> && git commit</code>. This can be undone
using <code>git revert</code>.</p>
<div class="paragraph">
<p>The deletion removes the superproject’s tracking data, which are
both the <code>gitlink</code> entry and the section in the <code>.gitmodules</code> file.
The submodule’s working directory is removed from the file
system, but the Git directory is kept around as it to make it
possible to checkout past commits without requiring fetching
from another repository.</p>
</div>
<div class="paragraph">
<p>To completely remove a submodule, manually delete
<code>$GIT_DIR/modules/<name>/</code>.</p>
</div>
</li>
</ul>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_active_submodules">ACTIVE SUBMODULES</h2>
<div class="sectionbody">
<div class="paragraph">
<p>A submodule is considered active,</p>
</div>
<div class="olist arabic">
<ol class="arabic">
<li>
<p>if <code>submodule.<name>.active</code> is set to <code>true</code></p>
<div class="paragraph">
<p>or</p>
</div>
</li>
<li>
<p>if the submodule’s path matches the pathspec in <code>submodule.active</code></p>
<div class="paragraph">
<p>or</p>
</div>
</li>
<li>
<p>if <code>submodule.<name>.url</code> is set.</p>
</li>
</ol>
</div>
<div class="paragraph">
<p>and these are evaluated in this order.</p>
</div>
<div class="paragraph">
<p>For example:</p>
</div>
<div class="literalblock">
<div class="content">
<pre>[submodule "foo"]
  active = false
  url = https://example.org/foo
[submodule "bar"]
  active = true
  url = https://example.org/bar
[submodule "baz"]
  url = https://example.org/baz</pre>
</div>
</div>
<div class="paragraph">
<p>In the above config only the submodule <em>bar</em> and <em>baz</em> are active,
<em>bar</em> due to (1) and <em>baz</em> due to (3). <em>foo</em> is inactive because
(1) takes precedence over (3)</p>
</div>
<div class="paragraph">
<p>Note that (3) is a historical artefact and will be ignored if the
(1) and (2) specify that the submodule is not active. In other words,
if we have a <code>submodule.<name>.active</code> set to <code>false</code> or if the
submodule’s path is excluded in the pathspec in <code>submodule.active</code>, the
url doesn’t matter whether it is present or not. This is illustrated in
the example that follows.</p>
</div>
<div class="literalblock">
<div class="content">
<pre>[submodule "foo"]
  active = true
  url = https://example.org/foo
[submodule "bar"]
  url = https://example.org/bar
[submodule "baz"]
  url = https://example.org/baz
[submodule "bob"]
  ignore = true
[submodule]
  active = b*
  active = :(exclude) baz</pre>
</div>
</div>
<div class="paragraph">
<p>In here all submodules except <em>baz</em> (foo, bar, bob) are active.
<em>foo</em> due to its own active flag and all the others due to the
submodule active pathspec, which specifies that any submodule
starting with <em>b</em> except <em>baz</em> are also active, regardless of the
presence of the .url field.</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_workflow_for_a_third_party_library">Workflow for a third party library</h2>
<div class="sectionbody">
<div class="literalblock">
<div class="content">
<pre># add a submodule
git submodule add <url> <path></pre>
</div>
</div>
<div class="literalblock">
<div class="content">
<pre># occasionally update the submodule to a new version:
git -C <path> checkout <new version>
git add <path>
git commit -m "update submodule to new version"</pre>
</div>
</div>
<div class="literalblock">
<div class="content">
<pre># See the list of submodules in a superproject
git submodule status</pre>
</div>
</div>
<div class="literalblock">
<div class="content">
<pre># See FORMS on removing submodules</pre>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_workflow_for_an_artificially_split_repo">Workflow for an artificially split repo</h2>
<div class="sectionbody">
<div class="literalblock">
<div class="content">
<pre># Enable recursion for relevant commands, such that
# regular commands recurse into submodules by default
git config --global submodule.recurse true</pre>
</div>
</div>
<div class="literalblock">
<div class="content">
<pre># Unlike the other commands below clone still needs
# its own recurse flag:
git clone --recurse <URL> <directory>
cd <directory></pre>
</div>
</div>
<div class="literalblock">
<div class="content">
<pre># Get to know the code:
git grep foo
git ls-files</pre>
</div>
</div>
<div class="literalblock">
<div class="content">
<pre># Get new code
git fetch
git pull --rebase</pre>
</div>
</div>
<div class="literalblock">
<div class="content">
<pre># change worktree
git checkout
git reset</pre>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_implementation_details">Implementation details</h2>
<div class="sectionbody">
<div class="paragraph">
<p>When cloning or pulling a repository containing submodules the submodules
will not be checked out by default; You can instruct <em>clone</em> to recurse
into submodules. The <em>init</em> and <em>update</em> subcommands of <em>git submodule</em>
will maintain submodules checked out and at an appropriate revision in
your working tree. Alternatively you can set <em>submodule.recurse</em> to have
<em>checkout</em> recursing into submodules (note that <em>submodule.recurse</em> also
affects other git commands, see <a href="git-config.html">git-config(1)</a> for a complete list).</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_see_also">SEE ALSO</h2>
<div class="sectionbody">
<div class="paragraph">
<p><a href="git-submodule.html">git-submodule(1)</a>, <a href="gitmodules.html">gitmodules(5)</a>.</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_git">GIT</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Part of the <a href="git.html">git(1)</a> suite</p>
</div>
</div>
</div>
</div>
<div id="footer">
<div id="footer-text">
Last updated 2020-06-01 18:38:37 UTC
</div>
</div>
</body>
</html>


text:
package org.osito.androidpromise.deferred;

public class Deferred<T> implements  Promise<T> {

    private TasksHolder tasks = new SameThreadTasksHolder();
    private TasksHolder mainThreadTasks = new MainThreadTasksHolder();
    private TasksHolder backgroundThreadTasks = new BackgroundThreadTasksHolder();
    private TasksHolder asyncTasks = new AsyncTasksHolder();

    protected Deferred(){}

    public static <T> Deferred<T> newDeferred() {
        return new Deferred<T>();
    }

    @Override
    public Promise<T> then(Task<T> task) {
        tasks.add(task);
        return this;
    }

    @Override
    public Promise<T> thenOnMainThread(Task<T> task) {
        mainThreadTasks.add(task);
        return this;
    }

    @Override
    public Promise<T> thenAsync(Task<T> task) {
        asyncTasks.add(task);
        return this;
    }

    @Override
    public Promise<T> thenOnBackgroundThread(Task<T> task) {
        backgroundThreadTasks.add(task);
        return this;
    }

    @Override
    public Promise<T> onError(Task<Throwable> task) {
        tasks.addOnError(task);
        return this;
    }

    @Override
    public Promise<T> onErrorOnMainThread(Task<Throwable> task) {
        mainThreadTasks.addOnError(task);
        return this;
    }

    @Override
    public Promise<T> onErrorAsync(Task<Throwable> task) {
        asyncTasks.addOnError(task);
        return this;
    }

    @Override
    public Promise<T> onErrorOnBackgroundThread(Task<Throwable> task) {
        backgroundThreadTasks.addOnError(task);
        return this;
    }

    public void resolve(T data) {
        tasks.resolve(data);
        mainThreadTasks.resolve(data);
        backgroundThreadTasks.resolve(data);
        asyncTasks.resolve(data);
    }

    public void reject() {
        reject(null);
    }

    public void reject(Throwable throwable) {
        tasks.reject(throwable);
        mainThreadTasks.reject(throwable);
        backgroundThreadTasks.reject(throwable);
        asyncTasks.reject(throwable);
    }

    @Override
    public <V> Promise<V> convert(final Converter<T, V> converter) {
        final Deferred<V> deferred = newDeferred();
        then(new Task<T>() {
            @Override
            public void run(T data) {
                try {
                    deferred.resolve(converter.transform(data));
                } catch (Exception ex) {
                    deferred.reject(ex);
                }
            }
        });
        onError(new Task<Throwable>() {
            @Override
            public void run(Throwable data) {
                deferred.reject(data);
            }
        });
        return deferred;
    }
}

redpajama_set_name: RedPajamaGithub


text:
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html
    PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">

  <title>Qt 4.3: qmake Variable Reference</title>
  <link rel="prev" href="qmake-reference.html" />
  <link rel="contents" href="qmake-manual.html" />
  <link rel="next" href="qmake-function-reference.html" />
  <link href="classic.css" rel="stylesheet" type="text/css" />

  	Home · All Classes · Main Classes · Grouped Classes · Modules · Functions

[Previous: qmake Reference]
[Contents]
[Next: qmake Function Reference]

qmake Variable Reference

<tt>qmake</tt>'s fundamental behavior is influenced by variable declarations that define the build process of each project. Some of these declare resources, such as headers and source files, that are common to each platform; others are used to customize the behavior of compilers and linkers on specific platforms.

Platform-specific variables follow the naming pattern of the variables which they extend or modify, but include the name of the relevant platform in their name. For example, <tt>QMAKE_LIBS</tt> can be used to specify a list of libraries that a project needs to link against, and <tt>QMAKE_LIBS_X11</tt> can be used to extend or override this list.

CONFIG

DEFINES

DEF_FILE

DEPENDPATH

DESTDIR

DESTDIR_TARGET

DLLDESTDIR

DISTFILES

DSP_TEMPLATE

FORMS

FORMS3

HEADERS

INCLUDEPATH

INSTALLS

LEXIMPLS

LEXOBJECTS

LEXSOURCES

LIBS

LITERAL_HASH

MAKEFILE

MAKEFILE_GENERATOR

MOC_DIR

OBJECTS

OBJECTS_DIR

OBJMOC

POST_TARGETDEPS

PRE_TARGETDEPS

PRECOMPILED_HEADER

QMAKE

QMAKESPEC

QMAKE_APP_FLAG

QMAKE_APP_OR_DLL

QMAKE_AR_CMD

QMAKE_BUNDLE_DATA

QMAKE_BUNDLE_EXTENSION

QMAKE_CC

QMAKE_CFLAGS_DEBUG

QMAKE_CFLAGS_MT

QMAKE_CFLAGS_MT_DBG

QMAKE_CFLAGS_MT_DLL

QMAKE_CFLAGS_MT_DLLDBG

QMAKE_CFLAGS_RELEASE

QMAKE_CFLAGS_SHLIB

QMAKE_CFLAGS_THREAD

QMAKE_CFLAGS_WARN_OFF

QMAKE_CFLAGS_WARN_ON

QMAKE_CLEAN

QMAKE_CXX

QMAKE_CXXFLAGS

QMAKE_CXXFLAGS_DEBUG

QMAKE_CXXFLAGS_MT

QMAKE_CXXFLAGS_MT_DBG

QMAKE_CXXFLAGS_MT_DLL

QMAKE_CXXFLAGS_MT_DLLDBG

QMAKE_CXXFLAGS_RELEASE

QMAKE_CXXFLAGS_SHLIB

QMAKE_CXXFLAGS_THREAD

QMAKE_CXXFLAGS_WARN_OFF

QMAKE_CXXFLAGS_WARN_ON

QMAKE_EXTENSION_SHLIB

QMAKE_EXT_MOC

QMAKE_EXT_UI

QMAKE_EXT_PRL

QMAKE_EXT_LEX

QMAKE_EXT_YACC

QMAKE_EXT_OBJ

QMAKE_EXT_CPP

QMAKE_EXT_H

QMAKE_FAILED_REQUIREMENTS

QMAKE_FILETAGS

QMAKE_FRAMEWORK_BUNDLE_NAME

QMAKE_FRAMEWORK_VERSION

QMAKE_INCDIR

QMAKE_INCDIR_OPENGL

QMAKE_INCDIR_QT

QMAKE_INCDIR_THREAD

QMAKE_INCDIR_X11

QMAKE_LFLAGS

QMAKE_LFLAGS_CONSOLE

QMAKE_LFLAGS_CONSOLE_DLL

QMAKE_LFLAGS_DEBUG

QMAKE_LFLAGS_PLUGIN

QMAKE_LFLAGS_QT_DLL

QMAKE_LFLAGS_RELEASE

QMAKE_LFLAGS_SHAPP

QMAKE_LFLAGS_SHLIB

QMAKE_LFLAGS_SONAME

QMAKE_LFLAGS_THREAD

QMAKE_LFLAGS_WINDOWS

QMAKE_LFLAGS_WINDOWS_DLL

QMAKE_LIBDIR

QMAKE_LIBDIR_FLAGS

QMAKE_LIBDIR_OPENGL

QMAKE_LIBDIR_QT

QMAKE_LIBDIR_X11

QMAKE_LIBS

QMAKE_LIBS_CONSOLE

QMAKE_LIBS_OPENGL

QMAKE_LIBS_OPENGL_QT

QMAKE_LIBS_QT

QMAKE_LIBS_QT_DLL

QMAKE_LIBS_QT_OPENGL

QMAKE_LIBS_QT_THREAD

QMAKE_LIBS_RT

QMAKE_LIBS_RTMT

QMAKE_LIBS_THREAD

QMAKE_LIBS_WINDOWS

QMAKE_LIBS_X11

QMAKE_LIBS_X11SM

QMAKE_LIB_FLAG

QMAKE_LINK_SHLIB_CMD

QMAKE_POST_LINK

QMAKE_PRE_LINK

QMAKE_LN_SHLIB

QMAKE_MAC_SDK

QMAKE_MAKEFILE

QMAKE_MOC_SRC

QMAKE_QMAKE

QMAKE_QT_DLL

QMAKE_RESOURCE_FLAGS

QMAKE_RUN_CC

QMAKE_RUN_CC_IMP

QMAKE_RUN_CXX

QMAKE_RUN_CXX_IMP

QMAKE_TARGET

QMAKE_UIC

QT

QTPLUGIN

RC_FILE

RCC_DIR

REQUIRES

RES_FILE

SOURCES

SRCMOC

SUBDIRS

TARGET

TARGET_EXT

TARGET_x

TARGET_x.y.z

TEMPLATE

TRANSLATIONS

UICIMPLS

UICOBJECTS

UI_DIR

UI_HEADERS_DIR

UI_SOURCES_DIR

VERSION

VER_MAJ

VER_MIN

VER_PAT

VPATH

YACCIMPLS

YACCOBJECTS

YACCSOURCES

CONFIG

The <tt>CONFIG</tt> variable specifies project configuration and compiler options. The values will be recognized internally by <tt>qmake</tt> and have special meaning. They are as follows.

These <tt>CONFIG</tt> values control compilation flags:

Option	Description

release	The project is to be built in release mode. This is ignored if <tt>debug</tt> is also specified.

debug	The project is to be built in debug mode.

debug_and_release	The project is built in both debug and release modes. This can have some unexpected side effects (see below for more information).

build_all	If <tt>debug_and_release</tt> is specified, the project is built in both debug and release modes by default.

ordered	When using the <tt>subdirs</tt> template, this option specifies that the directories listed should be processed in the order in which they are given.

warn_on	The compiler should output as many warnings as possible. This is ignored if <tt>warn_off</tt> is specified.

warn_off	The compiler should output as few warnings as possible.

Since the <tt>debug</tt> option overrides the <tt>release</tt> option when both are defined in the <tt>CONFIG</tt> variable, it is necessary to use the <tt>debug_and_release</tt> option if you want to allow both debug and release versions of a project to be built. In such a case, the Makefile that <tt>qmake</tt> generates includes a rule that builds both versions, and this can be invoked in the following way:

 make all

Adding the <tt>build_all</tt> option to the <tt>CONFIG</tt> variable makes this rule the default when building the project, and installation targets will be created for both debug and release builds.

Additionally, adding <tt>debug_and_release</tt> to the <tt>CONFIG</tt> variable will cause both <tt>debug</tt> and <tt>release</tt> to be defined in the contents of <tt>CONFIG</tt> when the project file is processed, causing scopes that test for each value to be processed for both debug and release modes. As a result, it may be useful to define mode-specific variables, such as QMAKE_LFLAGS_RELEASE, instead of general variables, such as QMAKE_LFLAGS, where possible.

The following options define the application/library type:

Option	Description

qt	The target is a Qt application/library and requires the Qt library and header files. The proper include and library paths for the Qt library will automatically be added to the project. This is defined by default, and can be fine-tuned with the <tt>\l{#qt}{QT}</tt> variable.

opengl	The target requires the OpenGL (or Mesa) headers/libraries. The proper include and library paths for these libraries will automatically be added to the project.

thread	The target is a multi-threaded application or library. The proper defines and compiler flags will automatically be added to the project.

x11	The target is a X11 application or library. The proper include paths and libraries will automatically be added to the project.

windows	The target is a Win32 window application (app only). The proper include paths,compiler flags and libraries will automatically be added to the project.

console	The target is a Win32 console application (app only). The proper include paths, compiler flags and libraries will automatically be added to the project.

dll	The target is a shared object/DLL.The proper include paths, compiler flags and libraries will automatically be added to the project.

staticlib	The target is a static library (lib only). The proper compiler flags will automatically be added to the project.

plugin	The target is a plugin (lib only). This enables dll as well.

designer	The target is a plugin for Qt Designer.

uic3	Configures qmake to run uic3 on the content of <tt>FORMS3</tt> if defined; otherwise the contents of <tt>FORMS</tt> will be processed instead.

no_lflags_merge	Ensures that the list of libraries stored in the <tt>LIBS</tt> variable is not reduced to a list of unique values before it is used.

resources	Configures qmake to run rcc on the content of <tt>RESOURCES</tt> if defined.

These options are used to set the compiler flags:

Option	Description

exceptions	Exception support is enabled.

rtti	RTTI support is enabled.

stl	STL support is enabled.

These options define specific things on Windows only:

Option	Description

flat	When using the vcapp template this will put all the source files into the source group and the header files into the header group regardless of what directory they reside in. Turning this option off will group the files within the source/header group depending on the directory they reside. This is turned on by default.

embed_manifest_dll	Embeds a manifest file in the DLL created as part of a library project.

embed_manifest_exe	Embeds a manifest file in the DLL created as part of an application project.

See qmake Platform Notes for more information on the options for embedding manifest files.

These options only have an effect on Mac OS X:

Option	Description

ppc	Builds a PowerPC binary.

x86	Builds an i386 compatible binary.

app_bundle	Puts the executable into a bundle (this is the default).

lib_bundle	Puts the library into a library bundle.

The build process for bundles is also influenced by the contents of the QMAKE_BUNDLE_DATA variable.

The <tt>CONFIG</tt> variable will also be checked when resolving scopes. You may assign anything to this variable.

For example:

 CONFIG += qt console newstuff
 ...
 newstuff {
     SOURCES += new.cpp
     HEADERS += new.h
 }

DEFINES

<tt>qmake</tt> adds the values of this variable as compiler C preprocessor macros (-D option).

For example:

 DEFINES += USE_MY_STUFF QT_DLL

DEF_FILE

This is only used on Windows when using the <tt>app</tt> template.

Specifies a <tt>.def</tt> file to be included in the project.

DEPENDPATH

This variable contains the list of all directories to look in to resolve dependencies. This will be used when crawling through <tt>included</tt> files.

DESTDIR

Specifies where to put the target file.

For example:

 DESTDIR = ../../lib

DESTDIR_TARGET

This variable is set internally by <tt>qmake</tt>, which is basically the <tt>DESTDIR</tt> variable with the <tt>TARGET</tt> variable appened at the end. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

DLLDESTDIR

Specifies where to copy the target dll.

DISTFILES

This variable contains a list of files to be included in the dist target. This feature is supported by UnixMake specs only.

For example:

 DISTFILES += ../program.txt

DSP_TEMPLATE

This variable is set internally by <tt>qmake</tt>, which specifies where the dsp template file for basing generated dsp files is stored. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

FORMS

This variable specifies the .ui files (see Qt Designer) to be processed through <tt>uic</tt> before compiling. All dependencies, headers and source files required to build these .ui files will automatically be added to the project.

For example:

 FORMS = mydialog.ui \
     mywidget.ui \
         myconfig.ui

If FORMS3 is defined in your project, then this variable must contain forms for uic, and not uic3. If CONFIG contains uic3, and FORMS3 is not defined, the this variable must contain only uic3 type forms.

FORMS3

This variable specifies the old style .ui files to be processed through <tt>uic3</tt> before compiling, when <tt>CONFIG</tt> contains uic3. All dependencies, headers and source files required to build these .ui files will automatically be added to the project.

For example:

 FORMS3 = my_uic3_dialog.ui \
      my_uic3_widget.ui \
          my_uic3_config.ui

HEADERS

Defines the header files for the project.

<tt>qmake</tt> will generate dependency information (unless <tt>-nodepend</tt> is specified on the command line) for the specified headers. <tt>qmake</tt> will also automatically detect if <tt>moc</tt> is required by the classes in these headers, and add the appropriate dependencies and files to the project for generating and linking the moc files.

For example:

 HEADERS = myclass.h \
           login.h \
           mainwindow.h

See also SOURCES.

INCLUDEPATH

This variable specifies the #include directories which should be searched when compiling the project. Use ';' or a space as the directory separator.

For example:

 INCLUDEPATH = c:/msdev/include d:/stl/include

INSTALLS

This variable contains a list of resources that will be installed when <tt>make install</tt> or a similar installation procedure is executed. Each item in the list is typically defined with attributes that provide information about where it will be installed.

For example, the following <tt>target.path</tt> definition describes where the build target will be installed, and the <tt>INSTALLS</tt> assignment adds the build target to the list of existing resources to be installed:

 target.path += $$[QT_INSTALL_PLUGINS]/imageformats
 INSTALLS += target

LEXIMPLS

This variable contains a list of lex implementation files. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

LEXOBJECTS

This variable contains the names of intermediate lex object files.The value of this variable is typically handled by <tt>qmake</tt> and rarely needs to be modified.

LEXSOURCES

This variable contains a list of lex source files. All dependencies, headers and source files will automatically be added to the project for building these lex files.

For example:

 LEXSOURCES = lexer.l

LIBS

This variable contains a list of libraries to be linked into the project. You can use the Unix <tt>-l</tt> (library) and -L (library path) flags and qmake will do the correct thing with these libraries on Windows (namely this means passing the full path of the library to the linker). The only limitation to this is the library must exist, for qmake to find which directory a <tt>-l</tt> lib lives in.

For example:

 unix:LIBS += -L/usr/local/lib -lmath
 win32:LIBS += c:/mylibs/math.lib

Note: On Windows, specifying libraries with the <tt>-l</tt> option, as in the above example, will cause the library with the highest version number to be used; for example, <tt>libmath2.lib</tt> could potentially be used instead of <tt>libmathlib</tt>. To avoid this ambiguity, we recommend that you explicitly specify the library to be used by including the <tt>.lib</tt> file name suffix.

By default, the list of libraries stored in <tt>LIBS</tt> is reduced to a list of unique names before it is used. To change this behavior, add the <tt>no_lflags_merge</tt> option to the <tt>CONFIG</tt> variable:

 CONFIG += no_lflags_merge

LITERAL_HASH

This variable is used whenever a literal hash character (<tt>#</tt>) is needed in a variable declaration, perhaps as part of a file name or in a string passed to some external application.

For example:

 # To include a literal hash character, use the $$LITERAL_HASH variable:
 urlPieces = http://doc.trolltech.com/4.0/qtextdocument.html pageCount
 message($$join(urlPieces, $$LITERAL_HASH))

By using <tt>LITERAL_HASH</tt> in this way, the <tt>#</tt> character can be used to construct a URL for the <tt>message()</tt> function to print to the console.

MAKEFILE

This variable specifies the name of the Makefile which <tt>qmake</tt> should use when outputting the dependency information for building a project. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

MAKEFILE_GENERATOR

This variable contains the name of the Makefile generator to use when generating a Makefile. The value of this variable is typically handled internally by <tt>qmake</tt> and rarely needs to be modified.

MOC_DIR

This variable specifies the directory where all intermediate moc files should be placed.

For example:

 unix:MOC_DIR = ../myproject/tmp
 win32:MOC_DIR = c:/myproject/tmp

OBJECTS

This variable is generated from the SOURCES variable. The extension of each source file will have been replaced by .o (Unix) or .obj (Win32). The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

OBJECTS_DIR

This variable specifies the directory where all intermediate objects should be placed.

For example:

 unix:OBJECTS_DIR = ../myproject/tmp
 win32:OBJECTS_DIR = c:/myproject/tmp

OBJMOC

This variable is set by <tt>qmake</tt> if files can be found that contain the Q_OBJECT macro. <tt>OBJMOC</tt> contains the name of all intermediate moc object files. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

POST_TARGETDEPS

All libraries that the target depends on can be listed in this variable. Some backends do not support this, these include MSVC Dsp, and ProjectBuilder .pbproj files. Generally this is supported internally by these build tools, this is useful for explicitly listing dependant static libraries.

This list will go after all builtin (and $$PRE_TARGETDEPS) dependencies.

PRE_TARGETDEPS

All libraries that the target depends on can be listed in this variable. Some backends do not support this, these include MSVC Dsp, and ProjectBuilder .pbproj files. Generally this is supported internally by these build tools, this is useful for explicitly listing dependant static libraries.

This list will go before all builtin dependencies.

PRECOMPILED_HEADER

This variable indicates the header file for creating a precompiled header file, to increase the compilation speed of a project. Precompiled headers are currently only supported on some platforms (Windows - all MSVC project types, Mac OS X - Xcode, Makefile, Unix - gcc 3.3 and up).

On other platforms, this variable has different meaning, as noted below.

This variable contains a list of header files that require some sort of pre-compilation step (such as with moc). The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE

This variable contains the name of the <tt>qmake</tt> program itself and is placed in generated Makefiles. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKESPEC

This variable contains the name of the <tt>qmake</tt> configuration to use when generating Makefiles. The value of this variable is typically handled by <tt>qmake</tt> and rarely needs to be modified. Use the <tt>QMAKESPEC</tt> environment variable instead.

QMAKE_APP_FLAG

This variable is empty unless the <tt>app</tt> TEMPLATE is specified. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified. Use the following instead:

 app {
     # Conditional code for 'app' template here
 }

QMAKE_APP_OR_DLL

This variable is empty unless the <tt>app</tt> or <tt>dll</tt> TEMPLATE is specified. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_AR_CMD

This is used on Unix platforms only.

This variable contains the command for invoking the program which creates, modifies and extracts archives. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_BUNDLE_DATA

This variable is used to hold the data that will be installed with a library bundle, and is often used to specify a collection of header files.

For example, the following lines add <tt>path/to/header_one.h</tt> and <tt>path/to/header_two.h</tt> to a group containing information about the headers supplied with the framework:

 FRAMEWORK_HEADERS.version = Versions
 FRAMEWORK_HEADERS.files = path/to/header_one.h path/to/header_two.h
 FRAMEWORK_HEADERS.path = Headers
 QMAKE_BUNDLE_DATA += FRAMEWORK_HEADERS

The last line adds the information about the headers to the collection of resources that will be installed with the library bundle.

Library bundles are created when the <tt>lib_bundle</tt> option is added to the CONFIG variable.

See qmake Platform Notes for more information about creating library bundles.

This is used on Mac OS X only.

QMAKE_BUNDLE_EXTENSION

This variable defines the extension to be used for library bundles. This allows frameworks to be created with custom extensions instead of the standard <tt>.framework</tt> directory name extension.

For example, the following definition will result in a framework with the <tt>.myframework</tt> extension:

 QMAKE_BUNDLE_EXTENSION = .myframework

This is used on Mac OS X only.

QMAKE_CC

This variable specifies the C compiler that will be used when building projects containing C source code. Only the file name of the compiler executable needs to be specified as long as it is on a path contained in the <tt>PATH</tt> variable when the Makefile is processed.

QMAKE_CFLAGS_DEBUG

This variable contains the flags for the C compiler in debug mode.The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CFLAGS_MT

This variable contains the compiler flags for creating a multi-threaded application or when the version of Qt that you link against is a multi-threaded statically linked library. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CFLAGS_MT_DBG

This variable contains the compiler flags for creating a debuggable multi-threaded application or when the version of Qt that you link against is a debuggable multi-threaded statically linked library. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CFLAGS_MT_DLL

This is used on Windows only.

This variable contains the compiler flags for creating a multi-threaded dll or when the version of Qt that you link against is a multi-threaded dll. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CFLAGS_MT_DLLDBG

This is used on Windows only.

This variable contains the compiler flags for creating a debuggable multi-threaded dll or when the version of Qt that you link against is a debuggable multi-threaded statically linked library. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CFLAGS_RELEASE

This variable contains the compiler flags for creating a non-debuggable application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CFLAGS_SHLIB

This is used on Unix platforms only.

This variable contains the compiler flags for creating a shared library. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CFLAGS_THREAD

This variable contains the compiler flags for creating a multi-threaded application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CFLAGS_WARN_OFF

This variable is not empty if the warn_off TEMPLATE option is specified. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CFLAGS_WARN_ON

This variable is not empty if the warn_on TEMPLATE option is specified. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CLEAN

This variable contains any files which are not generated files (such as moc and uic generated files) and object files that should be removed when using "make clean".

QMAKE_CXX

This variable specifies the C++ compiler that will be used when building projects containing C++ source code. Only the file name of the compiler executable needs to be specified as long as it is on a path contained in the <tt>PATH</tt> variable when the Makefile is processed.

QMAKE_CXXFLAGS

This variable contains the C++ compiler flags that are used when building a project. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified. The flags specific to debug and release modes can be adjusted by modifying the <tt>QMAKE_CXXFLAGS_DEBUG</tt> and <tt>QMAKE_CXXFLAGS_RELEASE</tt> variables, respectively.

QMAKE_CXXFLAGS_DEBUG

This variable contains the C++ compiler flags for creating a debuggable application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CXXFLAGS_MT

This variable contains the C++ compiler flags for creating a multi-threaded application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CXXFLAGS_MT_DBG

This variable contains the C++ compiler flags for creating a debuggable multi-threaded application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CXXFLAGS_MT_DLL

<tt>This is used on Windows only.</tt>

This variable contains the C++ compiler flags for creating a multi-threaded dll. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CXXFLAGS_MT_DLLDBG

<tt>This is used on Windows only.</tt>

This variable contains the C++ compiler flags for creating a multi-threaded debuggable dll. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CXXFLAGS_RELEASE

This variable contains the C++ compiler flags for creating an application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CXXFLAGS_SHLIB

This variable contains the C++ compiler flags for creating a shared library. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CXXFLAGS_THREAD

This variable contains the C++ compiler flags for creating a multi-threaded application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CXXFLAGS_WARN_OFF

This variable contains the C++ compiler flags for suppressing compiler warnings. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_CXXFLAGS_WARN_ON

This variable contains C++ compiler flags for generating compiler warnings. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_EXTENSION_SHLIB

This variable contains the extention for shared libraries. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

Note that platform-specific variables that change the extension will override the contents of this variable.

QMAKE_EXT_MOC

This variable changes the extention used on included moc files.

See also File Extensions.

QMAKE_EXT_UI

This variable changes the extention used on /e Designer UI files.

See also File Extensions.

QMAKE_EXT_PRL

This variable changes the extention used on created PRL files.

See also File Extensions, Library Dependencies.

QMAKE_EXT_LEX

This variable changes the extention used on files given to lex.

See also File Extensions, LEXSOURCES.

QMAKE_EXT_YACC

This variable changes the extention used on files given to yacc.

See also File Extensions, YACCSOURCES.

QMAKE_EXT_OBJ

This variable changes the extention used on generated object files.

See also File Extensions.

QMAKE_EXT_CPP

This variable changes the interpretation of all suffixes in this list of values as files of type C++ source code.

See also File Extensions.

QMAKE_EXT_H

This variable changes the interpretation of all suffixes in this list of values as files of type C header files.

See also File Extensions.

QMAKE_FAILED_REQUIREMENTS

This variable contains the list of requirements that were failed to be met when <tt>qmake</tt> was used. For example, the sql module is needed and wasn't compiled into Qt. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_FILETAGS

This variable contains the file tags needed to be entered into the Makefile, such as SOURCES and HEADERS. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_FRAMEWORK_BUNDLE_NAME

In a framework project, this variable contains the name to be used for the framework that is built.

By default, this variable contains the same value as the TARGET variable.

See qmake Platform Notes for more information about creating frameworks and library bundles.

This is used on Mac OS X only.

QMAKE_FRAMEWORK_VERSION

For projects where the build target is a Mac OS X framework, this variable is used to specify the version number that will be applied to the framework that is built.

By default, this variable contains the same value as the VERSION variable.

See qmake Platform Notes for more information about creating frameworks.

This is used on Mac OS X only.

QMAKE_INCDIR

This variable contains the location of all known header files to be added to INCLUDEPATH when building an application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_INCDIR_OPENGL

This variable contains the location of OpenGL header files to be added to INCLUDEPATH when building an application with OpenGL support. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_INCDIR_QT

This variable contains the location of all known header file paths to be added to INCLUDEPATH when building a Qt application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_INCDIR_THREAD

This variable contains the location of all known header file paths to be added to INCLUDEPATH when building a multi-threaded application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_INCDIR_X11

This is used on Unix platforms only.

This variable contains the location of X11 header file paths to be added to INCLUDEPATH when building a X11 application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS

This variable contains a general set of flags that are passed to the linker. If you need to change the flags used for a particular platform or type of project, use one of the specialized variables for that purpose instead of this variable.

QMAKE_LFLAGS_CONSOLE

This is used on Windows only.

This variable contains link flags when building console programs. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_CONSOLE_DLL

This is used on Windows only.

This variable contains link flags when building console dlls. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_DEBUG

This variable contains link flags when building debuggable applications. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_PLUGIN

This variable contains link flags when building plugins. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_QT_DLL

This variable contains link flags when building programs that use the Qt library built as a dll. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_RELEASE

This variable contains link flags when building applications for release. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_SHAPP

This variable contains link flags when building applications which are using the <tt>app</tt> template. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_SHLIB

This variable contains link flags when building shared libraries The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_SONAME

This variable specifies the link flags to set the name of shared objects, such as .so or .dll. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_THREAD

This variable contains link flags when building multi-threaded projects. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_WINDOWS

This is used on Windows only.

This variable contains link flags when building Windows GUI projects (i.e. non-console applications). The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LFLAGS_WINDOWS_DLL

This is used on Windows only.

This variable contains link flags when building Windows DLL projects. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBDIR

This variable contains the location of all known library directories.The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBDIR_FLAGS

This is used on Unix platforms only.

This variable contains the location of all library directory with -L prefixed. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBDIR_OPENGL

This variable contains the location of the OpenGL library directory.The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBDIR_QT

This variable contains the location of the Qt library directory.The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBDIR_X11

This is used on Unix platforms only.

This variable contains the location of the X11 library directory.The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS

This variable contains all project libraries. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_CONSOLE

This Windows-specific variable is no longer used.

Prior to Qt 4.2, this variable was used to list the libraries that should be linked against when building a console application project on Windows. QMAKE_LIBS_WINDOW should now be used instead.

QMAKE_LIBS_OPENGL

This variable contains all OpenGL libraries. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_OPENGL_QT

This variable contains all OpenGL Qt libraries.The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_QT

This variable contains all Qt libraries.The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_QT_DLL

This is used on Windows only.

This variable contains all Qt libraries when Qt is built as a dll. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_QT_OPENGL

This variable contains all the libraries needed to link against if OpenGL support is turned on. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_QT_THREAD

This variable contains all the libraries needed to link against if thread support is turned on. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_RT

This is used with Borland compilers only.

This variable contains the runtime library needed to link against when building an application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_RTMT

This is used with Borland compilers only.

This variable contains the runtime library needed to link against when building a multi-threaded application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_THREAD

This is used on Unix platforms only.

This variable contains all libraries that need to be linked against when building a multi-threaded application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_WINDOWS

This is used on Windows only.

This variable contains all windows libraries.The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_X11

This is used on Unix platforms only.

This variable contains all X11 libraries.The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIBS_X11SM

This is used on Unix platforms only.

This variable contains all X11 session management libraries. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LIB_FLAG

This variable is not empty if the <tt>lib</tt> template is specified. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_LINK_SHLIB_CMD

This variable contains the command to execute when creating a shared library. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_POST_LINK

This variable contains the command to execute after linking the TARGET together. This variable is normally empty and therefore nothing is executed, additionally some backends will not support this - mostly only Makefile backends.

QMAKE_PRE_LINK

This variable contains the command to execute before linking the TARGET together. This variable is normally empty and therefore nothing is executed, additionally some backends will not support this - mostly only Makefile backends.

QMAKE_LN_SHLIB

This variable contains the command to execute when creating a link to a shared library. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_MAC_SDK

This variable is used on Mac OS X when building universal binaries. This process is described in more detail in the Deploying an Application on Qt/Mac document.

QMAKE_MAKEFILE

This variable contains the name of the Makefile to create. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_MOC_SRC

This variable contains the names of all moc source files to generate and include in the project. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_QMAKE

This variable contains the location of qmake if it is not in the path. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_QT_DLL

This variable is not empty if Qt was built as a dll. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_RESOURCE_FLAGS

This variable is used to customize the list of options passed to the Resource Compiler in each of the build rules where it is used. For example, the following line ensures that the <tt>-threshold</tt> and <tt>-compress</tt> options are used with particular values each time that <tt>rcc</tt> is invoked:

 QMAKE_RESOURCE_FLAGS += -threshold 0 -compress 9

QMAKE_RUN_CC

This variable specifies the individual rule needed to build an object. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_RUN_CC_IMP

This variable specifies the individual rule needed to build an object. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_RUN_CXX

This variable specifies the individual rule needed to build an object. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_RUN_CXX_IMP

This variable specifies the individual rule needed to build an object. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_TARGET

This variable contains the name of the project target. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

QMAKE_UIC

This variable contains the location of uic if it is not in the path. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

It can be used to specify arguments to uic as well, such as additional plugin paths. For example:

     QMAKE_UIC = uic -L /path/to/plugin

QT

The values stored in the <tt>QT</tt> variable control which of the Qt modules are used by your project.

The table below shows the options that can be used with the <tt>QT</tt> variable and the features that are associated with each of them:

Option	Features

core (included by default)	QtCore module

gui (included by default)	QtGui module

network	QtNetwork module

opengl	QtOpenGL module

sql	QtSql module

svg	QtSvg module

xml	QtXml module

qt3support	Qt3Support module

By default, <tt>QT</tt> contains both <tt>core</tt> and <tt>gui</tt>, ensuring that standard GUI applications can be built without further configuration.

If you want to build a project without the QtGui module, you need to exclude the <tt>gui</tt> value with the "-=" operator; the following line will result in a minimal Qt project being built:

     QT -= gui # Only the core module is used.

Note that adding the <tt>opengl</tt> option to the <tt>QT</tt> variable automatically causes the equivalent option to be added to the <tt>CONFIG</tt> variable. Therefore, for Qt applications, it is not necessary to add the <tt>opengl</tt> option to both <tt>CONFIG</tt> and <tt>QT</tt>.

QTPLUGIN

This variable contains a list of names of static plugins that are to be compiled with an application so that they are available as built-in resources.

RC_FILE

This variable contains the name of the resource file for the application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

RCC_DIR

This variable specifies the directory where all intermediate resource files should be placed.

For example:

     unix:RCC_DIR = ../myproject/resources
     win32:RCC_DIR = c:/myproject/resources

REQUIRES

This is a special variable processed by <tt>qmake</tt>. If the contents of this variable do not appear in CONFIG by the time this variable is assigned, then a minimal Makefile will be generated that states what dependencies (the values assigned to REQUIRES) are missing.

This is mainly used in Qt's build system for building the examples.

RES_FILE

This variable contains the name of the resource file for the application. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

SOURCES

This variable contains the name of all source files in the project.

For example:

     SOURCES = myclass.cpp \
           login.cpp \
           mainwindow.cpp

See also HEADERS

SRCMOC

This variable is set by <tt>qmake</tt> if files can be found that contain the Q_OBJECT macro. <tt>SRCMOC</tt> contains the name of all the generated moc files. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

SUBDIRS

This variable, when used with the <tt>subdirs</tt> template contains the names of all subdirectories that contain parts of the project that need be built. Each subdirectory must contain its own project file.

For example:

     SUBDIRS = kernel \
               tools

It is essential that the project file in each subdirectory has the same name as the subdirectory itself, so that <tt>qmake</tt> can find it. For example, if the subdirectory is called <tt>myapp</tt> then the project file in that directory should be called <tt>myapp.pro</tt>.

If you need to ensure that the subdirectories are built in the order in which they are specified, update the CONFIG variable to include the <tt>ordered</tt> option:

     CONFIG += ordered

TARGET

This specifies the name of the target file.

For example:

     TEMPLATE = app
     TARGET = myapp
     SOURCES = main.cpp

The project file above would produce an executable named <tt>myapp</tt> on unix and 'myapp.exe' on windows.

TARGET_EXT

This variable specifies the target's extension. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

TARGET_x

This variable specifies the target's extension with a major version number. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

TARGET_x.y.z

This variable specifies the target's extension with version number. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

TEMPLATE

This variable contains the name of the template to use when generating the project. The allowed values are:

Option	Description

app	Creates a Makefile for building applications (the default).

lib	Creates a Makefile for building libraries.

subdirs	Creates a Makefile for building targets in subdirectories. The subdirectories are specified using the SUBDIRS variable.

vcapp	Windows only Creates an application project for Visual Studio. (See qmake Platform Notes for more information.)

vclib	Windows only Creates a library project for Visual Studio. (See qmake Platform Notes for more information.)

For example:

     TEMPLATE = lib
     SOURCES = main.cpp
     TARGET = mylib

The template can be overridden by specifying a new template type with the <tt>-t</tt> command line option. This overrides the template type after the .pro file has been processed. With .pro files that use the template type to determine how the project is built, it is necessary to declare TEMPLATE on the command line rather than use the <tt>-t</tt> option.

TRANSLATIONS

This variable contains a list of translation (.ts) files that contain translations of the user interface text into non-native languages.

See the Qt Linguist Manual for more information about internationalization (i18n) and localization (l10n) with Qt.

UICIMPLS

This variable contains a list of the generated implementation files by UIC. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

UICOBJECTS

This variable is generated from the UICIMPLS variable. The extension of each file will have been replaced by .o (Unix) or .obj (Win32). The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

UI_DIR

This variable specifies the directory where all intermediate files from uic should be placed. This variable overrides both UI_SOURCES_DIR and UI_HEADERS_DIR.

For example:

     unix:UI_DIR = ../myproject/ui
     win32:UI_DIR = c:/myproject/ui

UI_HEADERS_DIR

This variable specifies the directory where all declaration files (as generated by uic) should be placed.

For example:

     unix:UI_HEADERS_DIR = ../myproject/ui/include
     win32:UI_HEADERS_DIR = c:/myproject/ui/include

UI_SOURCES_DIR

This variable specifies the directory where all implementation files (as generated by uic) should be placed.

For example:

     unix:UI_SOURCES_DIR = ../myproject/ui/src
     win32:UI_SOURCES_DIR = c:/myproject/ui/src

VERSION

This variable contains the version number of the library if the <tt>lib</tt> TEMPLATE is specified.

For example:

     VERSION = 1.2.3

VER_MAJ

This variable contains the major version number of the library, if the <tt>lib</tt> template is specified.

VER_MIN

This variable contains the minor version number of the library, if the <tt>lib</tt> template is specified.

VER_PAT

This variable contains the patch version number of the library, if the <tt>lib</tt> template is specified.

VPATH

This variable tells <tt>qmake</tt> where to search for files it cannot open. With this you may tell <tt>qmake</tt> where it may look for things like SOURCES, and if it finds an entry in SOURCES that cannot be opened it will look through the entire VPATH list to see if it can find the file on its own.

See also DEPENDPATH.

YACCIMPLS

This variable contains a list of yacc source files. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

YACCOBJECTS

This variable contains a list of yacc object files. The value of this variable is typically handled by <tt>qmake</tt> or qmake.conf and rarely needs to be modified.

YACCSOURCES

This variable contains a list of yacc source files to be included in the project. All dependencies, headers and source files will automatically be included in the project.

For example:

     YACCSOURCES = moc.y

[Previous: qmake Reference]
[Contents]
[Next: qmake Function Reference]

<address>

Copyright © 2008 Trolltech
Trademarks

Qt 4.3.5

</address>


text:
// Public API for compiler
export {COMPILER_OPTIONS, Compiler, CompilerFactory, CompilerOptions, ModuleWithComponentFactories} from './linker/compiler';
export {ComponentFactory, ComponentRef} from './linker/component_factory';
export {ComponentFactoryResolver} from './linker/component_factory_resolver';
export {ElementRef} from './linker/element_ref';
export {NgModuleFactory, NgModuleRef} from './linker/ng_module_factory';
export {NgModuleFactoryLoader, getModuleFactory} from './linker/ng_module_factory_loader';
export {QueryList} from './linker/query_list';
export {SystemJsNgModuleLoader, SystemJsNgModuleLoaderConfig} from './linker/system_js_ng_module_factory_loader';
export {TemplateRef} from './linker/template_ref';
export {ViewContainerRef} from './linker/view_container_ref';
export {EmbeddedViewRef, ViewRef} from './linker/view_ref';