similar to: [LLVMdev] LLVM Build Problems on Windows with MSVC 8

Hi all, I have been experimenting with getting LLVM to build with MSVC8 express. I have succeeded in getting trunk to build and run the Fibonacci example in release mode. I have found various minor problems with the build system. First, it appears not to be able to run the configure subproject commands if there is a space in the directory path. Secondly, it fails to build different subprojects

George, > I have been experimenting with getting LLVM to build with > MSVC8 express. > > I have succeeded in getting trunk to build and run the > Fibonacci example in release mode. I have found various minor > problems with the build system. First, it appears not to be > able to run the configure subproject commands if there is a > space in the directory path.

Greetings. Since Halo 2 still doesn't seem to work in Wine, or at least noone put an entry saying it worked up in AppDB, I decided to give it another shot using 1.0-rc1. I have no hope that the original version (which is Vista-only) will ever EVER work in Wine, so I got me the dopeman XP version. This is cracked or something to work with XP. This version does not use an installer, but instead

Hi, All, I follow the menu http://llvm.org/docs/GettingStartedVS.html , but still failed to build LLVM debug version. Here's error message: 7>C:\study\llvm\projects\compiler-rt\lib\asan\asan_win.cc(69): fatal error C1189: #error : Please build the runtime with a non-debug CRT: /MD or /MT Any idear? -- Best Regards, Amy -------------- next part -------------- An HTML attachment was

I verified the patch and it compiles all the targets, both in Debug and Release modes. If there is no someone else to keep the MSVC projects files updated, I will try from time to time to update them and to add the new targets. Maybe a note must be put in "docs/GettingStartedVS.html" at the Requirements section that llvm needs now MSVC (Express) 2008 to compile. Razvan -----

As the title suggests, what is the status of compiling llvm on versions of MSVC less than 2012? Not so much "Does it work?", but more like "Should any thought be given to whether or not something will break it?" Right now there are a bunch of warnings when compiling LLDB on Windows because it uses various symbols which have been defined since VS2012, but which are re-defined

In the llvm file include/llvm/Support/DataTypes.h (.in/.cmake), for MSVCit defines some macros that are defined in the cstdint.hpp file in boost (and boost does it better, detailed below): The basic error is: R:\SDKs\boost\built_head\include\boost-1_38\boost/cstdint.hpp(347) : warning C4005: 'INT8_C' : macro redefinition

To the mailing list this time... On Sat, Mar 6, 2010 at 4:26 PM, OvermindDL1 <overminddl1 at gmail.com> wrote: > On Sat, Mar 6, 2010 at 4:19 PM, José Fonseca <jose.r.fonseca at gmail.com> wrote: >>>> --- a/include/llvm/System/DataTypes.h.cmake >>>> +++ b/include/llvm/System/DataTypes.h.cmake >>>> @@ -100,6 +100,9 @@ typedef u_int64_t uint64_t;

José Fonseca <jose.r.fonseca at gmail.com> writes: > Attached are two patches with MSVC build enchancements. > > They are quite trivial, but were necessary to correctly link LLVM > libraries with Mesa3D on Windows. [snip] > add_llvm_definitions( -D_SCL_SECURE_NO_DEPRECATE ) > + add_llvm_definitions( -D_SECURE_SCL=0 ) With this setting the default LLVM build becomes

LLVM's typedefs for int32_t etc. under MSVC (in Support/DataTypes.h) conflict with those used by other third-party libraries. Instead of these: #ifdef _MSC_VER typedef __int64 int64_t; typedef unsigned __int64 uint64_t; typedef signed int int32_t; typedef unsigned int uint32_t; typedef short int16_t; typedef unsigned short uint16_t; typedef signed char int8_t; typedef unsigned char uint8_t;

On Sun, Aug 9, 2009 at 3:35 PM, Óscar Fuentes<ofv at wanadoo.es> wrote: > Eli Friedman <eli.friedman at gmail.com> writes: > >> MSVC *is* continuously checked; see >> http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9.  Anyone >> who breaks the MSVC build will get a nastygram from buildbot. > > This is new news for me. > > If the developer

On Tue, 13 May 2008, Razvan Aciu wrote: > These are the updated .sln and .vcproj files for building llvm with MSVC > 2008. > It turned out that the compiling errors were because these projects wasn't > updated to reflect the actual status of the llvm files. > I checked all the files (removed, moved or added) and now they are ok. > It compiles all targets from the first

These are the updated .sln and .vcproj files for building llvm with MSVC 2008. It turned out that the compiling errors were because these projects wasn't updated to reflect the actual status of the llvm files. I checked all the files (removed, moved or added) and now they are ok. It compiles all targets from the first "Build Solution", both for Debug and for Release mode. You need

On Fri, Jan 29, 2016 at 6:27 PM, Matthias Braun via llvm-commits < llvm-commits at lists.llvm.org> wrote: > The point I was trying to make here is that all things that DataTypes.h > provides: > intXXX_t, uintXX_t, PRIdXX, INT64_MAX, HUGE_VAL, ssize_t ... > are all part of the C++11 standard and can be found in <cstdint>, <cmath> > (except for ssize_t) so I

As for memory/storage, I think you want these presented as early as possible so people don't go setting up a box only to find out, half a week later, that they can never do what they intended to do (build Clang in debug mode). The reason I use 32-bit Python is that it is what you need, if you want to make a Windows buildbot slave because the Win32 bindings are needed and I don't think

Hi i'm a new user but rsync is easy and a great tool I have a folder caled source and a folder caled destini, like this + Source |_ FolderA |____ File1 |____ File2 + Destini I use this comando to sync only File 1 rsync -a Souce/FolderA/File1 Destini it's copy the File 1 to Destini but i would like who rsync create te Folder A in the destini and put the File 1 inside Then. I read

Attached are two patches with MSVC build enchancements. They are quite trivial, but were necessary to correctly link LLVM libraries with Mesa3D on Windows. Jose -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Allow-to-build-against-static-MSVC-runtime.patch Type: text/x-patch Size: 2055 bytes Desc: not available URL:

Thanks for writing, Nate! Yikes, I totally missed those MSVS docs--it shows just how large and comprehensive LLVM has become! Thanks for helping clarify MSVS support! On Apr 1, 2011, at 2:03 PM, nate fries wrote: > Hi Andy. > This should be no problem, as long as you don't use MSVC's headers inside your scripted code (you should be able to use MinGW's to accomplish the

Hi, I had to add an include statement for the math header to LiveIntervalAnalysis.h to get it to compile today e.g #ifndef LLVM_CODEGEN_LIVEINTERVAL_ANALYSIS_H #define LLVM_CODEGEN_LIVEINTERVAL_ANALYSIS_H #include <math.h> It seems then to work without failures; odd. However, the deprecation warnings are not suppressed for std::_Uninit_Copy and std::_Copy_Opt (warning 4996) in xutility

Ok, I have just found the cause of the error messages I am getting, and it now makes sense to me why the 'normal' build works fine on Windows, Linux and OS X, and why my personal build works on Linux and OS X, but not on Windows. However, I still don't understand why I am getting the error messages I am getting. Anyway, it has to do with wanting to export some classes and function,