Anthony Green <[EMAIL PROTECTED]> writes:

> 2. Merge the projects into a single source base in support of all of
>    our combined goals.
> 
> [2] is also possible.  It will require developing a new build system
> in which we can specify JNI or CNI bindings.  In libgcj, we currently
> put CNI code in the directory with the java source.  It's easy to
> imagine creating cni and jni subdirectories for each package and
> maintain that code separately.  It's a little more complicated than
> this - but that's the general idea.
> 
> Deciding which way to go is important, but not as important as simply
> agreeing to work together.  The first step towards working together is
> for Cygnus to assign all of its libgcj code to the FSF, and for us
> both to adopt the GPL+exception license.

First, I'm in favor of adopting a license which allows for static
linking in a manner similar to how we allow dynamic linking now.  I
leave it to Cygnus and the FSF to work out the legal details because
IANAL.  

I prefer [2].  I feel that [1] does not go far enough to allow for
complete collaboration.  I'll examine [2] and send email to the list
on how I think it could be done including layout, etc.  Anthony is
obviously far more familiar with libgcj's build than I am so I really
appreciate your input.  Hmm, maybe we can even get all this worked out
and done before the end of the year.  :)

Brian
-- 
Brian Jones <[EMAIL PROTECTED]>

Reply via email to