-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C++ support #1
Comments
I can see a couple ways this could work:
2 is a lot easier, but to get maximum benefit, though, I think we need not just 1 but also parts of libavr to embrace C++, or at least move away from global scope variables. |
One of the problems I’d like to solve is to be able to build a zero-globals version of each firmware for VCV Rack so you can load multiple copies of each module without interference. Right now the monome-rack package makes a separate disk copy of each binary for each module you instantiate, to ensure each copy gets their own global memory locations. |
yeah 2 sounds a lot easier. updating libavr32 would make sense if there were more firmwares using it, but if we migrate everything to multipass we don't have to worry about it, right? are there some other benefits to upgrading libavr32 to C++? another thing to consider - aleph also uses libavr32. |
this is to discuss adding support for C++ based platforms - vcvrack etc.
The text was updated successfully, but these errors were encountered: