Apple Delivers Build 10A314 of Snow Leopard [Seed Notes]
Apple has seeded developers with the latest build of the next major Mac OS X upgrade, Snow Leopard.
In the latest build Apple is pushing developers to begin developing using the new 64-bit kernel included with the build. Although rumoured the “Marble” interface is not present in 10A314.
Seed notes can be seen below.
- It may take 5-10 minutes to get to the Mac OS X Installer when using a DVD.
- Setup Assistant sometimes crashes when migrating users. Please reboot and try again if you encounter this.
- iCal, Mail or Safari may hang sometimes due to a backround process (configd) crashing. Please reboot if you encounter this.
- If multiple users are editing the same documenut simultaneously over an AFP connection it may result in data loss. Only 3rd party applications that support this behavior, such as database applications, will hit this. Editing files with Finder, for example, is OK.
- Finder may crash on 32-bit machines when viewing movie previews through QuickLook, Finder’s column view or the Get Info window.
- Changing SSL setting for a Microsoft Exchange 2007 account refetches all of your messages.
- Mac Mini’s with a Core Solo CPU will run very slowly.
- ‘Repair Permissions’ in Disk Utility reports spurious errors.
- Portable Home Directory accounts cannot be created.
- Switching between Finder windows with Cmd-` does not work in this seed.
- The initial Welcome Page in Safari is blank.
- The contextual menu for the Finder icon in the Dock is missing some options.
- VoiceOver cannot be started in Setup Assistant using Cmd-F5. Workaround:
1) When you hear “Mac OS X has a built in Screen reader..” press escape.
2) Press the right arrow 13 times to get to the screen that reads “Congratulations, You have learned how to use..”.
Wait for this screen to finish reading and VoiceOver will launch.
3) You can then press the right arrow or escape key to return to Setup Assistant with VoiceOver running.
We strongly encourage you to start developing and testing 64-bit versions of your KEXTs. To help you along we’ve included the 64-bit transition guide with the seed.
- Launch Xcode in Snow Leopard
- Go to Help menu
- Select Documentation Viewer
- Search for “64-bit Transition Guide”
We’ve also enabled the 64-bit kernel, for development purposes only, in this seed on the following configurations:
Using 10A314 and one of the K64-capable machines listed above, simply boot the Mac with the ’6′ and ’4′ keys held down to use the 64-bit kernel. Observe that uname -v reports RELEASE_X86_64. Machines listed as “Default” will run K64 automatically when loaded with 10A314.
You can also set arch=x86_64 in your boot-args NVRAM variable, using nvram(8). When you’re done, you can remove the boot-arg, or if you can no longer boot into an OS to unset it, hold command-option-P-R to zap NVRAM.
If you just want one partition to boot x86_64, edit the file /Library/Preferences/SystemConfiguration/com.apple.Boot.plist and add arch=x86_64 to the kernel flags.
If some functionality is not working and you must revert to using the 32-bit kernel, you can either reboot with the ’3′ and ’2′ keys held down or set arch=i386 in your boot-args.
Xcode Changes Since the Last Seed
- A new startup screen allows you to open recent projects directly from the startup window.
- The list of project templates for New Project has been trimmed and all templates have been updated for Snow Leopard.
- The Build Results window has been updated with new options for grouping information.
- Code completion now adds opening or closing square brackets where needed.
- The tab key can now be used to advance to the next CodeSense placeholder token; ‘Enter’ or ‘Return’ reduces the placeholder to editable text.
- “Add Frameworks” now brings up a sheet of relevant frameworks in the current SDK.
- Significant performance improvements when building, searching, or indexing due to adoption of Grand Central technology.
Known Xcode Issues
- xcodebuild issues build commands as if building all files in the project, rather than just the ones that need to be built. It is not actually recompiling the files, simply retrieving the persisted build results.
- Similarly, the build status line may show a larger number of files to be rebuilt than actually need to be.