Commit | Line | Data |
---|---|---|
25924cae | 1 | - remove support for LIBT2N_EXPORT_GROUP(group) (this will simplify the generator a lot) |
7309b9a1 JT |
2 | - add option similar to gccs -MD (at the moment it is a fixed set of files generated and |
3 | they are handled in the makefile) | |
84b484fa JT |
4 | |
5 | open questions: | |
6 | - should projects using the codegen depend on installed version of ... or ship their own version? | |
e62269cb JT |
7 | * codegen binary: no |
8 | * Makefile snippet: no | |
84b484fa | 9 | * codegen-stubhead.hxx |
e62269cb JT |
10 | - get rid of codegen-stubhead.hxx or include a "copy" in each project |
11 | - makefile snippet must work for builds outside of libt2n | |
12 | (=> some variables must be set by configure, the snippet must be installed | |
13 | => pc file template must be installed, too) | |
26eca3d8 JT |
14 | |
15 | the variables which must be set: | |
16 | LIBT2N_CODEGEN="\$(top_builddir)/codegen/libt2n-codegen" | |
17 | LIBT2N_CLIENT_PCTEMPLATE="\$(top_srcdir)/codegen/clientlib.pc.in" | |
18 | LIBT2N_CODEGEN_MAKESNIPPET="include \$(top_srcdir)/codegen/codegen.make" | |
19 | ||
20 | LIBT2N_CODEGEN will be handled by AC_PATH_PROG | |
21 | the other two? can't we use pkgconfig?! | |
22 | perhaps best provide a m4 macro for use with autoconf? | |
23 | ||
24 | AC_DEFUN([LIBT2N_CODEGEN ... | |
25 | ||
26 | alternatively we could add a option --datadir to codegen which prints out the | |
27 | path to clientlib.pc.in and codegen.make | |
28 | (first solution is the better one) | |
29 | ||
30 | we can use pkg-config => best solution | |
31 | ||
1f0aa49f | 32 | - it would really be much nicer if the client lib includes would not depend upon boost serialization |
cf406235 JT |
33 | i thought a solution would be to provide this optionally by wrapping the corresponding includes in a #ifdef |
34 | but this does not work since command.hxx is included which depends on boost serialization headers anyway | |
35 | => we do not provide this for now | |
26eca3d8 | 36 |