Closed redconfetti closed 7 months ago
Thank you! I need to have a look, probably some change in the ICU library as you mentioned.
And you're correct, to make a new adaptation you only need Python - the C++ code will load the Python module as a "driver" to parse and compose MIDI messages to talk to the synth.
The .github/workflows/builds-macos.yml contains the following code.
brew reinstall icu4c
and does the configure with
cmake -S . -B build -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_PREFIX_PATH=/usr/local/Cellar/icu4c/73.2
This is missing from the documentation, but then again the code always wins anyway. I use the macos-latest build machines from github.
@redconfetti Thanks again for all the info and work! I have updated the documentation and the build files to make it easier to find the right icu4c version, but sadly there is a difference between Intel Macs and Apple Silicon Macs on where to search for it, so I made a comment in the README and the CMakeLists.txt to clarify this further.
let me know if you need any help with the adaptation you're planning!
I'm new here, and have tried to read the docs to make sure I'm doing things right. I intend to create an Adaptation for the Alesis QSR (Quadrasynth rack module). I'm not sure if getting a build environment is necessary for Adaptations. They appear to be Python powered, not C++.
ICU4c Version Updated
I ran into an issue with the ICU path. This was resolved by updating the ICU_ROOT path to reflect the current version installed by Homebrew, 74.2.
Header Not Found
However now I'm running into an issue during the build where an ICU related header isn't being found.
If I comment out the header include, I get these errors:
I am a Ruby dev, not a C++ dev, so I'm not very adept at resolving what might be a minor build issue.
I figure that the version change to 74.2 caused this. I see that the ucnv.h still exists in that release.
Rollback ICU4c Version
I explored installing an older version of the icu4c library, but that doesn't appear available with Homebrew
I don't see the Adaptation programming guide mentioning that you need a build environment. It sounds like the application makes use of Python adaptations, so I'm going to just try to use a published build for now. I'm leaving my notes here just in case it helps others.