How fist-shakingly infuriating! Let's assume for a second that I'm a stubborn fellow and want these to play nicely together so I can develop on my mac with python (instead of using c/cpp). The c/cpp samples work fine and dandy, but getting python to work? Ugh.
I've built the .dylib (the mac equivalent of a dll/so) and python can load it without a problem, but as soon as samples_py.py tries to run (using pythonw, the OS X way to run python code with GUIs):
libtcod.console_init_root(80, 50, 'libtcod python sample', False)
the terminal barfs and spits out:
Python[72013:60f] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Error (1002) creating CGSWindow'
along with a long stacktrace (the most relevant sections being):
11 libSDL-1.2.0.dylib 0x000000010222733f SDL_SetVideoMode + 527
12 libtcod_debug.dylib 0x00000001021c534f TCOD_sys_init + 755
13 libtcod_debug.dylib 0x00000001021a4056 TCOD_console_init + 390
14 libtcod_debug.dylib 0x00000001021a3ece TCOD_console_init_root + 279
Googling around, there's some strangeness with how OS X deals with making UIs and some people suggested using pygame to do the heavy lifting via putting this at the top of the samples_py.py (or libtcod.py):
which sadly results in a seg fault in pygame.
Some other sites reported a possible issue with the way applications register on the Mac and there was a bunch of ObjC that I didn't understand, and I didn't want to try to start understanding ObjC (though maybe that's the next step?).
Something's amiss and I'm running out of possible ideas. I imagine I'm not the first to try to cross this chasm (nor will I be the last), but if anyone's had any further success here, I'd be much obliged.