similar to: [LLVMdev] LLVM binaries for Windows and more

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

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.

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

Hi! I have trouble compiling the flac library using Microsofts free (yes MS gives it away including the optimizing C++ compiler msvc8.0) Visual Studio Express 2005. I get the output shown below. Does anyone have a way to make flac compile in VS 2005? Thanks! Ulrik 1>------ Rebuild All started: Project: replaygain_analysis_static, Configuration: Debug Win32 ------ 1>Deleting

On Sep 6, 2010, at 10:50 PM, David Shipman wrote: > Hi all, > > Just tried to build from svn sources with Visual Studio 2008, mostly > OK but fails > building the X86AsmParser lib - > > I see a few commits from yesterday that may have something to do with it, but no > idea what the solution is. Wow, that's a pretty terrible diagnostic. Does r113198 help? -Chris

Hello, I've been building Clang under Windows 7 and Visual Studio 2008 for a while now, but had not touched it in a few months. Last night I wiped my build tree to do a full rebuild with the latest version, and got the identical error as David Shipman was seeing last September. Are others able to build under VS9 right now? Thanks, John > Subject: Re: [LLVMdev] MS VS2008 build fails -

Hi all, Just tried to build from svn sources with Visual Studio 2008, mostly OK but fails building the X86AsmParser lib - I see a few commits from yesterday that may have something to do with it, but no idea what the solution is. -David See MSVC's beautiful and concise output below; Compiling... X86AsmParser.cpp C:\dev\MSVisualStudio\VC\include\xutility(313) : error C2664: 'bool

Hi, I have been using LLVM+Clang in my project for some time and it has been working just fine up to now (I am currently using version 3.5.1). However, with version 3.6 having just been released, I thought I would give it a try and update my code to use MCJIT rather than the now discontinued JIT. Well, this proved to be a relatively smooth process, and everything is now working fine on

Sorry, I am using CMake+JOM or CMake+Ninja, if Ninja is available on the developer’s machine. Either way, it fails in both cases with a message similar to the one I included below (which was obtained using CMake+Ninja). Just in case, my (current) CMakeLists.txt file can be found at here

Hi, Some random sample of VS warning: Lot of 64 bits conversions: AsmPrinter.cpp ..\..\lib\CodeGen\AsmPrinter.cpp(277) : warning C4244: 'initializing' : conversion from 'uint64_t' to 'unsigned int', possible loss of data ..\..\lib\CodeGen\AsmPrinter.cpp(614) : warning C4244: 'argument' : conversion from 'uint64_t' to 'int', possible loss of data

It compiles successfully with VC++ 7.1. You are apparently using VC++ 8.0, otherwise known as the Whidbey beta. The cause is no doubt due to bugs in Whidbey and this isn't the first one encountered. I'm sorry, but I cannot support beta Microsoft products (if only because I refuse to have them anywhere near my computer). All I can suggest is that you do a 'clean solution'

I'm not sure what causes this. Everything builds fine in Release mode but when I try to do a Debug build I get an error in Transforms (which causes all dependant projects to fail as well). I'm not exactly sure what causes the error, I'll try to investigate tomorrow (unless someone can figure out what it is by then). Below is the output from VS: ------ Build started: Project:

I'm not sure how many people are using Visual Studio to build the llvm tools, other than myself? When I compile the llvm tools on linux I do not see any warnings (I believe -Wall is set?). However, under visual studio there are a lot of warnings, mostly of this form: warning C4244: 'initializing' : conversion from 'uint64_t' to 'unsigned int', possible loss of data

On Fri, Aug 31, 2007 at 08:10:33PM -0400, Daniel Berlin wrote: > Suggestions, criticisms, etc, are welcome. I haven't studied the implementation, but I have a few comments on the interface, and some style comments, below. > Index: include/llvm/ADT/SparseBitmap.h > =================================================================== > --- include/llvm/ADT/SparseBitmap.h (revision

Hi I downloaded speex-1.2beta2 from svn.xiph.org/releases/speex and am trying to build the win32/VS2005/libspeex/lipspeex.vcproj When I try to build the Release configuration, I get the following error: LNK1181: cannot open input file '.\Release\medfilter.obj' Trying to build the Debug or Release_Dynamic configurations gives a related error: C1083: cannot open source file:

Hi, I've been doing some development for Pocket PC 2003 applications and have happened to chance upon Speex. To date, I've been having some issues in linking libspeex.lib with my application in MS Visual Studio 2005. Upon building my program, I will always receive the error: fatal error LNK1181: cannot open input file 'd:\Recorder\libspeex.lib' Recorder A brief description

Hi, I upgraded the Visual Studio SLN file to work with 2005 and had to make some changes. The first two have to do with the fact that the debug implementation of 2005's STL does all sort of validation, that's why they didn’t show up on 2003. I'm not set up for patch submission yet, but if somebody has time to review these changes that'd be greatly appreciated. Meanwhile

Hola Jaap, I'm curious which version of the source are you working with? It sounds like you and I were working on the same problem yesterday, but I didn't see those particular compiler errors. (I saw a couple of other ones for which I submitted a patch). I did see errors like the ones you saw with the CVS LLVM 2.0 sources a while back, namely the missing < operator and the debug STL

I am attempting to build the RC1 drop of libspeex for Windows with the MSVC toolchain (VS2013) and MinGW, the following is my configure line: CC=cl.exe CFLAGS=-MD ./configure --enable-shared=no --prefix /builds/Windows81/x86 --host i686-pc-mingw32 During the configure process (specifically the "checking whether the C compiler works...") I get a Windows popup telling me that the test

I am trying to build 1.2beta1. I downloaded the sources from http://downloads.us.xiph.org/releases/speex/speex-1.2beta1.tar.gz and tried compiling it under visual studio 2005. it gave the following errors: LIB : fatal error LNK1181: cannot open input file '.\debug_rtl_dll\medfilter.obj' Build log was saved at