JNI和Java：蚂蚁电话拨打或使呼叫蚂蚁？ [英] JNI and Java: ant calling make or make calling ant?

问题描述

我只是做我第一次进JNI（Java本地接口）的世界提供文件系统更改通知从特定于平台的C / C ++ code到Java。也就是说，除非有人提出了一些辉煌库这样做，我已经错过了。

I'm just about to make my first trip into the world of JNI (Java Native Interface) to provide file system change notifications from platform specific C/C++ code to Java. That is unless someone suggest some brilliant library for doing this that I've missed.

作为新JNI我已经设法找到它和它的库发电侧接口方面多文档，但我还没有发现太多打造的本地库。

Being new to JNI I've managed to find much documentation on the interface side of it and library generation side of it, but I've not found much on building the native library.

我已经有了基于蚂蚁为pre-现有的Java源的现有版本，所以我试图找出我是否应该让蚂蚁打电话让创建库或者如果它是最好的获得使创建库之后调用蚂蚁？

I've got an existing build based on ant for the pre-existing Java source, so I'm trying to work out if I should get ant to call make to create the library or if it's best to get make to call ant after creating the library?

无论选择跳出作为是非常好的，但双方似乎不是试图让蚂蚁调用编译器编译code和直接生成库越好。

Neither option jumps out as being terribly nice, but both seem better than trying to get ant to call a compiler to compile the code and generate the library directly.

推荐答案

我不喜欢强烈的做，因为它隐含的规则集和治疗空白的。我个人使用cpp任务（ http://ant-contrib.sourceforge.net/cpptasks/ index.html的）做我的C编译。他们不是像化妆那样灵活，但他们也远不复杂，这将意味着你不用负担你的开发人员在学习化妆。

I strongly dislike make because of its implicit ruleset and treatment of whitespace. Personally I would use cpp tasks (http://ant-contrib.sourceforge.net/cpptasks/index.html) to do my C compilation. They are not as flexible as make but they are also far less complex and it will mean you don't have to burden your developers with learning make.

这篇关于JNI和Java：蚂蚁电话拨打或使呼叫蚂蚁？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！