Commit | Line | Data |
---|---|---|
22c93e2c JT |
1 | multiple command groups test: howto multiplex multiple commands on one stream? |
2 | don't multiplex but a select on multiple groups would be nice | |
3 | ||
4 | include problem: | |
5 | - i don't see a solution using gccxml | |
6 | - a simple solution would be to have a special include file containing the neccessary includes (or 2: one for the type definitions and one for the serialization) | |
7 | - another solution would be to extract the includes from the file and add them to the generated code | |
8 | both solutions only work if the include paths used during compilation of a program using the library are correct[tm] | |
3ac2ff0e | 9 | now we use the first solution |
22c93e2c | 10 | |
0cfa3fb2 | 11 | - test using valgrind |
a3b94a2c JT |
12 | - would be nice to reduce amount of changed files |
13 | (codegen output is often the same as the existing files - something similar to ccache | |
14 | for codegen - but not overwriting output files if they are the same) | |
7f435356 | 15 | - howto include the part after "# always the same:" in all makefiles (using the codegenerator) |
44a58add | 16 | (we now use make's include) |
373558f7 JT |
17 | - lib name should be group name + suffix/prefix ?! |
18 | user should have complete control => no default suffix/perfix | |
19 | headers should be installed in pkgincludedir? maybe yes on the other hand | |
20 | the user can pass the directory to configure via --includedir | |
044cb458 JT |
21 | - the example should not get installed (but still it should show how to build a lib that gets installed :-( |
22 | (overwriting install: doesn't work) | |
373558f7 JT |
23 | => perhaps split libt2n package into 3 packages? |
24 | libt2n | |
25 | libt2n-example-codegen | |
26 | libt2n-example-libusage | |
7f435356 JT |
27 | - at the moment make dist from within a clean source will not work |
28 | (this is related to the nodist problem / old automake version) | |
29 | this is caused by BUILT_SOURCES not working for make dist(check?) | |
30 | and the dependency generation | |
31 | ||
32 | distcheck -> dist -> distdir -> DISTFILES | |
33 | ||
34 | all -> all-redirect -> all-am -> Makefile -> BUILT_SOURCES => bene | |
35 | ||
36 | => how to add dependency on BUILT_SOURCES for dist? | |
37 | the real problem is that make dist should not depend on BUILT_SOURCES | |
38 | unfortunately we can't fix this as long as we use a old automake version | |
53b891ed | 39 | (DISTFILES includes generated files we would like to mark as noinst) |
d0a97d0b JT |
40 | - make clean / make distclean?! make clean geht beim zweiten mal nicht |
41 | now it works?! why?! | |
42 | das ganze ist abhängig davon in welchem verzeichnis man ist?! | |
43 | das problem ist: | |
44 | BUILT_SOURCES -> generierte files -> codegen ! | |
45 | (make clean in toplevel src dir -> codegen does not exist) | |
46 | ||
47 | => how to get rid off BUILT_SOURCES | |
48 | or how to get rid off dependency off clean and dist on BUILT_SOURCES files ? | |
49 | (the nodist problem) | |
50 | ||
51 | getting rid off BUILT_SOURCES would not suffice | |
52 | (explicit dependencies still would depend upon the files) | |
53 | => the real problem is the missing nodist | |
54 | ||
55 | => workaround for old automake version? | |
56 | a workaround would require us not to use _SOURCES but still be able to add object files | |
57 | to the libs/bins created | |
58 | looking at the generated Makefile this perhaps could be done via _OBJECTS | |
59 | ||
60 | nodist wurde mit automake 1.5 eingeführt (2001-08-23) | |
61 | ||
62 | what doesn't work: | |
63 | - make dist and make clean only work if you did a make all | |
64 | ||
65 | hmm Makefile should not depend on BUILT_SOURCES | |
66 | http://sources.redhat.com/ml/bug-automake/2000/msg00040.html | |
67 |