AFAICT the Java XPCOM folk decided long ago to not be involved in 
the mozilla trunk. xpcom/typelib/xpidl/xpidl_java.c is slowly 
rotting.

We're accepting patches. File a blackwood bug (Component: Java to 
XPCOM Bridge). Perhaps someone will do the work.

John.

Marcus Fellinger wrote:

> Currently, there are two versions of xpidl that accept the -m java 
> parameter, and generate java code. One is in xpcom/typelib/xpidl, the 
> other is in java/xpcom/java/xpidl. However, only the later will generate 
>  compilable java-code.
> 
> If you use the xpidl from the xpcom-tree, it will produce .java-files 
> that contain nsID symbols. However, nsID was removed from Blackwood some 
> time ago, and replaced with IID, CID, and ID. The xpidl from the 
> java-tree correctly uses these.
> 
> If one first builds SeaMonkeyAll, and then Blackwood, the xpidl from the 
> java-tree won't be build, because a newer version already exists from 
> the SeaMonkey-build. So, the wrong xpidl-version is used, causing the 
> build to brake.
> 
> We should integrate the xpidl-for-java code into the main xpidl-code, or 
> drop the java-support from the main xpidl-code, and give the two 
> versions different names, so there won't be any build conflicts.
> 
> What do you think about this?
> 
> - Marcus
> 


Reply via email to