similar to: [LLVMdev] Build script for llvm/cmake/msvc

Hi Any reason why the CMake build doesn't include more target backends under MSVC? (Currently only x86). I just tried turning on all the backends and everything seems to build OK. I don't know if they all run correctly. If there isn't a good reason, attached is the trivial patch to include all targets. scott -------------- next part -------------- A non-text attachment was

Hi, I just commited ( rev 58461 ) a patch which change the name of the generated solution file for a CMake build. (from 'project' to 'LLVM'). This has the consequence that if you use the GUI of MSVC, you will need to manually open to the new solution (the old one isn't deleted but will not be updated anymore). This will also force a full rebuild. Regards, Cédric ps: Is

Dear all, I am writing a compiler backend using LLVM with MSVC and have noticed that in LLVM version 2.6 it is no longer possible to use Just-In-Time Debugger at the point of assertion failure. The call stack is printed instead and the debugger stops at some strange location with the call stack like the following: > msvcr80d.dll!_NMSG_WRITE(int rterrnum=5111881) Line 198 C

Dear all, would appreciate a suggestion about the following situation : I am running a script in R, and shall i execute it in the terminal, step by step, it works fine. however, if i do source ("script.R"), it does not complete and I am getting the error : "Can only modify plain character vectors." what may go wrong ? thank you for your help, -- bogdan [[alternative HTML

Hi to all out there, i know this is not the right mailinglist for this issue, but i?m hoping to get maybe here an answer to my problem. i have succesfully migrated 12.000 mailboxes on a debaian with washington imap to maildir on sles10 with dovecot. although i had some post-converting work to do, i can say that almost everything went fine. but there is one problem with my LDA. When postfix is

On Wed, Dec 23, 2015 at 5:49 PM, Aaron Ballman <aaron at aaronballman.com> wrote: > On Wed, Dec 23, 2015 at 11:29 AM, Jakob Bornecrantz via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> I'm building on Windows x64 using cmake, Ninja and VS 2013 express on Windows 7. >> >> So I have been using the LLVMSharp method on getting a usable loadable >>

Now that the commit of... ------------------------------------------------------------------------ r236534 | achurbanov | 2015-05-05 16:02:52 -0400 (Tue, 05 May 2015) | 13 lines Integrate libiomp CMake into LLVM CMake build system. This patch integrates the libiomp CMake build system into the LLVM CMake build system so that users can checkout libiomp into the projects directory of llvm and

This sounds like an operating system specific question, in that "submit the R script to a PBS HPC scheduler" would be the kind of action that would run R with very different environment variables and possibly different access credentials than your usual interactive terminal. A thorough reading of the "Installation and Administration Guide" and some study of your HPC

Ruben Van Boxem <vanboxem.ruben at gmail.com> writes: >>> I'm trying to build svn LLVM with Visual Studio 2010: >>> >>> cd build >>> cmake .. -G"NMake Makefiles" >>> nmake >>> >>> and several link steps fail due to a missing symbol: >>> >>> > LLVMX86CodeGen.lib(X86JITInfo.cpp.obj) : error

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

2010/12/31 Francois Pichet <pichet2000 at gmail.com>: > I don't normally build using nmake.. but I just tried and it worked 100% > here. > Are you sure you are using the trunk? > > On Fri, Dec 31, 2010 at 7:32 AM, Ruben Van Boxem <vanboxem.ruben at gmail.com> > wrote: >> >> I first sent this to the Clang dev list, but they told me to come here:

The attached patch modifies the CMake/LLVMBuild scripts to build llvm-config on Windows if sed is found on the user's PATH. It also teaches LLVMBuild about MSVC library naming so llvm-config will produce the proper lists of library names. Any comments? Okay to commit? ----------------------------------------------------------------------------------- This email message is for the sole use

Justin Holewinski <jholewinski at nvidia.com> writes: > The attached patch modifies the CMake/LLVMBuild scripts to build > llvm-config on Windows if sed is found on the user's PATH. It also > teaches LLVMBuild about MSVC library naming so llvm-config will > produce the proper lists of library names. > > Any comments? Okay to commit? The presence of sed does not mean

I was getting some "application failed to start properly" pages, but production.log was not showing anything. Looking closer I''ve noticed that server_error.log (the apache log) was giving lines like: "malformed header from script. Bad header=<html>: dispatch.fcgi, referer:" I was able to determine the cause, and that was that some pages were starting with a space

Hello! I'm wondering whether compiler-rt is expected to be buildable with MSVC 2013. I am currently getting: Error 49 error LNK2005: _free already defined in asan_malloc_win.obj E:\llvm\crt_build\lib\asan\MSVCRT.lib(MSVCR120.dll) Which seems to be the only issue (aside from ~50 warnings, which I'll happily work on cleaning up). I get this when I build the ALL_BUILD project in the

On Thu, Oct 23, 2014 at 1:13 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote: > Yes it is. > Are you doing a Debug or Release build? > Using ninja? Release build, cmake + MSVC (not using ninja). Perhaps I have it configured stupidly; I have it as an out-of-tree folder, did: E:\llvm\crt_build>cmake -DLLVM_CONFIG_PATH=E:\llvm\2013\Debug\bin -G "Visual Studio 12"

On Sun, Aug 9, 2009 at 10:03 AM, Óscar Fuentes<ofv at wanadoo.es> wrote: >> Also, now msvc support multiple target. So it's better to set it as >> ${LLVM_ALL_TARGETS} >> It's can working, why not set it to:. > > I think most LLVM users on Windows are interested on X86 only. This > saves a lot of time on the build process and creates smaller >

Yes. I’ll handle the documentation updates too. I’ll base the list of C++11 features on the MSDN documentation. -Chris > On Jan 30, 2015, at 3:57 PM, Aaron Ballman <aaron at aaronballman.com> wrote: > > On Fri, Jan 30, 2015 at 6:51 PM, Chris Bieneman <cbieneman at apple.com> wrote: >> +Alex Bradbury >> >> Sounds to me like we have no known users still on

Hi, everyone. Does anyone faced with the MSVC Debug build issues of clang-tblgen and llvm-tblgen? I'm using Windows10 Pro. MSVC and GCC. Here is my cmake setup: cmake -GNinja ../llvm -DLLVM_ENABLE_PROJECTS=clang -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Debug When building debug with GCC, cmd shows next: D:\llvm-project\buildn2\bin>clang-tblgen.exe --version LLVM

I’m trying to figure out how to build compiler-rt 3.5.0 with Visual Studio 2013. In an autotools build or cmake on Linux, I believe putting the compiler-rt sources under llvm/projects is enough to build them automatically. Do I need to do anything specific to get the same with MSVC? I've tried setting -DLLVM_BUILD_EXTERNAL_COMPILER_RT either ON or OFF, but can't find any evidence of