Thanks for quick reply. I am checking this out. But my question is not about distribution of some custom libraries my app requires and depends on. No, it is about even a basic crystal app with no custom/exotic requirements but rather with the just dependencies on standard crystal libs and maybe a few other “mainstream” shards.
Possibly I am not following completely the article you linked but brew bottles or not one would still need crystal installed to run the pre-compiled crystal app (on macos - with no static linking) Or are you saying it would be necessary and possible to include all standard crystal libs in the brew bottle and somehow ensure they are visible and linked during runtime when app is run?