[OS X TeX] i-Installer & Jaguar (10.2) Trivial Fix

Jon Guyer jguyer at his.com
Mon Oct 7 23:52:25 EDT 2002

At 11:10 PM -0400 10/7/02, Juan Manuel Palacios wrote:

>	Cocoa apps and traditional UNIX apps are all Mach-0
>executable since they are compile against the kernel (Mach), so how
>can a Carbon app be sometimes recognized as Mach-0 and sometimes as

It depends on how they were linked. Carbon applications are 
frequently ports from Classic, which uses Code Fragment Manager 
linking. Barring any particular need, retaining CFM linking is the 
path of least resistance in this case, so that's what you usually 
see. This is particularly true because until relatively recently the 
only way to generate Mach-O Carbon apps was with Project Builder, 
which cannot produce CFM apps. In contrast, most Classic apps were 
built with CodeWarrior, which could not produce CFM until recent 

When a Carbon app has particular want or need of access to the Unix 
subsystem, then Mach-O linking is preferable, despite the added 
difficulties. The Finder falls into this category because it works at 
the file system level and must ensure tight integration between 
Finder views and command line views. The project I'm working on, 
Alpha, also falls into this category, because it is driven by Tcl 
scripts and we wanted to be able to exploit the fact that Apple now 
ships Tcl as part of the system.

There are also performance benefits to Mach-O linking, but it's not 
for the faint of heart.


   Jonathan E. Guyer

Mac TeX info, resources, and news can be found at:
List archives can be found at:
Threaded list archives can be found at:
See message headers for list info.

More information about the MacOSX-TeX mailing list