X-Git-Url: http://developer.intra2net.com/git/?p=libt2n;a=blobdiff_plain;f=codegen%2FTODO;h=a40a06dddd4d02049997049fad1bb4734a970c9b;hp=cbc6c1c8d8f4bdc01e365d868f51642067be165e;hb=d37ba346490f74d11dbd2e676d6968b2cb46af8c;hpb=630ececc28458d4442e8a128f215f2450f46bf95

diff --git a/codegen/TODO b/codegen/TODO
index cbc6c1c..a40a06d 100644
--- a/codegen/TODO
+++ b/codegen/TODO
@@ -1,36 +1,26 @@
 - remove support for LIBT2N_EXPORT_GROUP(group) (this will simplify the generator a lot)
 - add option similar to gccs -MD (at the moment it is a fixed set of files generated and
-  they are handled in the makefile)
+  they are handled in the makefile snippet [codegen.make])
 
 open questions:
 - should projects using the codegen depend on installed version of ... or ship their own version?
-	* codegen binary: no
-	* Makefile snippet: no
-	* codegen-stubhead.hxx
-- get rid of codegen-stubhead.hxx or include a "copy" in each project
+- get rid of codegen-stubhead.hxx or include a "copy" in each project?
+  first we said yes but now i say no because the lib depends on the libt2n headers anyway
 - makefile snippet must work for builds outside of libt2n
-  (=> some variables must be set by configure, the snippet must be installed
-   => pc file template must be installed, too)
-
-   the variables which must be set:
+  => some variables must be set by configure
+  the variables which must be set:
 	LIBT2N_CODEGEN="\$(top_builddir)/codegen/libt2n-codegen"
 	LIBT2N_CLIENT_PCTEMPLATE="\$(top_srcdir)/codegen/clientlib.pc.in"
 	LIBT2N_CODEGEN_MAKESNIPPET="include \$(top_srcdir)/codegen/codegen.make"
 
-   LIBT2N_CODEGEN will be handled by AC_PATH_PROG
-   the other two? can't we use pkgconfig?!
-   perhaps best provide a m4 macro for use with autoconf?
-   
-	AC_DEFUN([LIBT2N_CODEGEN ...
-
-   alternatively we could add a option --datadir to codegen which prints out the
-   path to clientlib.pc.in and codegen.make
-   (first solution is the better one)
-
-   we can use pkg-config => best solution
+  we store the variables in the .pc file of libt2n
+  maybe wrap the calls to pkg-config in a m4 macro
+  (=> projects using libt2n-codegen need only one line in configure.in)
 
 - it would really be much nicer if the client lib includes would not depend upon boost serialization
   i thought a solution would be to provide this optionally by wrapping the corresponding includes in a #ifdef
   but this does not work since command.hxx is included which depends on boost serialization headers anyway
   => we do not provide this for now
 
+- add example using a generated client library
+  (=> depends on installed example)