Date:	Tue, 10 Oct 2000 08:10:51 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: Memory amount and PMODE
In-Reply-To:	<v2p4uskshf9medv9uaoqlrb3l58bt27r0r@4ax.com>
Message-ID:	<Pine.SUN.3.91.1001010080735.6606G-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 10 Oct 2000, Damian Yerrick wrote:

> This has me a bit worried: You mentioned that CWSDPMI r5 can be
> linked into an application.  Will this have the same viral effect
> that cygwin.dll has (any app built with CWSDPMI r5 must be GPL'd)?
> Or will there be a libstdcxx-style exception?

CWSDPMI is already distributed with the same exception as djdevNNN.zip: 
you are allowed to use the unchanged binary without implying GPL.  Only 
if you change the sources, your work falls under GPL.

This doesn't change with r5, so I don't see any point in worrying.

> >and tools needed to rebuild the application with the updated code.
> 
> Wouldn't redistributing Borland C++ be copyright infringement?

CWSDPMI distribution doesn't include Borland's tools.

> Or is there some other way to build CWSDPMI?

There's only one way: you need to have Turbo C 2.x or later.

- Raw text -