• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Single project or two separate projects?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Single project or two separate projects?


  • Subject: Re: Single project or two separate projects?
  • From: Trygve Inda <email@hidden>
  • Date: Tue, 28 Feb 2006 04:25:52 +0000
  • Thread-topic: Single project or two separate projects?

> Trygve,
>
> On 27/02/2006, at 12:47 AM, Trygve Inda wrote:
>> I have a Cocoa-based System Pref Pane and it will need to  communicate with a
>> Carbon-based background app (no GUI) to do some work. The Carbon  app is
>> meant to be embedded in the Cocoa's bundle so the user sees only a  single
>> app/file.
>
> I have a Cocoa Sys Pref that communicates with a C daemon.
>
>> Can I put these into a single Xcode project?
>
> Yep. That's the way I do it. The build process can put the faceless
> app in the Pref Pane's bundle for you, as well as building it first
> if it has been touched.
>
>> Is there anyway to debug both at the same time?
>
> Ah, that's a little tricky - some other Pref Pane developer said they
> wrote a very small additional app that just hosted their pref pane,
> then debugged the host and the pref pane together. That's because
> debugging System Preferences is a bit hard without the source.

Is there some sort of sample code to do this? I am not sure how this would
work since there would still be two apps and the debugger can't launch my
PrefPane as a normal app - so how do I debug it? I can see that it would
launch the hosting app, but then debugging my PrefPane - not sure...

> Debugging the faceless app is another problem in itself. I'd suggest
> debugging it separately - one code base for one executable. Any
> reason you need the running at the same time? If they both have to be
> running, I'd suggest building one as deployment and one as
> development and debug one at a time (that's what I do with a
> different, client/server project). Just simplifies things a great deal.

While I can do one at a time, since they communicate with each other, it'd
be nice to be able to see data in one and then see that all goes well in the
communications process.

Thanks for any thoughts and suggestions,

Trygve


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: Single project or two separate projects? (From: Heath Raftery <email@hidden>)

  • Prev by Date: Re: FileMerge Replacements
  • Next by Date: force to use framework in a specific path
  • Previous by thread: Re: Single project or two separate projects?
  • Next by thread: Re: Single project or two separate projects?
  • Index(es):
    • Date
    • Thread