• 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
Spurious linker errors in dependent projects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Spurious linker errors in dependent projects


  • Subject: Spurious linker errors in dependent projects
  • From: Greg Hurrell <email@hidden>
  • Date: Tue, 5 Jul 2005 00:18:24 +0200

I have a problem with a project under Xcode 2.1:

"Project A" has a dependency on "Project B", and "Project B" has a dependency on "Project C".

"Project C" builds fine on it's own.

"Project B" builds fine on it's own, after successfully and automatically building the dependency ("Project C").

"Project A" fails to build because "Project B" fails to build, and "Project B" fails to build because "Project C" fails to build with a spurious linker warning. Specifically, libtool spits out a bunch of lines like this:

/usr/bin/libtool: can't open file: /Users/ghurrell/work/build- intermediates/WDB.build/Debug/WDBBase.build/Objects-normal/ppc/ MoreOSUtils.o (No such file or directory)

The "missing" files refer to a number of files that used to be in "Project C" a few revisions ago. They are now switched off. "Project C" builds fine without them. It also builds fine when included as a dependency of "Project B". But when included as a dependency of "Project B" and indirectly "Project A" it fails to build.

Any suggestions how I can work around this very frustrating bug? Where is the stale information being cached? I've tried deleting my build and build intermediates directory, cleaning all targets repeatedly, rebuilding the code sense indices of all the projects, and I've even done a text search in the project file for "Project A" to find out if there are any stale references to those files in it (there aren't).

If I look at the "LinkFileList" file produced by Xcode the unwanted entries are being added to the list when building as an indirect dependency of "Project A". When build independently ("Project C") or as a dependency of "Project B" the exact same file does not contain the unwanted entries. If I delete the entries by hand Xcode unhelpfully adds them straight back in for me on trying to build "Project A".

Best wishes,
Greg
_______________________________________________
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: Spurious linker errors in dependent projects
      • From: Greg Hurrell <email@hidden>
  • Prev by Date: Re: Old: Command-K not compiling
  • Next by Date: Re: [OT] Listing cvs tag names
  • Previous by thread: dragging files and folders to the project
  • Next by thread: Re: Spurious linker errors in dependent projects
  • Index(es):
    • Date
    • Thread