11 |
|
The binary building rules require explicit specification of the binary targets |
12 |
|
e.g. |
13 |
|
<p> |
14 |
+ |
<font color=green> |
15 |
|
<pre> |
16 |
|
<External ref=cmsim> |
17 |
|
<External ref=X11> |
18 |
|
<Use ref=CARF> |
19 |
+ |
<Lib name=examplelib></lib> |
20 |
|
<bin file=example1.cpp> |
21 |
|
You can write between bin tags some documentation to describe what the binary |
22 |
|
does |
28 |
|
</External> |
29 |
|
</External> |
30 |
|
</pre> |
31 |
+ |
</font> |
32 |
|
This file will build two executables called (example1 and mytestexe) from files example1.cpp and example2.cpp respectively. Both are built in the context of |
33 |
|
external libraries cmsim and X11 as well as a local package from the same |
34 |
|
project called CARF <p> |
35 |
|
<em><b>Note: Theres still much work to be done here</b></em><br> |
36 |
|
<ul> |
37 |
< |
<li> Use tag not yet working. |
35 |
< |
<li> </External> tag does not remove the inclusion of the specified |
37 |
> |
<li> </External> and </Use> tags do not remove the |
38 |
|
external package as you might expect. |
39 |
|
<li> Anything Outside of the bin tags will be included in the |
40 |
|
GNUmakefile. This allows you the full functionality of gmake |
46 |
|
The only time you might want to override this is to exclude some files from a |
47 |
|
build or include external package headers or assign the module to a group. |
48 |
|
<br>e.g.<p> |
49 |
+ |
<font color=green> |
50 |
|
<pre> |
51 |
|
<Group name=G3> |
52 |
|
skip_files := FakeClusterizer.cc SigmaClusterizer.cc |
53 |
|
</pre> |
54 |
+ |
</font> |
55 |
|
<li>Empty Group |
56 |
|
Sometimes the default builds arn't wanted at all. Switch them off with |
57 |
|
<p> |
58 |
+ |
<font color=green> |
59 |
|
<pre> |
60 |
|
<AssociateGroup> |
61 |
|
none |
62 |
|
</AssociateGroup> |
63 |
|
</pre> |
64 |
+ |
</font> |