-
Notifications
You must be signed in to change notification settings - Fork 65
Expand file tree
/
Copy pathMakeProjectCreator.html
More file actions
9733 lines (7913 loc) · 362 KB
/
MakeProjectCreator.html
File metadata and controls
9733 lines (7913 loc) · 362 KB
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
<!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">
<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>
<p 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.
</p>
<p 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.
</p>
<p 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. The structure and
syntax of the MPC files are described in the
<a href="#Writing_MPC_Files">Writing MPC and MWC Files</a> section.
In addition, a complete example of the use of MPC is shown in the <a href=
"MakeProjectCreator.html#ExampleMPCFile" class="XRef">
Example MPC
File
</a> section.
</p>
</div>
<div>
<h3 class="Head2">Using MPC</h3>
<hr>
<p 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.
</p>
<p 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.
</p>
<p class="Body">
<a name="Figure_1-2"></a>This diagram shows a
high-level view of project file generation using mpc.pl.
</p>
<p class="Body">
<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.png" alt=
"Generating projects with mpc.pl">
</div>
</td>
</tr>
</table>
</p>
<p 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.
</p>
<p 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.
</p>
<p class="Body">
The following diagram shows a high-level view of
workspace file generation using mwc.pl.
</p>
<h6 class="FigTitle">Generating workspaces with mwc.pl</h6>
<p class="Body">
<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.png" alt=
"Generating workspaces with mwc.pl">
</div>
</td>
</tr>
</table>
</p>
<div>
<h4 class="Head3">Supported Build Tools</h4>
<p class="BodyNoLead">
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.
</p>
<h6 class="NumberedTableTitle">MPC Types</h6>
<p class="Body">
<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">cmake</em>
</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Support for CMake requires user provided modules for custom commands.</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">vc11</em>
</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio 2012.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode">
<em class="TableCode">vc12</em>
</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio 2013.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode">
<em class="TableCode">vc14</em>
</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio 2015.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode">
<em class="TableCode">vs2017</em>
</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio 2017.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode">
<em class="TableCode">vs2019</em>
</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio 2019.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode">
<em class="TableCode">vs2022</em>
</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio 2022.</p>
</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<p class="TblCode">
<em class="TableCode">vs2026</em>
</p>
</td>
<td rowspan="1" colspan="1">
<p class="Tbl-Body">Visual Studio 2026.</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>
</p>
</div>
<div>
<h4 class="Head3">Command Line</h4>
<p 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.
</p>
<p class="Body">
The table below describes each option with the
more commonly used options in bold and project specific options in
italics.
</p>
<p class="Body">
<h6 class="NumberedTableTitle">
<a name=
"Command%20Line%20Options"></a>Command Line Options
</h6>
</p>
<p class="Body">
<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 <a href="#Base_Project">base project</a>. 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 <a href="#Base_Project">base project</a> 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">