verify support for stupid asshole osx

[dankamongmen]

Much as it pains me, we probably ought try to pick up some of that OS X market share. I flat-out refuse to pursue Windows. I don't have any OS X hardware, so ... patches welcome? Testing welcome? Hey @plotfi have apple give me a computer to support notcurses on.

[ghost]

Some pointers for OSX:

• You can generate OSX icons for Linux with icsutils
• An app bundle dmg is just an iso with a special structure. It can be created on Linux also. Here is one example.
• Alt-{something} keystrokes on OSX generally do not result in ESC-{something} as they do under xterm with metaSendsEscape. Instead it is Cmd-{something}, IF that setting is enabled in the Terminal.app / iTerm2 profile.
• OSX fixed-width fonts generally suck for line-drawing / CP437 glyphs. If you need something that really looks like "VGA" but with Unicode codepoints, this TTF version of Terminus is pretty good, it might be worth pointing your users to if they complain of missing glyphs.

[jaroslov]

Trying to build on a bare-bones macOS dies when looking for 'tinfo>=6.1;ncursesw>=6.1'. The terminfo on latest macOS is 5.7; the ncursesw is 5.7. Both are 2008 vintage. That was a shit year — not as shit as 2020 — but still pretty shit.

[jaroslov]

brew install ncurses drops 6.2 into a 'keg', but the CMakeFile isn't playing ball.

==> Caveats
ncurses is keg-only, which means it was not symlinked into /usr/local,
because macOS already provides this software and installing another version in
parallel can cause all kinds of trouble.

If you need to have ncurses first in your PATH run:
  echo 'export PATH="/usr/local/opt/ncurses/bin:$PATH"' >> ~/.zshrc

For compilers to find ncurses you may need to set:
  export LDFLAGS="-L/usr/local/opt/ncurses/lib"
  export CPPFLAGS="-I/usr/local/opt/ncurses/include"

For pkg-config to find ncurses you may need to set:
  export PKG_CONFIG_PATH="/usr/local/opt/ncurses/lib/pkgconfig"

==> Summary
🍺  /usr/local/Cellar/ncurses/6.2: 3,913 files, 8.6MB

Anyways, I know jack-all about CMake, so the best I can do is look at line 68 and say to myself "gee! it'd be great if I could point you somewhere else!"

I just changed the tinfo/ncursesw versions to look for 5.7, because that's totally safe. I commented out the need for librt, because fuck it — that's how Apple compiles it's posix4, anyways.

The Makefile generates, but dies when it can't find uchar.h.

... that may be the showstopper. uchar.h is simply not available, at any price, on macOS.

Maybe I could hack this out to just support ASCII. In case you're not aware, ASCII is just like UTF-8, as long as you pretend the rest of the world doesn't exist. And about 2/3rds of the US.

[kdheepak]

I'm also interested in using notcurses on osx, and ran into the same issues mentioned above. I'm wondering if there's any potential ideas for working around this?

[Charadon]

Yeah, that's where progress ends for Windows also, it gets stuck at not finding uchar.h.

[dankamongmen]

oh hey holy shit, i missed all the action on this bug! catching up....

[dankamongmen]

Rumor has it that @grendello has taken ownership of a Mac, and is looking to do something here! and there was much rejoycing.

[dankamongmen]

https://github.com/dankamongmen/notcurses/runs/1101716635?check_suite_focus=true we now have a github action CI for macos, meaning this might move forward!

[jaroslov]

HAWT.

[kdheepak]

Has the CI for macos been dropped again? I don't see it in the latest commits.

[dankamongmen]

there's never been any ci for mac, so far as i'm aware?

[dankamongmen]

https://drone.dsscaw.com:4443/dankamongmen/notcurses/ if you can see this, this is all the ci i know of

[kdheepak]

Sorry, I thought your previous comment here in this thread suggested that there might have been a CI at some point: #195 (comment)

[dankamongmen]

Sorry, I thought your previous comment here in this thread suggested that there might have been a CI at some point: #195 (comment)

oh no problem, just wanted to make sure we hadn't stood up some OS X CI without me knowing =]

[dankamongmen]

recent events have me hoping that this will see life by 3.0.0 this fall

[dankamongmen]

Initial OSX support is present. It currently requires exporting several directories as PKG_CONFIG_PATH, which will obviously need to get fixed. Other than that, everything seems to work.