All tricks in this blog are only for educational purpose. Learn these tricks only for your knowledge. Please donot try these to harm any one. We will not take any responsibility in any case. All softwares and tools on this site are here for private purposes only and If you want to use a software for business purpose, please purchase it. I do not host many of these tools. I Post links that I have found from numerous Search engines. I will not be responsible for any of harm you will do by using these tools.


Friday, September 24, 2010

Xcode Tools 2.4.1 For Mac OS X version 10.4.x (Tiger)

Compatibility • Xcode Tools 2.4.1 is a full release of the Xcode development tools suite. It requires Mac OS X v10.4.xand is able to upgrade previous installations of Xcode Tools 1.x and 2.x releases.• Xcode 2.4.1 supports development for Mac OS X 10.2 (Jaguar), Mac OS X 10.3 (Panther), or Mac OS X10.4 (Tiger) or Universal binaries for Power PC and Intelarchitectures on Mac OS X 10.4 using Mac OS XSDK support. Development for Mac OS X 10.2 requires downloading and installing the separate 10.2.8SDK package available from the ADC website.• The Xcode project file format and extension changed for Xcode 2.1 and later. See the productdocumentation for more information. Changes in this release • Selected fixes were made in the Xcode IDE, cctools, debugger, and compiler. • CHUD has been updated to version 4.4.3. CHUD also releases independent from the Xcode Toolsreleases. Current versions of CHUD can be found at: http://developer.apple.com/tools/download/ • The 10.3.9 and 10.4u SDK’s have been updated. Known issues: Commonly-reported issues known in this release • Spaces inproject path item: Any build setting that contains a path (or includes another build settingthat resolves to a path) must be enclosed in double quotes if the path is likely to contain a spacecharacter. Xcode will handle the quoted value correctly, but will fail if an unquoted value resolves to apath that includes a space.• For build settings that do not have explicit per-architecture versions, you can define the explicitly-supported build setting in terms of another, per-architecture setting which you define manually. Forexample, to define the Other Linker Flags setting using a mix of architecture-independent andarchitecture-dependent settings, you can configure your build settings with the following definitions:OTHER_LDFLAGS = -flag1 -flag2 $(OTHER_LDFLAGS_$(CURRENT_ARCH))OTHER_LDFLAGS_ppc = -ppc_specific_flagOTHER_LDFLAGS_i386 = -intel_specific_flag• Referencing files and folders when a symlink is in the path: ?X code tracks symlinks (like/usr/lib/libz.a). However, there is a regression with references to files and folders where a symlink exists anywhere but the last path component. Symlinks like /tmp/ (which points to /private/tmp/) are handled properly. The biggest impact is to files and folders on statically mounted networkvolumes(dynamically mounted network volumes are not affected). The only workarounds are to either only use absolute paths for references that are affected or to move such files to locally mounted or dynamically mounted network volumes.• Limitations When importing Code Warrior 10 projects: ?Xcode 2.3 and later don’t recognize the new optional text based project format available in Code Warrior Development Studio for Mac OS v10.• Shared libraries window bugs?: You are unable to change the load level of libraries shown in the Shared libraries window.• Setting breakpoints in #included files that aren’t members of a target: ?If Xcode is choosing the wrong location for your breakpoint, you can either edit the location column in the breakpoint window with the correct executable/dylib/framework/Zero Link file or add the file to the target with a ‘Copy Headers’ build phase.• Setting breakpoints in dylib C++ Templates using DWARF?:

Download Xcode Tools 2.4.1 For Mac OS X version 10.4.x (Tiger).


Post a Comment