libdejector-devel Mailing List for libdejector
Brought to you by:
abiggerhammer,
robhansen
Menu
▾
▴
libdejector-devel
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
|---|
|
From: Robert J. H. <rj...@si...> - 2005-12-28 12:25:31
|
Here's an interesting question for you. Consider the canonical "./configure && make && make install" dance. There are some interesting questions re: targets. * Which language bindings should be built? * How do we know where to install them? There are (at least) three ways to address this. The first one is quick but dirty, and the last is more complex but better. * We require Perl, Python, Java, PHP, etc., in our configure script This has the major disadvantage of if you just want the PHP wrappers, you have to install the JDK anyway. On the other hand, it has the major advantage of being quick to code and dead simple. Our makefile target is simple: we make all the bindings and install them to their default locations. * We require Perl, Python, Java, PHP, etc., in our configure script and have specialized Makefile targets Like above, but instead of "make" you'd do "make python ; make python-install", "make perl ; make perl-install", etc. Advantage is that it only builds what you want. Disadvantages are that (a) it breaks the standard Autotools build dance, and (b) if you've already got all the languages anyway, why not build everything all at once? It's not like the SWIG bindings take a long time to compile. * We default to only Python, but allow options to configure to enable other bindings to be build. (e.g., "./configure --enable-perl --enable-php --disable-python") Advantage: it's the most Autotoolsy solution. Disadvantage: ... it's the most Autotoolsy solution. I have no idea how to do conditional compilation in Autotools. I strongly suspect it would end in tears, bloodshed, thoughts of suicide and homicide, and me slinging a lot of m4 macros around. Thoughts? |
|
From: Robert J. H. <rj...@si...> - 2005-12-20 05:06:17
|
Meredith L. Patterson wrote: > Also, feel free to change the deadlines of any of the tasks I created; I > picked 31 January as an arbitrary "that sounds achievable" timeframe. 31 Jan is pretty achievable. We can probably get them knocked out by January 16, but don't quote me on that. Well, at least, bindings for Perl and PHP--I don't know how much work will be involved in libsablot or the grammatical foo. The good news is compare.c should be trivial to port to libsablot. |
|
From: Meredith L. P. <ml...@th...> - 2005-12-19 15:57:27
|
Rob, We had discussed a number of improvements to be made to the libdejector engine, scripting language support, grammars, &c. In the interest of keeping a list, I've added a number of tasks to the Tasks list on the libdejector SourceForge page. I assigned you all the SWIG-related ones, and all the grammar-related ones to myself. I also assigned the libsablot port to myself, and created a "multiple bracketings" task that's unassigned. If you'd like to claim it, feel free; if not, it can wait. Also, feel free to change the deadlines of any of the tasks I created; I picked 31 January as an arbitrary "that sounds achievable" timeframe. --mlp |
