similar to: [LLVMdev] [PATCH] cindex.py using find_library

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

Hi, I'm trying to debug a function I wrote to calculate the cindex for a hierarchical tree. For this it is useful to compare my calculations with those in output from the clustindex function, in the cclust library. There's no way, however, to have the cindex value for a given output of the cclust function, as a NA value is always returned. This happens almost surely because the cindex in

Hi, I am parsing a C++ file using cindex.py and want to get the template parameters to a specific node. However, the tree seems to be different depending on if the template parameter is a struct/class or a simple type such as int or float. In the first case the template type is appended as a child to the VAR_DECL node (the TYPE_REF node seen in the example below), but this is not the case with

Hi, I'm try to build llvm on my PC but it failed. I'm using following 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\CIndex && D:\Tools\Building\cmake\bin\cmake.exe -E cmake_link_script CMakeFiles\CIndex.dir\link.txt --verbose=1 D:\Tools\Building\gcc\bin\g++.exe -shared -o ..\..\..\..\bin\libCIndex.dll -Wl,--out-implib,..\..\..\..\lib\libCIndex.dll.a -Wl,--major-image-version,0,--minor-image-version,0 CMakeFiles\CIndex.dir\CIndex.cpp.obj ..\..\..\..\lib\libLLVMMC.a

Hello, I'm trying to use the python libclang bindings to write a C++ style-checker, and I'd like to detect all the typedefs to recommend switching to using. I'm using libclang 3.8, with the python bindings provided with it. When I parse a file with index = clang.cindex.Index.create() tu = index.parse(f, ['-x', 'c++', '-std=c++11', '-fsyntax-only',

On 6 March 2010 10:47, Eric Christopher <echristo at apple.com> wrote: > > On Mar 6, 2010, at 2:44 AM, Aaron Gray wrote: > > > > > clang fails with a dynamic linking problem. > > What's the problem? and if you would please file a bug that would be > awesome :) > > thanks! > > Eric, Neither Cygwin nor MinGW support Dynamic Linking. I am getting

On 5 March 2010 22:09, Aaron Gray <aaronngray.lists at googlemail.com> wrote: > Thanks Chris. Built LLVM okay from SVN and am running 'make check' and > building LLVM-GCC, also will check whether clang builds on Cygwin too. > LLVM-GGC builds and installs okay using gcc-4.2.4 minimum. 'make check' runs okay too. clang fails with a dynamic linking problem. Aaron

On Mar 6, 2010, at 2:44 AM, Aaron Gray wrote: > > clang fails with a dynamic linking problem. What's the problem? and if you would please file a bug that would be awesome :) thanks! -eric

On Mar 6, 2010, at 3:49 AM, Aaron Gray wrote: > > I am hoping I can just not build the indexer and will see if I can get a patch together first for 2.7 before submitting a bug report if I have to. > > Okay here's a patch to no build the CIndexer on Cygwin and MinGW :- > > Index: tools/Makefile > =================================================================== >

Hello, Am Donnerstag, 15. März 2012, 21:15:02 schrieb Gregory Szorc: > There was some talk on IRC last week about desire for Python bindings to > LLVM's Object.h C interface. So, I coded up some and you can now find > some Python bindings in trunk at bindings/python. Currently, the > interfaces for Object.h and Disassembler.h are implemented. FYI: I recently startet working on

Hi LLVMDev, There’s been a good bit of progress this month, and with the dev meeting later this week I thought I’d send out a second update. There are only two outstanding blocking issues that don’t have patches proposed, PR 21568 & PR 23947. I would greatly appreciate if someone who works on Mips would take a look at PR 23947. The following issues have been marked as fixed since the last

After upgrading to 8.1.1911, bcc-tools and bpftrace seem to be broken. Current package versions I have: bpftrace-0.9-3.el8.x86_64 and bcc-tools-0.8.0-4.el8.x86_64 Both of these seem to be pulling in LLVM version 7, rather than the version 8 that is in 8.1.1911: [root at localhost ~]# bpftrace bpftrace: error while loading shared libraries: libclangFrontend.so.7: cannot open shared object file:

On 6 March 2010 19:12, Chris Lattner <clattner at apple.com> wrote: > On Mar 6, 2010, at 3:49 AM, Aaron Gray wrote: > > >> I am hoping I can just not build the indexer and will see if I can get a >> patch together first for 2.7 before submitting a bug report if I have to. >> > > Okay here's a patch to no build the CIndexer on Cygwin and MinGW :- >

[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

On 6 March 2010 11:16, Aaron Gray <aaronngray.lists at googlemail.com> wrote: > On 6 March 2010 10:47, Eric Christopher <echristo at apple.com> wrote: > >> >> On Mar 6, 2010, at 2:44 AM, Aaron Gray wrote: >> >> > >> > clang fails with a dynamic linking problem. >> >> What's the problem? and if you would please file a bug that

There was some talk on IRC last week about desire for Python bindings to LLVM's Object.h C interface. So, I coded up some and you can now find some Python bindings in trunk at bindings/python. Currently, the interfaces for Object.h and Disassembler.h are implemented. I'd like to stress that things are still rough around the edges, so use at your own risk. I intend to smooth things over in

On Sun, Oct 23, 2011 at 10:34 PM, James Molloy wrote: > Hi, > > 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

> > - Using CMake for the release binaries. I think I promised we'd do > > this for 3.7. I haven't actually started looking at this yet, but I'm > > still optimistic. > > I'm absolutely in agreement with this. Most of us already use CMake > for development, a lot of the buildbots are based on it and I think we > all agree that autoconf is deprecated.

I have what I hope is a simple question regarding a security practice I''ve been using in my first Rails app. I want to know if it''s worthwhile or if the extra typing isn''t worth it. I have 3 models that are related to each other. class User < AR:Base has_one :library end class Library < AR:Base belongs_to :user has_many :items end class Item < AR:Base