From: "PureNative Software" <info@pure-native.com>
To: <mauve-discuss@sources.redhat.com>
Subject: Using Mauve for Our Project
Date: Fri, 25 Jul 2003 03:00:00 -0000 [thread overview]
Message-ID: <00d301c35259$2c0c5ac0$9865fea9@yourviu5vcdub5> (raw)
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.
Regards,
Vargas
PureNative Software
next reply other threads:[~2003-07-25 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 3:00 PureNative Software [this message]
2003-07-29 1:00 ` Brian Jones
2003-07-29 3:51 ` Stephen Crawley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00d301c35259$2c0c5ac0$9865fea9@yourviu5vcdub5' \
--to=info@pure-native.com \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).