public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Charles S. Wilson" <cwilson@ece.gatech.edu>
To: dickey@herndon4.his.com
Cc: ehud@unix.simonwiesel.co.il, cygwin@sources.redhat.com,
	bug-ncurses@gnu.org
Subject: Re: ncurses/terminfo problems
Date: Sun, 19 Nov 2000 12:53:00 -0000	[thread overview]
Message-ID: <3A183D91.BC29DC53@ece.gatech.edu> (raw)
In-Reply-To: <20001119150903.A26183@home.dickey.net>

Thomas Dickey wrote:
> 
> On Sun, Nov 19, 2000 at 02:58:13PM -0500, Charles S. Wilson wrote:
> >
> > extern NCURSES_EXPORT(type, funcname) (args....)
> > extern NCURSES_EXPORT_VAR(type) varname
> 
> hmm - is that for mapping to native dll stuff, or part of cywgin's dll
> support?  

it's for mapping to native dll stuff.

> (I thought all of that overly-precise specification was discarded
> long ago since it's too cumbersome for practical use -- except of course on
> win32...)

yep. but we're on win32.

> 
> why isn't 'extern' part of the macro, btw?

because I also had to edit the various scripts, like
ncurses/tinfo/MKnames.awk which defines macros based on other macros:

  #define DCL(it) NCURSES_EXPORT_VAR(IT) it[]

However, DCL(it) is used in the file which **defines** the variables,
not merely in the files which **declare** the variables.  So, you can't
use 'extern' there.

Actually, I originally DID define NCURSES_EXPORT... with 'extern' but
had to remove it (and put it BACK into all the source files from which
I'd removed it) for this reason.

> 
> > Yes, it would be better to fix up
> > libtool/autoconf/automake/Makefile.am/Makefile.in etc.  I'll get to that
> > -- this is just a first step.
> 
> ;-)
> 
> > If you are interested in absorbing the *first* patch for ncurses-5.3,
> > I'll gladly submit it and get the paperwork for FSF copyright assignment
> > filled out...and I'll verify that it doesn't break anything on Linux
> > (Solaris, HPUX) if you like.
> 
> Maybe - the first thing that pops into my head is how it impacts
> lib_gen.c (I assume that still works).

Yes, I had to munge up lots of the scripts to get things right.  *That*
is only part I'm worried about whether it still works on Linux &etc.  (I
*think* it should be okay -- since, in this context,
Linux=Cygwin_static_build)

Scripts affected:

ncurses/tty/MKexpanded.sh
ncurses/tty/MKnames.awk
ncurses/tty/MKfallback.sh
ncurses/tty/MKcaptab.awk
ncurses/base/MKunctrl.awk
ncurses/base/MKlib_gen.sh
ncurses/base/MKkeyname.awk

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-11-19 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-19  9:05 Ehud Karni
2000-11-19 10:15 ` Charles S. Wilson
2000-11-19 10:28   ` Thomas Dickey
2000-11-19 11:47     ` Christopher Faylor
2000-11-19 11:59     ` Charles S. Wilson
2000-11-19 12:08       ` Thomas Dickey
2000-11-19 12:53         ` Charles S. Wilson [this message]
2000-11-19 14:30           ` Thomas Dickey
2000-11-20 15:10 ` J. J. Farrell

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=3A183D91.BC29DC53@ece.gatech.edu \
    --to=cwilson@ece.gatech.edu \
    --cc=bug-ncurses@gnu.org \
    --cc=cygwin@sources.redhat.com \
    --cc=dickey@herndon4.his.com \
    --cc=ehud@unix.simonwiesel.co.il \
    /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).