After moving from manually created XCode project to CMake-generated XCode C project my compiled binary dylib size has grown significantly: from about 35 Mb to about 53 Mb.

All the compilation and linking settings I could compare in XCode projects look pretty much the same (including vs. not including debug symbols, optimization levels, etc.). I wonder if there are any tools to inspect dylib contents - what occupies size in first place.

Thank you.

CodePudding user response：

I would personally go with nm tool. You can inspect any dlyb file iteratively, section-by-section or just print everything:

nm -a /path/to/my/lib.dylib