• 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: Clean all targets
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Clean all targets


  • Subject: Re: Clean all targets
  • From: Jack Repenning <email@hidden>
  • Date: Tue, 6 May 2008 18:21:19 -0700

On May 6, 2008, at 5:42 PM, Michael wrote:

What is the reason one choose to do this? Or, perhaps, what is the downside of NOT "Cleaning all targets"?

Is your question "why does anyone ever need to clean any targets"? Or is it "why might there be more than one to be cleaned"?


More than one: I'll illustrate from my own project, scplugin. It includes a daemon process, a Finder plug-in, and its own private little build of Subversion. Each of those is a separate target:

- the Subversion target rebuilds Subversion, but that takes a long time, and the Subversion build doesn't fit very well into Xcode's model, and therefore the Subversion target isn't very smart about not building when it's not needed, so it's better to leave it out of the automatic build process. This depends on stuff downloaded from the net, and has to be rebuilt whenever Subversion pushes a new release.

- the daemon is a stand-alone program, containing the major portion of our own code, and can take a fairish while to build. This depends on the Subversion stuff, and also on virtually any of our code changes.

- the plugin is pretty small, just some strings for menu labels and a bit of code to lob the request over to the daemon; this avoids polluting Finder's space with all our bugs and bulk. This hardly ever has to be rebuilt, because there's so little code to go wrong.

Why to clean:

- the Subversion build consists of a bunch of web downloads, shell scripts, makefiles, a few ruby scripts, a whole bunch of stuff. It's rather cobbled-together, and really can't be trusted to rebuild over itself. But all its results end up in a single directory, so it's easy to clean, and has to be cleaned whenever we upgrade our version of Subversion.

- the daemon build is quite well-formed and Xcode-conformal, and it rebuilds over itself quite reliably. But one might still want to clean it up (or, clean just the Development or Deployment build areas) to save disk space.

- the plugin is so small, so simple, so stable, I don't imagine it ever really needs to be cleaned ... but it can be



-==-
Jack Repenning
email@hidden
Project Owner
SCPlugin
http://scplugin.tigris.org
"Subversion for the rest of OS X"


_______________________________________________ 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
  • Follow-Ups:
    • Re: Clean all targets
      • From: Michael <email@hidden>
References: 
 >Clean all targets (From: Michael <email@hidden>)
 >Re: Clean all targets (From: Nick Zitzmann <email@hidden>)
 >Re: Clean all targets (From: Michael <email@hidden>)

  • Prev by Date: Re: Clean all targets
  • Next by Date: Re: Clean all targets
  • Previous by thread: Re: Clean all targets
  • Next by thread: Re: Clean all targets
  • Index(es):
    • Date
    • Thread