Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Do Multi-Architecture Binaries take a lot of extra disk space?

0
Posted

Do Multi-Architecture Binaries take a lot of extra disk space?

0

MAB, disk space multi application binary, MAB The concept of NEXTSTEP binaries is different to other platforms. On NEXTSTEP only the real program is compiled and linked in a hardware specific manner. E.g. the GUI and the multilanguage support are usable on any platform running NEXTSTEP and will do so under OPENSTEP. Therefore the real binary part is sometimes really small. Anyway it might be a good choice to thin such a fat binary. NeXT ships tools for this purpose. Look at the manpages for lipo. If an application wasn’t installed using the standard NeXT tool Installer, it might also be a good choice to look into the application drawer and delete other languages supported but not used by the application. This additional data is found in the different *.lproj subdirectories in the application’s folder. To get there, activate the application’s icon and select Open as directory from the Workspace’s File menu item.

0

MAB, disk space multi application binary, MAB The concept of NEXTSTEP binaries is different to other platforms. On NEXTSTEP only the real program is compiled and linked in a hardware specific manner. E.g. the GUI and the multilanguage support are usable on any platform running NEXTSTEP and will do so under OPENSTEP. Therefore the real binary part is sometimes really small. Anyway it might be a good choice to thin such a fat binary. NeXT ships tools for this purpose. Look at the manpages for lipo. If an application wasn’t installed using the standard NeXT tool Installer, it might also be a good choice to look into the application drawer and delete other languages supported but not used by the application. This additional data is found in the different *.lproj subdirectories in the application’s folder. To get there, activate the application’s icon and select Open as directory from the Workspace’s File menu item. 6.3 How difficult is it to recompile existing NeXT applications over to NEX

0

MAB, disk space multi application binary, MAB The concept of NEXTSTEP binaries is different to other platforms. On NEXTSTEP only the real program is compiled and linked in a hardware specific manner. E.g. the GUI and the multilanguage support are usable on any platform running NEXTSTEP and will do so under OPENSTEP. Therefore the real binary part is sometimes really small. Anyway it might be a good choice to thin such a fat binary. NeXT ships tools for this purpose. Look at the manpages for lipo. If an application wasn’t installed using the standard NeXT tool Installer, it might also be a good choice to look into the application drawer and delete other languages supported but not used by the application. This additional data is found in the different *.lproj subdirectories in the application’s folder. To get there, activate the application’s icon and select Open as directory from the Workspace’s File menu item.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123