search for: liblibclang

Hi, I accidentally noticed the following line when building LLVM and Clang on Windows 7 x64 using Mingw64: Linking CXX shared library ..\..\..\..\bin\liblibclang.dll "Liblib" seems a bit overkill. FYI. BTW, for those who happen to search on LLVM, Clang, Windows, and Mingw64: The v3.1 release does NOT build with Mingw64. I believe this has been fixed in the Subversion sources as they build without problems. There's a thread about this here...

On 28 May 2012, at 16:46, Mikael Lyngvig wrote: > > Hi, > > I accidentally noticed the following line when building LLVM and Clang on Windows 7 x64 using Mingw64: > > Linking CXX shared library ..\..\..\..\bin\liblibclang.dll > > "Liblib" seems a bit overkill. FYI. See http://llvm.org/bugs/show_bug.cgi?id=12620 for links to several threads on the clang mailing list over the last 2 years. The latest change was trunk at r156809 -- it attempted to fix the cmake build system such that it builds &quot...

On 06/22/2012 07:42 AM, David Röthlisberger wrote: > On 22 Jun 2012, at 00:08, Óscar Fuentes wrote: >> > Albert Graef <Dr.Graef at t-online.de> writes: >> > - libclang ends up as liblibclang.so (building clang along with LLVM). >>> >> Surely that's not intended? >> > >> > There was some discussion about this on the past, but I can't recall all >> > the details. In any case, it is something easy enough to change. > > This should...

...delete afterwards. That's much better than overwriting/removing the previous version. > - No libLLVM-<version>.so. I get this with the autoconf-based build if > shared libraries are enabled, but not with the cmake build. This is very easy to implement. > - libclang ends up as liblibclang.so (building clang along with LLVM). > Surely that's not intended? There was some discussion about this on the past, but I can't recall all the details. In any case, it is something easy enough to change.

On 22 Jun 2012, at 00:08, Óscar Fuentes wrote: > Albert Graef <Dr.Graef at t-online.de> writes: > - libclang ends up as liblibclang.so (building clang along with LLVM). >> Surely that's not intended? > > There was some discussion about this on the past, but I can't recall all > the details. In any case, it is something easy enough to change. This should be fixed as of 3.1. See http://llvm.org/bugs/show...

...libLLVMJIT.a libLLVMSupport.a libLLVMX86Info.a clang/ libclangLex.a libgtest_main.a libLLVMCodeGen.a libLLVMLinker.a libLLVMTableGen.a libLLVMX86Utils.a libclangAnalysis.a libclangParse.a liblibclang.a libLLVMCore.a libLLVMMC.a libLLVMTarget.a libLTO.a libclangARCMigrate.a libclangRewrite.a liblibclang.so@ libLLVMDebugInfo.a libLLVMMCDisassembler.a libLLVMTransformUtils.a libLTO.so libclangAST.a libclangSema.a...

James, > [ 94%] [ 94%] Building CXX object > tools/clang/tools/libclang/CMakeFiles/libclang.dir/IndexingContext.cpp.o > Building CXX object > tools/clang/lib/StaticAnalyzer/Core/CMakeFiles/clangStaticAnalyzerCore.dir/M > emRegion.cpp.o > Linking CXX shared library ../../../../lib/liblibclang.so I am suspicious, I guess you might not enable optimization on cmake build. 1) make sure with "make VERBOSE=1" 2) make sure you would set proper CMAKE_BUILD_TYPE, or CMAKE_CXX_FLAGS. ...Takumi

...quickly try a new LLVM version. I know that cmake doesn't provide this out of the box, but then it should be added as a custom target. - No libLLVM-<version>.so. I get this with the autoconf-based build if shared libraries are enabled, but not with the cmake build. - libclang ends up as liblibclang.so (building clang along with LLVM). Surely that's not intended? Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr.Graef at t-online.de, ag at muwiinfa.geschichte.uni-mainz.de WWW: http://www.musikinformatik.uni-mainz.de/ag

Anton Korobeynikov <anton at korobeynikov.info> writes: > I think cmake system lacks many features of autoconf system. In > addition to already said thing, I think the major missing thing is > cross-compilation support. > You can easy cross-compile llvm/clang via standard > --build/--host/--target flags. If you will show that this will be > possible by cmake - then

where should the file build_llvm_package.bat be placed and how should the build_llvm_package.bat be called? or is there a another way to do a two stage build of the llvm project on windows starting with using visual studio 2017 community. -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

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