Closed jofemodo closed 5 years ago
Hey, this assumes you have the soundfonts copied from somewhere - I suggest that is added to the docs and it needs to be a command before the build.
Yes. I've copied the files by hand. As it's not overwriten by the "git pull", i don't think is needed to do that on every build. The soundfonts are more than 3GB ... We could do an "if [ ! -d blablabla ]" ...
Also, is a problem to do it the "unpack" call after the building process? I hope no ...
Regards,
Regarding the copying of soundfont files ... is really needed to make a hard-copy or it would work with a soft link?
I'm cancelling this PR and will create a new one ...
Hi @guysoft !
As we are really close, i would like to start including soundfonts in the build. Perhaps it will be better if we could have 2 different builds:
What is the best way of achieving this? CustomPiOS variants? Or better to have 2 different modules? Or perhaps having 2 projects in Jenkins and using an environment variable for configuring this?