> > Hmm... Nearly nothing really portable or generalizable here. Mainly
> > addition of some proprietary threading code,
>
> Was it enough to change files in arch/?
>
Most of the Chorus specific code takes place in arch/ but some
unixims have to be disabled/rewritten elsewhere.
> > removal of unix-style signal handling
>
> Same as the windows port required.
>
> > and replacement of new/delete operators by calls to malloc/free.
>
> Ah, yes. I would also get it to compile without a C++ compiler.
> Unfortunately, it is required to get the JNI work with C++
> programs. :-(
>
In that case, it was motivated by unresolved references at link time.
One just have not to forget to set the vtable after the call to malloc :-)
> Please send patches. :-)
The port is currently too ugly. Too many OS-specific hacks
outside of the arch/ branch... Then, it does not use the
autoconf/automake/libtool stuff but specific Imakefiles.
--Christophe
