[cfe-commits] r74027 - in /cfe/trunk: clang.xcodeproj/ clang.xcodeproj/project.pbxproj include/clang/AST/DeclCXX.h include/clang/Basic/DiagnosticSemaKinds.td lib/Sema/Sema.h lib/Sema/SemaExpr.cpp lib/Sema/SemaStmt.cpp test/CXX/class/class.local/p1.cpp test/CXX/class/class.local/p3.cpp

[Ted Kremenek]

On Jun 23, 2009, at 6:15 PM, Fariborz Jahanian wrote:

>
> On Jun 23, 2009, at 5:56 PM, Anders Carlsson wrote:
>
>> Hi Ted!
>>
>> My main reason is that I like having an Xcode project that has only
>> clang - this makes it easier to navigate (especially using command-
>> option-d in Xcode) since there are fewer files, fewer declarations,
>> etc. I never build from the project, so it doesn't need to be kept
>> super up-to-date, and I volunteer to do so.
>
> I want to use this for exact same reason. Using CMake based  
> xcode.proj makes navagiation
> inconvenient.

Hi Fariborz (and Anders),

While I see your point, it would be great if we could figure out how  
to make the CMake-generated Xcode project more useful in this  
respect.  I myself have found using the CMake generated Xcode project  
easy to navigate.  If I want to restrict my attention to only the  
clang sources, I just select the clangXXX subgroups of "Sources".   
This way only the clang sources show up in the detail view.

> Also not all dependencies are in place.

If you see these we should fix them.  Thanks to Doug's efforts with  
the cmake files, I myself am able to build a completely working clang  
using the CMake-generated Xcode project.  Using 'ccmake' to generate  
the Xcode project, I am also only building the X86 codegen target, so  
you aren't beholden to building all of LLVM.

The main reason I think we should (eventually) remove the  
clang.xcodeproj is that while it is a temporary convenience, in the  
long term it is (a) confusing to new contributors and (b) I think its  
a suboptimal development experience when using Xcode.  It's basically  
an Xcode project that is only useful for source navigation, but not  
for building.  I think that sends a mixed message to people wanting to  
do all of their development in Xcode.  Further, Doug has enhanced the  
CMake-generated Xcode projects to enable them to actually run the  
Clang tests within Xcode.  I see all of this as a great quality-of- 
life improvement.

I think we can leave the clang.xcodeproj in for now, but I really  
think we should consider what steps needed to be taken to eventually  
remove it.  If the CMake-generated Xcode project isn't up to snuff for  
whatever reason, we should talk about how to make it better.  Ideally,  
I don't want you, Anders, or anyone who is using the clang.xcodeproj  
Xcode project to feel mandated to switch to the CMake-generated Xcode  
project; I want you to feel there is a compelling reason for doing so.

Ted