• 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: Xcode-users Digest, Vol 7, Issue 16
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode-users Digest, Vol 7, Issue 16


  • Subject: Re: Xcode-users Digest, Vol 7, Issue 16
  • From: Alexander Bokovikov <email@hidden>
  • Date: Sun, 10 Jan 2010 01:44:46 +0500


On 10.01.2010, at 0:55, Greg Guerin wrote:

Are you making all these changes on a project you haven't backed up?

Good question! :) I did backup of all sources, so I can't loose too much.


In fact most of problems were covered in my misunderstanding of how Target Properties panel works. Switching it into "Current Config/ Current Target" reveals all options I should change for different targets. Now I've resolved the problem with precompiled variable, so it is recognized by the code.

There are two problems I still have though:

1. My project (both targets) uses static FPC library, which is built as a dependent target for each of my ObjC project targets. For some reason I get a lot of errors like "Unit xxxx was not (re)built, please delete it from project...", when I'm building "new" target, which I added, as you suggested. I added it by "Duplicate" menu of the initial target. My FPC library is set as a dependency for both "ObjC" targets. Both targets are looking as the same, but only one works.

2. Second problem probably belongs to FPC specifics. I can't make Pascal code to recognize similar precompiled variable, which I add to FPC_XXXX_OPTIONS in the target properties. I don't know how to make FPC to "globalize" this precompiled variable for all FPC units.

I believe these problems are related more to FPC than to XCode.

Finally I've found very strange (for me) XCode behavior. I'd like to add a plugin file into Plugins subdirectory of the bundle. I tried to use Copy Files target build phase + Add Existing Files. No luck. All such files (or links) are always added to Bundle Resources sections and they can't be moved to the Copy Files phase. The only way I've found is the next:

- add the file (plugin package) to the XCode project, as a link
- it is automatically added to "Copy Bundle Resources" section
- drag it from there and drop into the Copy Files phase

The same solution works if I need to add something into MacOS subdirectory. Is this an XCode feature or bug?

Thanks
-Alex

_______________________________________________
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: How to set executable/product name by compiler switch?
      • From: Jonas Maebe <email@hidden>
  • Prev by Date: Building and using the BWToolkit project from within another project
  • Next by Date: Re: How to set executable/product name by compiler switch?
  • Previous by thread: Re: Building and using the BWToolkit project from within another project
  • Next by thread: Re: How to set executable/product name by compiler switch?
  • Index(es):
    • Date
    • Thread