Closed mmuman closed 5 years ago
Hmm I'm concerned about the utf8.h header in includes/ … shouldn't it be in a subdir?
I wrote a haikuports recipe. The base package is empty because no dynamic lib, not sure I should make one though…
Can you tell me what you mean about utf8.h? Would you prefer it to be put into something like includes/linenoise/utf8.h
Yeah, it would make more sense I think. The name is generic enough it could collide with a system header. On Haiku at least we have a UTF8.h header in os/support (but it's in the default search path) for example. Now, do you really need a separate header for just 3 functions?
There you go, recipe available ;-)
These make it work on Haiku.