[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building 64-bit version of ncurses on Solaris 8

From: Daniel Weaver
Subject: Re: Building 64-bit version of ncurses on Solaris 8
Date: Fri, 01 Feb 2002 17:20:33 -0800

At 06:05 PM 2/1/02 -0600, Albert Chin wrote:
>On Fri, Feb 01, 2002 at 03:31:12PM -0500, Thomas Dickey wrote:
>> > I think trio has replacement for all the functions. The libxml project
>> > currently uses it and we haven't seen any obvious problems.
>> > 
>> > We *need* a 64-bit version of the ncurses library so we're prepared to
>> > submit a patch with *some* solution.
>> sure - I don't have any problem with that.  (Disabling the function isn't
>> a very close third alternative).
>What's the best way to conditionally compile the trio files if needed?
>I plan on placing the source files in ncurses/base. A few ideas:

Trio does not have the same copyright as ncurses.  Trio uses a MIT type
of free software while ncurses uses the GNU Copy-left.  The copy-left
strictly forbids mixing copyrights.  Distributing trio sources code
with ncurses would violate the copy-left.

The correct way to use trio is at the library level (not the source level).
It's OK to build a libtrio4ncurses.a file but not OK to mix the sources.
(Include files are a special case and are generally exempt from this

Any changes you make directly to ncurses are also OK because they are
original work.  Read the Copy-left before deciding how to use these
two packages:

>  1. add to ncurses/modules but then they'd be compiled all
>     the time (though not used)
>  2. hack mk-1st.awk and mk-2nd.awk
>  3. modify ncurses/modules at run time with the new trio files
>  4. modify ncurses/modules and add teh trio libraries but
>     preface them by BUILD_TRIO. we'd then run sed on the file
>     before feeding to awk to leave them in or remove them depending
>     on whether or not the trio libraries are needed.
>albert chin (address@hidden)
>Bug-ncurses mailing list
Dan Weaver, ZNYX Networks

reply via email to

[Prev in Thread] Current Thread [Next in Thread]