Hi Adam and Mark! Great job you've both done! (Voice of Troy McClure :-) Hi, I'm Gerald, you may remember me as the author of the jnicc task... I've submitted it in mid-february, but it didn't generate as much interest as yours... Anyway, looking at your tasks, I think mine stinks :-)
In comparison, I intended my task to be a complete jni solution (as the name implies): it can generate jni header files from java source code, compile C code and link everything into one library (on different platforms)... Have a look at my old post to see how it works (search for 'jnicc' in the dev-list). Of course, you're free to take some of this code (but I don't think you'll find anything good in there). I don't have much time to work on it anymore, but I'd be interested in using the new compiler task you're writing, so I'd like to make some suggestions... It's just what I personally need, see if you can help me without too much more work... (Sorry if I've missed something in your discussion, and say silly things here) - OS checking: I'd like the compiler to run only on a given OS. Like the os attribute of the Exec task. - JNI header generation: There's already a couple of tasks doing this, but why not create a new and better one, that works well and is consistent with your compiler task? And seeing the quality of your code, I'm sure you can do wonders! - I've noticed the 'flatten' option in Adam's task... Does it keep the filename intact, or prepend the directory, a la javah? (com/com/foo/bar.c -> com_com_foo_bar.o) If possible, I'd prefer the 2nd solution, it prevents possible name overlaps... - Combining compiler and linker in one task would be good (for me at least!). Ok, That's all for the moment! I don't have much time on my hands, but if I can help, I will... Cheers, Gerald.
