Closed elfring closed 10 years ago
I see the need for these things in larger projects, but this project has one library and 6 source files, so it just seems like unneeded complexity.
The only advantage I can think of now, would be to automatically select curses based on the available libraries (ncurses, ncursesw, pdcurses). But autoscan does not even show it as a dependency.
Would you like to be able to select the appropriate interface for the library "curses" by a configuration script?
If you like to make a proposal, that would be great. But the current solution works fine except for Windows, so no need for it.
I suggest to reuse a higher level build system than your current small make file so that powerful checks for software features will become easier.