Build standalone application with message to MAX

AlexandreAudio's icon

Hi,

I would like to build a standalone application (.exe) with the message to Max on Windows (10). So I found in the documentation the message "; max buildcollective".

In the following example I can build it but it open a box to choose the path and the format (xmf or exe) :
1. ; max openfile thefile patch.maxpat

2. ; max buildcollective thefile

If I want to directly create the application I have to mention the path and the format in the message to Max :
; max buildcollective thefile mypath/thefile.exe

It creates the exe file correctly with the usual traces on Max Console : "Starting Build for thefile.exe...", "Copying..." .... and "Finished script."
The problem is that the resource folder and the mxf are not next to the exe file, they are somewhere but I didn't found them.

So does anyone tried this before? It seems to be an old issue: https://cycling74.com/forums/max5-buildcollective

Max version: "8.1.11 (17de540) (64-bit windows)"
    

AlexandreAudio's icon

+1 Any idea?

Nodanoma's icon

Yes,
There seems to be no way to avoid pop-up dialogs, which is quite inexplicable to me since it would not seem difficult to have max understand the commands correctly which it is able to execute when the user chooses directory and name manually.…

When attempting to export apps using the offered scripting with an explicit path I get an outputfile which is not an application but a json-file with no extension, obviously unusable. No methods have worked.

I don't mind choosing folder and application name manually that much. The problem is often that the output filename has to be in line with any subsequent scripting to copy files etc. and therefore does not tolerate other filenames, let alone paths. A script message to max would be the easiest and while the documentation states that the messages buildplugin and buildcollective are used for batch collective building I must say that it surely is not

I do find it remarkable that this topic never gets addressed or fixed. But I don't know the ins and outs.

I have tried to discuss this bug or unexpected behaviour here before.