[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: Thomas Dickey
Subject: Re: Building 64-bit version of ncurses on Solaris 8
Date: Fri, 1 Feb 2002 20:09:38 -0500
User-agent: Mutt/1.3.21i

On Fri, Feb 01, 2002 at 06:47:54PM -0600, Albert Chin wrote:
> On Fri, Feb 01, 2002 at 07:34:00PM -0500, Thomas Dickey wrote:
> > On Fri, Feb 01, 2002 at 06:05:05PM -0600, Albert Chin wrote:
> > > 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:
> > 
> > The simplest way is to include them from ncurses/base/vsscanf.c -- then
> > you have only to modify that file, e.g.,
> > 
> >     #include <base/triostuff.c>
> > 
> > But it would be better, I think, to add a configure option & check to
> > link against trio.
> I'm doing the same thing that ncurses/base/memmove.c does. I just wrap
> the three .c files in:
>   #if NEED_TRIO
>   ...
>   #endif
> And, in vsscanf.c, I just define the vsscanf function to call
> trio_vsscanf.

I think have the general idea.
> And, there is an autoconf test for vsnprintf and vsscanf that sets
> NEED_TRIO if need be.
> One last item. Why don't you add $(LDFLAGS) when creating the shared
> library? Trio is dependent on -lm which means ncurses will be as well.

I guess I don't add $(LDFLAGS) because I didn't need it (yet).
If we're building something with "ld -r" or similar, it would be
part of the special cases in $(MK_SHARED_LIB).

> Dunno if you're gonna like this though.

If it's too inconvenient, I'll rewrite it.  (I don't know offhand why
it should need the math library, since the ordinary floating-point
stuff is adequate for sscanf's conversions - but it's something to
keep in mind).

Thomas E. Dickey <address@hidden>

reply via email to

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