Re: Curses problem: initscr and endwin missing

I once built the Curses distribution on Windows with PDCurses. I can't recover the details (the machine has been long retired), but it wasn't much harder than specifying the correct locations for the headers and the import library. The result was nice: I was able to run some Perl scripts with Curses, they seemed to behave well.

Comment on Re: Curses problem: initscr and endwin missing

Replies are listed 'Best First'.
Re^2: Curses problem: initscr and endwin missing by hsmyers (Canon) on Feb 18, 2021 at 20:18 UTC
My current plan A is to roll up my sleeves and tear apart the cpan Curses.pm module and see what makes it tick. I'm hoping for here is a plan B or C. I'm using PDCurses with a copied and renamed lib to libcurses. It makes compiling easier. --hsm "Never try to teach a pig to sing...it wastes your time and it annoys the pig."	[reply]
Re^3: Curses problem: initscr and endwin missing by Anonymous Monk on Feb 22, 2021 at 13:54 UTC
Does it tell you anything useful if you run `Makefile.PL` with environment variable `CURSES_VERBOSE` set to a truthy value? It seems that all tests for existence of Curses functions somehow managed to fail.	[reply] [d/l] [select]
Re^4: Curses problem: initscr and endwin missing by hsmyers (Canon) on Feb 22, 2021 at 21:37 UTC
When I installed Curses.pm there were no error messages, suggesting a clean install. There is no reason why I can't run it again to see if there was any indication of something amiss. For that matter, I can add another line or two to the minimal example file and see if it continues happily possible bitching about improper initialization but alive for all that. So what do you do when your fireplace runs out of room for another iron? --hsm "Never try to teach a pig to sing...it wastes your time and it annoys the pig."	[reply]


Clear questions and runnable code get the best and fastest answer
	PerlMonks