Re: Debugging Quick Look plugins
Re: Debugging Quick Look plugins
- Subject: Re: Debugging Quick Look plugins
- From: Chris Espinosa <email@hidden>
- Date: Wed, 23 Jan 2008 10:45:11 -0800
On Jan 23, 2008, at 9:46 AM, Steve Mills wrote: I found the docs that explain how to debug a Quick Look plugin <http://developer.apple.com/documentation/UserExperience/Conceptual/Quicklook_Programming_Guide/QLDebugTest/chapter_11_section_2.html>. But one thing I've found is that I have to manually copy the built plugin into /Library/QuickLook/. If I don't do that, then the debugger tries to start up, but then exits without displaying the qumanage window for the preview or thumbnail. My project has the default settings from the project template, including the Installation Directory of /Library/QuickLook. Is there something else I need to do in order for Xcode to copy the built plugin into that dir so it will debug correctly? Or should something else be changed so it can be debugged from the build directory?
This is a general Xcode FAQ. The Installation Directory is only used in two circumstances:
1) when you do an 'xcodebuild install' from the command line 2) if you specifically and intentionally check 'Deployment Postprocessing' in the build configuration you use for Release
The reason the former is preferred over the latter (and neither is default or automatic) is that installation often involves using escalated privileges to set ownership and permissions on the installed product, or to install it in places that require escalated privileges. We don't have a mechanism in the IDE to let Xcode do the whole build as your user but just the installation as a superuser, and if we don't do that, the first build-and-install would work but the second one would fail because your user can't overwrite a file originally written by a superuser.
The solution is to either set Deployment Postprocessing (and make sure permissions are set correctly) so you can repeatedly do Build Release from the Xcode IDE, or to go to the command line to debug, or to put a symlink in /Library/Quicklook to your Build Products folder where your regular debuggable executable is going to land after every rebuild. I prefer the latter solution myself, and use it frequently for all kinds of system plugins.
Chris |
_______________________________________________
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