This is the mail archive of the
mailing list for the Mauve project.
Re: Using Mauve for Our Project
- From: Stephen Crawley <crawley at dstc dot edu dot au>
- To: "PureNative Software" <info at pure-native dot com>
- Cc: mauve-discuss at sources dot redhat dot com, crawley at piglet dot dstc dot edu dot au
- Date: Tue, 29 Jul 2003 13:51:22 +1000
- Subject: Re: Using Mauve for Our Project
> I am presently involved with the NewJ Library for C++, a cleanroom
> implementation of the Java API in 100% native C++, for C++ environments. It
> uses natural C++ like CNI does, but it does not require any VM at all and
> works with regular ANSI C++ compilers (like gcc and VC++) without requiring
> extensions. We have been using Mauve internally for some time now and are
> really benefiting from it. In fact, we have converted the entire Mauve
> project to native C++. We are wishing to make this native C++ version of
> Mauve available as open source to the public. However, the NewJ Library for
> C++ just like Sun's Java Platform is based on open standards but is not open
> source. Thus, compiling our C++ version of Mauve requires our NewJ Library
> header files and static library, which are not open source. (The Trial
> Edition is available as a free download from our Web site at
> http://www.pure-native.com.) Is it permissible for us to distribute our C++
> version of Mauve to the public without the underlying library being open
> source? This seems partially covered by the FAQ but we wish to have some
> clarification before proceeding. Thank you in advance.
Don't make any decisions based on your interpretation of the Mauve FAQ.
The Mauve software is covered by the terms of the GNU Public License.
For more information, refer here:
You would also be advised to talk to a lawyer.