search for: find_librari

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:

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

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

> > - 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.

On Thu, Oct 08, 2020 at 09:38:22AM +0200, Martin Kletzander wrote: > On Wed, Oct 07, 2020 at 04:50:26PM -0700, Román González wrote: > > Hello there, > > > > I'm trying to play with musl and libvirt to see if I'm able to build a > > libvirt client binary without dynamic lib dependencies. I have two > > questions: > > > > 1) to your knowledge,

Hi LLVMDev, The following issues have been fixed since the last update I sent out. Completed: * Bug 19462 - Use the INSTALL(EXPORT ...) to export CMake definitions * Bug 21561 - Update release scripts to use CMake These issues are still outstanding. Classification of blocking vs non-blocking are my own opinions, please let me know if you disagree. All non-blocking issues are still serious bugs

> > If you want to do a minimal build of libvirt you can run meson with > --auto-features=disabled which will disable most of the features and you > can explicitly enable only the things that you want to use (this is what > most distributions are doing when building packages). I just noticed > that there are some build options where this doesn't work so I'll post >

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

Hello all, Ive got Mac OS X Leopard (10.5.8), ruby 1.8.6 (2009-06-08 patchlevel 369) [universal-darwin9.0] and mysql 5.0.67 installed and working fine with Rails 2.1.0. "which ruby" outputs /usr/bin/ruby. I can see the mysql symlink in / usr/local/mysql. I can also see the mysql-5.0.67-osx10.5-x86 folder in /usr/local . Im trying to upgrade my Rails apps to 2.3.5 but when i try to

Hi Chris, Looking forward to continued support for CMake! Along that note, I wanted to add one bug to your list of things to track, which to me seems up your alley but maybe was filed in the wrong bucket (or is actually someone else's problem). Bug 24154 - CMake shared files are broken in llvm-3.7-dev Cheers, Brenden On Wed, Jul 29, 2015 at 1:20 PM Chris Bieneman <beanz at

Hi Brenden, Thanks for the heads up. I don’t expect that to be a blocker for deprecating autoconf because autoconf doesn’t have an equivalent of LLVMExports.cmake. That said it is a real issue and I’ll track it with the other issues on this list, and I’ve added it as a dependency on the meta bug (PR15732) to make it easier to keep track of. Thanks, -Chris > On Jul 29, 2015, at 4:48 PM,

Description =========== This patch adds support of CMake meta build system, so you can generate Unix makefiles, VS 6.0-2017 projects and many more. Features ======== * Win32 and Linux tested * Travis CI test added * Generates working Visual Studio 6.0-2017 solutions * Generates working Unix Makefile * Supported options (<option> - <default value>): * `ENABLE_FLOATING_POINT` - on

Daniel, Note the openmp library only has cmake build machinery preventing autoconf-based builds. Jack On Tue, Jun 23, 2015 at 10:18 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Hi, > > I'll do Mips as usual. Are we going to do an autoconf-based build for LLVM 3.7? If so, I might try Mips64 packages too. > >> -----Original

On Mon, Feb 8, 2016 at 12:45 PM, Hans Wennborg <hans at chromium.org> wrote: > Chris Bieneman is probably your best bet, and maybe also Dan Liew. > Hans, My current, and hopefully final, revision of the proposed patch is simplified and reworked to solve the problem entirely from cmake without touching the the llvm-build python scripts. Basically, the new fix for avoiding the

On Wed, Sep 02, 2020 at 11:56:58PM +0000, Chen Wenwei wrote: > Found pkg-config: /usr/local/bin/pkg-config (0.29.2) > Did not find CMake 'cmake' > Found CMake: NO > Run-time dependency libapparmor found: NO (tried pkgconfig and cmake) > Library attr found: YES > Library audit found: YES > Run-time dependency bash-completion found: YES 2.1 > Run-time dependency blkid

$ file /home/andy/misc/bootstrap/out/native/include/zlib.h /home/andy/misc/bootstrap/out/native/include/zlib.h: C source, ASCII text $ cmake /home/andy/misc/bootstrap/llvm-6.0.0.src -DCMAKE_PREFIX_PATH=/home/andy/misc/bootstrap/out/native -DCMAKE_INSTALL_PREFIX=/home/andy/misc/bootstrap/out/native -DCMAKE_BUILD_TYPE=Release -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly; \ -- Looking for

Hello there, I'm trying to play with musl and libvirt to see if I'm able to build a libvirt client binary without dynamic lib dependencies. I have two questions: 1) to your knowledge, is this exercise futile? 2) Do you know if there is a way to *only* compile the library bits? I want to reduce the number of dependencies in the build, and only construct the libvirt libraries, not

Hello everyone, There is still some time to go, but I would like to share my preliminary plan for 3.7. The idea is to keep us on the 6-month release cycle, which means: - Branch for 3.7 on 14 July 2015 - Release 3.7 end of August (absolutely no later than 4 September) I also have a few things I'd like to try this time: - Announce the first release candidate on llvm-announce to encourage

Hans, I have posted a complete patch for solving the linkage issues with LLVM_LINK_LLVM_DYLIB on Phabricator at http://reviews.llvm.org/D16945. The bulk of the fix the simple changes of... Index: cmake/modules/AddLLVM.cmake =================================================================== --- cmake/modules/AddLLVM.cmake (revision 259743) +++ cmake/modules/AddLLVM.cmake (working copy) @@