I’d like to set up a Daisy project where libDaisy and DaisySP act as external libraries, ideally placed in a “/libs/” folder of example, within my project structure.
Using the standard “helper.py” script, my project ends up inside the Daisy environment. However, I’d prefer to structure it the other way around, keeping my project independent while referencing libDaisy and DaisySP as external dependencies.
Has anyone successfully set up a project this way? Any suggestions on the best approach?
You can use helper.py anywhere, then edit Makefile to correct relative paths for libDaisy and DaisySP.
I do this all the time, which leaves the DaisyExamples directory ‘pure’.
This architecture question is interesting. I like the question a lot and I contemplated it and came up with one way of separating it but I am doing it the other way around, having it in a separate repo but looking like it is in the tree.
I published my Molysynth yesterday here. Have a look and see if that way of doing it is resonable for you. The advantage is that it works out of the box both independently and as part of Daisy tree, the only disadvantage is that the top level has some Daisy source in it.
Anyway, let us share ideas here. How do other people develop stuff off-line and/or independently of the Daisy source while at the same time making it super easy to put it on the DSP?