similar to: [LLVMdev] Update VS2005

Applied: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080616/063951.html Thanks Cedric! On Jun 20, 2008, at 2:36 PM, Cédric Venet wrote: > Hi, > > Last time patch contained a new file, but it seems this is not > supported so > I attached it here: > Common.vsprops => llvm/win32/ > This allow to set properties (like preprocessor definition) to all the

Hi, Just a small update for the project files for adding a missing preprocessor definition for VS2005 (without SP1). It suppress the (bogus) M$ deprecated warning. Regards, Cédric Ps: perhaps I should update to SP1 instead :) -------------- next part -------------- A non-text attachment was scrubbed... Name: updVS2005prj080612.patch Type: application/octet-stream Size: 31834 bytes Desc: not

Hi, Three new files added: lib\Analysis\ValueTracking.cpp lib\CodeGen\StackSlotColoring.cpp lib\CodeGen\LiveStackAnalysis.cpp Regards, Cédric -------------- next part -------------- A non-text attachment was scrubbed... Name: updVS2005prj.patch Type: application/octet-stream Size: 1064 bytes Desc: not available URL:

On 17.01.2011 12:35, Raju wrote: > Dear friends > Recently i have downloaded Theora video codec from http://www.xiph.org/ > , > here its having both encoder and decoder , how can i build only > decoder on VC + windows platform , if i build now i will be getting " > Cannot open include file: 'ogg/ogg.h': No such file or directory " > pls send me solution for

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

On Fri, 27 Jan 2006, Jeff Cohen wrote: > _CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it in > VS2003. It shouldn't hurt to define it though, even if VC2003 where it does nothing. Right? -Chris > Morten Ofstad wrote: > >> Jeff Cohen wrote: >> >>> The project files need frequent updating. I cannot maintain VS2005 >>>

Jeff Cohen wrote: > The project files need frequent updating. I cannot maintain VS2005 > project files, so while they could be distributed with LLVM, they will > become broken fast. Also, VS2003 and VS2005 project and solution files > cannot coexist in the same directories, further complicating matters. The VS2003 project files convert without problems -- you might want to add in

_CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it in VS2003. Morten Ofstad wrote: > Jeff Cohen wrote: > >> The project files need frequent updating. I cannot maintain VS2005 >> project files, so while they could be distributed with LLVM, they >> will become broken fast. Also, VS2003 and VS2005 project and >> solution files cannot coexist in

The project files need frequent updating. I cannot maintain VS2005 project files, so while they could be distributed with LLVM, they will become broken fast. Also, VS2003 and VS2005 project and solution files cannot coexist in the same directories, further complicating matters. Aaron Gray wrote: > Hi Morten, > > If you can make the VS2005 project files availiable on the net then I

Hi, what are the goals of VS2005 support for building LLVM? I'm syncing to the v3 branch and while the branch compiles perfectly with VS2008, there are a significant amount of compile errors and warnings with VS2005 SP1 (8.0.50727.867 with KB926601 SP1, to be precise). I also have the latest WSDK installed. A few months back there were only a few minor issues that I managed to clear up.

OK, it's not that bad - it's even better than before :) The main issue is RWMutex.inc and the use of PSRWLOCK. This requires _WIN32_WINNT to be >= 0x0600, which is not true for VS2005 SP1. Rather than #define _WIN32_WINNT 0x0600 (the file notes that this should build on all Win32 variants), extending the copy/paste of winbase.h to this works fine: #if defined(__MINGW32__) ||

On Fri, 27 Jan 2006, Jeff Cohen wrote: > The new property manager doesn't exist in VS2003 either. Don't know where to > add it. Isn't there a place to add -D_CRT_SECURE_NO_DEPRECATE for the preprocessor? Isn't this all we are talking about, or am I missing something? -Chris >> On Fri, 27 Jan 2006, Jeff Cohen wrote: >> >>> _CRT_SECURE_NO_DEPRECATE

I don't know. If that's all it was, why is there a special new property manager to set it? Morten will need to explain what to do in VS2003 to make VS2005 happy. Chris Lattner wrote: > On Fri, 27 Jan 2006, Jeff Cohen wrote: > >> The new property manager doesn't exist in VS2003 either. Don't know >> where to add it. > > > Isn't there a place to

Hi Francois, I have all licensed versions of VS at my disposal (the benefits of being a former MS employee) but I'm currently using VS2005 due to specific technical reasons that I can't disclose. The "Getting Started" page states support of 2005 SP1 which, if it's not being maintained, is not true and should be updated. Cheers, - Don ----- Original Message ----- From:

Hi Morten, If you can make the VS2005 project files availiable on the net then I can test them as I have VS2005 now, so then with Chris'es okay then they could be distributed with LLVM. Thanks, Aaron ----- Original Message ----- From: "Morten Ofstad" <morten at hue.no> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Thursday, January 26,

The new property manager doesn't exist in VS2003 either. Don't know where to add it. Chris Lattner wrote: > On Fri, 27 Jan 2006, Jeff Cohen wrote: > >> _CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it >> in VS2003. > > > It shouldn't hurt to define it though, even if VC2003 where it does > nothing. Right? > > -Chris >

In the v7.0 SDK I see _WIN32_WINNT defined in several places: winresrc.h0x0500 if not defined already (Windows 2000) sdkddkver.h0x0601 if not defined already (Windows 7) objbase.hSet based on NTDDI_VERSION, if not defined already objidl.hSimiler to objbase.h sdkddkver.h is included by windows.h in the v7.0 SDK. With SP1 VC2005, it's defined as 0x0500 in only one place (winresrc.h). So it

Please forgive me if this is covered elsewhere. I did a lot of searches but could not find anything pertaining to what I would like to do. I am developing a product using C/C++ for which the end customer has settled on Visual Studio 2005. I am able to build on my Mac with GNU tools for development and testing but deliverables must be built with VS2005. I am currently using VMWare Fusion but

Hello Jeff, Jeff Cohen wrote on 28/01/2006 at 11:43 a.m.: > I don't know. If that's all it was, why is there a special new property > manager to set it? Morten will need to explain what to do in VS2003 to > make VS2005 happy. IMHO all you need to do is go to Project properties -> C/C++ -> Preprocessor definitions and add _CRT_SECURE_NO_DEPRECATE Best regards,

Hello, On Wed, Oct 1, 2008 at 8:29 PM, Kerry Bonin <kerry at vscape.com> wrote: > - Anyone else see this? > - Who maintains the Win32 projects (at least the VS2005)? I'd be happy > to work with to solve. > - If nobody is actively maintaining this build, I'd be glad to fix and > contribute back. I'm currently listed as a Win32 build system maintainer, but I