• 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: In iOS/MacOS XCode project, MacOS static library product appears "red" in Navigator, and shows no path in Assistant.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: In iOS/MacOS XCode project, MacOS static library product appears "red" in Navigator, and shows no path in Assistant.


  • Subject: Re: In iOS/MacOS XCode project, MacOS static library product appears "red" in Navigator, and shows no path in Assistant.
  • From: Michael Hanna <email@hidden>
  • Date: Mon, 18 Jul 2011 15:40:29 -0400

Glad to know I'm not alone.

I fixed the build issue, forgot to add the libraries to the target(oops). But yes, I still get the "red" products.

Michael

On Mon, Jul 18, 2011 at 3:18 PM, Jens Alfke <email@hidden> wrote:

On Jul 18, 2011, at 6:22 AM, Michael Hanna wrote:

> In Xcode 4, I have a subproject building a static lib for both iOS and MacOS. It's originally an iOS project. Both the iOS static lib.a and the MacOS build libMac.a build product appear in the DerivedData/proj-xxxxx/Build/Products as expected. BUT in the Navigator, the libMac.a file appears "red" as if the project is missing the lib product somehow.

I see this quite a lot in this same situation[1], where one project in a workspace links against a library built by another project.

> Also, when I click on the iOS lib.a file in the Navigator, I see the path in the Assistant but when I click on the "red" libMac.a file in the Navigator, there is no path listed(even though the file exists). Seems XCode 4 has lost the mac build.

I’ve been able to fix this by using the Identity/Type area in the Utilities panel. Clicking the tiny icon below the Location pop-up (looks like a little window or something?) brings up a file-open panel from which I can select the file. First change the Location pop-up to “Relative to build products”, though.

I have to say that this has been one of the most frustrating parts of working with Xcode 4 so far. It seems as though inter-project library dependencies have a lot of weird bugs, even in the latest available Xcode builds.

—Jens

[1] https://github.com/couchbaselabs/iOS-Couchbase is the project I’m working on

 _______________________________________________
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: 
 >In iOS/MacOS XCode project, MacOS static library product appears "red" in Navigator, and shows no path in Assistant. (From: Michael Hanna <email@hidden>)
 >Re: In iOS/MacOS XCode project, MacOS static library product appears "red" in Navigator, and shows no path in Assistant. (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: In iOS/MacOS XCode project, MacOS static library product appears "red" in Navigator, and shows no path in Assistant.
  • Next by Date: XCode 4.0.2 Doesn't Name Build Products Folder to <Configuration>
  • Previous by thread: Re: In iOS/MacOS XCode project, MacOS static library product appears "red" in Navigator, and shows no path in Assistant.
  • Next by thread: XCode 4.0.2 Doesn't Name Build Products Folder to <Configuration>
  • Index(es):
    • Date
    • Thread