Re: Spurious linker errors in dependent projects
Re: Spurious linker errors in dependent projects
- Subject: Re: Spurious linker errors in dependent projects
- From: Greg Hurrell <email@hidden>
- Date: Tue, 5 Jul 2005 19:06:43 +0200
For the record, I have worked around the bug by deleting the old
".xcode" project files, even though they were no longer referenced
anywhere (ie. in the move to Xcode 2.1 I had upgraded all my projects
to the new ".xcodeproj" project type; deleted all references to the
old project files including the files themselves, and all referenced
targets and products; added the new project files; added the
appropriate targets, products and dependencies from the new project
files). After deleting the old files everything worked.
El 05/07/2005, a las 0:18, Greg Hurrell escribió:
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
_______________________________________________
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