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
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685
5686
5687
5688
5689
5690
5691
5692
5693
5694
5695
5696
5697
5698
5699
5700
5701
5702
5703
5704
5705
5706
5707
5708
5709
5710
5711
5712
5713
5714
5715
5716
5717
5718
5719
5720
5721
5722
5723
5724
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833
5834
5835
5836
5837
5838
5839
5840
5841
5842
5843
5844
5845
5846
5847
5848
5849
5850
5851
5852
5853
5854
5855
5856
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876
5877
5878
5879
5880
5881
5882
5883
5884
5885
5886
5887
5888
5889
5890
5891
5892
5893
5894
5895
5896
5897
5898
5899
5900
5901
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917
5918
5919
5920
5921
5922
5923
5924
5925
5926
5927
5928
5929
5930
5931
5932
5933
5934
5935
5936
5937
5938
5939
5940
5941
5942
5943
5944
5945
5946
5947
5948
5949
5950
5951
5952
5953
5954
5955
5956
5957
5958
5959
5960
5961
5962
5963
5964
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975
5976
5977
5978
5979
5980
5981
5982
5983
5984
5985
5986
5987
5988
5989
5990
5991
5992
5993
5994
5995
5996
5997
5998
5999
6000
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
6018
6019
6020
6021
6022
6023
6024
6025
6026
6027
6028
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044
6045
6046
6047
6048
6049
6050
6051
6052
6053
6054
6055
6056
6057
6058
6059
6060
6061
6062
6063
6064
6065
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106
6107
6108
6109
6110
6111
6112
6113
6114
6115
6116
6117
6118
6119
6120
6121
6122
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149
6150
6151
6152
6153
6154
6155
6156
6157
6158
6159
6160
6161
6162
6163
6164
6165
6166
6167
6168
6169
6170
6171
6172
6173
6174
6175
6176
6177
6178
6179
6180
6181
6182
6183
6184
6185
6186
6187
6188
6189
6190
6191
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212
6213
6214
6215
6216
6217
6218
6219
6220
6221
6222
6223
6224
6225
6226
6227
6228
6229
6230
6231
6232
6233
6234
6235
6236
6237
6238
6239
6240
6241
6242
6243
6244
6245
6246
6247
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
6273
6274
6275
6276
6277
6278
6279
6280
6281
6282
6283
6284
6285
6286
6287
6288
6289
6290
6291
6292
6293
6294
6295
6296
6297
6298
6299
6300
6301
6302
6303
6304
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323
6324
6325
6326
6327
6328
6329
6330
6331
6332
6333
6334
6335
6336
6337
6338
6339
6340
6341
6342
6343
6344
6345
6346
6347
6348
6349
6350
6351
6352
6353
6354
6355
6356
6357
6358
6359
6360
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386
6387
6388
6389
6390
6391
6392
6393
6394
6395
6396
6397
6398
6399
6400
6401
6402
6403
6404
6405
6406
6407
6408
6409
6410
6411
6412
6413
6414
6415
6416
6417
6418
6419
6420
6421
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439
6440
6441
6442
6443
6444
6445
6446
6447
6448
6449
6450
6451
6452
6453
6454
6455
6456
6457
6458
6459
6460
6461
6462
6463
6464
6465
6466
6467
6468
6469
6470
6471
6472
6473
6474
6475
6476
6477
6478
6479
6480
6481
6482
6483
6484
6485
6486
6487
6488
6489
6490
6491
6492
6493
6494
6495
6496
6497
6498
6499
6500
6501
6502
6503
6504
6505
6506
6507
6508
6509
6510
6511
6512
6513
6514
6515
6516
6517
6518
6519
6520
6521
6522
6523
6524
6525
6526
6527
6528
6529
6530
6531
6532
6533
6534
6535
6536
6537
6538
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555
6556
6557
6558
6559
6560
6561
6562
6563
6564
6565
6566
6567
6568
6569
6570
6571
6572
6573
6574
6575
6576
6577
6578
6579
6580
6581
6582
6583
6584
6585
6586
6587
6588
6589
6590
6591
6592
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6616
6617
6618
6619
6620
6621
6622
6623
6624
6625
6626
6627
6628
6629
6630
6631
6632
6633
6634
6635
6636
6637
6638
6639
6640
6641
6642
6643
6644
6645
6646
6647
6648
6649
6650
6651
6652
6653
6654
6655
6656
6657
6658
6659
6660
6661
6662
6663
6664
6665
6666
6667
6668
6669
6670
6671
6672
6673
6674
6675
6676
6677
6678
6679
6680
6681
6682
6683
6684
6685
6686
6687
6688
6689
6690
6691
6692
6693
6694
6695
6696
6697
6698
6699
6700
6701
6702
6703
6704
6705
6706
6707
6708
6709
6710
6711
6712
6713
6714
6715
6716
6717
6718
6719
6720
6721
6722
6723
6724
6725
6726
6727
6728
6729
6730
6731
6732
6733
6734
6735
6736
6737
6738
6739
6740
6741
6742
6743
6744
6745
6746
6747
6748
6749
6750
6751
6752
6753
6754
6755
6756
6757
6758
6759
6760
6761
6762
6763
6764
6765
6766
6767
6768
6769
6770
6771
6772
6773
6774
6775
6776
6777
6778
6779
6780
6781
6782
6783
6784
6785
6786
6787
6788
6789
6790
6791
6792
6793
6794
6795
6796
6797
6798
6799
6800
6801
6802
6803
6804
6805
6806
6807
6808
6809
6810
6811
6812
6813
6814
6815
6816
6817
6818
6819
6820
6821
6822
6823
6824
6825
6826
6827
6828
6829
6830
6831
6832
6833
6834
6835
6836
6837
6838
6839
6840
6841
6842
6843
6844
6845
6846
6847
6848
6849
6850
6851
6852
6853
6854
6855
6856
6857
6858
6859
6860
6861
6862
6863
6864
6865
6866
6867
6868
6869
6870
6871
6872
6873
6874
6875
6876
6877
6878
6879
6880
6881
6882
6883
6884
6885
6886
6887
6888
6889
6890
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
6902
6903
6904
6905
6906
6907
6908
6909
6910
6911
6912
6913
6914
6915
6916
6917
6918
6919
6920
6921
6922
6923
6924
6925
6926
6927
6928
6929
6930
6931
6932
6933
6934
6935
6936
6937
6938
6939
6940
6941
6942
6943
6944
6945
6946
6947
6948
6949
6950
6951
6952
6953
6954
6955
6956
6957
6958
6959
6960
6961
6962
6963
6964
6965
6966
6967
6968
6969
6970
6971
6972
6973
6974
6975
6976
6977
6978
6979
6980
6981
6982
6983
6984
6985
6986
6987
6988
6989
6990
6991
6992
6993
6994
6995
6996
6997
6998
6999
7000
7001
7002
7003
7004
7005
7006
7007
7008
7009
7010
7011
7012
7013
7014
7015
7016
7017
7018
7019
7020
7021
7022
7023
7024
7025
7026
7027
7028
7029
7030
7031
7032
7033
7034
7035
7036
7037
7038
7039
7040
7041
7042
7043
7044
7045
7046
7047
7048
7049
7050
7051
7052
7053
7054
7055
7056
7057
7058
7059
7060
7061
7062
7063
7064
7065
7066
7067
7068
7069
7070
7071
7072
7073
7074
7075
7076
7077
7078
7079
7080
7081
7082
7083
7084
7085
7086
7087
7088
7089
7090
7091
7092
7093
7094
7095
7096
7097
7098
7099
7100
7101
7102
7103
7104
7105
7106
7107
7108
7109
7110
7111
7112
7113
7114
7115
7116
7117
7118
7119
7120
7121
7122
7123
7124
7125
7126
7127
7128
7129
7130
7131
7132
7133
7134
7135
7136
7137
7138
7139
7140
7141
7142
7143
7144
7145
7146
7147
7148
7149
7150
7151
7152
7153
7154
7155
7156
7157
7158
7159
7160
7161
7162
7163
7164
7165
7166
7167
7168
7169
7170
7171
7172
7173
7174
7175
7176
7177
7178
7179
7180
7181
7182
7183
7184
7185
7186
7187
7188
7189
7190
7191
7192
7193
7194
7195
7196
7197
7198
7199
7200
7201
7202
7203
7204
7205
7206
7207
7208
7209
7210
7211
7212
7213
7214
7215
7216
7217
7218
7219
7220
7221
7222
7223
7224
7225
7226
7227
7228
7229
7230
7231
7232
7233
7234
7235
7236
7237
7238
7239
7240
7241
7242
7243
7244
7245
7246
7247
7248
7249
7250
7251
7252
7253
7254
7255
7256
7257
7258
7259
7260
7261
7262
7263
7264
7265
7266
7267
7268
7269
7270
7271
7272
7273
7274
7275
7276
7277
7278
7279
7280
7281
7282
7283
7284
7285
7286
7287
7288
7289
7290
7291
7292
7293
7294
7295
7296
7297
7298
7299
7300
7301
7302
7303
7304
7305
7306
7307
7308
7309
7310
7311
7312
7313
7314
7315
7316
7317
7318
7319
7320
7321
7322
7323
7324
7325
7326
7327
7328
7329
7330
7331
7332
7333
7334
7335
7336
7337
7338
7339
7340
7341
7342
7343
7344
7345
7346
7347
7348
7349
7350
7351
7352
7353
7354
7355
7356
7357
7358
7359
7360
7361
7362
7363
7364
7365
7366
7367
7368
7369
7370
7371
7372
7373
7374
7375
7376
7377
7378
7379
7380
7381
7382
7383
7384
7385
7386
7387
7388
7389
7390
7391
7392
7393
7394
7395
7396
7397
7398
7399
7400
7401
7402
7403
7404
7405
7406
7407
7408
7409
7410
7411
7412
7413
7414
7415
7416
7417
7418
7419
7420
7421
7422
7423
7424
7425
7426
7427
7428
7429
7430
7431
7432
7433
7434
7435
7436
7437
7438
7439
7440
7441
7442
7443
7444
7445
7446
7447
7448
7449
7450
7451
7452
7453
7454
7455
7456
7457
7458
7459
7460
7461
7462
7463
7464
7465
7466
7467
7468
7469
7470
7471
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content=
"HTML Tidy for Linux (vers 1 September 2005), see www.w3.org">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta http-equiv="Content-Style-Type" content="text/css">
<meta name="id" content=
"$Id: MakeProjectCreator.html 1996 2011-04-05 13:04:47Z hudson_d $">
<link rel="STYLESHEET" href="MakeProjectCreator.css" charset="ISO-8859-1"
type="text/css">
<title>MPC</title>
</head>
<body bgcolor="#FFFFFF">
<div>
<h2 class="ChapterNum"> </h2>
</div>
<div>
<h1 class="Head1">The Makefile, Project, and Workspace Creator (MPC)</h1>
<div>
<h3 class="Head2">Introduction</h3>
<hr>
<ul>
<li class="Body">Maintaining multiple build tool files for a
multi-platform project can be quite a challenge, especially when the
project structure and platforms are constantly changing and evolving.
A project may support Makefiles, Visual C++ project files, Borland
Makefiles, and many others. Adding files, deleting files, changing
project options or even changing the name of the target within your
project will require you to expend time updating each build tool
file. What you need instead is a single location to store project
specific information to avoid repetitious, tedious modifications to
multiple build tool files. This is where Makefile Project Creator
(MPC) comes into the picture.</li>
<li class="Body">MPC can be used to generate build tool specific
project files from a generic mpc file. The MPC project file is a
collection of source files that make up a single build target. MPC
uses platform specific input along with mpc files and generates build
tool specific files like makefiles, Visual C++ workspace and project
files, Visual Studio solution and project files, etc.</li>
<li class="Body">MPC provides many advantages over the build tool
files it replaces. It provides mechanisms for minimizing maintenance
of project build files. It does this through support for project
inheritance and defaults for all aspects of a project, and the syntax
is simple and easy to use and maintain. These and other features will
be discussed in detail in the following sections. A complete example
of the use of MPC is shown in the <a href=
"MakeProjectCreator.html#ExampleMPCFile" class="XRef">Example MPC
File</a> section.</li>
</ul>
</div>
<div>
<h3 class="Head2">Using MPC</h3>
<hr>
<ul>
<li class="Body">An MPC project is a set of parameters that describe
an individual build target (such as a library or executable). These
parameters include the target name, include paths, source files,
header files, etc. One or more projects can be defined within a
single mpc file. An MPC workspace is just an arbitrary collection of
projects.</li>
<li class="Body">Projects can be generated (without workspaces) by
using the mpc.pl script. Multiple mpc files can be passed to this
script. If no mpc files are passed to the script, it will search for
project-related files (such as source files, header files, etc.) and
incorporate them into a default project.</li>
<li class="Body"><a name="Figure 1-2"></a>This diagram shows a
high-level view of project file generation using mpc.pl.</li>
<li style="list-style: none">
<h6 class="FigTitle">Generating projects with mpc.pl</h6>
<table border="1" summary="Generating projects with mpc.pl">
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
<div>
<img src="images/mpc.gif" alt=
"Generating projects with mpc.pl">
</div>
</td>
</tr>
</table>
</li>
<li class="Body">To generate workspaces, you must run <em class=
"Code">mwc.pl</em>. This script will generate projects from mpc files
and create a workspace based on those mpc files. If no mwc files are
passed to the script, it will search in the current directory and its
subdirectories for all mpc files and incorporate them into a single
workspace.</li>
<li class="Body">For make based project types (make, gnuace, bmake,
nmake), a workspace is just a top-level makefile. But, for graphical
interfaces such as Visual Studio, a workspace is the top-level file
that groups all of the project files together.</li>
<li class="Body">The following diagram shows a high-level view of
workspace file generation using mwc.pl.</li>
<li style="list-style: none">
<h6 class="FigTitle">Generating workspaces with mwc.pl</h6>
<table border="1" summary="Generating workspaces with mwc.pl">
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
<div>
<img src="images/mwc.gif" alt=
"Generating workspaces with mwc.pl">
</div>
</td>
</tr>
</table>
</li>
</ul>
<div>
<h4 class="Head3">Supported Build Tools</h4>
<ul>
<li class="Body">MPC generates workspaces and projects for use with
many build tools. This table lists the MPC types (used with
mpc’s <em class="Code">-type</em> option) and their
associated build tools.</li>
<li style="list-style: none">
<h6 class="NumberedTableTitle">MPC Types</h6>
<table border="1" summary="MPC Types">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Type</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Build Tool</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">automake</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">GNU Automake.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">bcb2007</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Borland C++ Builder 2007.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">bcb2009</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">CodeGear C++ Builder 2009.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">bds4</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Support for Borland Developer Studio 4
is incomplete.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">bmake</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Borland Make.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">cc</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Code Composer Studio 2.0</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">
<a href="CDT6.html">cdt6</a></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Eclipse CDT 6 (for Eclipse "Galileo" 3.5)
</p></td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">
<a href="CDT6.html"><!--CDT6.html describes cdt7 as well
-->cdt7</a></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Eclipse CDT 7 (for Eclipse "Helios" 3.6)
</p></td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">em3</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">eMbedded Visual C++ 3.00 and 4.00.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">ghs</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Green Hills C++ Builder.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">gnuace</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">GNU Make for ACE/TAO/CIAO only
(ACE/TAO/CIAO extension).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">html</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">html pages are generated for
visualization of project information.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">make</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Generic make. The makefiles generated
by this project type can be used with any version of make.
However, due to configuration issues, it should not be used
with ACE or TAO.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">nmake</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Microsoft NMake.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">
<a href="RpmSpec.html">rpmspec</a></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">RPM packaging .spec files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">sle</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Support for Visual SlickEdit is
incomplete.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">vc6</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual C++ 6.0.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">vc7</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio .NET 2002.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">vc71</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio .NET 2003.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">vc8</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio 2005.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">vc9</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio 2008.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode">vc10</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio 2010.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode"><a href="WB26.html">
wb26</a></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Wind River Workbench 2.6.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class="TableCode"><a href="WB30.html">
wb30</a></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Wind River Workbench 3.0.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">wix</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Wix toolset for .msi creation.</p>
</td>
</tr>
</table>
</li>
</ul>
</div>
<div>
<h4 class="Head3">Command Line</h4>
<ul>
<li class="BodyNoLead">The command line options for the workspace
creator (<em class="Code">mwc.pl</em>) and the project creator
(<em class="Code">mpc.pl</em>) are exactly the same. The project
creator is used to generate one or more separate projects by
passing mpc files to it on the command line. The workspace creator
is used to generate one or more workspaces and the projects related
to those workspaces.</li>
<li class="Body">The table below describes each option with the
more commonly used options in bold and project specific options in
italics.</li>
<li style="list-style: none">
<h6 class="NumberedTableTitle"><a name=
"Command Line Options"></a>Command Line Options</h6>
<table border="1" summary="Command Line Options">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Option</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-base</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option allows the user to force
every project to inherit from a specified base project. This
option can be used multiple times to force multiple
inheritance upon a project.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-complete</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This hidden option can be used to
generate a tcsh <em class="TableCode">complete</em> command
that allows a user of the tcsh shell to complete on options
as well as file names.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-exclude</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If this option is used with <em class=
"Code">mwc.pl</em> , the directories or mwc files provided
in a comma separated list will be excluded when searching
for mpc files. Each element provided for exclusion should
be relative to the starting directory. This option has no
effect when used with <em class="Code">mpc.pl</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-expand_vars</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option instructs MPC to perform
direct replacement of $() variables with the values from
the environment (if the <em class="Code">-use_env</em>
option is used) or the values specified by the <em class=
"Code">-relative</em> option.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-feature_file</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option allows the user to override
the default feature file (<em class="Code">MPC/config/</em>
<em class="Code">default.features</em> or <em class=
"Code">ACE_wrappers/bin/MakeProjectCreator/config/default.features</em>
) which may or may not exist. This file can be used to
override feature values specified in the <em class=
"Code">global.features</em> file located in the <em class=
"Code">config</em> directory. Feature files are described
in the <a href="MakeProjectCreator.html#TheFeatureFile"
class="XRef">Feature File</a> section.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-features</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies the feature list to set
before processing. This is a comma separated list and
should contain no spaces. The -features option can be
used multiple times on the same command line, the
effect is the same as if the parameters had been
specified with a single -features options, with the
parameters joined by commas.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-for_eclipse</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Allows generated makefiles to be used
with Eclipse.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-gendot</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A .dot file, for use with Graphviz,
will be created for each workspace processed.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-genins</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option instructs MPC to generate
an “install” file after processing each
project. These “install” files can be used with
the prj_install.pl script which will copy portions of the
project related files into a user specified location.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-gfeature_file</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies the global feature file. The
default global feature file is <em class=
"Code">global.features</em> found in the <em class=
"Code">config</em> directory.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-global</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option specifies the global input
file. Values stored within this base project are applied to
all generated projects. The default value is <em class=
"Code">ACE_wrappers/bin/MakeProjectCreator/global.mpb or
MPC/config/global.mpb</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-hierarchy</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If this option is used with <em class=
"Code">mwc.pl</em> , it will generate a workspace at each
directory between the directory in which it is run and the
location of a processed mpc file. This option has no effect
when used with <em class="Code">mpc.pl</em> and is the
default for “make” based workspace types.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">-include</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Include search directories are added
with this option. These search directories are used when
locating base projects, template input files and templates.
It can be used multiple times on the same command line.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-into</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option specifies that all
generated project files will be placed in a mirrored
directory structure. If any project within the
workspace is referenced via a full path, use of this
option is likely to cause problems.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-language</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option is used to specify which
language to assume when generating projects. The default
language is <em class="Code">cplusplus</em>, but <em class=
"Code">csharp</em>, <em class="Code">java</em> and
<em class="Code">vb</em> are also supported.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-make_coexistence</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Make based project types that normally
name the workspace <em class="Code">Makefile</em>
(<em class="Code">bmake</em> or <em class="Code">nmake</em>
) will name the generated output files such that they can
coexist within the same directory. In essence, the
<em class="Code">bmake</em> and <em class="Code">nmake</em>
workspace names will not be <em class="Code">Makefile</em>,
but the name of the workspace followed by the project type
(<em class="Code">.bmake</em> or <em class=
"Code">.nmake</em> ).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-name_modifier</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option allows the user to modify
the output names of projects and workspaces. These are
usually determined by either the mpc or mwc file, but can
be modified using a pattern replacement. The parameter
passed to this option will be used as the pattern and any
asterisks (*) found in the pattern will be replaced with
the project or workspace name depending on which type of
file is being created.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-apply_project</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option is only useful with the
<em class="Code">-name_modifier</em> option. When used in
conjunction with <em class="Code">-name_modifier</em>, the
pattern will be applied to the project name in addition to
the project or workspace name.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-nocomments</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Comments will not be placed in the
generated workspace files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-noreldefs</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option specifies that the default
relative definitions should not be generated. See the
<em class="TableCode">-relative</em> option below.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-notoplevel</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option tells <em class=
"TableCode">mwc.pl</em> to generate all workspace related
project files, but do not generate the associated
workspace. This option tells <em class=
"TableCode">mpc.pl</em> to process all mpc files passed in,
but it will not generate any project files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-recurse</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Search from the current directory for
any input files and process them from the directory in
which they are located.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">-relative</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Relative paths are used to replace
variables enclosed with <em class="TableCode">$()</em>. By
default, any environment variable that ends in <em class=
"TableCode">_ROOT</em> will be automatically used as a
relative path replacement. For more information see
<a href="MakeProjectCreator.html#Additional%20-relative%20information"
class="XRef">the -relative Option.</a>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-relative_file</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option allows you to override the
default relative definitions file, which is default.rel
under the MPC config directory..</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-static</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies that static project files
will be generated from the MPC projects. The default is to
generate dynamic project files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-template</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option allows a user to specify an
alternate template. Each project type has its own template
and this option allows a user to override the default
template.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-ti</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Each project type has a set of template
input files. With this option the default template input
file can be overridden for a particular project type. For
more information see <a href=
"MakeProjectCreator.html#Additional%20-ti%20information"
class="XRef">the -ti Option.</a>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">-type</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option specifies the type of
project or workspace to be generated. It can be specified
multiple times to generate different project types for a
single set of input files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-use_env</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option instructs MPC to replace
all <em class="TableCode">$()</em> instances with the
corresponding environment variable value instead of using
values provided by the -relative option.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-value_project</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Use this option to override an mpc
project assignment from the command line. This can be used
to introduce new name value pairs to a project. However, it
must be a valid project assignment. For more information
see <a href=
"MakeProjectCreator.html#Additional%20-value_project%20information"
class="XRef">the -value_project Option.</a>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">-value_template</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This option can be used to override
existing template input variable values from the command
line. It can not be used to introduce new template input
name value pairs. For more information see <a href=
"MakeProjectCreator.html#Additional%20-value_template%20information"
class="XRef">the -value_template Option.</a>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">-version</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The MPC version is printed and no files
are processed.</p>
</td>
</tr>
</table>
</li>
</ul>
<div>
<h5 class="Head4">Additional Option Descriptions</h5>
<ul>
<li class="BodyNoLead">Some of the options in <a href=
"MakeProjectCreator.html#Command%20Line%20Options" class=
"XRef">Command Line Options</a> require an expanded explanation.
You will find more information on the <em class=
"Code">-relative</em>, <em class="Code">-ti</em>, <em class=
"Code">-value_project</em> and <em class=
"Code">-value_template</em> options below.</li>
</ul>
<div>
<h6 class="Head5"><a name=
"Additional -relative information"></a>The -relative Option.</h6>
<ul>
<li class="BodyNoLead">Some project types do not (completely)
support the idea of accessing environment variables through the
use of <em class="Code">$()</em>, and therefore MPC must ensure
that generated projects are usable in these cases. In order to
avoid the existence of <em class="Code">$()</em> variables
within the generated project files, relative paths are put in
place of those (where possible).</li>
<li class="Body">The <em class="Code">-relative</em> option
takes a single parameter of a name value pair, for
example:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">mwc.pl -relative
PROJ_TOP=/usr/projects/top</p>
<p class="Code"> </p>
</li>
<li class="Body">In above example, if the text <em class=
"Code">"$(PROJ_TOP)</em> " is found as a value for any mpb,
mpc, mpd, or mpt variable then it is replaced by a path that is
relative to <em class="Code">/usr/projects/top</em>. For
example, if an mpc file located under <em class=
"Code">/usr/projects/top/dir</em> contained the following:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">project {</p>
<p class="Code"> includes += $(PROJ_TOP)</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">The generated project file would contain text
similar to:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">CPPFLAGS += -I..</p>
<p class="Code"> </p>
</li>
<li class="Body">The <em class="Code">$(PROJ_TOP)</em> string
was replaced with a directory value that is relative to the
directory in which the mpc file is located.</li>
</ul>
</div>
<div>
<a name="Additional -ti information"></a>
<h6 class="Head5">The -ti Option.</h6>
<ul>
<li class="BodyNoLead">The <em class="Code">-ti</em> option
allows you to identify different template input files based on
the type of target being built. Template input files correspond
to four different categories: <em class="Code">dll</em>,
<em class="Code">lib</em>, <em class="Code">dll_exe</em>, and
<em class="Code">lib_exe</em>. Not all project types
distinguish between the different categories, but the templates
for various project types will be combined with different
template input files, depending on the build target type, to
generate different output.</li>
<li class="Body">To override the default template input file
names, a <em class="Code">-ti</em> option is provided. The
<em class="Code">-ti</em> option takes a single parameter of
the form <em class="Code">type:file</em>. The <em class=
"Code">type</em> is one of the four categories stated above and
the <em class="Code">file</em> is the base name of an mpt file
located somewhere in the include search paths.</li>
<li class="Body">The following example shows a usage of the -ti
option. It says that when generating a static project (lib),
use the <em class="Code">vc7lib</em> template input file and
when generating a dynamic project (dll), use the <em class=
"Code">vc7dll</em> template input file:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">mpc.pl -type vc71 -ti lib:vc7dsplib -ti
dll:vc7dspdll</p>
<p class="Code"> </p>
</li>
<li class="Body">These happen to be the default values for the
<em class="Code">vc71</em> type, but it illustrates that a
different template input can be specified for each
category.</li>
</ul>
</div>
<div>
<a name="Additional -value_project information"></a>
<h6 class="Head5">The -value_project Option.</h6>
<ul>
<li class="BodyNoLead">The <em class="Code">-value_project</em>
option can be useful when the need arises to modify the value
of an MPC variable across one or more mpc files. For example,
if you wanted to generate all of your projects with an
additional include search path you would run the following
command:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">mwc.pl -value_project
includes+=/include/path</p>
<p class="Code"> </p>
</li>
<li class="Body">In the above example, an additional include
search path of <em class="Code">/include/path</em> would be
placed in all generated projects.</li>
</ul>
</div>
<div>
<a name="Additional -value_template information"></a>
<h6 class="Head5">The -value_template Option.</h6>
<ul>
<li class="BodyNoLead">This option modifies existing or adds
new template input name/value pairs. For example, if you wanted
to generate dynamic <em class="Code">vc71</em> projects with
only <em class="Code">Release</em> targets, you would run the
following command:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">mwc.pl -type vc71 -value_template
configurations=Release</p>
<p class="Code"> </p>
</li>
<li class="Body">To find out what template input variables are
defined, see the individual mpd file of interest (<em class=
"Code">$ACE_ROOT/bin/MakeProjectCreator/templates/*.mpd</em>
and <em class="Code">$MPC_ROOT/templates/*.mpd</em> ) and
search for names used within <em class="Code"><%</em> and
<em class="Code">%></em> or use the <em class=
"Code">document_template.pl</em> script described in the
<a href="#Document%20Template%20Script">Template Variable
Documentation</a> section. Names that are not listed as project
keywords (see <a href="MakeProjectCreator.html#82186" class=
"XRef">Assignment Keywords</a>) are template variables.</li>
</ul>
</div>
</div>
</div>
<div>
<h4 class="Head3">Configuration Files</h4>
<ul>
<li class="BodyNoLead">
<h6 class="Head5">Codebase Configuration File</h6>
</li>
<li class="BodyNoLead">This configuration file can be used to
specify alternate locations for the MPC Configuration File
(discussed below). If a <em class="Code">base.cfg</em> is found
underneath the <em class="Code">config</em> directory in the MPC
root directory, it will be read to determine the location of
MPC.cfg based on the directory in which MPC was started.</li>
<li class="Body">For example, if <em class=
"Code">$MPC_ROOT/mwc.pl</em> is run under <em class=
"Code">/foo/bar_root/src</em> and <em class=
"Code">$MPC_ROOT/config/base.cfg</em> contained:</li>
<li class="Body">
<p class="Code"> </p>
<p class="Code">/foo/bar_root = /foo/bar_root/MPC/config</p>
<p class="Code"> </p>
</li>
<li class="Body">MPC would attempt to open and read <em class=
"Code">/foo/bar_root/MPC/config/MPC.cfg</em> as the MPC
Configuration File. If the base configuration file is not present,
MPC will try to use <em class="Code">$MPC_ROOT/config/MPC.cfg</em>
as the MPC Configuration File.</li>
<li class="Body">You may reference environment variables, accessed
via the dollar sign (e.g., <em class="Code">$NAME</em>), on either
side of the equals sign. In either this file or the MPC
Configuration File (see below), an alternate form of environment
variable reference may be used for variables which are not expected
to be defined in all scenarios. These variables use the syntax
<em class="Code">$?NAME</em> instead of <em class="Code">$NAME</em>.
With this syntax, if the environment variable
<em class="Code">NAME</em> is not defined, no error or warning is
printed by MPC, and the substring starting with
<em class="Code">$?NAME</em> until the next whitespace is expanded
to the empty string.</li>
</ul>
<ul>
<li class="BodyNoLead">
<h6 class="Head5">MPC Configuration File</h6>
</li>
<li class="BodyNoLead">In an effort to move away from the use of
environment variables, a configuration file has been introduced.
The configuration file (<em class="Code">MPC.cfg</em>) can contain
settings to provide command line options, control logging and
direct MPC to dynamic project types.</li>
<li class="Body">The following keywords are allowed in the
configuration file.</li>
<li class="Body">
<table border="1" summary="Configuration File Keywords">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Keyword</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">command_line</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Provide additional command line options
to MPC. The value of this setting will be prepended to the
options passed to <em class="Code">mwc.pl</em> or
<em class="Code">mpc.pl</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">default_type</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Provide a single project type (as
specified by the <em class="Code">-type</em> option) as the
default project type.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">dynamic_types</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This comma separated list points to
directories in which MPC will search for Perl modules to
implement additional MPC project types, base projects or
template files. This setting can be used to augment or
replace functionality in MPC. For each suitable directory
found, it will add a <em class="Code">modules</em> include
path for Perl to find modules, add a <em class=
"Code">config</em> include path to locate base projects and
a <em class="Code">template</em> include path to find MPC
templates.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">includes</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Similar to the <em class=
"Code">-include</em> command line option, it adds the list
of comma separated paths to the MPC include search
paths.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">logging</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If this setting contains <em class=
"Code">info=1</em>, informational messages will be printed.
If it contains <em class="Code">warn=1</em>, warning
messages will be printed. If it contains <em class=
"Code">diag=1</em>, diagnostic messages will be printed. If
it contains <em class="Code">debug=1</em>, debug message
will be printed. And lastly, if it contains <em class=
"Code">detail=1</em>, detail messages will be printed. If
it contains none of these, MPC will not print out any
information or warnings when processing projects or
workspaces. Errors are always printed if any are
encountered. The default value is <em class="Code">warn=1,
diag=1, detail=1</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">main_functions</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Provide additional main functions to be
recognized in conjunction with automatic executable project
recognition. The value assigned should be of the form
<em class="Code"><language>:<func name>[,
<language>:<func name>]*</em>. A function can
be specified for all languages by only providing the
function name.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">verbose_ordering</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If this is set, mwc.pl will warn the
user about references to projects in the <em class=
"Code">after</em> keyword that have not been processed.</p>
</td>
</tr>
</table>
</li>
</ul>
</div>
<div>
<h4 class="Head3">Environment Variables</h4>
<ul>
<li class="BodyNoLead">MPC recognizes a few environment variables
that alter the way it performs certain tasks. The sections below
describe each one and the effect it has on MPC.</li>
<li class="Body">The <em class=
"Code">MPC_DEPENDENCY_COMBINED_STATIC_LIBRARY</em> environment
variable only affects the way workspace dependencies are created
for <em class="Emphasis">static</em> projects with the <em class=
"Code">em3</em>, <em class="Code">vc6</em>, <em class=
"Code">vc7</em>, <em class="Code">vc71</em>, vc8, vc9 and
<em class="Code">vc10</em> project types. If this environment
variable is set, MPC will generate inter-project dependencies for
libraries within a single workspace. This is usually not desired
since adding these dependencies in a static workspace has the side
effect of including dependee libraries into the dependent
library.</li>
<li class="Body">The <em class="Code">MPC_GHS_UNIX</em> environment
variable is only meaningful when generating the ghs project files.
By default, the ghs type assumes that it is for Windows. Set this
environment variable prior to running MPC if this is not the
case.</li>
<li class="Body">The <em class="Code">MPC_USE_WIN_COMMANDS</em>
environment variable causes the Windows related pseudo template
variables to be used regardless of the type of project being
generated.</li>
</ul>
</div>
</div>
<div>
<h3 class="Head2">Writing MPC and MWC Files</h3>
<hr>
<ul>
<li class="Body">You may want to familiarize yourself with the
various input files for MPC. The input file types and the syntax of
each are discussed in the sections below.</li>
</ul>
<div>
<h4 class="Head3">Input Files</h4>
<ul>
<li class="BodyNoLead">There are four different input files
associated with MPC. For most users of MPC, the main files of
concern are mpc and mwc files.</li>
</ul>
<div>
<h5 class="Head4">Project Files (mpc)</h5>
<ul>
<li class="BodyNoLead">Project files, those with the <em class=
"Code">mpc</em> extension, contain such things as include paths,
library paths, source files and inter-project dependencies. An
mpc file can contain one or more “projects” each of
which needs to be uniquely named to avoid project generation
errors. Projects represent build targets such as libraries and
executables.</li>
</ul>
</div>
<div>
<h5 class="Head4">Workspace Files (mwc)</h5>
<ul>
<li class="BodyNoLead">Workspaces are defined by providing a list
of mpc files, directories or other mwc files in a single mwc
file. For each mpc file, the Workspace Creator calls upon the
Project Creator to generate the project. After all of the
projects are successfully generated, the tool-specific workspace
is generated containing the projects and any defined
inter-project dependency information (if supported by the build
tool). An mwc file can contain one or more
“workspaces,” each of which needs to be uniquely
named. If no workspace files are provided to the workspace
creator, the current directory is traversed and any mpc files
located will be part of the workspace that is generated.</li>
</ul>
</div>
<div>
<h5 class="Head4">Base Project Files (mpb)</h5>
<ul>
<li class="BodyNoLead">One of the many unique and useful features
of MPC is that the project definition files can use inheritance.
Project inheritance allows a user to set up a base project (mpb
file) that can contain information that is applicable to all
derived projects. Common project attributes, such as include
paths, library paths, and inter-project dependencies, could be
described in this base project and any project that inherits from
it would contain this information as well.</li>
</ul>
</div>
<div>
<h5 class="Head4">Base Workspace Files (mwb)</h5>
<ul>
<li class="BodyNoLead">As with projects, workspaces can also
inherit from other workspaces. A base workspace can provide
workspace information that may be common to other
workspaces.</li>
</ul>
</div>
</div>
<div>
<h4 class="Head3">General Input File Syntax</h4>
<ul>
<li class="BodyNoLead">In this section we discuss the syntax of the
various files. We also describe some of the default values that go
along with these files.</li>
</ul>
<div>
<h5 class="Head4">mwc and mwb</h5>
<ul>
<li class="BodyNoLead">Workspaces can contain individual mpc
files or directories. There can be one or more workspaces defined
within a single mwc file.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">workspace(optional name):
optional_base_workspace {</p>
<p class="Code"> file.mpc</p>
<p class="Code"> directory</p>
<p class="Code"> other.mwc</p>
<p class="Code"> </p>
<p class="Code"> exclude(vc6, vc7, vc71, vc8, vc9,
vc10, nmake) {</p>
<p class="Code"> this_directory</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> exclude(prop:microsoft) {</p>
<p class="Code"> non_microsoft</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> specific(rpmspec) {</p>
<p class="Code"> rpm_version = 1.0</p>
<p class="Code"> }</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="BodyNoLead">A workspace can be given a name. This is
the value given in the parentheses after the keyword <em class=
"Code">workspace</em>. If the workspace is not given a name, the
workspace name is taken from the name of the mwc file without the
extension.</li>
<li class="Body">Workspaces can also inherit from other
workspaces. In the above example, <em class=
"Code">optional_base_workspace</em> would be the base name of an
mwb file with no extension that contains workspace information.
This information would then be included in each workspace that
inherits from it.</li>
<li class="Body">The lines between the curly braces
contain assignments, mpc files, directories, other
workspace files or exclusion sections. For each listed item,
<ul>
<li>an mpc file will be included in the workspace</li>
<li>a directory recursively traversed and any mpc files
found will be included</li>
<li><a name="AggregatedWorkspace"></a>a workspace file will be aggregated into the main workspace.</li>
</ul>
<li class="Body">A workspace can have assignments interspersed
within the directories and mpc files. These assignments modify
the way projects are generated.</li>
<li class="Body">The <em class="Code">cmdline</em> setting can be
used to provide command line options that would normally be
passed to <em class="Code">mwc.pl</em> (see <a href=
"MakeProjectCreator.html#Command%20Line%20Options" class=
"XRef">Command Line Options</a>). However, the <em class=
"Code">-type</em>, <em class="Code">-recurse</em> , <em class=
"Code">-noreldefs</em> , <em class="Code">-make_coexistence</em>,
<em class="Code">-genins</em>, <em class="Code">-into</em> and
<em class="Code">-language</em> options as well as input files
are ignored. Environment variables may be accessed through
<em class="Code">$NAME</em>, where <em class="Code">NAME</em> is
the environment variable name. The <em class="Code">cmdline</em>
assignment may be useful for workspaces that require specific
<em class="Code">mwc.pl</em> options in order to process
correctly.</li>
<li class="Body">The only other setting supported by mwc.pl is
<em class="Code">implicit</em>. If <em class="Code">implicit</em>
is set to <em class="Code">1</em> then default project files are
generated in each directory where no mpc file exists. The
<em class="Code">implicit</em> keyword can also be set to the
name of a base project. In this case, the implicitly generated
project will inherit from the base project specified in the
assignment. Either way, if the directory does not contain files
that can be used within a project, no project is created. Setting
<em class="Code">implicit</em> can be useful when you want to
define specific workspaces, but the MPC defaults are sufficient
for the directories involved within the workspace.</li>
<li class="Body"><a name="workspaceSpecific"></a>Workspaces
support a <em class="Code">specific</em> clause
conceptually and syntactically similar to <a
href="#projectSpecific">the project <em
class="Code">specific</em> clause.</a> Any variables
assigned within the clause are only available to
workspaces, not to projects. Two sorts of assignments are
possible: first are assignments to the keywords
<em class="Code">cmdline</em> and <em class="Code">implicit</em>
and the second are type-specific variables. Consult the
documentation for the type for details on type-specific variables.
Keyword assignments impact the entire workspace, not just the
<em class="Code">specific</em> scope.</li>
<li class="Body">Scoped assignments are assignments that are
associated with specific mpc files or directories listed with the
scope of the assignment. The following example shows a scoped
assignment of <em class="Code">cmdline</em> that only applies to
<em class="Code">one of the mpc files listed in the
workspace</em>. In this example, <em class=
"Code">directory/foo.mpc</em> would be processed as if the
<em class="Code">-static</em> option had been passed on the
command line whereas other directories and mpc files would
not.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">workspace {</p>
<p class="Code"> ...</p>
<p class="Code"> static {</p>
<p class="Code"> cmdline += -static</p>
<p class="Code"> directory/foo.mpc</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> exclude(gnuace, make) {</p>
<p class="Code"> some.mpc</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> // Associate the name "other" with
dir3</p>
<p class="Code"> associate(other) {</p>
<p class="Code"> dir3</p>
<p class="Code"> }</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">Exclusion sections are used to prevent
directories and mpc files from being processed. These excluded
directories and mpc files will be skipped when generating project
files and workspaces. The <em class="Code">exclude</em> keyword
accepts project types as well as properties (see <a href=
"MakeProjectCreator.html#properties" class="XRef">Properties</a>)
within the parentheses (as above), which will cause the workspace
creator to only exclude the listing for particular types. If no
types are provided, exclusion will take place for all project
types.</li>
<li class="Body">The <em class="Code">associate</em> scope
associates a name with one or more directories. This does not add
directories to a workspace, it only makes an association. This
may or may not have an effect on the generated workspace; it
depends solely upon whether the project type supports
associations. Currently <em class="Code">automake</em> is the
only project type that supports associations. Each directory
listed under an association is grouped together and built
conditionally based on the association name.</li>
<li class="Body">Comments are similar to the C++ style comments.
Any text after a double slash (<em class="Code">//</em> ) is
considered a comment.</li>
</ul>
</div>
<div>
<h5 class="Head4">mpc and mpb</h5>
<div>
<h6 class="Head5">Project Declarations</h6>
<ul>
<li class="BodyNoLead">Project declarations are similar to
workspace declarations, but are a bit more complex. An mpc file
can contain one or more “projects” and each project
can inherit from base projects.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">project(optional name): base_project,
another_base_project {</p>
<p class="Code"> exename = client</p>
<p class="Code"> includes += directory_name
other_directory</p>
<p class="Code"> libpaths += /usr/X11R6/lib</p>
<p class="Code"> </p>
<p class="Code"> Header_Files {</p>
<p class="Code"> file1.h</p>
<p class="Code"> file2.h</p>
<p class="Code"> fileN.h</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> Source_Files {</p>
<p class="Code"> file1.cpp</p>
<p class="Code"> file2.cpp</p>
<p class="Code"> fileN.cpp</p>
<p class="Code"> }</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="BodyNoLead">If the optional project name is not
given, then the project name is taken from the name of the mpc
file without the extension. Therefore, if your mpc file is
going to contain multiple projects, it is important to provide
project names to prevent each generated project from
overwriting the other. MPC will issue an error and stop if
duplicate project names are detected.</li>
</ul>
</div>
<div>
<h6 class="Head5">Base Projects</h6>
<ul>
<li class="BodyNoLead">Base projects can be of the extension
<em class="Code">mpb</em> and <em class="Code">mpc</em>. If a
file with the name of the base project with an <em class=
"Code">mpb</em> or <em class="Code">mpc</em> extension cannot
be found within the mpc include search path, a fatal error is
issued and processing halts.</li>
</ul>
</div>
<div>
<h6 class="Head5">Assignment Keywords</h6>
<ul>
<li class="BodyNoLead">This table shows the keywords that can
be used in an assignment (i.e., <em class="Code">=</em>,
<em class="Code">+=</em> or <em class="Code">-=</em> ) within
an mpc file. The most commonly used keywords are shown in bold
face.</li>
<li style="list-style: none">
<h6 class="NumberedTableTitle"><a name="82186"></a>Assignment
Keywords</h6>
<table border="1" summary="Assignment Keywords">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Keyword</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">after</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies that this project must be
built after 1 or more project names listed.</p>
<p class="Tbl-Body">An extended syntax is available
in order to associate name-value pairs with a
dependency: <em class="Code"><project
name[:name=value]></em><br>
These name-value pairs may be used in the creation
of the dependencies of the project.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">avoids</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies which features should be
disabled in order to generate the project file. Under
the GNUACE type, it also specifies which make macros
should not be set to build the target.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">custom_only</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This setting instructs MPC to
create projects that only contain custom generation
targets. Any files included in the projects will be
provided by custom component lists defined through the
use of <em class="Code">Define_Custom</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">dependent_upon</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This keyword can only be used
as a header component scoped setting (ie. inside
the scope of Header_Files). It determines which
file the header file is dependent upon for vc8,
and vc9 only.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">dllout</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If defined, specifies where the
dynamic libraries will be placed. This overrides libout
in the dynamic case.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">dynamicflags</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies preprocessor flags passed
to the compiler when building a dynamic library.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">exename</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Determines that the project will be
an executable and the name of the executable
target.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">exeout</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies where executables will be
placed.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">includes</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies one or more directories
to supply to the compiler for use as include search
paths.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">libout</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies where the dynamic and
static libraries will be placed.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">libpaths</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies one or more directories
to supply to the compiler for use as library search
paths.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">libs</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies one or more libraries to
link into the target. Library modifiers may be added
when being processed in the template file. For example,
library modifiers are added when using the vc6 project
type.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">lit_libs</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as libs except
that a library modifier will not be added.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">macros</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Values supplied here will be passed
directly to the compiler as command line defined
macros.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">managed</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies that the source files
should be compiled as managed C++. This is only
supported by the <em class="Code">nmake</em>,
<em class="Code">vc7</em>, <em class="Code">vc71</em>,
<em class="Code">vc8</em>, <em class="Code">vc9</em>,
and <em class="Code">vc10</em> project types.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">no_pch</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">It specifies that precompiled
headers should not be used for the source files listed
within the scope of it’s setting. This keyword
can only be used as a source component scoped setting
(i.e., inside the scope of Source_Files).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">pch_header</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The name of the precompiled header
file. See the discussion below this table for more
information.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">pch_source</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The name of the precompiled source
file. See the discussion below this table for more
information.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">postbuild</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If this is defined in the project,
the value will be interpreted as commands to run after
the project has been successfully built. The <em class=
"Code"><% %></em> construct (see <a href=
"MakeProjectCreator.html#MPD%20Syntax" class=
"XRef">Template Files</a>) can be used within this
value to access template variables and functions of the
template parser. See <a href=
"#Common%20Pseudo%20Variables" class="XRef">Common
Pseudo Variables</a> for a list of pseudo variables
that are also available.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">postclean</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If this is defined in the project,
the value will be interpreted as commands to run after
the project has been cleaned. It should be noted that
this setting is not supported by all project types. As
with <em class="Code">postbuild</em>, the <em class=
"Code"><% %></em> construct (see <a href=
"MakeProjectCreator.html#MPD%20Syntax" class=
"XRef">Template Files</a>) can be used within this
value to access template variables and functions of the
template parser. See <a href=
"#Common%20Pseudo%20Variables" class="XRef">Common
Pseudo Variables</a> for a list of pseudo variables
that are also available.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">prebuild</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If this is defined in the project,
the value will be interpreted as commands to run before
the project has been built. As with <em class=
"Code">postbuild</em>, the <em class="Code"><%
%></em> construct (see <a href=
"MakeProjectCreator.html#MPD%20Syntax" class=
"XRef">Template Files</a>) can be used within this
value to access template variables and functions of the
template parser. See <a href=
"#Common%20Pseudo%20Variables" class="XRef">Common
Pseudo Variables</a> for a list of pseudo variables
that are also available.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">pure_libs</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is similar to <em class=
"Code">lit_libs</em> except that no prefix or extension
is added to the names specified.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">recurse</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If set to 1, MPC will recurse into
directories listed under component listings (such as
Source_Files, Header_Files, etc.) and add any component
corresponding files to the list. This keyword can be
used as a global project setting or a component scoped
setting.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">recursive_includes</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is similar to <em class=
"Code">includes</em> in that it provides include paths
to the compiler. However, each path supplied will be
recursively searched for sub-directories which will
also be provided as include paths to the compiler.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">recursive_libpaths</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is similar to <em class=
"Code">libpaths</em> in that it provides library search
paths to the linker. However, each path supplied will
be recursively searched for sub-directories which will
also be provided as library search paths to the
linker.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">requires</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies which features should be
enabled in order to generate the project file. Under
the GNUACE type, it also specifies which make macros
should be set to build the target.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">sharedname</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Determines that the project will be
a library and the name of the dynamic library target.
See the discussion below this table for more
information.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">staticflags</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies preprocessor flags passed
to the compiler when building a static library.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="Bold"><em class=
"TableCode">staticname</em></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Determines that the project will be
a library and the name of the static library
target.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">tagchecks</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">For GNUACE Make only, specifies one
or more names to search for in the macros specified by
tagname.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">tagname</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies the GNUACE Make macro to
check before building the target.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">version</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Specifies the version number for
the library or executable.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">webapp</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Determines whether the project is a
Web Application. A web application project will have no
project file written but the information will be
included in the workspace if web applications are
supported by the project type.</p>
</td>
</tr>
</table>
</li>
<li class="BodyNoLead">Assignments can also use the <em class=
"Code">+=</em> and <em class="Code">-=</em> operators to add
and subtract values from keyword values.</li>
<li class="Body">Assignments can be bracketed by curly braces
so they can span multiple lines. The opening curly brace must
be the last thing on the same line as the operator and the closing
brace must be on its own line (but can have leading white space).
Optionally, \n, \s, or \ns can be included after the operator. These
indicate that new lines should be retained (\n) and leading white space
should be retained (\s).</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">specific(rpmspec) {</p>
<p class="Code"> rpm_description = \ns {</p>
<p class="Code">This description</p>
<p class="Code">spans multiple lines.</p>
<p class="Code"> }</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">If a <em class="Code">sharedname</em> is
specified in the mpc file and <em class="Code">staticname</em>
is not used, then <em class="Code">staticname</em> is assumed
to be the same as <em class="Code">sharedname</em>. This also
applies in the opposite direction.</li>
<li class="Body">If neither exename, sharedname nor staticname
is specified, MPC will search the source files for a <em class=
"Code">main</em> function. If a <em class="Code">main</em> is
found, the exename will be set to the name of the file, minus
the extension, that contained the <em class="Code">main</em>
function. Otherwise, sharedname and staticname will be set to
the project name.</li>
<li class="Body">If the project name, exename, sharedname or
staticname contain an asterisk it instructs MPC to dynamically
determine a portion of the name based on certain defaults. If
the project name contains an asterisk, then the asterisk will
be replaced with the default project name. If exename,
sharedname or staticname contains an asterisk, then the
asterisk will be replaced with the project name.</li>
<li class="Body">If the <em class="Code">pch_header</em>
keyword is not used and a file exists, in the directory in
which the mpc file is located, that matches <em class=
"Code">*_pch.h</em> it is assumed to be the precompiled header
for that directory. If there are multiple pch files in the
directory, then the precompiled header that closely matches the
project name will be chosen. Similar logic applies for the
<em class="Code">pch_source</em> keyword.</li>
</ul>
</div>
<div>
<a name="16907"></a>
<h6 class="Head5">Components</h6>
<ul>
<li class="BodyNoLead">An mpc file can also specify the files
to be included in the generated “project” file.
These files are specified using the component names shown in
the following table. However, most of the time users will want
to allow MPC to provide the default values for project
files.</li>
<li style="list-style: none">
<h6 class="NumberedTableTitle">Component Names and Default
Values</h6>
<table border="1" summary=
"Component Names and Default Values">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Name</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Default Value</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">Source_Files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Defaults to all files in the
directory that have the following extensions:
<em class="Code">cpp</em>, <em class="Code">cxx</em>,
<em class="Code">cc</em>, <em class="Code">c</em>, and
<em class="Code">C</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">Header_Files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Defaults to all files in the
directory that have the following extensions:
<em class="Code">h</em>, hpp, <em class=
"Code">hxx</em>, and <em class="Code">hh</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">Inline_Files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Defaults to all files in the
directory that have the following extensions:
<em class="Code">i</em> and <em class=
"Code">inl</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">Template_Files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Defaults to all files in the
directory that end in the following: <em class=
"Code">_T.cpp</em>, <em class="Code">_T.cxx</em>,
<em class="Code">_T.cc</em>, <em class=
"Code">_T.c</em>, and <em class="Code">_T.C</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">Documentation_Files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Defaults to all files in the
directory that match the following: <em class=
"Code">README</em>, <em class="Code">readme</em>,
<em class="Code">.doc</em>, <em class="Code">.html</em>
and <em class="Code">.txt</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">Resource_Files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Defaults to all files in the
directory that match the project name and have an
<em class="Code">rc</em> extension.</p>
</td>
</tr>
</table>
</li>
<li class="Body">If a component is not specified in the mpc
file, the default value will be used. To disallow a particular
set of files that may exist in the directory, you must declare
an empty set of the particular component type.</li>
<li class="Body">Each component name accepts two forms. The
first form is a simple list of files within the construct.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">Source_Files {</p>
<p class="Code"> file1.cpp</p>
<p class="Code"> file2.cpp</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">The second form is a complex list of files
within named blocks.</li>
<li style="list-style: none">
<a name="MPC grouping example"></a>
<p class="Code"> </p>
<p class="Code">Source_Files(MACRO_NAME) {</p>
<p class="Code"> BlockA {</p>
<p class="Code"> file1.cpp</p>
<p class="Code"> file2.cpp</p>
<p class="Code"> }</p>
<p class="Code"> BlockB {</p>
<p class="Code"> file3.cpp</p>
<p class="Code"> file4.cpp</p>
<p class="Code"> }</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">The second form allows the user to logically
group the files to make future maintenance easier. Using this
form has the effect of visually grouping files in the generated
project file for the <em class="Code">em3</em>, <em class=
"Code">gnuace</em>, <em class="Code">vc6</em>, <em class=
"Code">vc7</em>, <em class="Code">vc71</em>, vc8, vc9 and
<em class="Code">vc10</em> project types.</li>
<li class="Body">If a file is listed in the <em class=
"Code">Source_Files</em> component list and a corresponding
header or inline file exists in the directory, it is added to
the corresponding component list unless it is already
listed.</li>
</ul>
</div>
<div>
<h6 class="Head5">Verbatim Clause</h6>
<ul>
<li class="BodyNoLead">The <em class="Code">verbatim</em>
construct can be used to place text into a generated project
file verbatim. The <em class="Code">verbatim</em> syntax is as
follows:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">verbatim(<project type>,
<location>) {</p>
<p class="Code"> ...</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">When MPC is generating a project of type
<em class="Code"><project type></em> and encounters a
<em class="Code">marker</em> in the template file (see <a href=
"MakeProjectCreator.html#38037" class="XRef">Template File
Keywords</a>) that matches the <em class=
"Code"><location></em> name, it will place the text found
inside the construct directly into the generated project. If
the text inside the construct requires that white space be
preserved, each line must be enclosed in double quotes. The
following <em class="Code">verbatim</em> example would result
in <em class="Code">gnuace</em> generated projects having a
rule at the bottom of the GNUmakefile where the <em class=
"Code">all:</em> target depends on <em class=
"Code">foo</em>.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">verbatim(gnuace, bottom) {</p>
<p class="Code"> all: foo</p>
<p class="Code">}</p>
</li>
</ul>
</div>
<div>
<h6 class="Head5">Expand Clause</h6>
<ul>
<li class="BodyNoLead">The <em class="Code">expand</em> keyword
can be used to provide values for variable names enclosed
within <em class="Code">$()</em>. In the example below, we see
the name <em class="Code">VAR_NAME</em> inside the parenthesis.
Whenever MPC sees <em class="Code">$(VAR_NAME)</em> it will
attempt to replace it with values from the expansion list. MPC
will first try to replace it with the value of the environment
variable named <em class="Code">ENV_VAR</em>. If that
environment variable has a value, it will be used. Otherwise,
it will continue down the list until a suitable value is found.
In this example, the text <em class=
"Code">last_resort_value</em> will be used. MPC will leave the
<em class="Code">$()</em> value as it was in the event that no
value is found.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">expand(VAR_NAME) {</p>
<p class="Code"> $ENV_VAR</p>
<p class="Code"> last_resort_value</p>
<p class="Code">}</p>
</li>
</ul>
</div>
<div>
<h6 class="Head5"><a name="projectSpecific">Specific Clause</a></h6>
<ul>
<li class="BodyNoLead">The <em class="Code">specific</em>
keyword can be used to define assignments that are specific to
a particular project type or property specified in the
parenthesis. This will allow platform or OS-specific values to
be placed into a project. For example, on one platform you may
want to link in a library named <em class="Code">qt-mt</em>,
but on another you need to link in <em class=
"Code">qt-mt230nc</em>.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">specific(prop:windows) {</p>
<p class="Code"> lit_libs += qt-mt230nc</p>
<p class="Code">} else {</p>
<p class="Code"> lit_libs += qt-mt</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">If an else clause is provided, it is required
to be on the same line as the closing curly brace. You may also
negate the project type or property (using ’!’)
which will cause the specific to be evaluated for all types
except the type specified.</li>
<li class="Body">If a keyword used within a <em class=
"Code">specific</em> section is not recognized as a valid MPC
keyword, it is interpreted to be template value modifier. In
this situation, this construct works exactly the same way as
the <em class="Code">-value_template</em> command line option
(see <a href="MakeProjectCreator.html#Command%20Line%20Options"
class="XRef">Command Line Options</a>).</li>
<a name="properties">
<li class="Body">The following table shows which properties
apply to which project types. The <em class="Code">static</em>
property (not represented in the table) is set if the -static
option is supplied when processing the project files.
Additionally, a property that corresponds to the language
will be set (e.g., cplusplus, csharp, java, vb).</li>
<li class="Body">
<h6 class="NumberedTableTitle"><a name=
"Property Table"></a>Property Table</h6>
<table border="1" summary="Property Table">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Project Type</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">borland</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">make</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">microsoft</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">windows</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">automake</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">bcb2007</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">bcb2009</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">bds4</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">bmake</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">cc</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">em3</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">ghs</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Depends</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">make</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">nmake</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">vc6</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">vc7</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">vc71</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">vc8</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">vc9</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">vc10</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">wix</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"> </p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Yes</p>
</td>
</tr>
</table>
</li>
<li class="Body">The ghs project type can be used on both
Windows and UNIX. The windows property will be active if the
<em class="Code">MPC_GHS_UNIX</em> environment variable is not
set during project generation.</li>
</ul>
</div>
<div>
<h6 class="Head5">Conditional Clause</h6>
<ul>
<li class="Body">This scope allows addition of source files
conditionally based on a particular project type or property
(see the <a href="#Property%20Table" class="XRef">property
table</a>). The syntax is as follows:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">conditional(<project type|property> [,
<project type|property> ...]) {</p>
<p class="Code"> source1.cpp</p>
<p class="Code"> ...</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code">conditional(<project type|property> [,
<project type|property> ...]) {</p>
<p class="Code"> source1.cpp</p>
<p class="Code"> ...</p>
<p class="Code">} else {</p>
<p class="Code"> source2.cpp</p>
<p class="Code"> ...</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">If the else is provided, it is required to be
on the same line as the closing curly brace. You may also
negate the project type (using ’!’) which will
cause the conditional to be evaluated for all types except the
type specified.</li>
</ul>
</div>
<div>
<a name="Custom Types and Build Rules"></a>
<h6 class="Head5">Custom Types and Build Rules</h6>
<ul>
<li class="BodyNoLead">MPC allows you to define your own custom
file types to support a variety of custom build rules. Below is
an example of a custom definition.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">project {</p>
<p class="Code"> Define_Custom(MOC) {</p>
<p class="Code"> automatic = 0</p>
<p class="Code"> command =
$(QTDIR)/bin/moc</p>
<p class="Code"> output_option =
-o</p>
<p class="Code"> inputext = .h</p>
<p class="Code"> pre_extension =
_moc</p>
<p class="Code"> source_outputext =
.cpp</p>
<p class="Code"> keyword mocflags =
commandflags</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> // Custom Component</p>
<p class="Code"> MOC_Files {</p>
<p class="Code"> QtReactor.h</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> Source_Files {</p>
<p class="Code"> QtReactor_moc.cpp</p>
<p class="Code"> }</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">The above example defines a custom file type,
“<em class="Code">MOC</em> ”, that describes basic
information about how to process the input files and what
output files are created. Once the custom file type is defined,
<em class="Code">MOC_Files</em> can be used to specify the
input files for this new file type.</li>
<li class="Body">Define_Custom definitions may use single
inheritance. This is useful for creating aliased names:
<p class="Code">Define_Custom(QtMOC) : MOC {</p>
<p class="Code">}</p>
</li>
<li class="Body">The following table contains the keywords that
can be used within the scope of <em class=
"Code">Define_Custom</em>.</li>
<li style="list-style: none">
<a name="32899"></a>
<h6 class="NumberedTableTitle">Define_Custom Keywords</h6>
<table border="1" summary="Define_Custom Keywords">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Keyword</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">automatic_in</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If set to 1, then attempt to
automatically determine which files belong to the set
of input files for the custom type. If set to 0, then
no files are automatically added to the input
files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">automatic_out</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If set to 1, then attempt to
automatically determine which generated files belong to
the set of components (<em class=
"Code">Source_Files</em>, <em class=
"Code">Inline_Files</em> , <em class=
"Code">Header_Files</em>, <em class=
"Code">Template_Files</em>, <em class=
"Code">Resource_Files</em> and <em class=
"Code">Documentation_Files</em>) based on type files
that the command generates. If omitted, then
automatic_out is assumed to be 1.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">command</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The name of the command that should
be used to process the input files for the custom
type.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">commandflags</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Any options that should be passed
to the command.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">dependent</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If this is given a value, then a
dependency upon that value will be given to all of the
generated files. The default for this is unset and no
dependency will be generated.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">dependent_libs</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If this is given a value, then a dependency upon that
library value will be given to all of the generated files.
The format for this entry should be the basename for the
library (no library prefix, postfix, or extension)
preceded by any relative or absolute path to the library.
The typical use for this would be so that a project is
rebuilt when a library needs to be rebuilt for its
dependent executable. The default for this is unset and no
dependency will be generated.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">inputext</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is a comma separated list of
input file extensions that belong to the command.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">keyword
<name></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is a special assignment that
allows the user to map <name> into the project
level namespace. The value (if any) that is assigned to
this construct must be one of the keywords that can be
used within a Define_Custom clause. The result of this
assignment is the ability modify the value of keywords
that are normally only accessible within the scope of a
custom component (e.g. <em class="Code">command</em>,
<em class="Code">commandflags</em>, etc.).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">libpath</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If the command requires a library
that is not in the normal library search path, this
keyword can be used to ensure that the command is able
to find the library that it needs to run.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">output_option</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If the command takes an option to
specify a single file output name, then set it here.
Otherwise, this should be omitted.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">output_follows_input</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This setting defaults to 1 and
indicates that output files from the custom command
will end up in the same directory as the input files.
If this is set to 0, it is assumed that the output
files will go into the same directory as the .mpc
file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">pch_postrule</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If this is set to 1, then a rule
will be added to the custom rule that will modify the
source output files to include the precompiled header
file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">postcommand</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This allows users to create
arbitrary commands that will be run after the main
command is run to process the custom input files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">pre_extension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If the command produces multiple
files of the same extension, this comma separated list
can be used to specify them. For example, <em class=
"Code">tao_idl</em> creates two types of files per
extension (<em class="Code">C.h</em>, <em class=
"Code">S.h</em>, <em class="Code">C.cpp</em>,
<em class="Code">S.cpp</em>, etc.) This applies to all
extension types.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">source_pre_extension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_extension
except that it only applies to source files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">inline_pre_extension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_extension
except that it only applies to inline files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">header_pre_extension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_extension
except that it only applies to header files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">template_pre_extension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_extension
except that it only applies to template files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">resource_pre_extension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_extension
except that it only applies to resource files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">documentation_pre_extension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_extension
except that it only applies to documentation files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">generic_pre_extension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_extension
except that it only applies to generic files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">pre_filename</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The syntax for this is the same as
<em class="Code">pre_extension</em>, but the values
specified are prepended to the file name instead of the
extension. This applies to all extension types.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">source_pre_filename</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_filename
except that it only applies to source files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">inline_pre_filename</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_filename
except that it only applies to inline files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">header_pre_filename</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_filename
except that it only applies to header files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">template_pre_filename</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_filename
except that it only applies to template files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">resource_pre_filename</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_filename
except that it only applies to resource files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">documentation_pre_filename</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_filename
except that it only applies to documentation files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">generic_pre_filename</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_filename
except that it only applies to generic files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">pre_dirname</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The syntax for this is the same as
<em class="Code">pre_filename</em>, but the value
specified is prepended to the directory portion of the
file name instead of the file name itself. If a
separate directory is desired, the <em class=
"Code">pre_dirname</em> setting should end in a
slash.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">source_pre_dirname</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_dirname
except that it only applies to source files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">inline_pre_dirname</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_dirname
except that it only applies to inline files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">header_pre_dirname</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_dirname
except that it only applies to header files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">template_pre_dirname</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_dirname
except that it only applies to template files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">resource_pre_dirname</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_dirname
except that it only applies to resource files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">documentation_pre_dirname</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_dirname
except that it only applies to documentation files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">generic_pre_dirname</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is the same as pre_dirname
except that it only applies to generic files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">source_outputext</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is a comma separated list of
possible source file output extensions. If the command
does not produce source files, then this can be
omitted.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">inline_outputext</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is a comma separated list of
possible inline file output extensions. If the command
does not produce inline files, then this can be
omitted.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">header_outputext</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is a comma separated list of
possible header file output extensions. If the command
does not produce header files, then this can be
omitted.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">template_outputext</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is a comma separated list of
possible template file output extensions. If the
command does not produce template files, then this can
be omitted.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">resource_outputext</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is a comma separated list of
possible resource file output extensions. If the
command does not produce resource files, then this can
be omitted.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">documentation_outputext</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is a comma separated list of
possible documentation file output extensions. If the
command does not produce documentation files, then this
can be omitted.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">generic_outputext</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">If the command does not generate
any of the other output types listed above, then the
extensions should be listed under this.</p>
</td>
</tr>
</table>
</li>
<li class="Body">There is a special interaction between custom
components and the source, header and inline components. If a
<em class="Code">custom</em> definition is set to be
“automatic” and custom component files are present
but not specified, the default custom generated names are added
to the source, header and inline component lists unless those
names are already listed (or partially listed) in those
component lists. See <a href=
"MakeProjectCreator.html#Custom%20Types%20and%20Build%20Rules"
class="XRef">Custom Types and Build Rules</a> for more
information about defining your own custom type.</li>
<li class="Body">Particular output extensions for custom build
types are not required. However, at least one output extension
type is required for MPC to generate a target. Your command
does not necessarily have to generate output, but an extension
type is required if you want the input file to be processed
during the project compilation.</li>
<li class="Body">If the custom output can not be represented
with the above output extension keywords (*_outputext) and you
have knowledge of the output files <em class="Emphasis">a
priori</em>, you can represent them with the <em class=
"Code">>></em> construct.</li>
<li class="Body">Below is an example that demonstrates the use
of <em class="Code">>></em>. The command takes an input
file name of foo.prp and produces two files that have
completely unrelated filenames, <em class="Code">hello.h</em>
and <em class="Code">hello.cpp</em>.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">project {</p>
<p class="Code"> Define_Custom(Quogen) {</p>
<p class="Code"> automatic = 0</p>
<p class="Code"> command = perl quogen.pl</p>
<p class="Code"> commandflags = --debuglevel=1
--language=c++ \</p>
<p class="Code">
--kernel_language=c++</p>
<p class="Code"> inputext = .prp</p>
<p class="Code"> keyword quogenflags =
commandflags</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> Quogen_Files {</p>
<p class="Code"> foo.prp >>
hello.h hello.cpp</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> Source_Files {</p>
<p class="Code"> hello.cpp</p>
<p class="Code"> }</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">You can use the <em class="Code"><<</em>
construct to represent dependencies for specific custom input
file. For instance, in the above example, assume that foo.prp
depends upon foo.in, we would represent this by adding
<em class="Code"><<</em> foo.in as shown below.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">Quogen_Files {</p>
<p class="Code"> foo.prp >> hello.h
hello.cpp << foo.in</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">An additional construct can be used within the
scope of a <em class="Code">Define_Custom</em>. This construct
is called <em class="Code">optional</em>, and can be used to
represent optional custom command output that is dependent upon
particular command line parameters passed to the custom
command.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">project {</p>
<p class="Code"> Define_Custom(TEST) {</p>
<p class="Code"> optional(keyword)
{</p>
<p class="Code">
flag_keyword(option) +=
value [, value]</p>
<p class="Code"> }</p>
<p class="Code"> }</p>
<p class="Code">}</p>
</li>
<li class="Body">In the above fragment, <em class=
"Code">keyword</em> can be any of the <em class=
"Code">pre_extension</em>, <em class="Code">pre_filename</em>
keywords or any of the keywords that end in <em class=
"Code">_outputext</em>. The <em class="Code">flag_keyword</em>
can be any of the custom definition keywords, however only
<em class="Code">commandflags</em> has any functional value.
The <em class="Code">flag_keyword</em> value is searched for
the <em class="Code">option</em> value contained inside the
parenthesis. If it is found the <em class="Code">value</em> or
<em class="Code">values</em> after the += are added to the list
specified by <em class="Code">keyword</em>. This can also be
negated by prefixing the <em class="Code">option</em> with an
exclamation point (!).</li>
<li class="Body">The example below shows how the <em class=
"Code">optional</em> construct is used by the custom definition
for the <em class="Code">tao_idl</em> command (see <em class=
"Code">ACE_wrappers/TAO/MPC/config/taoidldefaults.mpb</em> ).
The <em class="Code">-GA</em> option causes <em class=
"Code">tao_idl</em> to generate an additional source file
(based on the idl file name) with an <em class=
"Code">A.cpp</em> extension. The <em class="Code">-Sc</em>
option causes <em class="Code">tao_idl</em> to suppress the
generation of <em class="Code">S_T</em> related files.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">Define_Custom(IDL) {</p>
<p class="Code"> ...</p>
<p class="Code"> inputext = .idl</p>
<p class="Code"> source_pre_extension = C, S</p>
<p class="Code"> header_pre_extension = C, S</p>
<p class="Code"> inline_pre_extension = C, S</p>
<p class="Code"> source_outputext = .cpp, .cxx,
.cc, .C</p>
<p class="Code"> header_outputext = .h, .hpp,
.hxx, .hh</p>
<p class="Code"> inline_outputext = .inl, .i</p>
<p class="Code"> keyword idlflags =
commandflags</p>
<p class="Code"> </p>
<p class="Code"> optional(source_pre_extension)
{</p>
<p class="Code"> commandflags(-GA) +=
A</p>
<p class="Code"> }</p>
<p class="Code"> optional(template_outputext)
{</p>
<p class="Code"> commandflags(!-Sc) +=
S_T.cpp, S_T.cxx, S_T.cc, S_T.C</p>
<p class="Code"> }</p>
<p class="Code"> optional(header_pre_extension)
{</p>
<p class="Code"> commandflags(!-Sc) +=
S_T</p>
<p class="Code"> }</p>
<p class="Code"> optional(inline_pre_extension)
{</p>
<p class="Code"> commandflags(!-Sc) +=
S_T</p>
<p class="Code"> }</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">For custom file types, there are a few
keywords that can be used within the custom file type component
lists: <em class="Code">command</em>, <em class=
"Code">commandflags</em>, <em class="Code">dependent</em>,
<em class="Code">dependent_libs</em>, <em class="Code">gendir</em>,
<em class="Code">postcommand</em>, and <em class=
"Code">recurse</em>.</li>
<li class="Body">The <em class="Code">recurse</em> keyword
works as described in <a href="MakeProjectCreator.html#82186"
class="XRef">Assignment Keywords</a>.</li>
<li class="Body">The <em class="Code">command</em>, <em class=
"Code">commandflags</em>, <em class="Code">dependent</em>,
<em class="Code">dependent_libs</em> and
<em class="Code">postcommand</em> keywords can be used to
augment or override the value defined in the <em class=
"Code">Define_Custom</em> section.</li>
<li class="Body">The <em class="Code">gendir</em> keyword can
be used (only if <em class="Code">output_option</em> is set in
<em class="Code">Define_Custom</em> ) to specify the directory
in which the generated output will go. Here is an example:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">MOC_Files {</p>
<p class="Code"> commandflags += -nw</p>
<p class="Code"> gendir = moc_generated</p>
<p class="Code"> QtReactor.h</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code">Source_Files {</p>
<p class="Code">
moc_generated/QtReactor_moc.cpp</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">In the above example, the <em class=
"Code">-nw</em> option is added to <em class=
"Code">commandflags</em> and the generated file (<em class=
"Code">QtReactor_moc.cpp</em> ) is placed in the <em class=
"Code">moc_generated</em> directory. If the <em class=
"Code">MOC</em> custom definition did not have an <em class=
"Code">output_option</em> setting, then options would need to
be added to <em class="Code">commandflags</em> or a <em class=
"Code">postcommand</em> would need to be defined to ensure that
the output actually went into the <em class=
"Code">moc_generated</em> directory.</li>
</ul>
<div>
<h6 class="Head6">Modify_Custom</h6>
<ul>
<li class="Body">An existing <em class=
"Code">Define_Custom</em> section can be modified by using
<em class="Code">Modify_Custom</em>. The syntax of the body
is identical to that of a <em class=
"Code">Define_Custom</em>. The example below shows a
modification to the TAO IDL defaults found in <em class=
"Code">taoidldefaults.mpb</em> of the TAO+ACE distribution.
Everything provided by the <em class=
"Code">Define_Custom(IDL)</em> remains unchanged except for
the values set within the <em class=
"Code">Modify_Custom(IDL).</em></li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">project: taoidldefaults {</p>
<p class="Code"> specific(!automake) {</p>
<p class="Code"> tao_idlflags += -Sc
-hs _s.h -si _s.i -ss _s.cpp -hc .h -ci .i -cs .cpp</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> // This allows "make idl_stubs"
to work</p>
<p class="Code"> verbatim(gnuace, macros) {</p>
<p class="Code"> IDL_CLIENT_HDR_EXT
?= .h</p>
<p class="Code"> IDL_CLIENT_INL_EXT
?= .i</p>
<p class="Code"> IDL_CLIENT_SRC_EXT
?= .cpp</p>
<p class="Code"> IDL_SERVER_HDR_EXT
?= _s.h</p>
<p class="Code"> IDL_SERVER_INL_EXT
?= _s.i</p>
<p class="Code"> IDL_SERVER_SRC_EXT
?= _s.cpp</p>
<p class="Code"> }</p>
<p class="Code"> </p>
<p class="Code"> Modify_Custom(IDL) {</p>
<p class="Code">
source_pre_extension = , _s</p>
<p class="Code">
header_pre_extension = , _s</p>
<p class="Code">
inline_pre_extension = , _s</p>
<p class="Code"> inline_outputext
= .i</p>
<p class="Code"> }</p>
<p class="Code">}</p>
</li>
</ul>
</div>
<div>
<h6 class="Head6">Custom Post Command</h6>
<ul>
<li class="BodyNoLead">When defining a <em class=
"Code">postcommand</em> as part of a <em class=
"Code">Define_Custom</em>, a few pseudo template variables
are available to provide some flexibility. The following
table shows the pseudo template variables that can be
accessed only from the <em class="Code">postcommand</em>.
Please note that <em class="Code"><%</em> and <em class=
"Code">%></em> are part of the syntax.</li>
<li style="list-style: none">
<h6 class="NumberedTableTitle">Post Command Pseudo
Variables</h6>
<table border="1" summary="Post Command Pseudo Variables">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Variable</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%input%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The input file to the
command.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%input_basename%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The basename of the input file to
the command.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%input_dirname%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The directory name of the input
file to the command.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%input_noext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The input file to the command
with the extension stripped off.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%input_ext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This gives the file extension of
the input file (if there is one).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%output%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file created by the
original command.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%output_basename%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The basename of the output file
to the command.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%output_dirname%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The directory name of the output
file to the command.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%output_noext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file created by the
original command with the extension stripped off.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%output_ext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This gives the file extension of
the output file (if there is one).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="2">
<p class="TblCode">The output file can be referenced
as a generic output file, or it can be referenced as
a component file using one of the following
variables. If it does not match the specific type the
value will be empty.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%documentation_file%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file if it is a
documentation file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%header_file%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file if it has a
header file extension.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%inline_file%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file if it has an
inline file extension.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%resource_file%></em> (<em class=
"TableCode"><%resx_file%></em> for C# and
VB)</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file if it has a
resource file extension.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%source_file%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file if it has a
source file extension.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%template_file%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file if it is a
template file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%documentation_file_noext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file without an
extension if it is a documentation file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%header_file_noext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file without an
extension if it has a header file extension.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%inline_file_noext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file without an
extension if it has an inline file extension.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%resource_file_noext%></em>
(<em class="TableCode"><%resx_file_noext%></em>
for C# and VB)</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file without an
extension if it has a resource file extension.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%source_file_noext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file without an
extension if it has a source file extension.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%template_file_noext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output file without an
extension if it is a template file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="2">
<p class="TblCode">The extensions of the input and
output files are also available as pseudo
variables.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%input_ext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The extension of the input file
(if it has one).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%output_ext%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The extension of the output file
(if it has one).</p>
</td>
</tr>
</table>
</li>
<li class="Body"> </li>
<li class="Body">The following table describes the pseudo
template variables that can be used in the <em class=
"Code">command</em>, <em class="Code">commandflags</em>,
<em class="Code">dependent</em>, <em class=
"Code">output_option</em> and <em class=
"Code">postcommand</em> settings.</li>
<li style="list-style: none">
<h6 class="NumberedTableTitle"><a name=
"Common Pseudo Variables"></a>Common Pseudo Variables</h6>
<table border="1" summary="Common Pseudo Variables">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Variable</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%and%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform and project
non-specific representation of a command conditional
and.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%cat%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific command
to print a file to the terminal.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%cmdsep%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A project and platform
non-specific command separator which always runs
right-hand side of the command. For example, in the
following psuedo commmand string, both the <em class=
"Code"><%cat%></em> and <em class=
"Code"><%mv%></em> commands would be run.
<em class="Code"><%cat%> <%source_file%>
<%gt%> foo <%cmdsep%> <%mv%> foo
other_dir</em></p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%cmp%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific command
to compare two files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%cp%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific command
to copy a file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%crlf%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific line
ending.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%equote%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A project non-specific escaped
double quote.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%gendir%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output directory specified by
the <em class="Code">gendir</em> setting. This
variable is not available to <em class=
"Code">postbuild</em>, <em class=
"Code">postclean</em>, or<em class=
"Code">prebuild.</em></p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%gt%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform and project
non-specific representation of a greater than
sign.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%lt%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform and project
non-specific representation of a less than sign.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%mkdir%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific command
to make a directory.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%mv%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific command
to move a file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%nul%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific null
device.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%pathsep%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific path
separator (; or :).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%or%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform and project
non-specific representation of a command conditional
or.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%os%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Returns either win32 or unix.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%prj_type%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The project type as supplied
by the -type command line option.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%quote%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A project non-specific
representation of a double quote.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%rm%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific command
to delete a file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%rmdir%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific recursive
directory delete command.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%slash%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A platform non-specific directory
separator.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%temporary%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">A temporary file name. The
generated temporary file name contains no directory
portion and is the same for each use within the same
variable setting.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="2">
<p class="TblCode">The following variables will
be set to the known extension for Windows based
project types and empty on non-Windows based
project types.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%bat%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The extension for batch
files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%cmd%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The extension for command
files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode"><em class=
"TableCode"><%exe%></em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The extension for executable
files.</p>
</td>
</tr>
</table>
</li>
</ul>
</div>
</div>
</div>
<div>
<a name="TheFeatureFile" id="TheFeatureFile"></a>
<h5 class="Head4">The Feature File</h5>
<ul>
<li class="BodyNoLead">The term feature, as used by MPC,
describes different concepts or external software that a project
may require in order to build properly. The feature file
determines which features are enabled or disabled which has a
direct effect on whether or not MPC generates a project.</li>
<li class="Body">It supports the standard comment (<em class=
"Code">//</em> ) and assignment of numbers to feature names.
These feature names will correspond to values given to the
<em class="Code">requires</em> and <em class="Code">avoids</em>
keywords in mpc files.</li>
<li class="Body">If a feature is not listed in the feature file
or is listed with a boolean value of true (1), that feature is
enabled. If a feature is listed and has a boolean value of false
(0), that feature is disabled.</li>
<li class="Body">If a feature name is listed in the <em class=
"Code">requires</em> value for a particular project and that
feature is enabled, that project will be generated. If the
feature is not enabled, the project will not be generated.</li>
<li class="Body">The opposite holds true for the <em class=
"Code">avoids</em> keyword. If a feature name is listed in the
<em class="Code">avoids</em> value for a project and the feature
is disabled, that project will be generated. If the feature is
enabled, the project will not be generated.</li>
<li class="Body">The global feature file for MPC contains the
following values.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">boost = 0</p>
<p class="Code">bzip2 = 0</p>
<p class="Code">java = 0</p>
<p class="Code">mfc = 0</p>
<p class="Code">python = 0</p>
<p class="Code">qt = 0</p>
<p class="Code">rpc = 0</p>
<p class="Code">swig_java = 0</p>
<p class="Code">swig_perl = 0</p>
<p class="Code">swig_php = 0</p>
<p class="Code">swig_python = 0</p>
<p class="Code">swig_ruby = 0</p>
<p class="Code">swig_tcl = 0</p>
<p class="Code">uses_wchar = 0</p>
<p class="Code">xalan = 0</p>
<p class="Code">xerces = 0</p>
<p class="Code">xerces2 = 0</p>
<p class="Code">xerces3 = 0</p>
<p class="Code">ziparchive = 0</p>
<p class="Code">zlib = 0</p>
<p class="Code">zzip = 0</p>
<p class="Code"> </p>
</li>
<li class="Body">In the above contents, all of these features are
disabled for each project generated. If these values do not suit
your needs, then you must do one of the following:</li>
<li class="BodyNoLead">
<ul>
<li>Create a project specific feature file in the <em class=
"Code">config</em> directory (ex., <em class=
"Code">make.features</em> for the <em class="Code">make</em>
project type) to set features for a particular project
type.</li>
<li>Create a <em class="Code">default.features</em> file in
the <em class="Code">config</em> directory that contains the
feature set you need. These will be applied to all project
types.</li>
<li>Create a feature file anywhere you like with the features
you want and use the <em class="Code">-feature_file</em>
option to specify the location.</li>
<li>Use the <em class="Code">-features</em> option to
dynamically modify the feature settings.</li>
</ul>
</li>
<li class="Body">Generated projects will have a combination of
features specified in the <em class="Code">global.features</em>
file as well as in your feature file. Therefore, if a feature is
disabled in the global file and you want to enable it, you must
explicitly enable it in your feature file.</li>
</ul>
</div>
<div>
<h5 class="Head4">Feature Projects</h5>
<ul>
<li class="BodyNoLead">A feature project contains information as
a project would, but can only be a base project and will only be
added to a sub project if the features that it requires are
enabled or the features that it avoids are disabled.</li>
<li class="Body">A feature definition requires at least one
feature name. A name by itself specifies that the feature must be
enabled. A ’!’ in front of the feature name indicates
that the feature must be disabled. There may be more than one
comma separated feature listed between the parenthesis.</li>
<li class="Body">The following example show how to declare a
feature project.</li>
<li class="Body">
<p class="Code"> </p>
<p class="Code">// ziparchive.mpb</p>
<p class="Code">feature(ziparchive) {</p>
<p class="Code"> includes += $(ZIPARCHIVEROOT)</p>
<p class="Code"> libpaths +=
$(ZIPARCHIVEROOT)/lib</p>
<p class="Code"> libs +=
ziparch</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">With this example, any project that inherits
from the <em class="Code">ziparchive</em> base feature project
will contain the project information only if the <em class=
"Code">ziparchive</em> feature is enabled.</li>
</ul>
</div>
</div>
<div>
<h4 class="Head3">Defaults</h4>
<ul>
<li class="BodyNoLead">MPC has been designed to minimize the amount
of maintenance that goes into keeping build tool files up-to-date
with the project. If your source code is organized <em class=
"Emphasis">properly</em>, the maintenance of your mpc files should
be minimal.</li>
<li class="Body">With the use of inheritance and proper code
arrangement, an mpc file for a TAO related project may be as simple
as:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">project: taoserver {</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">This project definition could be used to generate
a project for a TAO server with multiple idl, header and source
files.</li>
<li class="Body">The idea of <em class="Emphasis">proper</em>
source layout is basically summarized as <em class="Emphasis">one
directory per binary target.</em> If only the files that pertain to
a single target are located in the directory with the mpc file,
then the MPC defaults will satisfy most project needs.</li>
<li class="Body">Of course, it will not always be possible or
desirable to organize your project code in this fashion, so all
defaulting behavior can be overridden. The next sections describe
the default behaviors of MPC and how to override them.</li>
</ul>
<div>
<h5 class="Head4">Source Files</h5>
<ul>
<li class="BodyNoLead">New source files are added and others are
removed quite often in a developing project. If the <em class=
"Code">Source_Files</em> component is left out of an mpc file,
then MPC will assume that any file matching one of the <em class=
"Emphasis">source</em> extensions is to be included in the
project. For most project types, the source extensions are:
<em class="Code">.cpp</em>, <em class="Code">.cxx</em>,
<em class="Code">.cc</em>, <em class="Code">.c</em> and
<em class="Code">.C</em>. Only the following extensions are
considered source extensions: <em class="Code">.cpp</em>,
<em class="Code">.cxx</em> and <em class="Code">.c</em> for the
<em class="Code">em3</em> and <em class="Code">vc6</em> project
types as eMbedded Visual C++ and Visual C++ 6.0 do not understand
files with the <em class="Code">.cc</em> or <em class=
"Code">.C</em> extension.</li>
</ul>
</div>
<div>
<h5 class="Head4">Template Files</h5>
<ul>
<li class="BodyNoLead">MPC assumes that any file matching one of
the <em class="Emphasis">template</em> extensions is to be
included in the project if the <em class=
"Code">Template_Files</em> component is left out of an mpc file.
For most project types, the template extensions are: <em class=
"Code">_T.cpp</em>, <em class="Code">_T.cxx</em>, <em class=
"Code">_T.cc</em>, <em class="Code">_T.c</em>, and <em class=
"Code">_T.C</em>. However, only the <em class="Code">_T.cpp</em>
and <em class="Code">_T.cxx</em> extensions are considered
template extensions for the <em class="Code">em3</em> and
<em class="Code">vc6</em> project types.</li>
<li class="Body">If the <em class="Code">Source_Files</em>
component is defaulted, and a file is explicitly listed in the
Template_Files section that happens to appear to MPC as a source
file (i.e., has a source file extension, but does not have
<em class="Code">_T</em> directly before it), MPC will
automatically exclude it from the <em class=
"Code">Source_Files</em> component.</li>
</ul>
</div>
<div>
<h5 class="Head4">Inline Files</h5>
<ul>
<li class="BodyNoLead">As with source files, the <em class=
"Code">Inline_Files</em> component can be left out of an mpc file
to allow it to generate defaults. Files that match the <em class=
"Code">.i</em> and <em class="Code">.inl</em> extensions are
considered inline files.</li>
<li class="Body">The <em class="Code">Inline_Files</em> component
has a special interaction with the <em class=
"Code">Source_Files</em> component. If the <em class=
"Code">Source_Files</em> component has files listed and the
<em class="Code">Inline_Files</em> component is omitted, then
each source file is <em class="Emphasis">matched</em> to an
inline file. If the matching inline file is found or would be
generated from a custom command, it is added to the <em class=
"Code">Inline_Files</em> component list.</li>
</ul>
</div>
<div>
<h5 class="Head4">Header Files</h5>
<ul>
<li class="BodyNoLead">As with source files, the <em class=
"Code">Header_Files</em> component can be left out of an mpc file
to allow it to generate defaults. Files that match the <em class=
"Code">.h</em>, <em class="Code">.hpp</em>, <em class=
"Code">.hxx</em>, and <em class="Code">.hh</em> extensions are
considered header files.</li>
<li class="Body">The <em class="Code">Header_Files</em> component
has a special interaction with the <em class=
"Code">Source_Files</em> component. If the <em class=
"Code">Source_Files</em> component has files listed and the
<em class="Code">Header_Files</em> component is omitted, then
each source file is <em class="Emphasis">matched</em> to a header
file. If the matching header file is found or would be generated
from a custom command, then it is added to the <em class=
"Code">Header_Files</em> component list.</li>
</ul>
</div>
<div>
<h5 class="Head4">Documentation Files</h5>
<ul>
<li class="BodyNoLead">The <em class=
"Code">Documentation_Files</em> component, if omitted, will
default to all files that end in the following: <em class=
"Code">README</em>, <em class="Code">readme</em>, <em class=
"Code">.doc</em>, <em class="Code">.html</em> and <em class=
"Code">.txt</em>.</li>
</ul>
</div>
<div>
<h5 class="Head4">Resource Files</h5>
<ul>
<li class="BodyNoLead">The <em class="Code">Resource_Files</em>
component, if omitted, will default to only the files that end in
<em class="Code">.rc</em> and are similar to the name of the
project. For example, if a directory contains three <em class=
"Code">.rc</em> files and the project name is <em class=
"Code">foo</em>, only the <em class="Code">.rc</em> files that
contain the word <em class="Code">foo</em> will automatically be
added to the <em class="Code">Resource_Files</em> component
list.</li>
</ul>
</div>
<div>
<h5 class="Head4">Custom Defined Files</h5>
<ul>
<li class="BodyNoLead">The <em class="Code">Custom Defined
Files</em> components have a special interaction with the
<em class="Code">Source_Files</em> component. If the custom
command generates source files and has the <em class=
"Code">automatic_out</em> setting set to 1, they will
automatically be added to the <em class="Code">Source_Files</em>
component list. If any of the files listed in the <em class=
"Code">Source_Files</em> components list match any of the
generated source file names, then none of the generated source
file names will be automatically added to the <em class=
"Code">Source_Files</em> components list.</li>
</ul>
</div>
<div>
<a name="ExampleMPCFile" id="ExampleMPCFile"></a>
<h5 class="Head4">Example MPC File</h5>
<ul>
<li class="BodyNoLead">The example below uses the directory
contents of <em class=
"Code">$TAO_ROOT/orbsvcs/performance-tests/RTEvent/lib</em> to
illustrate the simplicity of mpc files:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">Auto_Disconnect.cpp Loopback_Supplier.h
RTEC_Initializer.cpp</p>
<p class="Code">Auto_Disconnect.h Low_Priority_Setup.cpp
RTEC_Initializer.h</p>
<p class="Code">Auto_Disconnect.inl Low_Priority_Setup.h
rtec_perf_export.h</p>
<p class="Code">Auto_Functor.cpp Low_Priority_Setup.inl
RTEC_Perf.mpc</p>
<p class="Code">Auto_Functor.h Makefile RTPOA_Setup.cpp</p>
<p class="Code">Auto_Functor.inl ORB_Holder.cpp
RTPOA_Setup.h</p>
<p class="Code">Client_Group.cpp ORB_Holder.h
RTPOA_Setup.inl</p>
<p class="Code">Client_Group.h ORB_Holder.inl
RTServer_Setup.cpp</p>
<p class="Code">Client_Group.inl ORB_Shutdown.cpp
RTServer_Setup.h</p>
<p class="Code">Client_Options.cpp ORB_Shutdown.h
RTServer_Setup.inl</p>
<p class="Code">Client_Options.h ORB_Shutdown.inl
Send_Task.cpp</p>
<p class="Code">Client_Pair.cpp ORB_Task_Activator.cpp
Send_Task.h</p>
<p class="Code">Client_Pair.h ORB_Task_Activator.h
Send_Task_Stopper.cpp</p>
<p class="Code">Client_Pair.inl ORB_Task_Activator.inl
Send_Task_Stopper.h</p>
<p class="Code">Consumer.cpp ORB_Task.cpp
Send_Task_Stopper.inl</p>
<p class="Code">Consumer.h ORB_Task.h Servant_var.cpp</p>
<p class="Code">Control.cpp ORB_Task.inl Servant_var.h</p>
<p class="Code">Control.h Peer_Base.cpp Servant_var.inl</p>
<p class="Code">EC_Destroyer.cpp Peer_Base.h Shutdown.cpp</p>
<p class="Code">EC_Destroyer.h PriorityBand_Setup.cpp
Shutdown.h</p>
<p class="Code">EC_Destroyer.inl PriorityBand_Setup.h
Shutdown.inl</p>
<p class="Code">Federated_Test.idl PriorityBand_Setup.inl
Supplier.cpp</p>
<p class="Code">Implicit_Deactivator.cpp RIR_Narrow.cpp
Supplier.h</p>
<p class="Code">Implicit_Deactivator.h RIR_Narrow.h
SyncScope_Setup.cpp</p>
<p class="Code">Implicit_Deactivator.inl RT_Class.cpp
SyncScope_Setup.h</p>
<p class="Code">Loopback_Consumer.cpp RT_Class.h
SyncScope_Setup.inl</p>
<p class="Code">Loopback_Consumer.h RT_Class.inl
TAO_RTEC_Perf.dsp</p>
<p class="Code">Loopback.cpp RTClient_Setup.cpp
TAO_RTEC_Perf.dsw</p>
<p class="Code">Loopback.h RTClient_Setup.h
Task_Activator.cpp</p>
<p class="Code">Loopback_Pair.cpp RTClient_Setup.inl
Task_Activator.h</p>
<p class="Code">Loopback_Pair.h RTCORBA_Setup.cpp
Task_Activator.inl</p>
<p class="Code">Loopback_Pair.inl RTCORBA_Setup.h</p>
<p class="Code">Loopback_Supplier.cpp RTCORBA_Setup.inl</p>
<p class="Code"> </p>
</li>
<li class="Body">The following mpc file (<em class=
"Code">RTEC_Perf.mpc</em> ) shows the simple and small number of
lines required to generate usable build tool project files.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">project(RTEC_Perf): strategies, rtcorbaevent,
minimum_corba {</p>
<p class="Code"> sharedname = TAO_RTEC_Perf</p>
<p class="Code"> idlflags +=
-Wb,export_macro=TAO_RTEC_Perf_Export \</p>
<p class="Code">
-Wb,export_include=rtec_perf_export.h</p>
<p class="Code"> dllflags +=
TAO_RTEC_PERF_BUILD_DLL</p>
<p class="Code"> </p>
<p class="Code"> Template_Files {</p>
<p class="Code"> Auto_Disconnect.cpp</p>
<p class="Code"> Auto_Functor.cpp</p>
<p class="Code">
Low_Priority_Setup.cpp</p>
<p class="Code"> RIR_Narrow.cpp</p>
<p class="Code"> Servant_var.cpp</p>
<p class="Code"> Shutdown.cpp</p>
<p class="Code"> Task_Activator.cpp</p>
<p class="Code"> }</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">A line-by-line explanation of the example mpc
file is listed below.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">project(RTEC_Perf): strategies, rtcorbaevent,
minimum_corba {</p>
<p class="Code"> </p>
</li>
<li class="Body">The first line declares a project named
<em class="Code">RTEC_Perf</em> that inherits from the base
projects listed after the colon.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">sharedname = TAO_RTEC_Perf</p>
<p class="Code"> </p>
</li>
<li class="Body">Line two determines that the project is a
library and the library name is <em class=
"Code">TAO_RTEC_Perf</em>.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">idlflags +=
-Wb,export_macro=TAO_RTEC_Perf_Export \</p>
<p class="Code">-Wb,export_include=rtec_perf_export.h</p>
<p class="Code"> </p>
</li>
<li class="Body">Lines three and four add to the flags passed to
the IDL compiler when processing the idl files.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">dllflags += TAO_RTEC_PERF_BUILD_DLL</p>
<p class="Code"> </p>
</li>
<li class="Body">Line five adds <em class=
"Code">TAO_RTEC_PERF_BUILD_DLL</em> to the <em class=
"Code">dllflags</em>, which defines a macro that is used by the
<em class="Code">rtec_perf_export.h</em> header file.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">Template_Files {</p>
<p class="Code"> Auto_Disconnect.cpp</p>
<p class="Code"> Auto_Functor.cpp</p>
<p class="Code"> Low_Priority_Setup.cpp</p>
<p class="Code"> RIR_Narrow.cpp</p>
<p class="Code"> Servant_var.cpp</p>
<p class="Code"> Shutdown.cpp</p>
<p class="Code"> Task_Activator.cpp</p>
<p class="Code">}</p>
<p class="Code"> </p>
</li>
<li class="Body">Lines 7 through 15 name the listed cpp files as
part of the <em class="Code">Template_Files</em>.</li>
<li class="Body">You may have noticed that there isn’t much
to the file above. With the default behaviors that are built into
MPC, there does not need to be. We rely on the defaults to
determine the values of <em class="Code">IDL_Files</em>,
<em class="Code">Source_Files</em>, <em class=
"Code">Inline_Files</em> , and <em class=
"Code">Header_Files</em>. Since the template files do not match
the MPC built-in defaults, we must explicitly list them. We also
rely on inheritance to get many of the TAO-related options.</li>
</ul>
</div>
</div>
</div>
<div>
<h3 class="Head2">Adding a New Type</h3>
<hr>
<ul>
<li class="Body">If MPC does not support a particular build tool, you
may want to consider adding a new project type. For instance, support
could be added to MPC for Boost Jam, Xcode and many others. To do so
will require knowledge of the MPC input files, as well as Object
Oriented Perl.</li>
</ul>
<div>
<h4 class="Head3">Input File Syntax</h4>
<ul>
<li class="BodyNoLead">This section describes the syntax of the
files that are used during project generation.</li>
</ul>
<div>
<h5 class="Head4"><a name="MPD Syntax"></a>Template Files
(mpd)</h5>
<ul>
<li class="BodyNoLead">Template files make up the bulk of what
MPC puts into each generated project file. They provide the plain
text and the layout of the data provided by the mpc files, using
various template directives.</li>
<li class="Body">Template directives are declared using a
<em class="Code"><% %></em> construct. This construct is
used to create if statements, for loops and to access variables.
One thing to note is that any text, including white space, that
is not enclosed within <em class="Code"><% %></em> is left
untouched and is passed directly into the generated project
file.</li>
<li class="Body">An <em class="Code">if</em> statement can appear
on a single line or it can span multiple lines. For example, the
following line:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code"><%if(exename)%>BIN =
<%exename%><%else%>LIB =
<%sharedname%><%endif%></p>
<p class="Code"> </p>
</li>
<li class="Body">is equivalent to:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code"><%if(exename)%></p>
<p class="Code">BIN = <%exename%></p>
<p class="Code"><%else%></p>
<p class="Code">LIB = <%sharedname%></p>
<p class="Code"><%endif%></p>
<p class="Code"> </p>
</li>
<li class="Body"><a name="foreach syntax"></a> A <em class=
"Code">foreach</em> statement can also appear on a single line or
can span multiple lines. As described below in the keywords
section, the <em class="Code">foreach</em> statement evaluates
the variable in a space-separated list context.</li>
<li class="Body">There are a couple of ways to write a <em class=
"Code">foreach</em> loop. The first and preferred way is to name
the loop variable and then list each variable to be
evaluated.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">FILES=<%foreach(fvar, idl_files source_files
header_files)%> <%fvar%><%endfor%></p>
<p class="Code"> </p>
</li>
<li class="Body">The second way is to let the <em class=
"Code">foreach</em> statement determine the loop variable. With
this style, each value can be accessed via the first variable
name passed to the <em class="Code">foreach</em> with the
trailing ’<em class="Code">s</em> ’ removed.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">FILES=<%foreach(idl_files source_files
header_files)%> <%idl_file%><%endfor%></p>
<p class="Code"> </p>
</li>
<li class="Body">Note that the <em class=
"Code"><%idl_file%></em> variable will contain each
individual value of the <em class="Code">idl_files</em>,
<em class="Code">source_files</em> and <em class=
"Code">header_files</em> list. If the variable in the <em class=
"Code">foreach</em> does not end in ’<em class=
"Code">s</em> ’, the variable of the same name within the
<em class="Code">foreach</em> will contain each individual value,
e.g.,</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code"><%foreach(filelist)%>
<%filelist%><%endfor%></p>
<p class="Code"> </p>
</li>
<li class="Body">The following table lists keywords that can
appear in template files.</li>
<li style="list-style: none">
<a name="38037"></a>
<h6 class="NumberedTableTitle">Template File Keywords</h6>
<table border="1" summary="Template File Keywords">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Keyword</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">basename</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Evaluates the variable name and
removes the directory portion from that value.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">basenoextension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is similar to <em class=
"Code">basename</em> except that the extension is also
removed from the variable name value.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">comment</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The value passed to comment is
ignored and can be any set of characters, except a new
line or a closing parenthesis.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">compares</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function returns true if the
variable value (first parameter) is equal to the string
value (second parameter).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">contains</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function returns true if the
variable value (first parameter) contains the regular
expression (second parameter).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">deref</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Dereference the variable passed as
a parameter, treating its value as another variable
name and returning that variable's value.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">dirname</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Evaluates the variable name and
removes the <em class="Code">basename</em> from that
value.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">duplicate_index</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function returns a number based
on the number of times a file with the same name (but
different directory) is seen within a project. The
function returns false upon the first occurrence of a
file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">else</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Used with the <em class=
"Code">if</em> statement. An <em class="Code">else</em>
block will be evaluated if the statement does not
evaluate to true.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">endfor</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Used with <em class=
"Code">foreach</em>. This ends <em class=
"Code">foreach</em> block.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">endif</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Used with the <em class=
"Code">if</em> statement. This ends an <em class=
"Code">if</em> or <em class="Code">if/else</em>
block.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">ends_with</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function returns true if the
variable value (first parameter) ends with the regular
expression (second parameter).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">eval</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is similar to eval in perl. The
template variable passed to this function will be
evaluated within the context of the current template.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">extensions</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Returns a list of extensions based on
the component name parameter (e.g., source_files,
header_files, etc.)</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">flag_overrides</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is directly related to
overriding the project-wide settings in an mpc file. It
takes two variable names that are comma separated. The
first corresponds to a file name and the second is any
variable name.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">foreach</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The given variable names are
evaluated in a list context which is space separated.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">forfirst</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Used with <em class=
"Code">foreach</em>. The literal value passed to
<em class="Code">forfirst</em> will be placed on the
first iteration of <em class="Code">foreach</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">forlast</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Used with <em class=
"Code">foreach</em>. The literal value passed to
<em class="Code">forlast</em> will be placed on the last
iteration of <em class="Code">foreach</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">fornotfirst</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Used with <em class=
"Code">foreach</em>. The literal value passed to
<em class="Code">fornotfirst</em> will be placed on each
iteration of <em class="Code">foreach</em> except for the
first.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">fornotlast</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Used with <em class=
"Code">foreach</em>. The literal value passed to
<em class="Code">fornotlast</em> will be placed on each
iteration of <em class="Code">foreach</em> except for the
last.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">full_path</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Returns full path of the value of the
variable name passed a the parameter.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">has_extension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Returns true is the variable value
has a file extension.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">if</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Used to determine if a variable is
defined. The not operator (<em class="Code">!</em> ) can
be used to invert the if check. This construct will only
check for values defined within an mpc or mpt file.
Default values (even those implemented by the project
creators) are not considered in the <em class=
"Code">if</em> statement.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">keyname_used</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function is used to associate a
key with a variable value. If the key has been associated
with a variable value more than once, either through
physical repetition of the key in the template or through
evaluation of a foreach context, the count of association
will be appended to the output.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">lc</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Return the given variable value in
all lower case characters.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">marker</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is directly related to the
<em class="Code">verbatim</em> keyword from the mpc
syntax. This can be used to designate markers within a
template. Ex. <em class=
"Code"><%marker(local)%></em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">multiple</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function returns true if the
array parameter contains multiple values.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">noextension</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Evaluates the variable name value as
a file name and removes the extension from that value
including the period.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">normalize</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Convert spaces, dashes, slashes,
dollar signs, parenthesis and dots in the given variable
value to underscores.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">remove_from</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function will remove a file in a
component list. It requires three parameters. The first
parameter is a component name (e.g., Source_Files), the
second parameter is a regular expression pattern and
the third parameter is a project or template variable
name. The fourth and optional parameter allows you to
alter the project or template variable value by
removing the end matching portion. If the value of
the project or template variable (i.e., parameter
three) after being modified by parameter four and
having the regular expression pattern (i.e.,
parameter two) appended to it matches any value
within the compent list (named by parameter one), it
will be removed from that component list and passed
back.
any </p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">reverse</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function reverses the order of
the array parameter values.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">scope</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This is used to set the scope of
execution of a function that will operate on the template
output. A scope is begun by passing "enter" as the first
parameter and a function name as the second parameter.
Currently, the only function name supported is "escape".
The third parameter specifies a string on which the
function will operate. Any template text that matches the
string parameter while within this scope will be
transformed by the function parameter. A scope is then
ended by passing "leave".</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">set</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function is used to set or
create a template variable. This function takes two
parameters; the first is the template variable name
and the second is the variable value.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">sort</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function sorts the array
parameter values.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">starts_with</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function returns true if the
variable value (first parameter) starts with the regular
expression (second parameter).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">transdir</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Replaces values within the directory
portion of a variable value with something that can be
used as a relative path. The current working directory is
removed and ".." is replaced with "dotdot".</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">translate_vars</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The first parameter to this function
is the name of a variable. The second, optional,
parameter is the operating system for which the
project is being generated (e.g., linux, solaris,
win32, etc.) It replaces $(...) found within the
value of the variable with the equivalent environment
variable reference based on the operating system.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">uc</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Return the given variable value in
all upper case characters.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">ucw</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Return the given variable value with
the first letter of each word in upper case. Words are
separated by spaces or underscores.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">uniq</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This function returns the unique set
of the array parameter values.</p>
</td>
</tr>
</table>
</li>
<li class="Body">The following table lists special names that can
be used as variables in some template files. The variables listed
in the <a href=
"MakeProjectCreator.html#Common%20Pseudo%20Variables" class=
"XRef">Common Pseudo Variables</a> table can be used as well
(except for <em class="Code"><%temporary%></em>).</li>
<li style="list-style: none">
<h6 class="NumberedTableTitle">Special Values used in Template
Files</h6>
<table border="1" summary=
"Special Values used in Template Files">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Value</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">am_version</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Implemented by the Automake project
creator module, converts the <em class=
"Code">version</em> setting into a suitable value for
automake.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">ciao</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Implemented by the GNUACE project
creator module, specifies that the project uses CIAO.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">compilers</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Implemented by the Make project
creator module, provides the compiler name based on the
current project language.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">cppdir</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This value is implemented by the
BMake project creator module. It returns a semicolon
separated list of directories taken from each value in
the <em class="Code">Source_Files</em> list.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">custom_types</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Contains a list of the custom build
types. See <a href=
"MakeProjectCreator.html#Custom%20Types" class=
"XRef">Custom Types</a> for more details.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">cwd</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The full current working
directory.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">forcount</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This only has a value within the
context of a <em class="Code">foreach</em> and provides a
1 based count, by default, of the index of the elements
in <em class="Code">foreach</em>.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">guid</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This value is implemented by the VC7
and WIX project creator modules. It returns a <em class=
"Code">guid</em> value based on the project that is
usable within VC7, VC71, VC8, VC9, VC10 and WIX project
files.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">language</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This value is implemented by the VC7
and Make project creator modules. It returns the current
language setting for the project.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">make_file_name</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This value is implemented by the VC6
and EM3 project creator modules. It returns the project
name with the make file extension that corresponds to the
particular project type.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">project_file</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This variable contains the name of
the output file for the current project being
generated.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">project_name</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This variable contains the name of
the current project being generated.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">rcdir</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This value is implemented by the
BMake project creator module. It returns a semicolon
separated list of directories taken from each value in
the <em class="Code">Resource_Files</em> list.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">source_directory</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This value is implemented by the WIX
project creator module. It converts the variable portion
of the binary output directory (either <em class=
"Code">exeout</em>, <em class="Code">dllout</em>, or
<em class="Code">libout</em>) to a suitable value for
WIX.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">tao</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Implemented by the GNUACE project
creator module, specifies that the project uses TAO.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">vcversion</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This value is implemented by the
VC7ProjectCreator. It returns the version number of the
type of project being generated. 7.00 is return for vc7,
7.10 is return for vc71 and 8.00 is returned for vc8,
9.00 is returned for vc9, 10.00 is returned for vc10.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class="TableCode">vpath</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">This value is implemented by the
GNUACEProjectCreator. It returns a value, based on the
location of the source files, that specifies the
<em class="Code">VPATH</em> setting for GNU Make.</p>
</td>
</tr>
</table>
</li>
</ul>
<ul>
<li class="Body">
<h6 class="Head5"><a name="Document Template Script"></a>
Template Variable Documentation</h6>
</li>
<li class="Body">Template variables used within the MPC templates
are numerous and vary from template to template; there are far
too many to include in this document. However, you can generate
an HTML document containing all of the template variables used
within a template using the <em class=
"Code">document_template.pl</em> script found in the <em class=
"Code">devtools</em> directory under the MPC root directory. You
may find that some templates and individual template variables
are well documented and, unfortunately, some are not.</li>
<li class="Body">The script will generate documentation for an
individual template file. The usage is as follows:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">document_template.pl v1.3</p>
<p class="Code">Usage: document_template.pl <template>
[<html output> [language]]</p>
<p class="Code"> </p>
<p class="Code">html output - This defaults to the name of the
template file with the .mpd</p>
<p class="Code">
extension replaced with
.html.</p>
<p class="Code">language - This defaults to
the language for which the template is designed.</p>
<p class="Code">
It can be any of the valid
language settings for MPC:</p>
<p class="Code">
cplusplus csharp java
vb</p>
</li>
</ul>
<div>
<a name="Custom Types"></a>
<h6 class="Head5">Custom Types</h6>
<ul>
<li class="BodyNoLead">To support multiple custom build types,
a special keyword was introduced. The <em class=
"Code">custom_types</em> keyword is used to access the list of
custom types defined by the user. In a <em class=
"Code">foreach</em> context, each custom type can be accessed
through the <em class="Code">custom_type</em> keyword.</li>
<li class="Body">A variety of information is available from
each <em class="Code">custom_type</em> through the <em class=
"Code">-></em> operator. The input files, input extensions,
command, command output option, command flags, and output file
directory are all accessible through the field names that
correspond to the particular type.</li>
<li class="Body">The input files associated with the custom
type are accessed through <em class=
"Code">custom_type->input_files</em>. Each input file has a
set of output files associated with it which can be accessed in
a <em class="Code">foreach</em> context through c<em class=
"Code">ustom_type->input_file->output_files</em>. The
custom type fields are those listed in the <a href=
"MakeProjectCreator.html#32899" class="XRef">Define_Custom
Keywords</a> table as well as those listed in the following
table.</li>
<li style="list-style: none">
<h6 class="NumberedTableTitle">Custom Type Fields</h6>
<table border="1" summary="Custom Type Fields">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Value</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">dependencies</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The files on which the processing
of the custom input file depends.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">gendir</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The output directory associated
with a particular input file. This field has no meaning
when accessed directly through the <em class=
"Code">custom_type</em>. It should always be used
within the context of a <em class=
"Code">flag_overrides</em> (see <a href=
"MakeProjectCreator.html#38037" class="XRef">Template
File Keywords</a>).</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">input_files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The input files associated with the
custom type.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">inputexts</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The input file extensions
associated with the custom type.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">non_source_output_files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">All output files generated from the
custom input file that are not considered source code
files by MPC.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">output_files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">All output files generated from the
custom input file.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">source_output_files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">All output files generated from the
custom input file that are considered source code files
by MPC.</p>
</td>
</tr>
</table>
</li>
<li class="Body">The example below, which creates generic
makefile rules for building custom input files, shows basic use
of the custom type and the various fields that can be accessed.
The main limitation with the <em class="Code">custom_types</em>
keyword, as can be seen below, is that the <em class=
"Code">foreach</em> variable cannot be named as stated <a href=
"MakeProjectCreator.html#foreach%20syntax" class=
"XRef">previously</a>.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code"><%if(custom_types)%></p>
<p class="Code"><%foreach(custom_types)%></p>
<p class="Code">
<%foreach(custom_type->input_files)%></p>
<p class="Code">
<%foreach(custom_type->input_file->output_files)%></p>
<p class="Code">
<%custom_type->input_file->output_file%>:
<%custom_type->input_file%></p>
<p class="Code">
<%custom_type->command%>
<%custom_type->commandflags%> $@</p>
<p class="Code"> </p>
<p class="Code"><%endfor%></p>
<p class="Code"><%endfor%></p>
<p class="Code"><%endfor%></p>
<p class="Code"><%endif%></p>
<p class="Code"> </p>
</li>
<li class="Body">Certain project types don't support the same
input file used by multiple custom types (current examples of
this are vc10, cdt6, and cdt7). To accomodate these types, MPC
has a capability called "combined custom". With this capability
enabled in the specific ProjectCreator, MPC will "fold together"
the multiple custom steps so that the target tool (Visual Studio
or Eclipse CDT) sees it as a single custom step that happens to
run two or more commands. When "combined custom" is enabled,
the template needs to be written for it by checking if
<em class="Code">custom_type->input_file->commands</em> is
non-empty. If it isn't empty, the values in it can be iterated
over with a <em class="Code"><%foreach%></em>. During that
iteration, the following values can be obtained by the template.
Each one would appear in the template preceeded by
<em class="Code">custom_type->input_file-></em></li>
<li style="list-style: none">
<h6 class="NumberedTableTitle">Custom Type Fields for Combined
Custom</h6>
<table border="1"
summary="Custom Type Fields for Combined Custom">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Value</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">command</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The effective command, taking into
account the <em class="TableCode">flag_overrides</em>.
</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">command->outopt</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The <em class=
"TableCode">output_option</em> for this particular
command, taking into account the
<em class="TableCode">flag_overrides</em>.
</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">command->outfile</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The first output file for this
particular command (for use with
<em class="TableCode">outopt</em>).
</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">command->flags</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The <em class=
"TableCode">commandflags</em> for this particular
command, taking into account the
<em class="TableCode">flag_overrides</em>.
</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">command->gdir</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The <em class=
"TableCode">gendir</em> for this particular
command.
</p>
</td>
</tr>
</table>
</li>
</ul>
</div>
<div>
<h6 class="Head5">Grouped Files</h6>
<ul>
<li class="BodyNoLead">File grouping is part of the syntax of
mpc files. If a set of files are grouped within the mpc file,
they can be accessed as a group within the mpd file.</li>
<li class="Body">Files (such as <em class=
"Code">Source_Files</em>, <em class="Code">Header_Files</em> )
can be grouped together as shown <a href=
"MakeProjectCreator.html#MPC%20grouping%20example" class=
"XRef">here</a>. Within the mpd file, the different components
can be accessed by prepending <em class="Code">grouped_</em> to
the component (<em class="Code">grouped_source_files</em>,
<em class="Code">grouped_header_files</em>, etc.)</li>
<li style="list-style: none">
<h6 class="NumberedTableTitle">Grouped Files Field Names</h6>
<table border="1" summary="Grouped Files Field Names">
<tr>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Field Name</p>
</th>
<th rowspan="1" colspan="1">
<p class="Tbl-Heading">Description</p>
</th>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">files</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The input files associated with the
group.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="Tbl-Body"><em class=
"TableCode">component_name</em></p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">The name of the set of multiple
groups of files.</p>
</td>
</tr>
</table>
</li>
<li class="Body">The example below, which creates make macros
for each file group, shows basic use of grouping and the fields
that can be accessed. The main limitation with file grouping,
as can be seen below, is that the <em class="Code">foreach</em>
variable cannot be named as stated <a href=
"MakeProjectCreator.html#foreach%20syntax" class=
"XRef">previously</a>. The following example involves source
files, but any of the <a href="MakeProjectCreator.html#16907"
class="XRef">components</a> listed in the mpc and mpb section
can be used.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code"><%if(grouped_source_files)%></p>
<p class="Code"><%comment(Get back each set of grouped
files)%></p>
<p class="Code"><%foreach(grouped_source_files)%></p>
<p class="Code"><%comment(This will provide the name of
the group)%></p>
<p class="Code"><%grouped_source_file%> = \</p>
<p class="Code"><%comment(Get all the source files in a
single group)%></p>
<p class="Code">
<%foreach(grouped_source_file->files)%></p>
<p class="Code">
<%grouped_source_file->file)%><%fornotlast("
\\")%></p>
<p class="Code"><%endfor%></p>
<p class="Code"><%endfor%></p>
<p class="Code"> </p>
<p class="Code">ifndef
<%grouped_source_files->component_name%></p>
<p class="Code">
<%grouped_source_files->component_name%> = \</p>
<p class="Code"><%foreach(grouped_source_files)%></p>
<p class="Code">
<%grouped_source_file%><%fornotlast("
\\")%></p>
<p class="Code"><%endfor%></p>
<p class="Code">endif</p>
<p class="Code"><%endif%></p>
<p class="Code"> </p>
</li>
</ul>
</div>
</div>
<div>
<h5 class="Head4">Template Input Files (mpt)</h5>
<ul>
<li class="BodyNoLead">Template input files provide build tool
specific information that is common to all projects, such as
compiler switches, intermediate directories, compiler macros,
etc. Each project type can provide template input files for
dynamic libraries, static libraries, dynamic executables and
static executables. However, none of these are actually required
by MPC.</li>
<li class="Body">The template input files are more free-form than
the other MPC file types. It is similar to the mpc syntax except
that there is no project definition and there is only one
keyword. The keyword, <em class="Code">conditional_include</em>,
is used to include other mpt files if they can be found in the
MPC include search path. If the name listed in double quotes
after <em class="Code">conditional_include</em> is not found, it
is ignored and no warning is produced. The <em class=
"Code">mpt</em> extension is automatically added to the name
provided.</li>
<li class="Body">The template input files contain variable
assignments and collections of variable assignments. A variable
assignment is of the form:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">variable_name = value1 "value 2"</p>
<p class="Code">variable_name += another_value</p>
<p class="Code"> </p>
</li>
<li class="Body">This variable can then be used within the
corresponding mpd file.</li>
<li class="Body">Variable assignments can be grouped together and
named within the mpt file and used as scoped variables within the
mpd file. The following example shows the use of collections of
variable assignments.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">// mpt file</p>
<p class="Code">configurations = Release Debug</p>
<p class="Code">common_defines = WIN32 _CONSOLE</p>
<p class="Code"> </p>
<p class="Code">Release {</p>
<p class="Code"> compile_flags = /W3 /GX /O2 /MD
/GR</p>
<p class="Code"> defines = NDEBUG</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code">Debug {</p>
<p class="Code"> compile_flags = /W3 /Gm /GX /Zi /Od
/MDd /GR /Gy</p>
<p class="Code"> defines = _DEBUG</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code">conditional_include "vcfullmacros"</p>
<p class="Code"> </p>
</li>
<li class="Body">Below is the portion of the mpd file that would
use the information provided in the mpt file above.</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code"><%foreach(configurations)%></p>
<p class="Code">Name = <%configuration%></p>
<p class="Code"><%compile_flags%><%foreach(defines
common_defines)%> /D <%define%>=1<%endfor%></p>
<p class="Code"> </p>
<p class="Code"><%endfor%></p>
<p class="Code"> </p>
</li>
<li class="Body">The following output is generated from the above
example:</li>
<li style="list-style: none">
<p class="Code"> </p>
<p class="Code">Name = Release</p>
<p class="Code">/W3 /GX /O2 /MD /GR /D NDEBUG=1 /D WIN32=1 /D
_CONSOLE=1</p>
<p class="Code"> </p>
<p class="Code">Name = Debug</p>
<p class="Code">/W3 /Gm /GX /Zi /Od /MDd /GR /Gy /D _DEBUG=1 /D
WIN32=1 /D _CONSOLE=1</p>
<p class="Code"> </p>
</li>
<li class="Body">If a <em class="Code">foreach</em> variable
value corresponds to a variable group name, that variable group
is available within the scope of that <em class=
"Code">foreach</em>.</li>
<li class="Body"> </li>
</ul>
</div>
</div>
<div>
<h4 class="Head3">A Simple Example</h4>
<ul>
<li class="BodyNoLead">We will discuss what it would take to add
support for a fictional build tool throughout this section. The
<a href="MakeProjectCreator.html#Figure%201-2" class=
"XRef">Generating projects with mpc.pl diagram</a> shows the
relationship between the template and project creator discussed
below.</li>
</ul>
<div>
<h5 class="Head4">Template</h5>
<ul>
<li class="BodyNoLead">The best thing to do is to start with the
template. The template is the most important piece when adding a
new project type. It basically tells MPC how to lay out all of
the information it gathers while processing an mpc file. The
template file will have a mixture of plain text and the mpd
syntax described in the <a href=
"MakeProjectCreator.html#MPD%20Syntax" class="XRef">Template
Files</a> section. Here is our sample <em class=
"Code">fictional.mpd</em>.</li>
<li style="list-style: none">
<p class="Code">
//=======================================================================</p>
<p class="Code">// This project has been generated by MPC.</p>
<p class="Code">// CAUTION! Hand edit only if you know what you
are doing!</p>
<p class="Code">
//=======================================================================</p>
<p class="Code"> </p>
<p class="Code">// Section 1 - PROJECT OPTIONS</p>
<p class="Code">ctags:*</p>
<p class="Code">debugSwitches:-nw</p>
<p class="Code">//end-proj-opts</p>
<p class="Code"> </p>
<p class="Code">// Section 2 - MAKEFILE</p>
<p class="Code">Makefile.<%project_name%></p>
<p class="Code"> </p>
<p class="Code">// Section 3 - OPTIONS</p>
<p class="Code">//end-options</p>
<p class="Code"> </p>
<p class="Code">// Section 4 - TARGET FILE</p>
<p class="Code"><%if(exename)%></p>
<p class="Code"><%exename%></p>
<p class="Code"><%else%></p>
<p class="Code"><%if(sharedname)%></p>
<p class="Code"><%sharedname%></p>
<p class="Code"><%else%></p>
<p class="Code"><%if(staticname)%></p>
<p class="Code"><%staticname%></p>
<p class="Code"><%endif%></p>
<p class="Code"><%endif%></p>
<p class="Code"><%endif%></p>
<p class="Code"> </p>
<p class="Code">// Section 5 - SOURCE FILES</p>
<p class="Code"><%foreach(source_files)%></p>
<p class="Code"><%source_file%></p>
<p class="Code"><%endfor%></p>
<p class="Code">//end-srcfiles</p>
<p class="Code"> </p>
<p class="Code">// Section 6 - INCLUDE DIRECTORIES</p>
<p class="Code"><%foreach(includes)%></p>
<p class="Code"><%include%></p>
<p class="Code"><%endfor%></p>
<p class="Code">//end-include-dirs</p>
<p class="Code"> </p>
<p class="Code">// Section 7 - LIBRARY DIRECTORIES</p>
<p class="Code"><%foreach(libpaths)%></p>
<p class="Code"><%libpath%></p>
<p class="Code"><%endfor%></p>
<p class="Code">//end-library-dirs</p>
<p class="Code"> </p>
<p class="Code">// Section 8 - DEFINITIONS</p>
<p class="Code"><%foreach(macros defines)%></p>
<p class="Code">-D<%macro%></p>
<p class="Code"><%endfor%></p>
<p class="Code"><%if(pch_header)%></p>
<p class="Code"><%foreach(pch_defines)%></p>
<p class="Code">-D<%pch_define%></p>
<p class="Code"><%endfor%></p>
<p class="Code"><%endif%></p>
<p class="Code">//end-defs</p>
<p class="Code"> </p>
<p class="Code">// Section 9 - C FLAGS</p>
<p class="Code"><%cflags("-g")%></p>
<p class="Code"> </p>
<p class="Code">// Section 10 - LIBRARY FLAGS</p>
<p class="Code"><%libflags%></p>
<p class="Code"> </p>
<p class="Code">// Section 11 - SRC DIRECTORY</p>
<p class="Code">.</p>
<p class="Code"> </p>
<p class="Code">// Section 12 - OBJ DIRECTORY</p>
<p class="Code"><%objdir(".")%></p>
<p class="Code"> </p>
<p class="Code">// Section 13 - BIN DIRECTORY</p>
<p class="Code">
<%if(exeout)%><%exeout%><%else%>.<%endif%></p>
<p class="Code"> </p>
<p class="Code">// User targets section. Following lines will
be</p>
<p class="Code">// inserted into Makefile right after the
generated cleanall target.</p>
<p class="Code">// The Project File editor does not edit these
lines - edit the .vpj</p>
<p class="Code">// directly. You should know what you are
doing.</p>
<p class="Code">// Section 14 - USER TARGETS</p>
<p class="Code"><%marker(top)%></p>
<p class="Code"><%marker(macros)%></p>
<p class="Code"><%marker(local)%></p>
<p class="Code"><%marker(bottom)%></p>
<p class="Code">//end-user-targets</p>
<p class="Code"> </p>
<p class="Code">// Section 15 - LIBRARY FILES</p>
<p class="Code"><%foreach(libs lit_libs pure_libs)%></p>
<p class="Code"><%lib%></p>
<p class="Code"><%endfor%></p>
<p class="Code">//end-library-files</p>
<p class="Code"> </p>
</li>
<li class="Body">Note that output is generated differently
depending upon whether <em class="Code"><%exename%></em>,
<em class="Code"><%sharedname%></em> or <em class=
"Code"><%staticname%></em> is defined due to the if
statements that were used with relation these variable names.
Also, certain portions of the project file are only generated if
particular variables are set.</li>
</ul>
</div>
<div>
<h5 class="Head4">Project Creator</h5>
<ul>
<li class="BodyNoLead">Next, you would write the <em class=
"Code">FictionalProjectCreator.pm</em>. It may be best to start
with a copy of the <em class="Code">MakeProjectCreator.pm</em>
and edit it. Change the package name to <em class=
"Code">FictionalProjectCreator</em> and have it inherit from
<em class="Code">MakeProjectBase</em> and <em class=
"Code">ProjectCreator</em>. Then, override the methods that are
needed for this particular type.</li>
<li style="list-style: none">
<p class="Code">package FictionalProjectCreator;</p>
<p class="Code"> </p>
<p class="Code">#
************************************************************</p>
<p class="Code"># Description : A Fictional Project Creator</p>
<p class="Code"># Author : Chad Elliott</p>
<p class="Code"># Create Date : 10/01/2004</p>
<p class="Code">#
************************************************************</p>
<p class="Code"> </p>
<p class="Code">#
************************************************************</p>
<p class="Code"># Pragmas</p>
<p class="Code">#
************************************************************</p>
<p class="Code"> </p>
<p class="Code">use strict;</p>
<p class="Code"> </p>
<p class="Code">use MakeProjectBase;</p>
<p class="Code">use ProjectCreator;</p>
<p class="Code"> </p>
<p class="Code">use vars qw(@ISA);</p>
<p class="Code">@ISA = qw(MakeProjectBase ProjectCreator);</p>
<p class="Code"> </p>
<p class="Code">#
************************************************************</p>
<p class="Code"># Subroutine Section</p>
<p class="Code">#
************************************************************</p>
<p class="Code"> </p>
<p class="Code">sub convert_slashes {</p>
<p class="Code"> #my $self = shift;</p>
<p class="Code"> return 0;</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code"> </p>
<p class="Code">sub project_file_extension {</p>
<p class="Code"> #my $self = shift;</p>
<p class="Code"> return '.fic';</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code"> </p>
<p class="Code">sub get_dll_exe_template_input_file {</p>
<p class="Code"> #my $self = shift;</p>
<p class="Code"> return 'fictionalexe';</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code"> </p>
<p class="Code">sub get_dll_template_input_file {</p>
<p class="Code"> #my $self = shift;</p>
<p class="Code"> return 'fictionaldll';</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code"> </p>
<p class="Code">sub get_template {</p>
<p class="Code"> #my $self = shift;</p>
<p class="Code"> return 'fictional';</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code">1;</p>
<p class="Code"> </p>
</li>
<li class="Body">In our example, we inherit from the
MakeProjectBase which provides some methods that are common to
all “make” based project creators.</li>
<li class="Body">We override the <em class=
"Code">convert_slashes</em> method to return 0. A zero return
value tells MPC not to convert slashes to back slashes
(converting slashes is useful for Windows related build
tools).</li>
<li class="Body">We then override the <em class=
"Code">project_file_extension</em> method to return the project
file extension which is used by a method defined in the
MakeProjectBase module.</li>
<li class="Body">Next, we override the <em class=
"Code">get_dll_exe_template_input_file</em> and <em class=
"Code">get_dll_template_input_file</em> methods. Those methods
return the specific template input file names for a dynamic
executable and dynamic library, respectively.</li>
<li class="Body">Lastly, we override the <em class=
"Code">get_template</em> method to return the template file name
for our new project type. In our case, the method returns
<em class="Code">fictional</em> which corresponds to the name of
the template file we created earlier.</li>
<li class="Body">There are many other methods that can be
overridden to change the way MPC generates output. For a complete
list, see the “Virtual Methods To Be Overridden”
section of the <em class="Code">Creator.pm</em> and <em class=
"Code">ProjectCreator.pm</em>.</li>
</ul>
</div>
<div>
<h5 class="Head4">Workspace Creator</h5>
<ul>
<li class="BodyNoLead">The last part that you would need to write
is the <em class="Code">FictionalWorkspaceCreator.pm</em>. This
module is usually more code-intensive than its Project Creator
counterpart.</li>
<li style="list-style: none">
<p class="Code">package FictionalWorkspaceCreator;</p>
<p class="Code"> </p>
<p class="Code">#
************************************************************</p>
<p class="Code"># Description : A Fictional Workspace
Creator</p>
<p class="Code"># Author : Chad Elliott</p>
<p class="Code"># Create Date : 10/01/2004</p>
<p class="Code">#
************************************************************</p>
<p class="Code"> </p>
<p class="Code">#
************************************************************</p>
<p class="Code"># Pragmas</p>
<p class="Code">#
************************************************************</p>
<p class="Code"> </p>
<p class="Code">use strict;</p>
<p class="Code"> </p>
<p class="Code">use FictionalProjectCreator;</p>
<p class="Code">use WorkspaceCreator;</p>
<p class="Code"> </p>
<p class="Code">use vars qw(@ISA);</p>
<p class="Code">@ISA = qw(WorkspaceCreator);</p>
<p class="Code"> </p>
<p class="Code">#
************************************************************</p>
<p class="Code"># Subroutine Section</p>
<p class="Code">#
************************************************************</p>
<p class="Code"> </p>
<p class="Code">sub workspace_file_name {</p>
<p class="Code"> my $self = shift;</p>
<p class="Code"> return
$self->get_modified_workspace_name($self->get_workspace_name(),
'.fws');</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code"> </p>
<p class="Code">sub pre_workspace {</p>
<p class="Code"> my($self, $fh) = @_;</p>
<p class="Code"> my $crlf = $self->crlf();</p>
<p class="Code"> </p>
<p class="Code"> print $fh '<?xml version="1.0"
encoding="UTF-8"?>', $crlf,</p>
<p class="Code">
'<!--
MPC Command -->', $crlf,</p>
<p class="Code">
"<!--
$0 @ARGV -->", $crlf;</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code"> </p>
<p class="Code">sub write_comps {</p>
<p class="Code"> my($self, $fh) = @_;</p>
<p class="Code"> my $projects =
$self->get_projects();</p>
<p class="Code"> my @list =
$self->sort_dependencies($projects);</p>
<p class="Code"> my $crlf = $self->crlf();</p>
<p class="Code"> </p>
<p class="Code"> print $fh '<projects>',
$crlf;</p>
<p class="Code"> foreach my $project (@list) {</p>
<p class="Code"> print $fh " <project
path=\"$project\"/>$crlf";</p>
<p class="Code"> }</p>
<p class="Code"> print $fh
"</projects>$crlf";</p>
<p class="Code">}</p>
<p class="Code"> </p>
<p class="Code"> </p>
<p class="Code">1;</p>
<p class="Code"> </p>
<p class="Code"> </p>
</li>
<li class="Body">The first method we override from
WorkspaceCreator.pm is the <em class=
"Code">workspace_file_name</em> method. It is used to determine
the output file for the generated workspace.</li>
<li class="Body">Second, we override the <em class=
"Code">pre_workspace</em> method, which we use to print out the
generic unchanging section of our generated workspace.</li>
<li class="Body">Lastly, we override the <em class=
"Code">write_comps</em> method. This method is where the bulk of
the work is done in our workspace creator. A workspace creator
has many sets of data available. A reference to the list of
project file names can be obtained through the <em class=
"Code">get_projects</em> method; project-specific information can
be obtained through the <em class="Code">get_project_info</em>
method which returns an array reference where each array element
is an array containing the project name, project dependencies and
a project guid (if applicable).</li>
</ul>
</div>
</div>
</div>
</div>
</body>
</html>
|
