Closed gogins closed 4 years ago
The trouble with the above is inter-dependencies.
Add Scheme support?
First, get rid of some superfluous things.
.
Python packaging is wrong. I'm now building the CsoundAC Python extension module correctly, but it's not being installed by CPack correctly. An experienced user would be able to sort this out.
I'm trying to find Python in csound-extended now just the same way as it is done in csound.
Okay, that works, although it's not really done properly. But as long as Csound builds CppSound for 2.7 it will work. I should get rid of all that.
There is now an issue with the STK opcodes. I will see if it really is an issue. I don't think so.
I should perhaps replace my WebAssembly build with the "canonical" one and put in a shim to preserve my API. On second thought, keep it, as MIDI has been implemented in csound_embind.hpp.
The WebAssembly build now works and Emscripten's node does not interfere with the system node.
I think I have a simpler plan for breaking things up, essentially based on build system and licenses, and not on anything else.
I wonder about switching to GPL 3.0 to bring in Aeolus and VST.
This is nuts. I am trying to fix something is definitely mess but also definitely not broken, when I should be composing. I'm going to get this to build on my nice new little computer and let it go. Maybe I'll break it out into its own repository.
Closing this issue in favor of a simpler one.
Satisfying all dependencies for building csound-extended, which includes many components for several target environments using several languages, has become complex and fragile. This must be changed or I will continually be distracted from composing.
Consider the following options: