RE: Copy Files Build Phase for Spotlight copies other files
RE: Copy Files Build Phase for Spotlight copies other files
- Subject: RE: Copy Files Build Phase for Spotlight copies other files
- From: "Syd Polk" <email@hidden>
- Date: Wed, 25 Oct 2006 12:50:52 -0500
> -----Original Message-----
> From: xcode-users-bounces+sydvicious=email@hidden
> [mailto:xcode-users-bounces+sydvicious=email@hidden
> ] On Behalf Of Keith Blount
> Sent: Wednesday, October 25, 2006 12:45 PM
> To: email@hidden
> Cc: email@hidden
> Subject: Re: Copy Files Build Phase for Spotlight copies other files
>
> Thanks for your reply, David.
>
> I tried changing the copy build phase so that it pointed to
> Wrapper > Contents/Library/Spotlight instead, but it made no
> difference - as soon as I added a new class to the project,
> its header file was automatically placed in the Spotlight
> copy files build phase. Weird.
>
> I guess I'll have to use a script similar to yours - thanks
> for the tip. I would prefer it if Xcode didn't automatically
> plonk my headers in a build phase that I haven't asked it to, though.
Have you used the target inspector and marked the headers "Private"?
> Thanks again and all the best,
> Keith
>
>
> ------------------------------
> Date: Tue, 24 Oct 2006 15:17:47 -0700
> From: David Dunham <email@hidden>
> Subject: Re: Copy Files Build Phase for Spotlight copies other files
> too?
> To: xcode list Users <email@hidden>
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
> On 24 Oct 2006, at 13:20, Keith Blount wrote:
>
> > I am using a Copy Files build phase to copy my spotlight MDI into
> > my application bundle, as I found recommended in the Xcode-users
> > list archives. The way I have it set up is as follows:
> >
> > Destination: Resources
> > Path: ../Library/Spotlight
> > Copy only when installing: OFF
>
> Mine is to Wrapper, Contents/Library/Spotlight.
>
> > The problem, however, is that whenever I create or import class
> > files in my project, the .h file always gets placed inside this
> > copy files build phase automatically.
>
> I don't think I've seen this as such, but I have had problem with
> headers ending up in my build. I ended up just adding a script phase
> to get rid of them:
>
> find $TARGET_BUILD_DIR/$FRAMEWORKS_FOLDER_PATH -name Headers
> -exec rm
> -rf {} \; -prune
>
> David Dunham Development Manager
> +1 206 926 5722 GameHouse Studios
>
> ---ORIGINAL MESSAGE---
> Hello,
>
> I am using a Copy Files build phase to copy my spotlight
> MDI into my application bundle, as I found recommended in the
> Xcode-users list archives. The way I have it set up is as follows:
>
> Destination: Resources
> Path: ../Library/Spotlight
> Copy only when installing: OFF
>
> I
> imported my .mdimporter folder recursively creating folders
> and dragged
> it into this copy files build phase inside my application target.
>
> Everything works fine - the spotlight importer gets copied
> into Library/Spotlight and all works well.
>
> The
> problem, however, is that whenever I create or import class
> files in my
> project, the .h file always gets placed inside this copy files build
> phase automatically. This is really annoying, because it means that
> whenever I create a new file in my project, I then have to go the the
> targets folder, open up this build phase and delete the reference to
> the header file that has been created. If I don't do this, of
> course, I
> find that any .h files I have created end up in my .app bundle in the
> Library/Spotlight folder.
>
> I have several copy files build phases
> set up for various things (for the Sparkle framework, to copy some
> shell scripts into the executables folder of the app bundle etc) and
> none of these suffer from this same problem. I have tried deleting the
> Copy Files build phase for the spotlight importer and recreating it,
> but the problem just recurs in the newly created build phase.
>
> To
> me, this seems to suggest that either, a) there is something
> wrong with
> the settings I posted above, or b) creating a copy files with
> "Resources" as the destination automatically grabs any other resources
> that have been added to the project (though I haven't tested this).
>
> If
> anyone could tell me what I'm doing wrong, I would be very grateful.
> This isn't a massive problem seeing as everything works, but it is
> annoying having to go and delete those references every time I create
> or import new files.
>
> Thanks in advance for any help or advice,
> All the best,
> Keith
>
>
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> 40mac.com
>
> This email sent to email@hidden
>
_______________________________________________
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