Forgive my ignorance of how C and Cython interact with pygame_sdl2, but working code suddenly began exploding after the holidays on attempting to initialize the mixer. I pulled the newest master, tried reinstalling SDL2 and all dependencies, relinking, but I cannot get a working state.
I have tried a fresh virtualenv, brew installing dependencies, running fix-virtualenv (which now states it has already been run even on new virtualenvs, which seems odd). I will look into how python -m venv constructs virtualenvs vs the external virtualenv (old method), as I re-created new venvs, which may be involved.
It appears FLUIDSYNC has been renamed to MID and MODPLUG has been removed entirely, but I am not familiar with this code so this is shooting in the dark. It's possible this has even been addressed or doesn't affect pyame_sdl2, I'm just trying to collect as much pertinent info as I can.
I read a lot of potentially conflicting information regarding setup of mixer and SDL on Mac, and I've been cargo-culting for a while now (brew install + throw SDL2.framework into /Library/Frameworks). Is there a good rundown I can read somewhere on how pygame_sdl2 knows where to access SDL2.framework so I can troubleshoot? I would like to get comfortable enough to debug things like this on my own so I can contribute, as I very much enjoy this project.
The interesting bit in my debug trace may be here: mixer.cpython-36m-darwin.so 0x000000010f8271b8 __pyx_pw_11pygame_sdl2_5mixer_3init + 1336 (pygame_sdl2.mixer.c:2424)
BrandonBlair
commented
6 years ago
Forgive my ignorance of how C and Cython interact with pygame_sdl2, but working code suddenly began exploding after the holidays on attempting to initialize the mixer. I pulled the newest master, tried reinstalling SDL2 and all dependencies, relinking, but I cannot get a working state.
I have tried a fresh virtualenv, brew installing dependencies, running fix-virtualenv (which now states it has already been run even on new virtualenvs, which seems odd). I will look into how python -m venv constructs virtualenvs vs the external virtualenv (old method), as I re-created new venvs, which may be involved.
Example:
I read about a change to mixer header here: https://hg.libsdl.org/SDL_mixer/diff/92882ef2ab81/SDL_mixer.h
It appears FLUIDSYNC has been renamed to MID and MODPLUG has been removed entirely, but I am not familiar with this code so this is shooting in the dark. It's possible this has even been addressed or doesn't affect pyame_sdl2, I'm just trying to collect as much pertinent info as I can.
I read a lot of potentially conflicting information regarding setup of mixer and SDL on Mac, and I've been cargo-culting for a while now (brew install + throw SDL2.framework into /Library/Frameworks). Is there a good rundown I can read somewhere on how pygame_sdl2 knows where to access SDL2.framework so I can troubleshoot? I would like to get comfortable enough to debug things like this on my own so I can contribute, as I very much enjoy this project.
The interesting bit in my debug trace may be here:
mixer.cpython-36m-darwin.so 0x000000010f8271b8 __pyx_pw_11pygame_sdl2_5mixer_3init + 1336 (pygame_sdl2.mixer.c:2424)