blob: 1a032f29fd211b48afb13d1f2184340d9175311d (
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
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
|
#@@ if a showcase complicated the initial example then it should
# be implemented as a separate example.
%% build with nested directories from single Makefile
%% generation of headers/sources from some other source with
automatically generated dependencies (IDL showcase)
%% two executables in the same dir (though generally not recomended)
%% selection of PIC by a target (target-specific variables
inheritance) (read the bug report about this feature).
%% directory Makefiles (need a nice name for them)
%@ configuration target
- implemented disfigure only (for now).
- not complete
- need to implement configuration of installed dependencies.
%@ installation target
- prototype design
- needs completion
%@ test target
- only in libhello
%% generation of actual dependencies for C++/C
@@ use of C & C++ compiler from the same Makefile
@@ another C++/C compiler (Sun CC?)
@@ cleaning after messy compilers (Sun CC?)
@@ c subsystem
@@ Quite mode. all answers defaulted. Error if something is wrong.
@@ I need some way of programmatically supplying configuration
information (for example for debian package creation). Via
command line variables seems like a reasonable approach. Also
saving configuration seems like a good idea too (i.e. keeping
configuration around) but then I need to make sure there are
no absolute paths.
%@ Installation process for the build system itself.
- now installs only build system itself.
%% What am I going to do with corba? Maybe package it as a separate
incomplete subsystem?
@% All those "file not found" messages by make are quite nasty. I should
either fix make (preferable) or use -include.
- using -include for now
%% variable unsetting: do I still need it? Yes I do.
@@ installation of examples
@@ need to clean source code out of @@
@! target-specific vpath
@! Can .INTERMIDIATE help me with .d problem? No! Also it seems
saying something like %.o %.d: %.cxx won't work either? Need
to check this.
@! Need to run ranlib on certain platforms. Need to detect if I need to.
@! .cpp-options: if add/remove .cpp-options prereqs the target file does not
get regenerated. Probably need to save list of prereqs and compare with it.
@! shared library versioning
@! Need to think on a general idea of state saving (like I do with
.cpp-options). Is there a cleaner way of doing this?
|
