search for: libclang

...wing command, $ cmake -G "Ninja" ../llvm -DCMAKE_INSTALL_PREFIX=prefix=$INSTALL_PATH -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On $ ninja-build -j 2 I have skipped libcxx and libcxxabi package. It shows below error, 00:04:23 [3261/3430] Building CXX object tools/clang/tools/libclang/CMakeFiles/libclang.dir/CIndexCXX.cpp.o 00:04:30 [3262/3430] Building CXX object tools/clang/tools/libclang/CMakeFiles/libclang.dir/CIndex.cpp.o 00:04:30 FAILED: tools/clang/tools/libclang/CMakeFiles/libclang.dir/CIndex.cpp.o 00:04:30 /usr/bin/c++ -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_OBJC_REWRITER...

[Sorry about the crosspost. Since this is a clang build question but the build is invoked from the top-level LLVM directory I'm not sure where the question should go.] I've got a clang build against libstdc++ on Linux but I would really like one built against libc++/libc++abi. In other words I'd like to rebuild clang/llvm with clang using libc++ and libc++abi on Linux. I looked at

Hey everyone, first of all I just wanted to say thanks :) I've been using libclang for building my own C/C++ IDE and its great. I have, however discovered a bug (which I already submitted on llvm bugzilla but I got the impression that no one reads that :)). If I try to use clang_parseTranslationUnit on this code below: int main() { return reinterpret_cast libclang crashes. Thi...

...=32 > -DLLVM_BUILD_DOCS=ON -DCLANG_INCLUDE_DOCS=ON -DLIBCXX_CXX_ABI=libcxxabi > -DLIBCXX_CXX_ABI_INCLUDE_PATHS="/path/to/llvm/projects/libcxxabi/include" > /path/to/llvm > > This gets me a bit further but I am stuck here: > > Linking CXX shared library ../../../../lib/libclang.so > cd /ptmp/dag/build/clang/tools/clang/tools/libclang && > /opt/cmake/3.0.1/bin/cmake -E cmake_link_script > CMakeFiles/libclang.dir/link.txt --verbose=1 > /cray/css/compiler/cost/tools/x86_64-unknown-linux-gnu/clang/dev/bin/clang++ > -fPIC -stdlib=libc++ -fPIC -fvisibilit...

Hi everyone, i want to use libclang to create my own AST and use a node system like houdini is using to write own programms with a graphical interface. But libclang does not give full access to the AST - i need to build my own AST and need full access. Since there are no books about libclang i hope someone here can point me in the...

Hello all, Is there a reason why the library location code in cindex py does not use find_library() to locate libclang, like in the attached patch? Without it there were problems locating a versioned libclang.so.1 file on Debian, for example. Cheers, Mihai -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120624/3f1774fe/att...

On 06/25/2012 12:50 AM, Mihai Basa wrote: > Hello all, > > Is there a reason why the library location code in cindex py does not > use find_library() to locate libclang, like in the attached patch? > > Without it there were problems locating a versioned libclang.so.1 file > on Debian, for example. Hi Mihai, as this is a clang related question, I move your mail to the clang mailing list. To your patch: > --- cindex_o.py 2012-06-24 23:31:20.000000000...

...Unpacking rstudio (1.4.1717) ... dpkg: dependency problems prevent configuration of rstudio: rstudio depends on libssl1.0.0 | libssl1.0.2 | libssl1.1; however: Package libssl1.0.0 is not installed. Package libssl1.0.2 is not installed. Package libssl1.1 is not installed. rstudio depends on libclang-dev; however: Package libclang-dev is not installed. dpkg: error processing package rstudio (--install): dependency problems - leaving unconfigured Processing triggers for desktop-file-utils (0.26+mint3+victoria) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for...

...-enable-pic=yes --enable-keep-symbols=yes --enable-debug-runtime=yes --enable-optimized=no --enable-targets=x86 --enable-embed-stdcxx=yes --enable-jit=no CXXFLAGS=-fPIC CFLAGS=-fPIC Now i get this strange error,cannot link, pls help...how to proceed. llvm[4]: Linking Debug+Asserts Shared Library libclang.so /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: /home1/ragha/llvmsrc/llvm-3.2.src/build/tools/clang/tools/libclang/Debug+Asserts/ARCMigrate.o: relocation R_X86_64_PC32 against `std::basic_string<char, std::char_traits<char>, std::allocator<char> >::...

> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Raghavendra K > Subject: [LLVMdev] Linking Debug+Asserts Shared Library libclang.so: final link failed: Bad value > llvm[4]: Linking Debug+Asserts Shared Library libclang.so > /usr/lib64/gcc/x86_64-suse-linux/4.1.2 You might want to consider trying a version of gcc that's less than six years old. Note that there are several entries for problems with that version of...

...or your detailed reply, will look into the resources indicated. I'd like to avoid C++ if possible, let me see how it goes. Regards, Rajesh Jayaprakash On Tue 12 Mar, 2019, 6:35 PM Sachkov, Alexey, <alexey.sachkov at intel.com> wrote: > Hi Rajesh, > > If I understand correctly, libclang is a C interface to Clang features, > not LLVM. That means that you cannot get LLVM IR via libclang: The C > Interface to Clang provides a relatively small API that exposes facilities > for parsing source code into an abstract syntax tree (AST), loading > already-parsed ASTs, traversing...

...o C, storing the C code in a char buffer, and passing it to TCC programmatically via the API provided. I get a function pointer in return, which I store and invoke as needed. Delving into the LLVM documentation, I found that one possible way to achieve the same functionality in LLVM is to use clag/libclang to convert the C source to LLVM IR, load this IR into the the JIT context and (skipping some steps I'm yet to figure out) get the desired function pointer. Is this approach the right one? One issue I foresee is that libclang's clang_parseTranslateUnit() function expects the C code to be fr...

...; > I haven't seen those errors. Clang and LLVM both build with no warnings on the 3 versions of GCC I test with. MSVC reports loads of warnings however. > $ make happiness ... Updated to revision 142790. ... make[4]: Entering directory `/home/ecsardu/LLVM/build-tcclab1/tools/clang/tools/libclang' llvm[4]: Compiling CIndex.cpp for Release+Asserts build (PIC) llvm[4]: Compiling CIndexCXX.cpp for Release+Asserts build (PIC) llvm[4]: Compiling CIndexCodeCompletion.cpp for Release+Asserts build (PIC) llvm[4]: Compiling CIndexDiagnostic.cpp for Release+Asserts build (PIC) llvm[4]: Compiling...

Hello everyone, Source, binaries and docs for LLVM-5.0.0-rc2 are now available at http://prereleases.llvm.org/5.0.0/#rc2 (I'll add more binaries as they become available.) Please try it out, run tests, builds your favourite projects and file bugs about anything that needs to be fixed (including docs!), marking them blockers of http://llvm.org/pr33849. Cheers, Hans

The bug number is 13619. Oh, apparently it crashes if you substitute "reinterpret_cast" with "static_cast" or "dynamic_cast" as well. > > Hey everyone, > > > > first of all I just wanted to say thanks :) I've been using libclang for > building my own C/C++ IDE and its great. I have, however discovered a bug > (which I already submitted on llvm bugzilla but I got the impression that > no one reads that :)). If I try to use clang_parseTranslationUnit on this > code below: > > > > int main() { return r...

...selves. > > Some of the packagers should comment on this topic :) > > Breaking ABI in patch releases with no other changes? As a Debian packager (but not LLVM packager), I am opposed to changing ABI without bumping soversion and changing library name. If we have this: LLVM 3.4.0 => libclang-3.4.so.1 LLVM 3.4.1 => libclang-3.4.so.1 (same) but they are ABI-incompatible, that's going to cause trouble. But if we have this: LLVM 3.4.0 => libclang-3.4.so.1 LLVM 3.4.1 => libclang-3.4.so.2 (soname bumped) that's perfectly fine (I guess everybody here knew that already......

On Sat, Oct 22, 2011 at 12:24 AM, James Molloy wrote: > Hi Paul, > > That should be easy enough, because the LLVM build has no warnings in it! > > Some of us build with -Werror, and even with those of us that don't warnings are not tolerated. You're already seeing all the warnings that are coming out of the build :) So, all the "variable might be used

Nope, I parse the first time, and then reparse everytime something changes in my text buffer (because I syntax color based on what libclang gives me). And it worked fine (and fast) with clang_defaultEditingTranslationUnitOptions for clang_parseTranslationUnit and clang_defaultReparseOptions for clang_reparseTranslationUnit. Until I saw that clang_codeCompleteAt doesnt work with anything else than CXTranslationUnit_None. On Mon, Aug 2...

...KE_INSTALL_PREFIX=/tools/llvm/svn_head -DLLVM_TARGETS_TO_BUILD="X86;CppBackend" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=ON ../llvm Everything worked well, and in the end I got the following shared libraries: /tools/llvm/svn_head/lib/BugpointPasses.so /tools/llvm/svn_head/lib/libclang.so /tools/llvm/svn_head/lib/libclang.so.3.9 /tools/llvm/svn_head/lib/liblldb.so /tools/llvm/svn_head/lib/liblldb.so.3.9.0 /tools/llvm/svn_head/lib/libLTO.so /tools/llvm/svn_head/lib/LLVMHello.so However, with an autoconf build, I am used to seeing a libLLVM.so. From a 3.7.1 autoconf build: /tools...

Hi, I'm a happy user of libclang.so I got in trouble trying to get info from templated function such as /* File: t.cc */ template <class T1,class T2> void my_foo(T1 a,T2 b) { } I only got CXCursor_FunctionDecl cursor instead of CXCursor_FunctionTemplate and I don't getting CXCursor_TemplateTypeParameter. And argum...