At present, use JUCE programming, rely Introjucer to create and manage the project which undoubtedly convenient, however, the traditional “amalgamated” still has a great advantage and flexibility. Mr.Vinnie done a lot of useful work to provide people with more choices. We shouldn’t ignore his selfless dedication.
I have a question, by JUCE updates quite frequently, “amalgamated” with sync and consistent? Or always behind the latest version of JUCE module source code? How to resolve this conflict?
There are two amalgamations. One is the “pretend” amalgamation in the Juce distribution, which is not a true self contained amalgamation. The other is the amalgamation that I have put together using my modified version of the old Juce amalgamation tool. This true amalgamation is here:
http://github.com/vinniefalco/JuceAmalgam
You asked about the amalgamation staying “up to date”. I do plan on periodically recreating the amalgamation to reflect Jules changes in the master branch. Say, a couple of times a month. When Jules puts out tagged version of Juce I will definitely recreate the amalgamation, and tag it with the same label in my own repo. So you can always refer to a tagged amalgamation.
This having been said, unless you are picking up a new feature that you need, or there is a bugfix that you must obtain in order to move forward, there is no real disadvantage to having Juce sources that are a little out of date.
Now if you want to rebuild the amalgamation yourself, it is pretty straightforward, everything for doing so is in the “Source” directory of the JuceAmalgam repo. You also need to pick up my amalgamation tool:
You would also need to clone the Juce repo and make its directory a sibling of the Amalgamate tool directory (which should also be a sibling of the JuceAmalgam directory).
Thanks Vinnie, I have downloaded your Juce Amalgamation, I’ll attempt to more research and use.
