My workflow is to use the BinaryBuilder in the
JUCE/extras/BinaryBuilder directory to create the BinaryData.h/.cpp files and give them a namespace unique to my module.
Then I copy that file into the module, including the generated files in the module.h/.cpp.
Ideally I save a little shell script to update the file (so I don’t have to look it up again).
BinaryBuilder! Visit www.juce.com for more info.
Usage: BinaryBuilder sourcedirectory targetdirectory targetclassname [optional wildcard pattern]
BinaryBuilder will find all files in the source directory, and encode them
into two files called (targetclassname).cpp and (targetclassname).h, which it
will write into the target directory supplied.
Any files in sub-directories of the source directory will be put into the
resultant class, but #ifdef'ed out using the name of the sub-directory (hard to
explain, but obvious when you try it...)