-
Notifications
You must be signed in to change notification settings - Fork 326
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
faust2daisy generated code does not compile for -pod or -patch option #1089
Comments
In this part of the daisy architecture (ex_faust.cpp) the corresponding gui source files are included.
ValueConverter.h is included in DaisyControlUI.h and DaisyPatchInitControlUI.h |
Well But this means a bit of work ((-; |
hmmm... unfortunately I don't have this hardware to verify that stuff finally, since I've built my own hw interface for the raw daisy seed board. I could do it in blind mode without testing on the patch / pod only but thats not that good idea I think. |
Despite the fact that the code is duplicated, from the preprocessor logic the the weird thing is that ValueConverter.h is not included for the -pod and -patch Option. Don't get it why... |
But you could at least test if the restructured code would compile right ? |
lol... you owned me. Okay, I do my best, but it may need some days till I find the time. I hope someone can then test the code on hardware. |
faust2daisy generated code does not compile for -pod or -patch option
When compiling code using
faust2daisy
with option -pod or -patch the code does not compile.Only -patchsm is working.
The problem is that somehow ValueConverter.h is not included in the generated cpp file.
Steps for reproduction
Versions Used:
Daisy Toolchain Setup on Linux:
Create a folder, e.g.
$ mkdir ~/daisy
Get arm-none-eabi:
Get libDaisy:
Create
environment.rc
file with the following content:Compile libDaisy:
Compilation:
when running make within the generated folder
$ cd minimal_example $ make
a lot of the compilation errors appear, since ValueConverter.h is not included:
The text was updated successfully, but these errors were encountered: