XCode 2.1 dependency and indexer issues
XCode 2.1 dependency and indexer issues
- Subject: XCode 2.1 dependency and indexer issues
- From: Andreas Grosam <email@hidden>
- Date: Thu, 16 Jun 2005 12:18:41 +0200
With XCode 2.1 many problems with dependency and indexes disappeared
and I also much appreciate the other improvements - great job!
However, I experienced a few issues:
1 Indexer:
- std headers e.g. iostream
In brief: the indexer is unable to locate header files when building
against a SDK.
It works like a charm when XCode builds against the "Current Mac OS".
1.1 When building against an SDK, the following issue arises:
Suppose a source:
#include <iostream>
int main() { return 0; }
XCode's Indexer is always able to handle the different locations of the
iostream file and it is also able to populate the "headers popup" in
the top-right corner of the editor, even when choosing different SDKs.
However when opening the header file (iostream), it will NOT highlight
the syntax - and the "headers popup" for this header will not be
populated with the header files included from this file.
This can't be forced somehow, even when choosing the "Rebuild Code
Sense Index" button in the General tab of the Info window for the
project.
Any idea how to workaround this issue?
1.2 The indexer still does not preserve namespaces and qualified names.
(don't think there is a workaround available, though)
1.3 The Indexer gets confused when we have such class definitions:
#define EXPORT __attribute__((visibility("default")))
class EXPORT Foo {};
2 Dependencies
I still experiencing the same bug as in 1.5 :
when removing or reordering source files from the "Compile Sources"
build phase container from a Target, the linker does not re-link.
(filed bug report for 1.5 already)
Surprisingly, when re-ordering libraries in the "Link Binary With
Libraries" container, XCode *does* re-link.
I would much appreciate a "Force Link" button for such kinds of issues.
Is there something like this?
And a question:
Does the dependency mechanism remembering the system paths and
environment variables (which might affect the build process) when
building a product?
This is important too, for instance, I might put "custom" headers into
usr/local/include after finishing the build.
Then, re-building should recognize the change in the system paths and
the environment variables and take actions accordingly.
Regards
Andreas Grosam
_______________________________________________
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