Subject: Re: symlink for curses.h in buildlink? (Re: pkg/26849: misc/dialog fix for Interix)
To: Jeremy C. Reed <email@example.com>
From: Hiramatsu Yoshifumi <firstname.lastname@example.org>
Date: 09/07/2004 07:40:03
At Sat, 4 Sep 2004 16:24:40 -0700 (PDT),
"Jeremy C. Reed" <email@example.com> wrote:
> On Sat, 4 Sep 2004 firstname.lastname@example.org wrote:
> > Interix uses ncurses for its system curses, but doesn't install ncurses.h.
> > ++#elif defined __INTERIX
> > + #include <curses.h>
> > ++#else
> Shouldn't the buildlink system automatically add the curses.h header also?
> I was thinking that even though we only provide ncurses.h that we'd have a
> symlink for this when buildlinking.
I prefer this buildlink method.
But in this case, the buildlink system needs to detect operating system's
curses implementation from "ncurses", "ncurses without ncurses.h",
"not ncurses but compatible". Are there any robust way to do this detection?
// Hiramatsu Yoshifumi