This is a second try at #109, this time by including the curses modules in the static build instead of relying on the .so files in lib-dynload. Note that they are only included in macOS builds where the curses library is provided by the OS. Including curses modules on other platforms would not make such sense.
I think this is the right approach, given how other extension modules are included. However, when using the resulting built in an Xcode project, it will need to link against libncurses and libpanel.
This is a second try at #109, this time by including the curses modules in the static build instead of relying on the .so files in lib-dynload. Note that they are only included in macOS builds where the curses library is provided by the OS. Including curses modules on other platforms would not make such sense.
PR Checklist: