In article <4beb34a4.0309181751.17857b6posting.google.com> ,
[email]rgasparini29[/email] (Jorge) wrote:
That is not the right way to launch a Carbon application. Though the> I have create a background-only application using CarbonLib with
> CodeWarrior 8. This app tracks application usage and saves the
> information in a log file.
> To launch my application at startup, I need to create a script and
> configure it in /Library/StartupItems ... This script launches the
> Carbon app using the "open" command :
> open /Library/StartupItems/Resources/myCarbonApp
subject line of your posts refers to daemons, Carbon applications aren't
daemons because they connect to the window server. Applications that
connect to the window server should not be startup items. They can be
per-user login items, launched when a user logs in and closed when the
user logs out.
That's because it connects to the window server.> So far, it works fine, after startup I can see my process using
> "Process Viewer". However, the process is terminated at logout and is
> no more launched.
You need to build a Mach-O application and not link against any> So how do I make my process immune from termination at logout? Could
> be CarbonLib usage the source?
framework that pulls in the window server (e.g. Carbon or AppKit). If
you can limit your app to CoreServices or CoreFoundation, it'll work.
Hope this helps,
Eric Albert [email]ejalbertstanford.edu[/email]