blob: e51a4e60e959cee561c442e2d5f3f246648e6429 (
plain)
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
|
ceedling-subprojects
====================
Plugin for supporting subprojects that are built as static libraries. It continues to support
dependency tracking, without getting confused between your main project files and your
subproject files. It accepts different compiler flags and linker flags, allowing you to
optimize for your situation.
First, you're going to want to add the extension to your list of known extensions:
```
:extension:
:subprojects: '.a'
```
Define a new section called :subprojects. There, you can list as many subprojects
as you may need under the :paths key. For each, you specify a unique place to build
and a unique name.
```
:subprojects:
:paths:
- :name: libprojectA
:source:
- ./subprojectA/first/dir
- ./subprojectA/second/dir
:include:
- ./subprojectA/include/dir
:build_root: ./subprojectA/build/dir
:defines:
- DEFINE_JUST_FOR_THIS_FILE
- AND_ANOTHER
- :name: libprojectB
:source:
- ./subprojectB/only/dir
:include:
- ./subprojectB/first/include/dir
- ./subprojectB/second/include/dir
:build_root: ./subprojectB/build/dir
:defines: [] #none for this one
```
You can specify the compiler and linker, just as you would a release build:
```
:tools:
:subprojects_compiler:
:executable: gcc
:arguments:
- -g
- -I"$": COLLECTION_PATHS_SUBPROJECTS
- -D$: COLLECTION_DEFINES_SUBPROJECTS
- -c "${1}"
- -o "${2}"
:subprojects_linker:
:executable: ar
:arguments:
- rcs
- ${2}
- ${1}
```
That's all there is to it! Happy Hacking!
|
