search

Cycling74 / min-devkit

Tools, documentation, and reference implementation of a Max Package built using the Min-API.
MIT License
158 stars 31 forks source link

Statically linked build? #149

Closed mrobbetts closed 4 years ago

mrobbetts commented 4 years ago

Is it possible to get a statically-linked build out of this system? (I am trying to build my external using Nix on MacOS – which works – but have the result be redistributable to non-Nix MacOS.)

Currently I see:

$ otool -L /path/to/externals/myExternal~.mxo/Contents/MacOS/myExternal~ 
/path/to/externals/myExternal~.mxo/Contents/MacOS/myExternal~ :
    @executable_path/../Frameworks/JitterAPI.framework/Versions/A/JitterAPI (compatibility version 1.0.0, current version 1.0.0)
    /nix/store/1w5vfi5jvgkw44ahy8w3vdn6icmqfmxm-libc++-7.1.0/lib/libc++.1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
    /nix/store/7c9ilw9zna1m3dlkd4bp80czya62px0s-Libsystem-osx-10.12.6/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)

The libc++ and libSystem entries are clearly linker-non-grata.

I am quite new to cmake, so perhaps this is obvious, but I've tried a few things I can think of, to no success...

mrobbetts commented 4 years ago

Actually, I think this question was pretty stupid. Closing :)