| Re: JNI Best Practices with JDT/CDT? [message #75414] |
Thu, 10 July 2003 12:54 |
Eclipse User |
|
|
|
I checked it out, if you set up the project dependencies properly you should
be able to
have the projects built in the right order, and thus, with a proper
makefile, you could call
javah after your java classes are built.
JohnC
"John Camelon" <jcamelon@rational.com> wrote in message
news:behlkd$thj$1@eclipse.org...
> <user@domain.invalid> wrote in message
> news:3F0C2F09.2070202@domain.invalid...
>
> > I've now got the notion that what I'll really want to do is set up two
> > projects -- a Java project for the Java code and a second, C project
> > (which depends on the Java project? I think this is possible) for
> > building the C code in a more convenient manner. In this scheme it is
> > note entirely clear where the javah step might go. Ant? A new plugin?
>
> For the time being, C/C++ projects are not expected to have Java Natures.
> While
> there is nothing to prevent this currently, I'm sure it is not a
> configuration that we have
> tested much (if at all).
>
> I would believe that you could call javah a step in your regular makefile
> for building the C project.
> I am not sure currently how we handle inter-project dependencies for
> projects of different natures
> wrt build.
>
> JohnC
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03666 seconds
Home