[cfe-dev] Built Mavericks libclang.dylib Won't Link Out clang::FileManager

[Ted Kremenek]

On Nov 4, 2013, at 2:27 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote:

> On Sun, Nov 3, 2013 at 3:14 PM, support at goldencivet
> <support at goldencivet.com> wrote:
>> So it would seem we must be horking that dylib somehow.
> 
> This is the correct way of liking in order to use the C++ interface.
> Link to libclang.dylib only if you use the C interface.
> 
> Dmitri
> 
> -- 
> main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
> (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

Right.  libclang exports a truly stable (C) API.  None of the C++ entry points in Clang or LLVM are considered LLVM, and they are not exposed in the libclang dynamic library.