Open Radar

 
Summary:
Being able to incorporate the compiler as an object in applications leads to some interesting metaobject programming possibilities (see notes). While we can build the clang and llvm libraries from the upstream sources, it'd be useful to have the versions of the libraries that correspond to the compiler that's really in use to reduce incompatibility problems.

Steps to Reproduce:
1. try to write code that uses features from the clang-c/ headers and links to libclang

Expected Results:
I can use the libclang interfaces and libraries corresponding to my current version of Xcode (as determined by xcode-select).

Actual Results:
There is no first-party provision for these headers and libraries - I can build versions from llvm.org's svn but cannot readily tell which version of their sources corresponds to the version in an Xcode build. The specific source drops at www.opensource.apple.com do not always arrive in a timely fashion.

Version:
Not applicable.

Notes:
The specific use cases I have in mind for the libraries include syntax-aware automation tools like lints and documentation generators that should be aware of the same syntax as the compiler used in Xcode/xcodebuild. Additionally there are metaobject programming uses; a Smalltalk-style object browser in Cocoa could let you write Objective-C and reprogram the browser (unlike existing solutions like F-Script that interpret another language).

Configuration:
Not applicable.

Attachments: