Standalone from Project does not include explicit dependencies.
Hi all,
it seems there won't be anyone responding to a topic which has been addressed in many posts before, albeit, it never really got solved, besides: The documentation gives information which I cannot confirm. For example:
If you're managing a complex system with lots of potential dependencies, it's often easier to work with a project than to configure your collective manually using the collective editor. When you build a standalone from a project, Max will automatically use the implicit and explicit dependencies of the project to define your collective.
Unfortunately though, these dependencies are not included if they are not part of the toplevel patcher. Thus, one has to add all potential patchers in the toplevel patcher that the standalone may want to access by means of Messages to Max or [pcontrol], for exmaple.
This is basically undesirable and conflicts with the information provided above.
Since there is no Collective Editor for Projects — probably because they are assumed to collect all their dependencies naturally after cnsolidation — an alternative is to open an empty patcher and write a script for all the dependencies of the project, which really means to only define the open [toplevel patchername] and folder [projectofolder]. Is this the way to go then?
The buildcollective message to Max is helpful (as stated in the documentation: for batch collective building) but needs the toplevel patcher to be opened using a unique reference name. All doable but the support for a script is not provided — perhaps a feature request?
What's more, when building colelctives or standalones in batches, it would be very helpful if the target path and apptype could/should be included in the message as well, and the buildplugin message does not differentiate between Collectives and Standalones, which one always has to define. I have posted about this before.
So, what is the conclusion and the best way to ensure all project-dependencies are met after export?
The documentation is not correct as far as I understand it.