Standalone app asks for filenames in collective


    Jan 05 2021 | 3:40 pm
    Hi, I try to make a standalone of a quite complex patch. I add as usual all externals etc. into the "Build collective/Application" window, it build but then I get message in the Max-window that it misses files and there it gets weird, for example a message line is: FileNames: no such file in collective FileNames in my patch is the name of a coll-object [coll FileNames]. Why does the app ask for that. Does anyone know and if so, what do I need to do to make it just accept that this is coll? Or even more weird: I have a sub patcher called p slotchooser and I use the word slot in two comment-boxes and in the Max-window the standalone says: slot: no such file in collective. I built standalone before, but never experienced this.
    Thanks for advice

    • Jan 09 2021 | 7:57 am
      read coll help file where it says about naming the coll, and adding argument to prevent it from trying to load external file. example : coll MyFile change to : coll MyFile 1
    • Jan 10 2021 | 5:09 pm
      Thanks, that was one part of the problem, but it always looks for files that are not in the patch. For example a lot of jit. files. There is an jit.world in the patch but the Max-Window says that there is no jit.world in the collective. I should say, that I made the standalone from a project.
      It obviously does not really matter, only it is a bot ugly to get all these warnings at start...
    • Jan 11 2021 | 12:01 pm
      you can wipe console using ; max clearmaxwindow message - loadbang with delay or try to build clean standalone ... some suggestions : https://cycling74.com/forums/standalone-with-node-script-never-launches