Craig Southeren wrote:
>
> On Mon, 08 Feb 1999 02:27:31 +0000
> Dr Stephen Henson <[EMAIL PROTECTED]> wrote:
>
> > Josh MacDonald wrote:
> > >
> > > To solve your Makefile problems, I think you should all realize that
> > > the GNU autoconf solution, along with automake and libtool, have
> > > improved dramatically in the last couple of years. With libtool,
> > > your shared library problems are solved completely, with no effort,
> > > and it is supported by the the Cygnus utilities on Windows. What is
> > > the percieved value of perl, if I may ask?
> > >
> >
> > Would it work using VC++ under Windows as the compiler, that is Win 3.1
> > as well as Win32? Yes there is some demand to still support Win 3.1.
> >
> > The main problem with using Cygnus gcc is the license is incompatible
> > with the OpenSSL one: specifically the underlying SSLeay license which
> > we can't change even if we wanted to.
>
> Hear, hear.
>
> As much as the existing configuration system is a pain, please realise
> that not everyone uses Unix and Perl, and that not everyone likes the
> restrictions of the GPL.
(sorry to hear that B-( )
>
> IMHO, the a large part of the success of OpenSSL lies in the fact that
> is *can* be used in commercial products in lieu of proprietary solutions.
>
> Please don't compromise this.
I do not see any problem with this by using the GNU tools to work this.
GPL specificly does _not_ apply to 'documents' created with them.
That is why you can create proprietary products using the gcc.
Due to the underlying license from Eric and Tim we cannot change the
license. But we can use Autoconf and Libtool all we want without
restricting the license of the library. It those tools that you cannot
include in your proprietary software. That is why the distribution
needs to include the 'configure' and not just configure.in and autoconf.
But all you have to do is install the needed tools, that in no shape
or form limit you use with proprietary software, with one small
exception:
you cannot link or otherwise _include_ GPLed stuff in you program.
mfg lutz
--
*******************************************************************
Lutz Behnke Tel.: 040 / 766 29 1423
TC TrustCenter for Security Fax.: 040 / 766 29 577
in Data Networks GmbH email: [EMAIL PROTECTED]
Am Werder 1
21073 Hamburg, Germany
S/MIME Cryptographic Signature