Danny de Graan

Hi, I just created a standalone of a patch I made a while ago (macOS 10.14.6 & Max 8.2.1) and it added a maxclang.mxo in the extentions folder of the standalone.

The maxclang.mxo is 129.1mb big and I have no idea what it is and cannot find anything on the forum about it. My guess it has something to do with being compatible with Apple M1 chips machines and Monterey but i'm not sure.

If its not, I like to remove it since it makes the app more than double the size but I don't know if I can do this without any problems.

Hi, I just created a standalone of a patch I made a while ago (macOS 10.14.6 & Max 8.2.1) and it added a maxclang.mxo in the extentions folder of the standalone. 

If its not, I like to remove it since it makes the app more than double the size but I don't know if I can do this without any problems. 

Hi, I just created a standalone of a patch I made a while ago (macOS 10.14.6 & Max 8.2.1) and it added a maxclang.mxo in the extentions fold

standalone-adds-maxclang-mxo-which-is-129-1mb-big

same case here. While i was able to build a standalone with reasonable size, with max 8.21/8.22 the maxclang.mxo it self is 129 mo, and all externals have pretty much doubled in size.

Could we get some insight from cycling74? as assumed in the previous post, is it related to M1 support ?

(on mac OS.)
same case here. While i was able to build a standalone with reasonable size, with max 8.21/8.22 the maxclang.mxo it self is 129 mo, and all externals have pretty much doubled in size.

Could we get some insight from cycling74? as assumed in the previous post, is it related to M1 support ? 

The overall size increase of standalone's is somewhat due to the new feature of standalone's having a 'universal' architecture: containing both x86_64 and arm64 code.

You can thin the standalone.app to its native architecture with this bash function:

# shrink standalone.appshrink() {
    ditto --arch `uname -m` "${1}" "${1}-tmp"
    rm -rf "$1"
    mv "$1-tmp" "$1"
}

It is also worth noting that maxclang.mxo seems to be only required for gen code to work. If you don't use gen then you should be able to remove it without issues. This is also the case for MaxPlugInScanner, etc..

Frankly I don't understand why one needs a whole compiler for gen to run. Intuitively, one would think that static gen code should be compilable to specialized machine code and then stored in a standalone.

 The overall size increase of standalone's is somewhat due to the new feature of standalone's having a 'universal' architecture: containing both x86_64 and arm64 code.

Frankly I don't understand why one needs a whole compiler for gen to run. Intuitively, one would think that static gen code should be compilable to specialized  machine code and then stored in a standalone.

maxclang seems required for jit.gen to work, so as i m using jitter, i m stuck here.

Standalone adds maxclang.mxo which is 129.1mb big