excluding externals when building collectives

Feb 27, 2009 at 9:56am

excluding externals when building collectives

Hi there,

I am providing optional support of a commercial external (elastic) in my app, and as I would like to distribute the app as a collective, I need to exclude the locally installed external from being copied to the collective.

I already tried to make it fully dynamic (using js.newdefault), but the external is still referenced (probably the build routine instantiates the patcher tree and copies everything that is referenced).

The build interface doesn’t support exclude, only include. So looks like I am stuck, especially as mxf is not meant to be a means of protection, probably pretty easy to hack in order to get those externals out of it.

any idea ?

#42553
Feb 27, 2009 at 6:08pm

Try adding to the top of your collective script the line “excludeexternals true”. This will exclude *all* externals, but perhaps that is OK.

Rob

#152294
Feb 27, 2009 at 11:33pm
Rob Sussman wrote on Fri, 27 February 2009 19:08
Try adding to the top of your collective script the line “excludeexternals true”. This will exclude *all* externals, but perhaps that is OK.

If you go that route, you can add the externals you do want to include with the collective post facto. At least with Standalones on Mac OS. Just open the Standalone Bundle (Show Package Contents from the context menu in the Finder), and add the externals you need into the Contents/support/ folder. You can place them into a sub-folder called ‘externals’ or something if you want to keep things tidy.

#152295

You must be logged in to reply to this topic.