qmake-variable-reference.html 110 KB
Newer Older
xuebingbing's avatar
xuebingbing committed
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>
<html lang="en">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- qmake-manual.qdoc -->
  <title>Variables | qmake Manual</title>
  <link rel="stylesheet" type="text/css" href="style/offline-simple.css" />
  <script type="text/javascript">
    document.getElementsByTagName("link").item(0).setAttribute("href", "style/offline.css");
    // loading style sheet breaks anchors that were jumped to before
    // so force jumping to anchor again
    setTimeout(function() {
        var anchor = location.hash;
        // need to jump to different anchor first (e.g. none)
        location.hash = "#";
        setTimeout(function() {
            location.hash = anchor;
        }, 0);
    }, 0);
  </script>
</head>
<body>
<div class="header" id="qtdocheader">
  <div class="main">
    <div class="main-rounded">
      <div class="navigationbar">
        <table><tr>
<td ><a href="../qtdoc/index.html">Qt 5.11</a></td><td ><a href="qmake-manual.html">qmake Manual</a></td><td >Variables</td></tr></table><table class="buildversion"><tr>
<td id="buildversion" width="100%" align="right">Qt 5.11.2 Reference Documentation</td>
        </tr></table>
      </div>
    </div>
<div class="content">
<div class="line">
<div class="content mainContent">
  <link rel="prev" href="qmake-reference.html" />
  <link rel="next" href="qmake-function-reference.html" />
<p class="naviNextPrevious headerNavi">
<a class="prevPage" href="qmake-reference.html">Reference</a>
<span class="naviSeparator">  &#9702;  </span>
<a class="nextPage" href="qmake-function-reference.html">Replace Functions</a>
</p><p/>
<div class="sidebar">
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#config">CONFIG</a></li>
<li class="level1"><a href="#defines">DEFINES</a></li>
<li class="level1"><a href="#def-file">DEF_FILE</a></li>
<li class="level1"><a href="#dependpath">DEPENDPATH</a></li>
<li class="level1"><a href="#destdir">DESTDIR</a></li>
<li class="level1"><a href="#distfiles">DISTFILES</a></li>
<li class="level1"><a href="#dlldestdir">DLLDESTDIR</a></li>
<li class="level1"><a href="#forms">FORMS</a></li>
<li class="level1"><a href="#guid">GUID</a></li>
<li class="level1"><a href="#headers">HEADERS</a></li>
<li class="level1"><a href="#icon">ICON</a></li>
<li class="level1"><a href="#idlsources">IDLSOURCES</a></li>
<li class="level1"><a href="#includepath">INCLUDEPATH</a></li>
<li class="level1"><a href="#installs">INSTALLS</a></li>
<li class="level1"><a href="#leximpls">LEXIMPLS</a></li>
<li class="level1"><a href="#lexobjects">LEXOBJECTS</a></li>
<li class="level1"><a href="#lexsources">LEXSOURCES</a></li>
<li class="level1"><a href="#libs">LIBS</a></li>
<li class="level1"><a href="#literal-hash">LITERAL_HASH</a></li>
<li class="level1"><a href="#makefile">MAKEFILE</a></li>
<li class="level1"><a href="#makefile-generator">MAKEFILE_GENERATOR</a></li>
<li class="level1"><a href="#msvcproj">MSVCPROJ_*</a></li>
<li class="level1"><a href="#moc-dir">MOC_DIR</a></li>
<li class="level1"><a href="#objective-headers">OBJECTIVE_HEADERS</a></li>
<li class="level1"><a href="#objective-sources">OBJECTIVE_SOURCES</a></li>
<li class="level1"><a href="#objects">OBJECTS</a></li>
<li class="level1"><a href="#objects-dir">OBJECTS_DIR</a></li>
<li class="level1"><a href="#post-targetdeps">POST_TARGETDEPS</a></li>
<li class="level1"><a href="#pre-targetdeps">PRE_TARGETDEPS</a></li>
<li class="level1"><a href="#precompiled-header">PRECOMPILED_HEADER</a></li>
<li class="level1"><a href="#pwd">PWD</a></li>
<li class="level1"><a href="#out-pwd">OUT_PWD</a></li>
<li class="level1"><a href="#qmake">QMAKE</a></li>
<li class="level1"><a href="#qmakespec">QMAKESPEC</a></li>
<li class="level1"><a href="#qmake-ar-cmd">QMAKE_AR_CMD</a></li>
<li class="level1"><a href="#qmake-bundle-data">QMAKE_BUNDLE_DATA</a></li>
<li class="level1"><a href="#qmake-bundle-extension">QMAKE_BUNDLE_EXTENSION</a></li>
<li class="level1"><a href="#qmake-cc">QMAKE_CC</a></li>
<li class="level1"><a href="#qmake-cflags">QMAKE_CFLAGS</a></li>
<li class="level1"><a href="#qmake-cflags-debug">QMAKE_CFLAGS_DEBUG</a></li>
<li class="level1"><a href="#qmake-cflags-release">QMAKE_CFLAGS_RELEASE</a></li>
<li class="level1"><a href="#qmake-cflags-shlib">QMAKE_CFLAGS_SHLIB</a></li>
<li class="level1"><a href="#qmake-cflags-thread">QMAKE_CFLAGS_THREAD</a></li>
<li class="level1"><a href="#qmake-cflags-warn-off">QMAKE_CFLAGS_WARN_OFF</a></li>
<li class="level1"><a href="#qmake-cflags-warn-on">QMAKE_CFLAGS_WARN_ON</a></li>
<li class="level1"><a href="#qmake-clean">QMAKE_CLEAN</a></li>
<li class="level1"><a href="#qmake-cxx">QMAKE_CXX</a></li>
<li class="level1"><a href="#qmake-cxxflags">QMAKE_CXXFLAGS</a></li>
<li class="level1"><a href="#qmake-cxxflags-debug">QMAKE_CXXFLAGS_DEBUG</a></li>
<li class="level1"><a href="#qmake-cxxflags-release">QMAKE_CXXFLAGS_RELEASE</a></li>
<li class="level1"><a href="#qmake-cxxflags-shlib">QMAKE_CXXFLAGS_SHLIB</a></li>
<li class="level1"><a href="#qmake-cxxflags-thread">QMAKE_CXXFLAGS_THREAD</a></li>
<li class="level1"><a href="#qmake-cxxflags-warn-off">QMAKE_CXXFLAGS_WARN_OFF</a></li>
<li class="level1"><a href="#qmake-cxxflags-warn-on">QMAKE_CXXFLAGS_WARN_ON</a></li>
<li class="level1"><a href="#qmake-development-team">QMAKE_DEVELOPMENT_TEAM</a></li>
<li class="level1"><a href="#qmake-distclean">QMAKE_DISTCLEAN</a></li>
<li class="level1"><a href="#qmake-extension-shlib">QMAKE_EXTENSION_SHLIB</a></li>
<li class="level1"><a href="#qmake-extension-staticlib">QMAKE_EXTENSION_STATICLIB</a></li>
<li class="level1"><a href="#qmake-ext-moc">QMAKE_EXT_MOC</a></li>
<li class="level1"><a href="#qmake-ext-ui">QMAKE_EXT_UI</a></li>
<li class="level1"><a href="#qmake-ext-prl">QMAKE_EXT_PRL</a></li>
<li class="level1"><a href="#qmake-ext-lex">QMAKE_EXT_LEX</a></li>
<li class="level1"><a href="#qmake-ext-yacc">QMAKE_EXT_YACC</a></li>
<li class="level1"><a href="#qmake-ext-obj">QMAKE_EXT_OBJ</a></li>
<li class="level1"><a href="#qmake-ext-cpp">QMAKE_EXT_CPP</a></li>
<li class="level1"><a href="#qmake-ext-h">QMAKE_EXT_H</a></li>
<li class="level1"><a href="#qmake-extra-compilers">QMAKE_EXTRA_COMPILERS</a></li>
<li class="level1"><a href="#qmake-extra-targets">QMAKE_EXTRA_TARGETS</a></li>
<li class="level1"><a href="#qmake-failed-requirements">QMAKE_FAILED_REQUIREMENTS</a></li>
<li class="level1"><a href="#qmake-framework-bundle-name">QMAKE_FRAMEWORK_BUNDLE_NAME</a></li>
<li class="level1"><a href="#qmake-framework-version">QMAKE_FRAMEWORK_VERSION</a></li>
<li class="level1"><a href="#qmake-host">QMAKE_HOST</a></li>
<li class="level1"><a href="#qmake-incdir">QMAKE_INCDIR</a></li>
<li class="level1"><a href="#qmake-incdir-egl">QMAKE_INCDIR_EGL</a></li>
<li class="level1"><a href="#qmake-incdir-opengl">QMAKE_INCDIR_OPENGL</a></li>
<li class="level1"><a href="#qmake-incdir-opengl-es2">QMAKE_INCDIR_OPENGL_ES2</a></li>
<li class="level1"><a href="#qmake-incdir-openvg">QMAKE_INCDIR_OPENVG</a></li>
<li class="level1"><a href="#qmake-incdir-x11">QMAKE_INCDIR_X11</a></li>
<li class="level1"><a href="#qmake-info-plist">QMAKE_INFO_PLIST</a></li>
<li class="level1"><a href="#qmake-ios-deployment-target">QMAKE_IOS_DEPLOYMENT_TARGET</a></li>
<li class="level1"><a href="#qmake-lflags">QMAKE_LFLAGS</a></li>
<li class="level1"><a href="#qmake-lflags-console">QMAKE_LFLAGS_CONSOLE</a></li>
<li class="level1"><a href="#qmake-lflags-debug">QMAKE_LFLAGS_DEBUG</a></li>
<li class="level1"><a href="#qmake-lflags-plugin">QMAKE_LFLAGS_PLUGIN</a></li>
<li class="level1"><a href="#qmake-lflags-rpath">QMAKE_LFLAGS_RPATH</a></li>
<li class="level1"><a href="#qmake-lflags-rel-rpath">QMAKE_LFLAGS_REL_RPATH</a></li>
<li class="level1"><a href="#qmake-rel-rpath-base">QMAKE_REL_RPATH_BASE</a></li>
<li class="level1"><a href="#qmake-lflags-rpathlink">QMAKE_LFLAGS_RPATHLINK</a></li>
<li class="level1"><a href="#qmake-lflags-release">QMAKE_LFLAGS_RELEASE</a></li>
<li class="level1"><a href="#qmake-lflags-app">QMAKE_LFLAGS_APP</a></li>
<li class="level1"><a href="#qmake-lflags-shlib">QMAKE_LFLAGS_SHLIB</a></li>
<li class="level1"><a href="#qmake-lflags-soname">QMAKE_LFLAGS_SONAME</a></li>
<li class="level1"><a href="#qmake-lflags-thread">QMAKE_LFLAGS_THREAD</a></li>
<li class="level1"><a href="#qmake-lflags-windows">QMAKE_LFLAGS_WINDOWS</a></li>
<li class="level1"><a href="#qmake-libdir">QMAKE_LIBDIR</a></li>
<li class="level1"><a href="#qmake-libdir-flags">QMAKE_LIBDIR_FLAGS</a></li>
<li class="level1"><a href="#qmake-libdir-egl">QMAKE_LIBDIR_EGL</a></li>
<li class="level1"><a href="#qmake-libdir-opengl">QMAKE_LIBDIR_OPENGL</a></li>
<li class="level1"><a href="#qmake-libdir-openvg">QMAKE_LIBDIR_OPENVG</a></li>
<li class="level1"><a href="#qmake-libdir-x11">QMAKE_LIBDIR_X11</a></li>
<li class="level1"><a href="#qmake-libs">QMAKE_LIBS</a></li>
<li class="level1"><a href="#qmake-libs-egl">QMAKE_LIBS_EGL</a></li>
<li class="level1"><a href="#qmake-libs-opengl">QMAKE_LIBS_OPENGL</a></li>
<li class="level1"><a href="#qmake-libs-opengl-es1-qmake-libs-opengl-es2">QMAKE_LIBS_OPENGL_ES1, QMAKE_LIBS_OPENGL_ES2</a></li>
<li class="level1"><a href="#qmake-libs-openvg">QMAKE_LIBS_OPENVG</a></li>
<li class="level1"><a href="#qmake-libs-thread">QMAKE_LIBS_THREAD</a></li>
<li class="level1"><a href="#qmake-libs-x11">QMAKE_LIBS_X11</a></li>
<li class="level1"><a href="#qmake-lib-flag">QMAKE_LIB_FLAG</a></li>
<li class="level1"><a href="#qmake-link">QMAKE_LINK</a></li>
<li class="level1"><a href="#qmake-link-shlib-cmd">QMAKE_LINK_SHLIB_CMD</a></li>
<li class="level1"><a href="#qmake-ln-shlib">QMAKE_LN_SHLIB</a></li>
<li class="level1"><a href="#qmake-objective-cflags">QMAKE_OBJECTIVE_CFLAGS</a></li>
<li class="level1"><a href="#qmake-post-link">QMAKE_POST_LINK</a></li>
<li class="level1"><a href="#qmake-pre-link">QMAKE_PRE_LINK</a></li>
<li class="level1"><a href="#qmake-project-name">QMAKE_PROJECT_NAME</a></li>
<li class="level1"><a href="#qmake-provisioning-profile">QMAKE_PROVISIONING_PROFILE</a></li>
<li class="level1"><a href="#qmake-mac-sdk">QMAKE_MAC_SDK</a></li>
<li class="level1"><a href="#qmake-macosx-deployment-target">QMAKE_MACOSX_DEPLOYMENT_TARGET</a></li>
<li class="level1"><a href="#qmake-makefile">QMAKE_MAKEFILE</a></li>
<li class="level1"><a href="#qmake-qmake">QMAKE_QMAKE</a></li>
<li class="level1"><a href="#qmake-resource-flags">QMAKE_RESOURCE_FLAGS</a></li>
<li class="level1"><a href="#qmake-rpathdir">QMAKE_RPATHDIR</a></li>
<li class="level1"><a href="#qmake-rpathlinkdir">QMAKE_RPATHLINKDIR</a></li>
<li class="level1"><a href="#qmake-run-cc">QMAKE_RUN_CC</a></li>
<li class="level1"><a href="#qmake-run-cc-imp">QMAKE_RUN_CC_IMP</a></li>
<li class="level1"><a href="#qmake-run-cxx">QMAKE_RUN_CXX</a></li>
<li class="level1"><a href="#qmake-run-cxx-imp">QMAKE_RUN_CXX_IMP</a></li>
<li class="level1"><a href="#qmake-soname-prefix">QMAKE_SONAME_PREFIX</a></li>
<li class="level1"><a href="#qmake-target">QMAKE_TARGET</a></li>
<li class="level1"><a href="#qmake-target-company">QMAKE_TARGET_COMPANY</a></li>
<li class="level1"><a href="#qmake-target-description">QMAKE_TARGET_DESCRIPTION</a></li>
<li class="level1"><a href="#qmake-target-copyright">QMAKE_TARGET_COPYRIGHT</a></li>
<li class="level1"><a href="#qmake-target-product">QMAKE_TARGET_PRODUCT</a></li>
<li class="level1"><a href="#qmake-tvos-deployment-target">QMAKE_TVOS_DEPLOYMENT_TARGET</a></li>
<li class="level1"><a href="#qmake-uic-flags">QMAKE_UIC_FLAGS</a></li>
<li class="level1"><a href="#qmake-watchos-deployment-target">QMAKE_WATCHOS_DEPLOYMENT_TARGET</a></li>
<li class="level1"><a href="#qt">QT</a></li>
<li class="level1"><a href="#qtplugin">QTPLUGIN</a></li>
<li class="level1"><a href="#qt-version">QT_VERSION</a></li>
<li class="level1"><a href="#qt-major-version">QT_MAJOR_VERSION</a></li>
<li class="level1"><a href="#qt-minor-version">QT_MINOR_VERSION</a></li>
<li class="level1"><a href="#qt-patch-version">QT_PATCH_VERSION</a></li>
<li class="level1"><a href="#rc-file">RC_FILE</a></li>
<li class="level1"><a href="#rc-codepage">RC_CODEPAGE</a></li>
<li class="level1"><a href="#rc-defines">RC_DEFINES</a></li>
<li class="level1"><a href="#rc-icons">RC_ICONS</a></li>
<li class="level1"><a href="#rc-lang">RC_LANG</a></li>
<li class="level1"><a href="#rc-includepath">RC_INCLUDEPATH</a></li>
<li class="level1"><a href="#rcc-dir">RCC_DIR</a></li>
<li class="level1"><a href="#requires">REQUIRES</a></li>
<li class="level1"><a href="#resources">RESOURCES</a></li>
<li class="level1"><a href="#res-file">RES_FILE</a></li>
<li class="level1"><a href="#sources">SOURCES</a></li>
<li class="level1"><a href="#subdirs">SUBDIRS</a></li>
<li class="level1"><a href="#target">TARGET</a></li>
<li class="level1"><a href="#target-ext">TARGET_EXT</a></li>
<li class="level1"><a href="#target-x">TARGET_x</a></li>
<li class="level1"><a href="#target-x-y-z">TARGET_x.y.z</a></li>
<li class="level1"><a href="#template">TEMPLATE</a></li>
<li class="level1"><a href="#translations">TRANSLATIONS</a></li>
<li class="level1"><a href="#ui-dir">UI_DIR</a></li>
<li class="level1"><a href="#version">VERSION</a></li>
<li class="level1"><a href="#version-pe-header">VERSION_PE_HEADER</a></li>
<li class="level1"><a href="#ver-maj">VER_MAJ</a></li>
<li class="level1"><a href="#ver-min">VER_MIN</a></li>
<li class="level1"><a href="#ver-pat">VER_PAT</a></li>
<li class="level1"><a href="#vpath">VPATH</a></li>
<li class="level1"><a href="#winrt-manifest">WINRT_MANIFEST</a></li>
<li class="level1"><a href="#yaccsources">YACCSOURCES</a></li>
<li class="level1"><a href="#pro-file">_PRO_FILE_</a></li>
<li class="level1"><a href="#pro-file-pwd">_PRO_FILE_PWD_</a></li>
</ul>
</div>
<div class="sidebar-content" id="sidebar-content"></div></div>
<h1 class="title">Variables</h1>
<span class="subtitle"></span>
<!-- $$$qmake-variable-reference.html-description -->
<div class="descr"> <a name="details"></a>
<p>The fundamental behavior of qmake 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.</p>
<p>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, <code>QMAKE_LIBS</code> can be used to specify a list of libraries that a project needs to link against, and <code>QMAKE_LIBS_X11</code> can be used to extend or override this list.</p>
<a name="config"></a><a name="config"></a>
<h2 id="config">CONFIG</h2>
<p>Specifies project configuration and compiler options. The values are recognized internally by qmake and have special meaning.</p>
<p>The following <code>CONFIG</code> values control compilation flags:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >release</td><td >The project is to be built in release mode. If <code>debug</code> is also specified, the last one takes effect.</td></tr>
<tr valign="top" class="even"><td >debug</td><td >The project is to be built in debug mode.</td></tr>
<tr valign="top" class="odd"><td >debug_and_release</td><td >The project is prepared to be built in <i>both</i> debug and release modes.</td></tr>
<tr valign="top" class="even"><td >debug_and_release_target</td><td >This option is set by default. If <code>debug_and_release</code> is also set, the debug and release builds end up in separate debug and release directories.</td></tr>
<tr valign="top" class="odd"><td >build_all</td><td >If <code>debug_and_release</code> is specified, the project is built in both debug and release modes by default.</td></tr>
<tr valign="top" class="even"><td >autogen_precompile_source</td><td >Automatically generates a <code>.cpp</code> file that includes the precompiled header file specified in the .pro file.</td></tr>
<tr valign="top" class="odd"><td >ordered</td><td >When using the <code>subdirs</code> template, this option specifies that the directories listed should be processed in the order in which they are given.</td></tr>
<tr valign="top" class="even"><td >precompile_header</td><td >Enables support for the use of <a href="qmake-precompiledheaders.html">precompiled headers</a> in projects.</td></tr>
<tr valign="top" class="odd"><td >precompile_header_c (MSVC only)</td><td >Enables support for the use of <a href="qmake-precompiledheaders.html">precompiled headers</a> for C files.</td></tr>
<tr valign="top" class="even"><td >warn_on</td><td >The compiler should output as many warnings as possible. If <code>warn_off</code> is also specified, the last one takes effect.</td></tr>
<tr valign="top" class="odd"><td >warn_off</td><td >The compiler should output as few warnings as possible.</td></tr>
<tr valign="top" class="even"><td >exceptions</td><td >Exception support is enabled. Set by default.</td></tr>
<tr valign="top" class="odd"><td >exceptions_off</td><td >Exception support is disabled.</td></tr>
<tr valign="top" class="even"><td >rtti</td><td >RTTI support is enabled. By default, the compiler default is used.</td></tr>
<tr valign="top" class="odd"><td >rtti_off</td><td >RTTI support is disabled. By default, the compiler default is used.</td></tr>
<tr valign="top" class="even"><td >stl</td><td >STL support is enabled. By default, the compiler default is used.</td></tr>
<tr valign="top" class="odd"><td >stl_off</td><td >STL support is disabled. By default, the compiler default is used.</td></tr>
<tr valign="top" class="even"><td >thread</td><td >Thread support is enabled. This is enabled when CONFIG includes <code>qt</code>, which is the default.</td></tr>
<tr valign="top" class="odd"><td >c++11</td><td >C++11 support is enabled. This option has no effect if the compiler does not support C++11. By default, support is disabled.</td></tr>
<tr valign="top" class="even"><td >c++14</td><td >C++14 support is enabled. This option has no effect if the compiler does not support C++14. By default, support is disabled.</td></tr>
<tr valign="top" class="odd"><td >depend_includepath</td><td >Appending the value of INCLUDEPATH to DEPENDPATH is enabled. Set by default.</td></tr>
</table></div>
<p>When you use the <code>debug_and_release</code> option (which is the default under Windows), the project will be processed three times: one time to produce a &quot;meta&quot; Makefile, and two more times to produce a Makefile.Debug and a Makefile.Release.</p>
<p>During the latter passes, <code>build_pass</code> and the respective <code>debug</code> or <code>release</code> option is appended to <code>CONFIG</code>. This makes it possible to perform build-specific tasks. For example:</p>
<pre class="cpp">

  build_pass:CONFIG(debug, debug|release) {
      unix: TARGET = $$join(TARGET,,,_debug)
      else: TARGET = $$join(TARGET,,,d)
  }

</pre>
<p>As an alternative to manually writing build type conditionals, some variables offer build-specific variants, for example <a href="qmake-variable-reference.html#qmake-lflags-release">QMAKE_LFLAGS_RELEASE</a> in addition to the general <a href="qmake-variable-reference.html#qmake-lflags">QMAKE_LFLAGS</a>. These should be used when available.</p>
<p>The meta Makefile makes the sub-builds invokable via the <code>debug</code> and <code>release</code> targets, and a combined build via the <code>all</code> target. When the <code>build_all</code> <code>CONFIG</code> option is used, the combined build is the default. Otherwise, the last specified <code>CONFIG</code> option from the set (<code>debug</code>, <code>release</code>) determines the default. In this case, you can explicitly invoke the <code>all</code> target to build both configurations at once:</p>
<pre class="cpp">

  make all

</pre>
<p><b>Note: </b>The details are slightly different when producing Visual Studio and Xcode projects.</p><p>When linking a library, qmake relies on the underlying platform to know what other libraries this library links against. However, if linking statically, qmake will not get this information unless we use the following <code>CONFIG</code> options:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >create_prl</td><td >This option enables qmake to track these dependencies. When this option is enabled, qmake will create a file with the extension <code>.prl</code> which will save meta-information about the library (see <a href="qmake-advanced-usage.html#libdepend">Library Dependencies</a> for more info).</td></tr>
<tr valign="top" class="even"><td >link_prl</td><td >When this option is enabled, qmake will process all libraries linked to by the application and find their meta-information (see <a href="qmake-advanced-usage.html#libdepend">Library Dependencies</a> for more info).</td></tr>
</table></div>
<p><b>Note: </b>The <code>create_prl</code> option is required when <i>building</i> a static library, while <code>link_prl</code> is required when <i>using</i> a static library.</p><p>The following options define the application or library type:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >qt</td><td >The target is a Qt application or 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 <code>\l{#qt}{QT}</code> variable.</td></tr>
<tr valign="top" class="even"><td >x11</td><td >The target is an X11 application or library. The proper include paths and libraries will automatically be added to the project.</td></tr>
<tr valign="top" class="odd"><td >testcase</td><td >The target is an automated test. <a href="qmake-common-projects.html#building-a-testcase">A check target</a> will be added to the generated Makefile to run the test. Only relevant when generating Makefiles.</td></tr>
<tr valign="top" class="even"><td >insignificant_test</td><td >The exit code of the automated test will be ignored. Only relevant if <code>testcase</code> is also set.</td></tr>
<tr valign="top" class="odd"><td >windows</td><td >The target is a Win32 window application (app only). The proper include paths, compiler flags and libraries will automatically be added to the project.</td></tr>
<tr valign="top" class="even"><td >console</td><td >The target is a Win32 console application (app only). The proper include paths, compiler flags and libraries will automatically be added to the project.</td></tr>
<tr valign="top" class="odd"><td >shared</td><td  rowspan="2">The target is a shared object/DLL. The proper include paths, compiler flags and libraries will automatically be added to the project. Note that <code>dll</code> can also be used on all platforms; a shared library file with the appropriate suffix for the target platform (.dll or .so) will be created.</td></tr>
<tr valign="top" class="even"><td >dll</td></tr>
<tr valign="top" class="odd"><td >static</td><td  rowspan="2">The target is a static library (lib only). The proper compiler flags will automatically be added to the project.</td></tr>
<tr valign="top" class="even"><td >staticlib</td></tr>
<tr valign="top" class="odd"><td >plugin</td><td >The target is a plugin (lib only). This enables dll as well.</td></tr>
<tr valign="top" class="even"><td >designer</td><td >The target is a plugin for <i>Qt Designer</i>.</td></tr>
<tr valign="top" class="odd"><td >no_lflags_merge</td><td >Ensures that the list of libraries stored in the <code>LIBS</code> variable is not reduced to a list of unique values before it is used.</td></tr>
</table></div>
<p>These options define specific features on Windows only:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >flat</td><td >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.</td></tr>
<tr valign="top" class="even"><td >embed_manifest_dll</td><td >Embeds a manifest file in the DLL created as part of a library project.</td></tr>
<tr valign="top" class="odd"><td >embed_manifest_exe</td><td >Embeds a manifest file in the EXE created as part of an application project.</td></tr>
</table></div>
<p>See <a href="qmake-platform-notes.html#visual-studio-manifest-files">Platform Notes</a> for more information about the options for embedding manifest files.</p>
<p>The following options take an effect only on <a href="../qtdoc/internationalization.html#macos">macOS</a>:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >app_bundle</td><td >Puts the executable into a bundle (this is the default).</td></tr>
<tr valign="top" class="even"><td >lib_bundle</td><td >Puts the library into a library bundle.</td></tr>
</table></div>
<p>The build process for bundles is also influenced by the contents of the <a href="qmake-variable-reference.html#qmake-bundle-data">QMAKE_BUNDLE_DATA</a> variable.</p>
<p>The following options take an effect only on Linux/Unix platforms:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >largefile</td><td >Includes support for large files.</td></tr>
<tr valign="top" class="even"><td >separate_debug_info</td><td >Puts debugging information for libraries in separate files.</td></tr>
</table></div>
<p>The <code>CONFIG</code> variable will also be checked when resolving scopes. You may assign anything to this variable.</p>
<p>For example:</p>
<pre class="cpp">

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

</pre>
<a name="defines"></a><a name="defines"></a>
<h2 id="defines">DEFINES</h2>
<p>qmake adds the values of this variable as compiler C preprocessor macros (-D option).</p>
<p>For example:</p>
<pre class="cpp">

  DEFINES += USE_MY_STUFF

</pre>
<a name="def-file"></a><a name="def-file"></a>
<h2 id="def-file">DEF_FILE</h2>
<p><b>Note: </b>This variable is used only on Windows when using the <code>app</code> template.</p><p>Specifies a <code>.def</code> file to be included in the project.</p>
<a name="dependpath"></a><a name="dependpath"></a>
<h2 id="dependpath">DEPENDPATH</h2>
<p>Specifies a list of all directories to look in to resolve dependencies. This variable is used when crawling through <code>included</code> files.</p>
<a name="destdir"></a><a name="destdir"></a>
<h2 id="destdir">DESTDIR</h2>
<p>Specifies where to put the <a href="qmake-variable-reference.html#target">target</a> file.</p>
<p>For example:</p>
<pre class="cpp">

  DESTDIR = ../../lib

</pre>
<a name="distfiles"></a><a name="distfiles"></a>
<h2 id="distfiles">DISTFILES</h2>
<p>Specifies a list of files to be included in the dist target. This feature is supported by UnixMake specs only.</p>
<p>For example:</p>
<pre class="cpp">

  DISTFILES += ../program.txt

</pre>
<a name="dlldestdir"></a><a name="dlldestdir"></a>
<h2 id="dlldestdir">DLLDESTDIR</h2>
<p><b>Note: </b>This variable applies only to Windows targets.</p><p>Specifies where to copy the <a href="qmake-variable-reference.html#target">target</a> dll.</p>
<a name="forms"></a><a name="forms"></a>
<h2 id="forms">FORMS</h2>
<p>Specifies the UI files (see <a href="../qtdesigner/qtdesigner-manual.html">Qt Designer Manual</a>) to be processed by <code>uic</code> before compiling. All dependencies, headers and source files required to build these UI files will automatically be added to the project.</p>
<p>For example:</p>
<pre class="cpp">

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

</pre>
<a name="guid"></a><a name="guid"></a>
<h2 id="guid">GUID</h2>
<p>Specifies the GUID that is set inside a <code>.vcproj</code> file. The GUID is usually randomly determined. However, should you require a fixed GUID, it can be set using this variable.</p>
<p>This variable is specific to <code>.vcproj</code> files only; it is ignored otherwise.</p>
<a name="headers"></a><a name="headers"></a>
<h2 id="headers">HEADERS</h2>
<p>Defines the header files for the project.</p>
<p>qmake automatically detects whether <a href="../qtdoc/moc.html">moc</a> is required by the classes in the headers, and adds the appropriate dependencies and files to the project for generating and linking the moc files.</p>
<p>For example:</p>
<pre class="cpp">

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

</pre>
<p>See also <a href="qmake-variable-reference.html#sources">SOURCES</a>.</p>
<a name="icon"></a><a name="icon"></a>
<h2 id="icon">ICON</h2>
<p>This variable is used only on Mac OS to set the application icon. Please see <a href="../qtdoc/appicon.html">the application icon documentation</a> for more information.</p>
<a name="idlsources"></a><a name="idlsources"></a>
<h2 id="idlsources">IDLSOURCES</h2>
<p>This variable is used only on Windows for the Visual Studio project generation to put the specified files in the Generated Files folder.</p>
<a name="includepath"></a><a name="includepath"></a>
<h2 id="includepath">INCLUDEPATH</h2>
<p>Specifies the #include directories which should be searched when compiling the project.</p>
<p>For example:</p>
<pre class="cpp">

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

</pre>
<p>To specify a path containing spaces, quote the path using the technique described in <a href="qmake-project-files.html#whitespace">Whitespace</a>.</p>
<pre class="cpp">

  win32:INCLUDEPATH += &quot;C:/mylibs/extra headers&quot;
  unix:INCLUDEPATH += &quot;/home/user/extra headers&quot;

</pre>
<a name="installs"></a><a name="installs"></a>
<h2 id="installs">INSTALLS</h2>
<p>Specifies a list of resources that will be installed when <code>make install</code> 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.</p>
<p>For example, the following <code>target.path</code> definition describes where the build target will be installed, and the <code>INSTALLS</code> assignment adds the build target to the list of existing resources to be installed:</p>
<pre class="cpp">

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

</pre>
<p>For more information, see <a href="qmake-advanced-usage.html#installing-files">Installing Files</a>.</p>
<p>This variable is also used to specify which additional files will be deployed to embedded devices.</p>
<a name="leximpls"></a><a name="leximpls"></a>
<h2 id="leximpls">LEXIMPLS</h2>
<p>Specifies a list of Lex implementation files. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="lexobjects"></a><a name="lexobjects"></a>
<h2 id="lexobjects">LEXOBJECTS</h2>
<p>Specifies the names of intermediate Lex object files. The value of this variable is typically handled by qmake and rarely needs to be modified.</p>
<a name="lexsources"></a><a name="lexsources"></a>
<h2 id="lexsources">LEXSOURCES</h2>
<p>Specifies a list of Lex source files. All dependencies, headers and source files will automatically be added to the project for building these lex files.</p>
<p>For example:</p>
<pre class="cpp">

  LEXSOURCES = lexer.l

</pre>
<a name="libs"></a><a name="libs"></a>
<h2 id="libs">LIBS</h2>
<p>Specifies a list of libraries to be linked into the project. If you use the Unix <code>-l</code> (library) and -L (library path) flags, qmake handles the libraries correctly on Windows (that is, passes the full path of the library to the linker). The library must exist for qmake to find the directory where a <code>-l</code> lib is located.</p>
<p>For example:</p>
<pre class="cpp">

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

</pre>
<p>To specify a path containing spaces, quote the path using the technique described in <a href="qmake-project-files.html#whitespace">Whitespace</a>.</p>
<pre class="cpp">

  win32:LIBS += &quot;C:/mylibs/extra libs/extra.lib&quot;
  unix:LIBS += &quot;-L/home/user/extra libs&quot; -lextra

</pre>
<p>By default, the list of libraries stored in <code>LIBS</code> is reduced to a list of unique names before it is used. To change this behavior, add the <code>no_lflags_merge</code> option to the <a href="qmake-variable-reference.html#config">CONFIG</a> variable:</p>
<pre class="cpp">

  CONFIG += no_lflags_merge

</pre>
<a name="literal-hash"></a><a name="literal-hash"></a>
<h2 id="literal-hash">LITERAL_HASH</h2>
<p>This variable is used whenever a literal hash character (<code>#</code>) is needed in a variable declaration, perhaps as part of a file name or in a string passed to some external application.</p>
<p>For example:</p>
<pre class="cpp">

  # To include a literal hash character, use the $$LITERAL_HASH variable:
  urlPieces = http://doc.qt.io/qt-5/qtextdocument.html pageCount
  message($$join(urlPieces, $$LITERAL_HASH))

</pre>
<p>By using <code>LITERAL_HASH</code> in this way, the <code>#</code> character can be used to construct a URL for the <code>message()</code> function to print to the console.</p>
<a name="makefile"></a><a name="makefile"></a>
<h2 id="makefile">MAKEFILE</h2>
<p>Specifies the name of the generated Makefile. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="makefile-generator"></a><a name="makefile-generator"></a>
<h2 id="makefile-generator">MAKEFILE_GENERATOR</h2>
<p>Specifies the name of the Makefile generator to use when generating a Makefile. The value of this variable is typically handled internally by qmake and rarely needs to be modified.</p>
<a name="msvcproj"></a><a name="msvcproj"></a>
<h2 id="msvcproj">MSVCPROJ_*</h2>
<p>These variables are handled internally by qmake and should not be modified or utilized.</p>
<a name="moc-dir"></a><a name="moc-dir"></a>
<h2 id="moc-dir">MOC_DIR</h2>
<p>Specifies the directory where all intermediate moc files should be placed.</p>
<p>For example:</p>
<pre class="cpp">

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

</pre>
<a name="objective-headers"></a><a name="objective-headers"></a>
<h2 id="objective-headers">OBJECTIVE_HEADERS</h2>
<p>Defines the Objective-C++ header files for the project.</p>
<p>qmake automatically detects whether <a href="../qtdoc/moc.html">moc</a> is required by the classes in the headers, and adds the appropriate dependencies and files to the project for generating and linking the moc files.</p>
<p>This is similar to the HEADERS variable, but will let the generated moc files be compiled with the Objective-C++ compiler.</p>
<p>See also <a href="qmake-variable-reference.html#objective-sources">OBJECTIVE_SOURCES</a>.</p>
<a name="objective-sources"></a><a name="objective-sources"></a>
<h2 id="objective-sources">OBJECTIVE_SOURCES</h2>
<p>Specifies the names of all Objective-C/C++ source files in the project.</p>
<p>This variable is now obsolete, Objective-C/C++ files (.m and .mm) can be added to the <a href="qmake-variable-reference.html#sources">SOURCES</a> variable.</p>
<p>See also <a href="qmake-variable-reference.html#objective-headers">OBJECTIVE_HEADERS</a>.</p>
<a name="objects"></a><a name="objects"></a>
<h2 id="objects">OBJECTS</h2>
<p>This variable is automatically populated from the <a href="qmake-variable-reference.html#sources">SOURCES</a> variable. The extension of each source file is replaced by .o (Unix) or .obj (Win32). You can add objects to the list.</p>
<a name="objects-dir"></a><a name="objects-dir"></a>
<h2 id="objects-dir">OBJECTS_DIR</h2>
<p>Specifies the directory where all intermediate objects should be placed.</p>
<p>For example:</p>
<pre class="cpp">

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

</pre>
<a name="post-targetdeps"></a><a name="post-targetdeps"></a>
<h2 id="post-targetdeps">POST_TARGETDEPS</h2>
<p>Lists the libraries that the <a href="qmake-variable-reference.html#target">target</a> depends on. Some backends, such as the generators for Visual Studio and Xcode project files, do not support this variable. Generally, this variable is supported internally by these build tools, and it is useful for explicitly listing dependent static libraries.</p>
<p>This list is placed after all builtin (and <a href="qmake-variable-reference.html#pre-targetdeps">$$PRE_TARGETDEPS</a>) dependencies.</p>
<a name="pre-targetdeps"></a><a name="pre-targetdeps"></a>
<h2 id="pre-targetdeps">PRE_TARGETDEPS</h2>
<p>Lists libraries that the <a href="qmake-variable-reference.html#target">target</a> depends on. Some backends, such as the generators for Visual Studio and Xcode project files, do not support this variable. Generally, this variable is supported internally by these build tools, and it is useful for explicitly listing dependent static libraries.</p>
<p>This list is placed before all builtin dependencies.</p>
<a name="precompiled-header"></a><a name="precompiled-header"></a>
<h2 id="precompiled-header">PRECOMPILED_HEADER</h2>
<p>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, Apple - Xcode, Makefile, Unix - gcc 3.3 and up).</p>
<a name="pwd"></a><a name="pwd"></a>
<h2 id="pwd">PWD</h2>
<p>Specifies the full path leading to the directory containing the current file being parsed. This can be useful to refer to files within the source tree when writing project files to support shadow builds.</p>
<p>See also <a href="qmake-variable-reference.html#pro-file-pwd">_PRO_FILE_PWD_</a>.</p>
<p><b>Note: </b>Do not attempt to overwrite the value of this variable.</p><a name="out-pwd"></a><a name="out-pwd"></a>
<h2 id="out-pwd">OUT_PWD</h2>
<p>Specifies the full path leading to the directory where qmake places the generated Makefile.</p>
<p><b>Note: </b>Do not attempt to overwrite the value of this variable.</p><a name="qmake-systemvariable"></a><a name="qmake"></a>
<h2 id="qmake">QMAKE</h2>
<p>Specifies the name of the qmake program itself and is placed in generated Makefiles. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmakespec-systemvariable"></a><a name="qmakespec"></a>
<h2 id="qmakespec">QMAKESPEC</h2>
<p>A system variable that contains the full path of the qmake configuration that is used when generating Makefiles. The value of this variable is automatically computed.</p>
<p><b>Note: </b>Do not attempt to overwrite the value of this variable.</p><a name="qmake-ar-cmd"></a><a name="qmake-ar-cmd"></a>
<h2 id="qmake-ar-cmd">QMAKE_AR_CMD</h2>
<p><b>Note: </b>This variable is used on Unix platforms only.</p><p>Specifies the command to execute when creating a shared library. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-bundle-data"></a><a name="qmake-bundle-data"></a>
<h2 id="qmake-bundle-data">QMAKE_BUNDLE_DATA</h2>
<p><b>Note: </b>This variable is used on <a href="../qtdoc/internationalization.html#macos">macOS</a>, iOS, tvOS, and watchOS only.</p><p>Specifies the data that will be installed with a library bundle, and is often used to specify a collection of header files.</p>
<p>For example, the following lines add <code>path/to/header_one.h</code> and <code>path/to/header_two.h</code> to a group containing information about the headers supplied with the framework:</p>
<pre class="cpp">

  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

</pre>
<p>The last line adds the information about the headers to the collection of resources that will be installed with the library bundle.</p>
<p>Library bundles are created when the <code>lib_bundle</code> option is added to the <a href="qmake-variable-reference.html#config">CONFIG</a> variable.</p>
<p>See <a href="qmake-platform-notes.html#creating-frameworks">Platform Notes</a> for more information about creating library bundles.</p>
<a name="qmake-bundle-extension"></a>
<h2 id="qmake-bundle-extension">QMAKE_BUNDLE_EXTENSION</h2>
<p><b>Note: </b>This variable is used on <a href="../qtdoc/internationalization.html#macos">macOS</a>, iOS, tvOS, and watchOS only.</p><p>Specifies the extension to be used for library bundles. This allows frameworks to be created with custom extensions instead of the standard <code>.framework</code> directory name extension.</p>
<p>For example, the following definition will result in a framework with the <code>.myframework</code> extension:</p>
<pre class="cpp">

  QMAKE_BUNDLE_EXTENSION = .myframework

</pre>
<a name="qmake-cc"></a>
<h2 id="qmake-cc">QMAKE_CC</h2>
<p>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 <code>PATH</code> variable when the Makefile is processed.</p>
<a name="qmake-cflags"></a>
<h2 id="qmake-cflags">QMAKE_CFLAGS</h2>
<p>Specifies the C compiler flags for building a project. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified. The flags specific to debug and release modes can be adjusted by modifying the <code>QMAKE_CFLAGS_DEBUG</code> and <code>QMAKE_CFLAGS_RELEASE</code> variables, respectively.</p>
<a name="qmake-cflags-debug"></a><a name="qmake-cflags-debug"></a>
<h2 id="qmake-cflags-debug">QMAKE_CFLAGS_DEBUG</h2>
<p>Specifies the C compiler flags for debug builds. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-release"></a><a name="qmake-cflags-release"></a>
<h2 id="qmake-cflags-release">QMAKE_CFLAGS_RELEASE</h2>
<p>Specifies the C compiler flags for release builds. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-shlib"></a><a name="qmake-cflags-shlib"></a>
<h2 id="qmake-cflags-shlib">QMAKE_CFLAGS_SHLIB</h2>
<p><b>Note: </b>This variable is used on Unix platforms only.</p><p>Specifies the compiler flags for creating a shared library. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-thread"></a><a name="qmake-cflags-thread"></a>
<h2 id="qmake-cflags-thread">QMAKE_CFLAGS_THREAD</h2>
<p>Specifies the compiler flags for creating a multi-threaded application. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-warn-off"></a><a name="qmake-cflags-warn-off"></a>
<h2 id="qmake-cflags-warn-off">QMAKE_CFLAGS_WARN_OFF</h2>
<p>This variable is used only when the <code>warn_off</code> <a href="qmake-variable-reference.html#config">CONFIG</a> option is set. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-warn-on"></a><a name="qmake-cflags-warn-on"></a>
<h2 id="qmake-cflags-warn-on">QMAKE_CFLAGS_WARN_ON</h2>
<p>This variable is used only when the <code>warn_on</code> <a href="qmake-variable-reference.html#config">CONFIG</a> option is set. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-clean"></a><a name="qmake-clean"></a>
<h2 id="qmake-clean">QMAKE_CLEAN</h2>
<p>Specifies a list of generated files (by <a href="../qtdoc/moc.html">moc</a> and <a href="../qtdoc/uic.html">uic</a>, for example) and object files to be removed by <code>make clean</code>.</p>
<a name="qmake-cxx"></a>
<h2 id="qmake-cxx">QMAKE_CXX</h2>
<p>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 <code>PATH</code> variable when the Makefile is processed.</p>
<a name="qmake-cxxflags"></a>
<h2 id="qmake-cxxflags">QMAKE_CXXFLAGS</h2>
<p>Specifies the C++ compiler flags for building a project. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified. The flags specific to debug and release modes can be adjusted by modifying the <code>QMAKE_CXXFLAGS_DEBUG</code> and <code>QMAKE_CXXFLAGS_RELEASE</code> variables, respectively.</p>
<a name="qmake-cxxflags-debug"></a><a name="qmake-cxxflags-debug"></a>
<h2 id="qmake-cxxflags-debug">QMAKE_CXXFLAGS_DEBUG</h2>
<p>Specifies the C++ compiler flags for debug builds. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-release"></a><a name="qmake-cxxflags-release"></a>
<h2 id="qmake-cxxflags-release">QMAKE_CXXFLAGS_RELEASE</h2>
<p>Specifies the C++ compiler flags for release builds. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-shlib"></a><a name="qmake-cxxflags-shlib"></a>
<h2 id="qmake-cxxflags-shlib">QMAKE_CXXFLAGS_SHLIB</h2>
<p>Specifies the C++ compiler flags for creating a shared library. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-thread"></a><a name="qmake-cxxflags-thread"></a>
<h2 id="qmake-cxxflags-thread">QMAKE_CXXFLAGS_THREAD</h2>
<p>Specifies the C++ compiler flags for creating a multi-threaded application. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-warn-off"></a><a name="qmake-cxxflags-warn-off"></a>
<h2 id="qmake-cxxflags-warn-off">QMAKE_CXXFLAGS_WARN_OFF</h2>
<p>Specifies the C++ compiler flags for suppressing compiler warnings. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-warn-on"></a><a name="qmake-cxxflags-warn-on"></a>
<h2 id="qmake-cxxflags-warn-on">QMAKE_CXXFLAGS_WARN_ON</h2>
<p>Specifies C++ compiler flags for generating compiler warnings. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-development-team"></a><a name="qmake-development-team"></a>
<h2 id="qmake-development-team">QMAKE_DEVELOPMENT_TEAM</h2>
<p><b>Note: </b>This variable is used on <a href="../qtdoc/internationalization.html#macos">macOS</a>, iOS, tvOS, and watchOS only.</p><p>The identifier of a development team to use for signing certificates and provisioning profiles.</p>
<a name="qmake-distclean"></a><a name="qmake-distclean"></a>
<h2 id="qmake-distclean">QMAKE_DISTCLEAN</h2>
<p>Specifies a list of files to be removed by <code>make distclean</code>.</p>
<a name="qmake-extension-shlib"></a><a name="qmake-extension-shlib"></a>
<h2 id="qmake-extension-shlib">QMAKE_EXTENSION_SHLIB</h2>
<p>Contains the extension for shared libraries. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p><b>Note: </b>Platform-specific variables that change the extension override the contents of this variable.</p><a name="qmake-extension-staticlib"></a><a name="qmake-extension-staticlib"></a>
<h2 id="qmake-extension-staticlib">QMAKE_EXTENSION_STATICLIB</h2>
<p>Contains the extension for shared static libraries. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-ext-moc"></a>
<h2 id="qmake-ext-moc">QMAKE_EXT_MOC</h2>
<p>Contains the extension used on included moc files.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>.</p>
<a name="qmake-ext-ui"></a>
<h2 id="qmake-ext-ui">QMAKE_EXT_UI</h2>
<p>Contains the extension used on <i>Qt Designer</i> UI files.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>.</p>
<a name="qmake-ext-prl"></a>
<h2 id="qmake-ext-prl">QMAKE_EXT_PRL</h2>
<p>Contains the extension used on created PRL files.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>, <a href="qmake-advanced-usage.html#libdepend">Library Dependencies</a>.</p>
<a name="qmake-ext-lex"></a>
<h2 id="qmake-ext-lex">QMAKE_EXT_LEX</h2>
<p>Contains the extension used on files given to Lex.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>, <a href="qmake-variable-reference.html#lexsources">LEXSOURCES</a>.</p>
<a name="qmake-ext-yacc"></a>
<h2 id="qmake-ext-yacc">QMAKE_EXT_YACC</h2>
<p>Contains the extension used on files given to Yacc.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>, <a href="qmake-variable-reference.html#yaccsources">YACCSOURCES</a>.</p>
<a name="qmake-ext-obj"></a>
<h2 id="qmake-ext-obj">QMAKE_EXT_OBJ</h2>
<p>Contains the extension used on generated object files.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>.</p>
<a name="qmake-ext-cpp"></a>
<h2 id="qmake-ext-cpp">QMAKE_EXT_CPP</h2>
<p>Contains suffixes for files that should be interpreted as C++ source code.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>.</p>
<a name="qmake-ext-h"></a>
<h2 id="qmake-ext-h">QMAKE_EXT_H</h2>
<p>Contains suffixes for files which should be interpreted as C header files.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>.</p>
<a name="qmake-extra-compilers"></a>
<h2 id="qmake-extra-compilers">QMAKE_EXTRA_COMPILERS</h2>
<p>Specifies a list of additional compilers or preprocessors.</p>
<p>See also <a href="qmake-advanced-usage.html#adding-compilers">Adding Compilers</a>.</p>
<a name="qmake-extra-targets"></a>
<h2 id="qmake-extra-targets">QMAKE_EXTRA_TARGETS</h2>
<p>Specifies a list of additional qmake targets.</p>
<p>See also <a href="qmake-advanced-usage.html#adding-custom-targets">Adding Custom Targets</a>.</p>
<a name="qmake-failed-requirements"></a><a name="qmake-failed-requirements"></a>
<h2 id="qmake-failed-requirements">QMAKE_FAILED_REQUIREMENTS</h2>
<p>Contains the list of failed requirements. The value of this variable is set by qmake and cannot be modified.</p>
<p>See also <a href="qmake-test-function-reference.html#requires-condition">requires()</a> and <a href="qmake-variable-reference.html#requires">REQUIRES</a>.</p>
<a name="qmake-framework-bundle-name"></a>
<h2 id="qmake-framework-bundle-name">QMAKE_FRAMEWORK_BUNDLE_NAME</h2>
<p><b>Note: </b>This variable is used on <a href="../qtdoc/internationalization.html#macos">macOS</a>, iOS, tvOS, and watchOS only.</p><p>In a framework project, this variable contains the name to be used for the framework that is built.</p>
<p>By default, this variable contains the same value as the <a href="qmake-variable-reference.html#target">TARGET</a> variable.</p>
<p>See <a href="qmake-platform-notes.html#creating-frameworks">Creating Frameworks</a> for more information about creating frameworks and library bundles.</p>
<a name="qmake-framework-version"></a><a name="qmake-framework-version"></a>
<h2 id="qmake-framework-version">QMAKE_FRAMEWORK_VERSION</h2>
<p><b>Note: </b>This variable is used on <a href="../qtdoc/internationalization.html#macos">macOS</a>, iOS, tvOS, and watchOS only.</p><p>For projects where the build target is a <a href="../qtdoc/internationalization.html#macos">macOS</a>, iOS, tvOS, or watchOS framework, this variable is used to specify the version number that will be applied to the framework that is built.</p>
<p>By default, this variable contains the same value as the <a href="qmake-variable-reference.html#version">VERSION</a> variable.</p>
<p>See <a href="qmake-platform-notes.html#creating-frameworks">Creating Frameworks</a> for more information about creating frameworks.</p>
<a name="qmake-host"></a><a name="qmake-host"></a>
<h2 id="qmake-host">QMAKE_HOST</h2>
<p>Provides information about the host machine running qmake. For example, you can retrieve the host machine architecture from <code>QMAKE_HOST.arch</code>.</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Keys</th><th >Values</th></tr></thead>
<tr valign="top" class="odd"><td >.arch</td><td >Host architecture</td></tr>
<tr valign="top" class="even"><td >.os</td><td >Host OS</td></tr>
<tr valign="top" class="odd"><td >.cpu_count</td><td >Number of available cpus</td></tr>
<tr valign="top" class="even"><td >.name</td><td >Host computer name</td></tr>
<tr valign="top" class="odd"><td >.version</td><td >Host OS version number</td></tr>
<tr valign="top" class="even"><td >.version_string</td><td >Host OS version string</td></tr>
</table></div>
<pre class="cpp">

  win32-g++:contains(QMAKE_HOST.arch, x86_64):{
      message(&quot;Host is 64bit&quot;)
      ...
  }

</pre>
<a name="qmake-incdir"></a><a name="qmake-incdir"></a>
<h2 id="qmake-incdir">QMAKE_INCDIR</h2>
<p>Specifies the list of system header paths that are appended to <a href="qmake-variable-reference.html#includepath">INCLUDEPATH</a>. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-incdir-egl"></a><a name="qmake-incdir-egl"></a>
<h2 id="qmake-incdir-egl">QMAKE_INCDIR_EGL</h2>
<p>Specifies the location of EGL header files to be added to <a href="qmake-variable-reference.html#includepath">INCLUDEPATH</a> when building a target with OpenGL/ES or <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a> support. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-incdir-opengl"></a><a name="qmake-incdir-opengl"></a>
<h2 id="qmake-incdir-opengl">QMAKE_INCDIR_OPENGL</h2>
<p>Specifies the location of OpenGL header files to be added to <a href="qmake-variable-reference.html#includepath">INCLUDEPATH</a> when building a target with OpenGL support. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenGL implementation uses EGL (most OpenGL/ES systems), then <a href="qmake-variable-reference.html#qmake-incdir-egl">QMAKE_INCDIR_EGL</a> may also need to be set.</p>
<a name="qmake-incdir-opengl-es2"></a>
<h2 id="qmake-incdir-opengl-es2">QMAKE_INCDIR_OPENGL_ES2</h2>
<p>This variable specifies the location of OpenGL header files to be added to <a href="qmake-variable-reference.html#includepath">INCLUDEPATH</a> when building a target with OpenGL ES 2 support.</p>
<p>The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenGL implementation uses EGL (most OpenGL/ES systems), then <a href="qmake-variable-reference.html#qmake-incdir-egl">QMAKE_INCDIR_EGL</a> may also need to be set.</p>
<a name="qmake-incdir-openvg"></a><a name="qmake-incdir-openvg"></a>
<h2 id="qmake-incdir-openvg">QMAKE_INCDIR_OPENVG</h2>
<p>Specifies the location of <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a> header files to be added to <a href="qmake-variable-reference.html#includepath">INCLUDEPATH</a> when building a target with <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a> support. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a> implementation uses EGL then <a href="qmake-variable-reference.html#qmake-incdir-egl">QMAKE_INCDIR_EGL</a> may also need to be set.</p>
<a name="qmake-incdir-x11"></a><a name="qmake-incdir-x11"></a>
<h2 id="qmake-incdir-x11">QMAKE_INCDIR_X11</h2>
<p><b>Note: </b>This variable is used on Unix platforms only.</p><p>Specifies the location of X11 header file paths to be added to <a href="qmake-variable-reference.html#includepath">INCLUDEPATH</a> when building an X11 target. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-info-plist"></a><a name="qmake-info-plist"></a>
<h2 id="qmake-info-plist">QMAKE_INFO_PLIST</h2>
<p><b>Note: </b>This variable is used on <a href="../qtdoc/internationalization.html#macos">macOS</a>, iOS, tvOS, and watchOS platforms only.</p><p>Specifies the name of the property list file, <code>.plist</code>, you would like to include in your <a href="../qtdoc/internationalization.html#macos">macOS</a>, iOS, tvOS, and watchOS application bundle.</p>
<p>In the <code>.plist</code> file, you can define some variables which qmake will replace with the relevant values:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Placeholder(s)</th><th >Effect</th></tr></thead>
<tr valign="top" class="odd"><td ><code>${PRODUCT_BUNDLE_IDENTIFIER}</code>, <code>@BUNDLEIDENTIFIER@</code></td><td >Expands to the target bundle's bundle identifier string, for example: <code>com.example.myapp</code>. Determined by concatenating the values of QMAKE_TARGET_BUNDLE_PREFIX and QMAKE_BUNDLE, separated by a full stop (<code>.</code>).</td></tr>
<tr valign="top" class="even"><td ><code>${EXECUTABLE_NAME}</code>, <code>@EXECUTABLE@</code>, <code>@LIBRARY@</code></td><td >Equivalent to the value of QMAKE_APPLICATION_BUNDLE_NAME, QMAKE_PLUGIN_BUNDLE_NAME, or <a href="qmake-variable-reference.html#qmake-framework-bundle-name">QMAKE_FRAMEWORK_BUNDLE_NAME</a> (depending on the type of target being created), or TARGET if none of the previous values are set.</td></tr>
<tr valign="top" class="odd"><td ><code>${ASSETCATALOG_COMPILER_APPICON_NAME}</code>, <code>@ICON@</code></td><td >Expands to the value of ICON.</td></tr>
<tr valign="top" class="even"><td ><code>${QMAKE_PKGINFO_TYPEINFO}</code>, <code>@TYPEINFO@</code></td><td >Expands to the value of QMAKE_PKGINFO_TYPEINFO.</td></tr>
<tr valign="top" class="odd"><td ><code>${QMAKE_FULL_VERSION}</code>, <code>@FULL_VERSION@</code></td><td >Expands to the value of VERSION expressed with three version components.</td></tr>
<tr valign="top" class="even"><td ><code>${QMAKE_SHORT_VERSION}</code>, <code>@SHORT_VERSION@</code></td><td >Expands to the value of VERSION expressed with two version components.</td></tr>
<tr valign="top" class="odd"><td ><code>${MACOSX_DEPLOYMENT_TARGET}</code></td><td >Expands to the value of <a href="qmake-variable-reference.html#qmake-macosx-deployment-target">QMAKE_MACOSX_DEPLOYMENT_TARGET</a>.</td></tr>
<tr valign="top" class="even"><td ><code>${IPHONEOS_DEPLOYMENT_TARGET}</code></td><td >Expands to the value of QMAKE_IPHONEOS_DEPLOYMENT_TARGET.</td></tr>
<tr valign="top" class="odd"><td ><code>${TVOS_DEPLOYMENT_TARGET}</code></td><td >Expands to the value of <a href="qmake-variable-reference.html#qmake-tvos-deployment-target">QMAKE_TVOS_DEPLOYMENT_TARGET</a>.</td></tr>
<tr valign="top" class="even"><td ><code>${WATCHOS_DEPLOYMENT_TARGET}</code></td><td >Expands to the value of <a href="qmake-variable-reference.html#qmake-watchos-deployment-target">QMAKE_WATCHOS_DEPLOYMENT_TARGET</a>.</td></tr>
</table></div>
<p><b>Note: </b>When using the Xcode generator, the above <code>${var}</code>-style placeholders are replaced directly by the Xcode build system and are not handled by qmake. The <code>@var@</code> style placeholders work only with the qmake Makefile generators and not with the Xcode generator.</p><p>If building for iOS, and the <code>.plist</code> file contains the key <code>NSPhotoLibraryUsageDescription</code>, qmake will include an additional plugin to the build that adds photo access support (to, e.g&#x2e;, <a href="../qtwidgets/qfiledialog.html#setDirectory-1">QFile/QFileDialog</a>). See Info.plist documentation from Apple for more information regarding this key.</p>
<p><b>Note: </b>Most of the time, the default <code>Info.plist</code> is good enough.</p><a name="qmake-ios-deployment-target"></a>
<h2 id="qmake-ios-deployment-target">QMAKE_IOS_DEPLOYMENT_TARGET</h2>
<p><b>Note: </b>This variable is used on the iOS platform only.</p><p>Specifies the hard minimum version of iOS that the application supports.</p>
<p>For more information, see <a href="../qtdoc/platform-notes-ios.html#expressing-supported-ios-versions">Expressing Supported iOS Versions</a>.</p>
<a name="qmake-lflags"></a>
<h2 id="qmake-lflags">QMAKE_LFLAGS</h2>
<p>Specifies 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.</p>
<a name="qmake-lflags-console"></a><a name="qmake-lflags-console"></a>
<h2 id="qmake-lflags-console">QMAKE_LFLAGS_CONSOLE</h2>
<p><b>Note: </b>This variable is used on Windows only.</p><p>Specifies the linker flags for building console programs. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-debug"></a>
<h2 id="qmake-lflags-debug">QMAKE_LFLAGS_DEBUG</h2>
<p>Specifies the linker flags for debug builds. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-plugin"></a>
<h2 id="qmake-lflags-plugin">QMAKE_LFLAGS_PLUGIN</h2>
<p>Specifies the linker flags for building plugins. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-rpath"></a>
<h2 id="qmake-lflags-rpath">QMAKE_LFLAGS_RPATH</h2>
<p><b>Note: </b>This variable is used on Unix platforms only.</p><p>Specifies the linker flags needed to use the values from <a href="qmake-variable-reference.html#qmake-rpathdir">QMAKE_RPATHDIR</a>.</p>
<p>The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-rel-rpath"></a>
<h2 id="qmake-lflags-rel-rpath">QMAKE_LFLAGS_REL_RPATH</h2>
<p>Specifies the linker flags needed to enable relative paths in <a href="qmake-variable-reference.html#qmake-rpathdir">QMAKE_RPATHDIR</a>.</p>
<p>The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-rel-rpath-base"></a>
<h2 id="qmake-rel-rpath-base">QMAKE_REL_RPATH_BASE</h2>
<p>Specifies the string the dynamic linker understands to be the location of the referring executable or library.</p>
<p>The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-rpathlink"></a>
<h2 id="qmake-lflags-rpathlink">QMAKE_LFLAGS_RPATHLINK</h2>
<p>Specifies the linker flags needed to use the values from <a href="qmake-variable-reference.html#qmake-rpathlinkdir">QMAKE_RPATHLINKDIR</a>.</p>
<p>The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-release"></a>
<h2 id="qmake-lflags-release">QMAKE_LFLAGS_RELEASE</h2>
<p>Specifies the linker flags for release builds. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-app"></a>
<h2 id="qmake-lflags-app">QMAKE_LFLAGS_APP</h2>
<p>Specifies the linker flags for building applications. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-shlib"></a>
<h2 id="qmake-lflags-shlib">QMAKE_LFLAGS_SHLIB</h2>
<p>Specifies the linker flags used for building shared libraries. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-soname"></a>
<h2 id="qmake-lflags-soname">QMAKE_LFLAGS_SONAME</h2>
<p>Specifies the linker flags for setting the name of shared objects, such as .so or .dll. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-thread"></a>
<h2 id="qmake-lflags-thread">QMAKE_LFLAGS_THREAD</h2>
<p>Specifies the linker flags for building multi-threaded projects. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-windows"></a>
<h2 id="qmake-lflags-windows">QMAKE_LFLAGS_WINDOWS</h2>
<p><b>Note: </b>This variable is used on Windows only.</p><p>Specifies the linker flags for building Windows GUI projects (that is, non-console applications). The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libdir"></a>
<h2 id="qmake-libdir">QMAKE_LIBDIR</h2>
<p>Specifies a list of system library paths. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libdir-flags"></a>
<h2 id="qmake-libdir-flags">QMAKE_LIBDIR_FLAGS</h2>
<p><b>Note: </b>This variable is used on Unix platforms only.</p><p>Specifies the location of all library directories with -L prefixed. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libdir-egl"></a>
<h2 id="qmake-libdir-egl">QMAKE_LIBDIR_EGL</h2>
<p>Specifies the location of the EGL library directory, when EGL is used with OpenGL/ES or <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a>. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libdir-opengl"></a>
<h2 id="qmake-libdir-opengl">QMAKE_LIBDIR_OPENGL</h2>
<p>Specifies the location of the OpenGL library directory. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenGL implementation uses EGL (most OpenGL/ES systems), then <a href="qmake-variable-reference.html#qmake-libdir-egl">QMAKE_LIBDIR_EGL</a> may also need to be set.</p>
<a name="qmake-libdir-openvg"></a>
<h2 id="qmake-libdir-openvg">QMAKE_LIBDIR_OPENVG</h2>
<p>Specifies the location of the <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a> library directory. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a> implementation uses EGL, then <a href="qmake-variable-reference.html#qmake-libdir-egl">QMAKE_LIBDIR_EGL</a> may also need to be set.</p>
<a name="qmake-libdir-x11"></a>
<h2 id="qmake-libdir-x11">QMAKE_LIBDIR_X11</h2>
<p><b>Note: </b>This variable is used on Unix platforms only.</p><p>Specifies the location of the X11 library directory. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs"></a>
<h2 id="qmake-libs">QMAKE_LIBS</h2>
<p>Specifies all project libraries. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-egl"></a>
<h2 id="qmake-libs-egl">QMAKE_LIBS_EGL</h2>
<p>Specifies all EGL libraries when building Qt with OpenGL/ES or <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a>. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified. The usual value is <code>-lEGL</code>.</p>
<a name="qmake-libs-opengl"></a>
<h2 id="qmake-libs-opengl">QMAKE_LIBS_OPENGL</h2>
<p>Specifies all OpenGL libraries. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenGL implementation uses EGL (most OpenGL/ES systems), then <a href="qmake-variable-reference.html#qmake-libs-egl">QMAKE_LIBS_EGL</a> may also need to be set.</p>
<a name="qmake-libs-opengl-es1-qmake-libs-opengl-es2"></a>
<h2 id="qmake-libs-opengl-es1-qmake-libs-opengl-es2">QMAKE_LIBS_OPENGL_ES1, QMAKE_LIBS_OPENGL_ES2</h2>
<p>These variables specify all the OpenGL libraries for OpenGL ES 1 and OpenGL ES 2.</p>
<p>The value of these variables is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenGL implementation uses EGL (most OpenGL/ES systems), then <a href="qmake-variable-reference.html#qmake-libs-egl">QMAKE_LIBS_EGL</a> may also need to be set.</p>
<a name="qmake-libs-openvg"></a>
<h2 id="qmake-libs-openvg">QMAKE_LIBS_OPENVG</h2>
<p>Specifies all <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a> libraries. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified. The usual value is <code>-lOpenVG</code>.</p>
<p>Some <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a> engines are implemented on top of OpenGL. This will be detected at configure time and <a href="qmake-variable-reference.html#qmake-libs-opengl">QMAKE_LIBS_OPENGL</a> will be implicitly added to <a href="qmake-variable-reference.html#qmake-libs-openvg">QMAKE_LIBS_OPENVG</a> wherever the <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a> libraries are linked.</p>
<p>If the <a href="../qtquick/qtquick-visualcanvas-adaptations.html#openvg">OpenVG</a> implementation uses EGL, then <a href="qmake-variable-reference.html#qmake-libs-egl">QMAKE_LIBS_EGL</a> may also need to be set.</p>
<a name="qmake-libs-thread"></a>
<h2 id="qmake-libs-thread">QMAKE_LIBS_THREAD</h2>
<p><b>Note: </b>This variable is used on Unix platforms only.</p><p>Specifies all libraries that need to be linked against when building a multi-threaded target. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-x11"></a>
<h2 id="qmake-libs-x11">QMAKE_LIBS_X11</h2>
<p><b>Note: </b>This variable is used on Unix platforms only.</p><p>Specifies all X11 libraries. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lib-flag"></a>
<h2 id="qmake-lib-flag">QMAKE_LIB_FLAG</h2>
<p>This variable is not empty if the <code>lib</code> template is specified. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-link"></a>
<h2 id="qmake-link">QMAKE_LINK</h2>
<p>Specifies the linker that will be used when building application based projects. Only the file name of the linker executable needs to be specified as long as it is on a path contained in the <code>PATH</code> variable when the Makefile is processed. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-link-shlib-cmd"></a>
<h2 id="qmake-link-shlib-cmd">QMAKE_LINK_SHLIB_CMD</h2>
<p>Specifies the command to execute when creating a shared library. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-ln-shlib"></a>
<h2 id="qmake-ln-shlib">QMAKE_LN_SHLIB</h2>
<p>Specifies the command to execute when creating a link to a shared library. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-objective-cflags"></a>
<h2 id="qmake-objective-cflags">QMAKE_OBJECTIVE_CFLAGS</h2>
<p>Specifies the Objective C/C++ compiler flags for building a project. These flags are used in addition to <a href="qmake-variable-reference.html#qmake-cflags">QMAKE_CFLAGS</a> and <a href="qmake-variable-reference.html#qmake-cxxflags">QMAKE_CXXFLAGS</a>.</p>
<a name="qmake-post-link"></a>
<h2 id="qmake-post-link">QMAKE_POST_LINK</h2>
<p>Specifies the command to execute after linking the <a href="qmake-variable-reference.html#target">TARGET</a> together. This variable is normally empty and therefore nothing is executed.</p>
<p><b>Note: </b>This variable takes no effect on Xcode projects.</p><a name="qmake-pre-link"></a>
<h2 id="qmake-pre-link">QMAKE_PRE_LINK</h2>
<p>Specifies the command to execute before linking the <a href="qmake-variable-reference.html#target">TARGET</a> together. This variable is normally empty and therefore nothing is executed.</p>
<p><b>Note: </b>This variable takes no effect on Xcode projects.</p><a name="qmake-project-name"></a>
<h2 id="qmake-project-name">QMAKE_PROJECT_NAME</h2>
<p><b>Note: </b>This variable is used for Visual Studio project files only.</p><p>Determines the name of the project when generating project files for IDEs. The default value is the target name. The value of this variable is typically handled by qmake and rarely needs to be modified.</p>
<a name="qmake-provisioning-profile"></a><a name="qmake-provisioning-profile"></a>
<h2 id="qmake-provisioning-profile">QMAKE_PROVISIONING_PROFILE</h2>
<p><b>Note: </b>This variable is used on <a href="../qtdoc/internationalization.html#macos">macOS</a>, iOS, tvOS, and watchOS only.</p><p>The UUID of a valid provisioning profile. Use in conjunction with <a href="qmake-variable-reference.html#qmake-development-team">QMAKE_DEVELOPMENT_TEAM</a> to specify the provisioning profile.</p>
<p><b>Note: </b>Specifying the provisioning profile disables the automatically managed signing.</p><a name="qmake-mac-sdk"></a>
<h2 id="qmake-mac-sdk">QMAKE_MAC_SDK</h2>
<p>This variable is used on <a href="../qtdoc/internationalization.html#macos">macOS</a> when building universal binaries.</p>
<a name="qmake-macosx-deployment-target"></a>
<h2 id="qmake-macosx-deployment-target">QMAKE_MACOSX_DEPLOYMENT_TARGET</h2>
<p><b>Note: </b>This variable is used on the <a href="../qtdoc/internationalization.html#macos">macOS</a> platform only.</p><p>Specifies the hard minimum version of <a href="../qtdoc/internationalization.html#macos">macOS</a> that the application supports.</p>
<p>For more information, see <a href="../qtdoc/osx-deployment.html#macos-version-dependencies">macOS Version Dependencies</a>.</p>
<a name="qmake-makefile"></a>
<h2 id="qmake-makefile">QMAKE_MAKEFILE</h2>
<p>Specifies the name of the Makefile to create. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-qmake"></a>
<h2 id="qmake-qmake">QMAKE_QMAKE</h2>
<p>Contains the absolute path of the qmake executable.</p>
<p><b>Note: </b>Do not attempt to overwrite the value of this variable.</p><a name="qmake-resource-flags"></a>
<h2 id="qmake-resource-flags">QMAKE_RESOURCE_FLAGS</h2>
<p>This variable is used to customize the list of options passed to the <a href="../qtdoc/rcc.html">Resource Compiler</a> in each of the build rules where it is used. For example, the following line ensures that the <code>-threshold</code> and <code>-compress</code> options are used with particular values each time that <code>rcc</code> is invoked:</p>
<pre class="cpp">

  QMAKE_RESOURCE_FLAGS += -threshold 0 -compress 9

</pre>
<a name="qmake-rpathdir"></a>
<h2 id="qmake-rpathdir">QMAKE_RPATHDIR</h2>
<p><b>Note: </b>This variable is used on Unix platforms only.</p><p>Specifies a list of library paths that are added to the executable at link time so that the paths will be preferentially searched at runtime.</p>
<p>When relative paths are specified, qmake will mangle them into a form understood by the dynamic linker to be relative to the location of the referring executable or library. This is supported only by some platforms (currently Linux and Darwin-based ones) and is detectable by checking whether <a href="qmake-variable-reference.html#qmake-rel-rpath-base">QMAKE_REL_RPATH_BASE</a> is set.</p>
<a name="qmake-rpathlinkdir"></a>
<h2 id="qmake-rpathlinkdir">QMAKE_RPATHLINKDIR</h2>
<p>Specifies a list of library paths for the static linker to search for implicit dependencies of shared libraries. For more information, see the manual page for <code>ld(1)</code>.</p>
<a name="qmake-run-cc"></a>
<h2 id="qmake-run-cc">QMAKE_RUN_CC</h2>
<p>Specifies the individual rule needed to build an object. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-run-cc-imp"></a>
<h2 id="qmake-run-cc-imp">QMAKE_RUN_CC_IMP</h2>
<p>Specifies the individual rule needed to build an object. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-run-cxx"></a>
<h2 id="qmake-run-cxx">QMAKE_RUN_CXX</h2>
<p>Specifies the individual rule needed to build an object. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-run-cxx-imp"></a>
<h2 id="qmake-run-cxx-imp">QMAKE_RUN_CXX_IMP</h2>
<p>Specifies the individual rule needed to build an object. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-soname-prefix"></a>
<h2 id="qmake-soname-prefix">QMAKE_SONAME_PREFIX</h2>
<p>If defined, the value of this variable is used as a path to be prepended to the built shared library's <code>SONAME</code> identifier. The <code>SONAME</code> is the identifier that the dynamic linker will later use to reference the library. In general, this reference may be a library name or full library path. On <a href="../qtdoc/internationalization.html#macos">macOS</a>, iOS, tvOS, and watchOS, the path may be specified relatively using the following placeholders:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Placeholder</th><th >Effect</th></tr></thead>
<tr valign="top" class="odd"><td >@rpath</td><td >Expands to paths defined by LC_RPATH mach-o commands in the current process executable or the referring libraries.</td></tr>
<tr valign="top" class="even"><td >@executable_path</td><td >Expands to the current process executable location.</td></tr>
<tr valign="top" class="odd"><td >@loader_path</td><td >Expands to the referring executable or library location.</td></tr>
</table></div>
<p>In most cases, using <code>@rpath</code> is sufficient and recommended:</p>
<pre class="cpp">

  # &lt;project root&gt;/project.pro
  QMAKE_SONAME_PREFIX = @rpath

</pre>
<p>However, the prefix may be also specified using different placeholders, or an absolute path, such as one of the following:</p>
<pre class="cpp">

  # &lt;project root&gt;/project.pro
  QMAKE_SONAME_PREFIX = @executable_path/../Frameworks
  QMAKE_SONAME_PREFIX = @loader_path/Frameworks
  QMAKE_SONAME_PREFIX = /Library/Frameworks

</pre>
<p>For more information, see <a href="https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/dyld.1.html">dyld</a> documentation on dynamic library install names.</p>
<a name="qmake-target"></a>
<h2 id="qmake-target">QMAKE_TARGET</h2>
<p>Specifies the name of the project target. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-target-company"></a><a name="qmake-target-company"></a>
<h2 id="qmake-target-company">QMAKE_TARGET_COMPANY</h2>
<p>Windows only. Specifies the company for the project target; this is used where applicable for putting the company name in the application's properties. This is only utilized if the <a href="qmake-variable-reference.html#version">VERSION</a> or <a href="qmake-variable-reference.html#rc-icons">RC_ICONS</a> variable is set and the <a href="qmake-variable-reference.html#rc-file">RC_FILE</a> and <a href="qmake-variable-reference.html#res-file">RES_FILE</a> variables are not set.</p>
<a name="qmake-target-description"></a><a name="qmake-target-description"></a>
<h2 id="qmake-target-description">QMAKE_TARGET_DESCRIPTION</h2>
<p>Windows only. Specifies the description for the project target; this is used where applicable for putting the description in the application's properties. This is only utilized if the <a href="qmake-variable-reference.html#version">VERSION</a> or <a href="qmake-variable-reference.html#rc-icons">RC_ICONS</a> variable is set and the <a href="qmake-variable-reference.html#rc-file">RC_FILE</a> and <a href="qmake-variable-reference.html#res-file">RES_FILE</a> variables are not set.</p>
<a name="qmake-target-copyright"></a><a name="qmake-target-copyright"></a>
<h2 id="qmake-target-copyright">QMAKE_TARGET_COPYRIGHT</h2>
<p>Windows only. Specifies the copyright information for the project target; this is used where applicable for putting the copyright information in the application's properties. This is only utilized if the <a href="qmake-variable-reference.html#version">VERSION</a> or <a href="qmake-variable-reference.html#rc-icons">RC_ICONS</a> variable is set and the <a href="qmake-variable-reference.html#rc-file">RC_FILE</a> and <a href="qmake-variable-reference.html#res-file">RES_FILE</a> variables are not set.</p>
<a name="qmake-target-product"></a><a name="qmake-target-product"></a>
<h2 id="qmake-target-product">QMAKE_TARGET_PRODUCT</h2>
<p>Windows only. Specifies the product for the project target; this is used where applicable for putting the product in the application's properties. This is only utilized if the <a href="qmake-variable-reference.html#version">VERSION</a> or <a href="qmake-variable-reference.html#rc-icons">RC_ICONS</a> variable is set and the <a href="qmake-variable-reference.html#rc-file">RC_FILE</a> and <a href="qmake-variable-reference.html#res-file">RES_FILE</a> variables are not set.</p>
<a name="qmake-tvos-deployment-target"></a>
<h2 id="qmake-tvos-deployment-target">QMAKE_TVOS_DEPLOYMENT_TARGET</h2>
<p><b>Note: </b>This variable is used on the tvOS platform only.</p><p>Specifies the hard minimum version of tvOS that the application supports.</p>
<p>For more information, see <a href="../qtdoc/platform-notes-ios.html#expressing-supported-ios-versions">Expressing Supported iOS Versions</a>.</p>
<a name="qmake-uic-flags"></a>
<h2 id="qmake-uic-flags">QMAKE_UIC_FLAGS</h2>
<p>This variable is used to customize the list of options passed to the <a href="../qtdoc/uic.html">User Interface Compiler</a> in each of the build rules where it is used. For example, <code>-no-stringliteral</code> can be passed to use <a href="../qtcore/qlatin1string.html">QLatin1String</a> instead of <a href="../qtcore/qstring.html#QStringLiteral">QStringLiteral</a> in generated code (which is the default for dynamic libraries).</p>
<a name="qmake-watchos-deployment-target"></a>
<h2 id="qmake-watchos-deployment-target">QMAKE_WATCHOS_DEPLOYMENT_TARGET</h2>
<p><b>Note: </b>This variable is used on the watchOS platform only.</p><p>Specifies the hard minimum version of watchOS that the application supports.</p>
<p>For more information, see <a href="../qtdoc/platform-notes-ios.html#expressing-supported-ios-versions">Expressing Supported iOS Versions</a>.</p>
<a name="qt"></a>
<h2 id="qt">QT</h2>
<p>Specifies the <a href="../qtdoc/qtmodules.html">Qt modules</a> that are used by your project. For the value to add for each module, see the module documentation.</p>
<p>At the C++ implementation level, using a Qt module makes its headers available for inclusion and causes it to be linked to the binary.</p>
<p>By default, <code>QT</code> contains <code>core</code> and <code>gui</code>, ensuring that standard GUI applications can be built without further configuration.</p>
<p>If you want to build a project <i>without</i> the <a href="../qtgui/qtgui-index.html">Qt GUI</a> module, you need to exclude the <code>gui</code> value with the &quot;-=&quot; operator. The following line will result in a minimal Qt project being built:</p>
<pre class="cpp">

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

</pre>
<p>If your project is a <i>Qt Designer</i> plugin, use the value <code>uiplugin</code> to specify that the project is to be built as a library, but with specific plugin support for <i>Qt Designer</i>. For more information, see <a href="../qtdesigner/designer-creating-custom-widgets.html#building-and-installing-the-plugin">Building and Installing the Plugin</a>.</p>
<a name="qtplugin"></a>
<h2 id="qtplugin">QTPLUGIN</h2>
<p>Specifies a list of names of static Qt plugins that are to be linked with an application so that they are available as built-in resources.</p>
<p>qmake automatically adds the plugins that are typically needed by the used Qt modules (see <code>QT</code>). The defaults are tuned towards an optimal out-of-the-box experience. See <a href="../qtdoc/plugins-howto.html#static-plugins">Static Plugins</a> for a list of available plugins, and ways to override the automatic linking.</p>
<p>This variable currently has no effect when linking against a shared/dynamic build of Qt, or when linking libraries. It may be used for deployment of dynamic plugins at a later time.</p>
<a name="qt-version-variable"></a><a name="qt-version"></a>
<h2 id="qt-version">QT_VERSION</h2>
<p>Contains the current version of Qt.</p>
<a name="qt-major-version"></a><a name="qt-major-version"></a>
<h2 id="qt-major-version">QT_MAJOR_VERSION</h2>
<p>Contains the current major version of Qt.</p>
<a name="qt-minor-version"></a><a name="qt-minor-version"></a>
<h2 id="qt-minor-version">QT_MINOR_VERSION</h2>
<p>Contains the current minor version of Qt.</p>
<a name="qt-patch-version"></a><a name="qt-patch-version"></a>
<h2 id="qt-patch-version">QT_PATCH_VERSION</h2>
<p>Contains the current patch version of Qt.</p>
<a name="rc-file"></a>
<h2 id="rc-file">RC_FILE</h2>
<p>Specifies the name of the resource file for the application. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="rc-codepage"></a><a name="rc-codepage"></a>
<h2 id="rc-codepage">RC_CODEPAGE</h2>
<p>Windows only. Specifies the codepage that should be specified in a generated .rc file. This is only utilized if the <a href="qmake-variable-reference.html#version">VERSION</a> or <a href="qmake-variable-reference.html#rc-icons">RC_ICONS</a> variable is set and the <a href="qmake-variable-reference.html#rc-file">RC_FILE</a> and <a href="qmake-variable-reference.html#res-file">RES_FILE</a> variables are not set.</p>
<a name="rc-defines"></a><a name="rc-defines"></a>
<h2 id="rc-defines">RC_DEFINES</h2>
<p>Windows only. qmake adds the values of this variable as RC preprocessor macros (/d option). If this variable is not set, the <a href="qmake-variable-reference.html#defines">DEFINES</a> variable is used instead.</p>
<pre class="cpp">

  RC_DEFINES += USE_MY_STUFF

</pre>
<a name="rc-icons"></a><a name="rc-icons"></a>
<h2 id="rc-icons">RC_ICONS</h2>
<p>Windows only. Specifies the icons that should be included into a generated .rc file. This is only utilized if the <a href="qmake-variable-reference.html#rc-file">RC_FILE</a> and <a href="qmake-variable-reference.html#res-file">RES_FILE</a> variable are not set. More details about the generation of .rc files can be found in the <a href="qmake-platform-notes.html">Platform Notes</a>.</p>
<a name="rc-lang"></a><a name="rc-lang"></a>
<h2 id="rc-lang">RC_LANG</h2>
<p>Windows only. Specifies the language that should be specified in a generated .rc file. This is only utilized if the <a href="qmake-variable-reference.html#version">VERSION</a> or <a href="qmake-variable-reference.html#rc-icons">RC_ICONS</a> variable is set and the <a href="qmake-variable-reference.html#rc-file">RC_FILE</a> and <a href="qmake-variable-reference.html#res-file">RES_FILE</a> variables are not set.</p>
<a name="rc-includepath"></a>
<h2 id="rc-includepath">RC_INCLUDEPATH</h2>
<p>Specifies include paths that are passed to the Windows Resource Compiler.</p>
<a name="rcc-dir"></a><a name="rcc-dir"></a>
<h2 id="rcc-dir">RCC_DIR</h2>
<p>Specifies the directory for Qt Resource Compiler output files.</p>
<p>For example:</p>
<pre class="cpp">

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

</pre>
<a name="requires"></a><a name="requires"></a>
<h2 id="requires">REQUIRES</h2>
<p>Specifies a list of values that are evaluated as conditions. If any of the conditions is false, qmake skips this project (and its <a href="qmake-variable-reference.html#subdirs">SUBDIRS</a>) when building.</p>
<p><b>Note: </b>We recommend using the <a href="qmake-test-function-reference.html#requires-condition">requires()</a> function instead if you want to skip projects or subprojects when building.</p><a name="resources"></a><a name="resources"></a>
<h2 id="resources">RESOURCES</h2>
<p>Specifies the name of the resource collection files (qrc) for the target. For more information about the resource collection file, see <a href="../qtcore/resources.html">The Qt Resource System</a>.</p>
<a name="res-file"></a>
<h2 id="res-file">RES_FILE</h2>
<p>Specifies the name of the compiled Windows resource file for the target. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="sources"></a><a name="sources"></a>
<h2 id="sources">SOURCES</h2>
<p>Specifies the names of all source files in the project.</p>
<p>For example:</p>
<pre class="cpp">

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

</pre>
<p>See also <a href="qmake-variable-reference.html#headers">HEADERS</a>.</p>
<a name="subdirs"></a><a name="subdirs"></a>
<h2 id="subdirs">SUBDIRS</h2>
<p>This variable, when used with the <code>subdirs</code> <a href="qmake-variable-reference.html#template">template</a> specifies the names of all subdirectories or project files that contain parts of the project that need to be built. Each subdirectory specified using this variable must contain its own project file.</p>
<p>It is recommended that the project file in each subdirectory has the same base name as the subdirectory itself, because that makes it possible to omit the file name. For example, if the subdirectory is called <code>myapp</code>, the project file in that directory should be called <code>myapp.pro</code>.</p>
<p>Alternatively, you can specify a relative path to a .pro file in any directory. It is strongly recommended that you specify only paths in the current project's parent directory or its subdirectories.</p>
<p>For example:</p>
<pre class="cpp">

  SUBDIRS = kernel \
            tools \
            myapp

</pre>
<p>If you need to ensure that the subdirectories are built in the order in which they are specified, update the <a href="qmake-variable-reference.html#config">CONFIG</a> variable to include the <code>ordered</code> option:</p>
<pre class="cpp">

  CONFIG += ordered

</pre>
<p>It is possible to modify this default behavior of <code>SUBDIRS</code> by giving additional modifiers to <code>SUBDIRS</code> elements. Supported modifiers are:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Modifier</th><th >Effect</th></tr></thead>
<tr valign="top" class="odd"><td >.subdir</td><td >Use the specified subdirectory instead of <code>SUBDIRS</code> value.</td></tr>
<tr valign="top" class="even"><td >.file</td><td >Specify the subproject <code>pro</code> file explicitly. Cannot be used in conjunction with <code>.subdir</code> modifier.</td></tr>
<tr valign="top" class="odd"><td >.depends</td><td >This subproject depends on specified subproject.</td></tr>
<tr valign="top" class="even"><td >.makefile</td><td >The makefile of subproject. Available only on platforms that use makefiles.</td></tr>
<tr valign="top" class="odd"><td >.target</td><td >Base string used for makefile targets related to this subproject. Available only on platforms that use makefiles.</td></tr>
</table></div>
<p>For example, define two subdirectories, both of which reside in a different directory than the <code>SUBDIRS</code> value, and one of the subdirectories must be built before the other:</p>
<pre class="cpp">

  SUBDIRS += my_executable my_library
  my_executable.subdir = app
  my_executable.depends = my_library
  my_library.subdir = lib

</pre>
<a name="target"></a><a name="target"></a>
<h2 id="target">TARGET</h2>
<p>Specifies the name of the target file. Contains the base name of the project file by default.</p>
<p>For example:</p>
<pre class="cpp">

  TEMPLATE = app
  TARGET = myapp
  SOURCES = main.cpp

</pre>
<p>The project file above would produce an executable named <code>myapp</code> on unix and <code>myapp.exe</code> on Windows.</p>
<a name="target-ext"></a>
<h2 id="target-ext">TARGET_EXT</h2>
<p>Specifies the extension of <code>TARGET</code>. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="target-x"></a>
<h2 id="target-x">TARGET_x</h2>
<p>Specifies the extension of <code>TARGET</code> with a major version number. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="target-x-y-z"></a>
<h2 id="target-x-y-z">TARGET_x.y.z</h2>
<p>Specifies the extension of <code>TARGET</code> with a version number. The value of this variable is typically handled by qmake or <a href="qmake-variable-reference.html#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="template"></a><a name="template"></a>
<h2 id="template">TEMPLATE</h2>
<p>Specifies the name of the template to use when generating the project. The allowed values are:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >app</td><td >Creates a Makefile for building applications (the default). See <a href="qmake-common-projects.html#building-an-application">Building an Application</a> for more information.</td></tr>
<tr valign="top" class="even"><td >lib</td><td >Creates a Makefile for building libraries. See <a href="qmake-common-projects.html#building-a-library">Building a Library</a> for more information.</td></tr>
<tr valign="top" class="odd"><td >subdirs</td><td >Creates a Makefile for building targets in subdirectories. The subdirectories are specified using the <a href="qmake-variable-reference.html#subdirs">SUBDIRS</a> variable.</td></tr>
<tr valign="top" class="even"><td >aux</td><td >Creates a Makefile for not building anything. Use this if no compiler needs to be invoked to create the target; for instance, because your project is written in an interpreted language.<p><b>Note: </b>This template type is only available for Makefile-based generators. In particular, it will not work with the vcxproj and Xcode generators.</p></td></tr>
<tr valign="top" class="odd"><td >vcapp</td><td >Windows only. Creates an application project for Visual Studio. See <a href="qmake-platform-notes.html#creating-visual-studio-project-files">Creating Visual Studio Project Files</a> for more information.</td></tr>
<tr valign="top" class="even"><td >vclib</td><td >Windows only. Creates a library project for Visual Studio.</td></tr>
</table></div>
<p>For example:</p>
<pre class="cpp">

  TEMPLATE = lib
  SOURCES = main.cpp
  TARGET = mylib

</pre>
<p>The template can be overridden by specifying a new template type with the <code>-t</code> command line option. This overrides the template type <i>after</i> 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 <code>-t</code> option.</p>
<a name="translations"></a>
<h2 id="translations">TRANSLATIONS</h2>
<p>Specifies a list of translation (.ts) files that contain translations of the user interface text into non-native languages.</p>
<p>See the <a href="../qtlinguist/qtlinguist-index.html">Qt Linguist Manual</a> for more information about internationalization (i18n) and localization (l10n) with Qt.</p>
<a name="ui-dir"></a><a name="ui-dir"></a>
<h2 id="ui-dir">UI_DIR</h2>
<p>Specifies the directory where all intermediate files from uic should be placed.</p>
<p>For example:</p>
<pre class="cpp">

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

</pre>
<a name="version"></a><a name="version"></a>
<h2 id="version">VERSION</h2>
<p>Specifies the version number of the application if the <code>app</code> <a href="qmake-variable-reference.html#template">template</a> is specified or the version number of the library if the <code>lib</code> template is specified.</p>
<p>On Windows, triggers auto-generation of an .rc file if the <a href="qmake-variable-reference.html#rc-file">RC_FILE</a> and <a href="qmake-variable-reference.html#res-file">RES_FILE</a> variables are not set. The generated .rc file will have the FILEVERSION and PRODUCTVERSION entries filled with major, minor, patch level, and build number. Each number must be in the range from 0 to 65535. More details about the generation of .rc files can be found in the <a href="qmake-platform-notes.html">Platform Notes</a>.</p>
<p>For example:</p>
<pre class="cpp">

  win32:VERSION = 1.2.3.4 # major.minor.patch.build
  else:VERSION = 1.2.3    # major.minor.patch

</pre>
<a name="version-pe-header"></a>
<h2 id="version-pe-header">VERSION_PE_HEADER</h2>
<p>Windows only. Specifies the version number, that the Windows linker puts into the header of the .exe or .dll file via the /VERSION option. Only a major and minor version may be specified. If <a href="qmake-variable-reference.html#version-pe-header">VERSION_PE_HEADER</a> is not set, it falls back to the major and minor version from <a href="qmake-variable-reference.html#version">VERSION</a> (if set).</p>
<pre class="cpp">

  VERSION_PE_HEADER = 1.2

</pre>
<a name="ver-maj"></a>
<h2 id="ver-maj">VER_MAJ</h2>
<p>Specifies the major version number of the library if the <code>lib</code> <a href="qmake-variable-reference.html#template">template</a> is specified.</p>
<a name="ver-min"></a>
<h2 id="ver-min">VER_MIN</h2>
<p>Specifies the minor version number of the library if the <code>lib</code> <a href="qmake-variable-reference.html#template">template</a> is specified.</p>
<a name="ver-pat"></a>
<h2 id="ver-pat">VER_PAT</h2>
<p>Specifies the patch version number of the library if the <code>lib</code> <a href="qmake-variable-reference.html#template">template</a> is specified.</p>
<a name="vpath"></a>
<h2 id="vpath">VPATH</h2>
<p>Tells qmake where to search for files it cannot open. For example, if qmake looks for <code>SOURCES</code> and finds an entry that it cannot open, it looks through the entire VPATH list to see if it can find the file on its own.</p>
<p>See also <a href="qmake-variable-reference.html#dependpath">DEPENDPATH</a>.</p>
<a name="winrt-manifest"></a><a name="winrt-manifest"></a>
<h2 id="winrt-manifest">WINRT_MANIFEST</h2>
<p>Specifies parameters to be passed to the application manifest on <a href="../qtdoc/winrt-support.html">Windows Runtime</a>. The allowed values are:</p>
<div class="table"><table class="generic">
 <thead><tr class="qt-style"><th >Member</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >architecture</td><td >The target architecture. Defaults to <code>VCPROJ_ARCH</code>.</td></tr>
<tr valign="top" class="even"><td >background</td><td >Tile background color. Defaults to <code>green</code>.</td></tr>
<tr valign="top" class="odd"><td >capabilities</td><td >Specifies capabilities to add to the capability list.</td></tr>
<tr valign="top" class="even"><td >capabilities_device</td><td >Specifies device capabilities to add to the capability list (location, webcam, and so on).</td></tr>
<tr valign="top" class="odd"><td >CONFIG</td><td >Specifies additional flags for processing the input manifest file. Currently, <code>verbatim</code> is the only available option.</td></tr>
<tr valign="top" class="even"><td >default_language</td><td >The default language code of the application. Defaults to &quot;en&quot;.</td></tr>
<tr valign="top" class="odd"><td >dependencies</td><td >Specifies dependencies required by the package.</td></tr>
<tr valign="top" class="even"><td >description</td><td >Package description. Defaults to <code>Default package description</code>.</td></tr>
<tr valign="top" class="odd"><td >foreground</td><td >Tile foreground (text) color. Defaults to <code>light</code>. This option is only available for Windows Store apps on Windows 8 and Windows RT.</td></tr>
<tr valign="top" class="even"><td >iconic_tile_icon</td><td >Image file for the <code>iconic</code> tile template icon. Default provided by the mkspec.</td></tr>
<tr valign="top" class="odd"><td >iconic_tile_small</td><td >Image file for the small <code>iconic</code> tile template logo. Default provided by the mkspec.</td></tr>
<tr valign="top" class="even"><td >identity</td><td >The unique ID of the app. Defaults to reusing the existing generated manifest's UUID, or generates a new UUID if none is present.</td></tr>
<tr valign="top" class="odd"><td >logo_30x30</td><td >Logo image file of size 30x30 pixels. This is not supported on Windows Phone.</td></tr>
<tr valign="top" class="even"><td >logo_41x41</td><td >Logo image file of size 41x41 pixels. This is only supported on Windows Phone.</td></tr>
<tr valign="top" class="odd"><td >logo_70x70</td><td >Logo image file of size 70x70 pixels. This is not supported on Windows Phone.</td></tr>
<tr valign="top" class="even"><td >logo_71x71</td><td >Logo image file of size 71x71 pixels. This is only supported on Windows Phone.</td></tr>
<tr valign="top" class="odd"><td >logo_150x150</td><td >Logo image file of size 150x150 pixels. This is supported on all Windows Store App platforms.</td></tr>
<tr valign="top" class="even"><td >logo_310x150</td><td >Logo image file of size 310x150 pixels. This is supported on all Windows Store App platforms.</td></tr>
<tr valign="top" class="odd"><td >logo_310x310</td><td >Logo image file of size 310x310 pixels. This is supported on all Windows Store App platforms.</td></tr>
<tr valign="top" class="even"><td >logo_620x300</td><td >Splash screen image file of size 620x300 pixels. This is not supported on Windows Phone.</td></tr>
<tr valign="top" class="odd"><td >logo_480x800</td><td >Splash screen image file of size 480x800 pixels. This is only supported on Windows Phone.</td></tr>
<tr valign="top" class="even"><td >logo_large</td><td >Large logo image file. This has to be 150x150 pixels. Supported on all Windows Store App platforms. Default provided by the mkspec.</td></tr>
<tr valign="top" class="odd"><td >logo_medium</td><td >Medium logo image file. For Windows Phone the image must have a pixel size of 71x71, for other Windows Store App platforms 70x70. Default provided by the mkspec.</td></tr>
<tr valign="top" class="even"><td >logo_small</td><td >Small logo image file. For Windows Phone the image must have a pixel size of 44x44, for other Windows Store App platforms 30x30. Default provided by the mkspec.</td></tr>
<tr valign="top" class="odd"><td >logo_splash</td><td >Splash screen image file. For Windows Phone the image must have a pixel size of 480x800, for other Windows Store App platforms 620x300. Default provided by the mkspec.</td></tr>
<tr valign="top" class="even"><td >logo_store</td><td >Logo image file for Windows Store. Default provided by the mkspec.</td></tr>
<tr valign="top" class="odd"><td >logo_wide</td><td >Wide logo image file. This has to be 310x150 pixels. Supported on all Windows Store App platforms. Default provided by the mkspec.</td></tr>
<tr valign="top" class="even"><td >name</td><td >The name of the package as displayed to the user. Defaults to TARGET.</td></tr>
<tr valign="top" class="odd"><td >phone_product_id</td><td >The GUID of the product. Defaults to the value of <a href="qmake-variable-reference.html#winrt-manifest">WINRT_MANIFEST</a>.identity. (Windows Phone only)</td></tr>
<tr valign="top" class="even"><td >phone_publisher_id</td><td >The GUID of the publisher. Defaults to an invalid GUID. (Windows Phone only)</td></tr>
<tr valign="top" class="odd"><td >publisher</td><td >Display name of the publisher. Defaults to <code>Default publisher display name</code>.</td></tr>
<tr valign="top" class="even"><td >publisher_id</td><td >The publisher's distinguished name (default: <code>CN=MyCN</code>).</td></tr>
<tr valign="top" class="odd"><td >target</td><td >The name of the target (.exe). Defaults to TARGET.</td></tr>
<tr valign="top" class="even"><td >version</td><td >The version number of the package. Defaults to <code>1.0&#x2e;0&#x2e;0</code>.</td></tr>
<tr valign="top" class="odd"><td >minVersion</td><td >The minimum required Windows version to run the package. Defaults to the environment variable <code>UCRTVersion</code>.</td></tr>
<tr valign="top" class="even"><td >maxVersionTested</td><td >The maximum Windows version the package has been tested against. Defaults to <code>WINRT_MANIFEST.minVersion</code></td></tr>
</table></div>
<p>You can use any combination of those values.</p>
<p>For example:</p>
<pre class="cpp">

  WINRT_MANIFEST<span class="operator">.</span>publisher <span class="operator">=</span> MyCompany
  WINRT_MANIFEST<span class="operator">.</span>logo_store <span class="operator">=</span> someImage<span class="operator">.</span>png
  WINRT_MANIFEST<span class="operator">.</span>capabilities <span class="operator">+</span><span class="operator">=</span> internetClient
  WINRT_MANIFEST<span class="operator">.</span>capabilities_device <span class="operator">+</span><span class="operator">=</span> location

</pre>
<p>Additionally, an input manifest file can be specified by using <a href="qmake-variable-reference.html#winrt-manifest">WINRT_MANIFEST</a>.</p>
<p>For example:</p>
<pre class="cpp">

  WINRT_MANIFEST <span class="operator">=</span> someManifest<span class="operator">.</span>xml<span class="operator">.</span>in

</pre>
<p>In case the input manifest file should not be processed and only copied to the target directory, the verbatim configuration needs to be set.</p>
<pre class="cpp">

  WINRT_MANIFEST <span class="operator">=</span> someManifest<span class="operator">.</span>xml<span class="operator">.</span>in
  WINRT_MANIFEST<span class="operator">.</span>CONFIG <span class="operator">+</span><span class="operator">=</span> verbatim

</pre>
<p><b>Note: </b>The required image sizes of <i>logo_small</i>, <i>logo_medium</i>, and <i>logo_large</i> depend on the target platform. The general descriptions are overwritten if a description that specifies the size is provided.</p><a name="yaccsources"></a><a name="yaccsources"></a>
<h2 id="yaccsources">YACCSOURCES</h2>
<p>Specifies 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.</p>
<p>For example:</p>
<pre class="cpp">

  YACCSOURCES = moc.y

</pre>
<a name="pro-file"></a>
<h2 id="pro-file">_PRO_FILE_</h2>
<p>Contains the path to the project file in use.</p>
<p>For example, the following line causes the location of the project file to be written to the console:</p>
<pre class="cpp">

  message($$_PRO_FILE_)

</pre>
<p><b>Note: </b>Do not attempt to overwrite the value of this variable.</p><a name="pro-file-pwd"></a>
<h2 id="pro-file-pwd">_PRO_FILE_PWD_</h2>
<p>Contains the path to the directory containing the project file in use.</p>
<p>For example, the following line causes the location of the directory containing the project file to be written to the console:</p>
<pre class="cpp">

  message($$_PRO_FILE_PWD_)

</pre>
<p><b>Note: </b>Do not attempt to overwrite the value of this variable.</p></div>
<!-- @@@qmake-variable-reference.html -->
<p class="naviNextPrevious footerNavi">
<a class="prevPage" href="qmake-reference.html">Reference</a>
<span class="naviSeparator">  &#9702;  </span>
<a class="nextPage" href="qmake-function-reference.html">Replace Functions</a>
</p>
        </div>
       </div>
   </div>
   </div>
</div>
<div class="footer">
   <p>
   <acronym title="Copyright">&copy;</acronym> 2018 The Qt Company Ltd.
   Documentation contributions included herein are the copyrights of
   their respective owners.<br/>    The documentation provided herein is licensed under the terms of the    <a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation    License version 1.3</a> as published by the Free Software Foundation.<br/>    Qt and respective logos are trademarks of The Qt Company Ltd.     in Finland and/or other countries worldwide. All other trademarks are property
   of their respective owners. </p>
</div>
</body>
</html>