two-level namespace mach-o linker
Asked on 2025-11-26
1 search
The concept of a "two-level namespace" in the context of Mach-O linker is not directly covered in the provided WWDC session segments. However, if you are interested in understanding more about how modules and linking work in Apple's development environment, you might find the session titled "Demystify explicitly built modules" helpful. This session discusses how modules are built and used in Xcode, which could provide some insights into related topics like linking and namespaces.
For more detailed information, you might want to explore resources or documentation specifically focused on Mach-O and linker behavior in Apple's development ecosystem.
Port advanced games to Apple platforms
Discover how simple it can be to reach players on Apple platforms worldwide. We’ll show you how to evaluate your Windows executable on Apple silicon, start your game port with code samples, convert your shader code to Metal, and bring your game to Mac, iPhone, and iPad. Explore enhanced Metal tools that understand HLSL shaders to validate, debug, and profile your ported shaders on Metal.
Demystify explicitly built modules
Explore how builds are changing in Xcode 16 with explicitly built modules. Discover how modules are used to build your code, how explicitly built modules improve transparency in compilation tasks, and how you can optimize your build by sharing modules across targets.
Explore Swift and Java interoperability
Learn how you can mix Swift and Java in a single codebase. We’ll introduce the swift-java interoperability project, which allows you to use Swift in Java programs or vice versa. We’ll show you how to use the tools and libraries offered by swift-java to write safe and performant code that interoperates between these two runtimes.