search for: vs2005

_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 VS2...

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 fi...

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 > >> Morten Ofstad wrote: >> >>> Jeff Cohen wrote: >>> >>>> The project files...

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 >...

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 add -D_CRT_SECURE_NO_DEPRECATE for the > preprocessor? Isn...

...9;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 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:...

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...

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...

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&qu...

...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 have moved to invoking DEVENV directly from the command line and no longer use or need the full blown IDE. I am looking for a way to get DEVENV from VS2005 to run under Wine (again the IDE IS NOT needed or wanted). Is there a way to do this? How do I set...

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__) || _WIN32_WINNT < 0x0600 I'm still getting random crashes running llvm-tblgen.exe which I think is...

OK, fixed the problem with the intrin.h header that doesn't exist in previous versions of VS... -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: JIT.patch URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060126/7e55b0d0/attachment.ksh>

...Tue, Nov 8, 2011 at 8:02 AM, Don Williamson <don.williamson at yahoo.com> wrote: > > > 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__) || _WIN32_WINNT < 0x0600 > > I'm still getting random crashes running llvm-...

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: Francois Pichet <pichet2000 at gmail.com&g...

...gone now). The only thing you could do which would make them more compact would be to get rid of the subdirectories under each vs-version. There is no real need for it and it just makes things a little confusing. Win32 ------ vs2003 -----All .sln, .vcproj | |------vs2005 -----All .sln, .vcproj | |------vs2008 -----All .sln,.bcproj You could also remove the old Visual Studio 6 files, .dsw, .dsp since that compiler is no longer supported by MS. -Aron From: kamaji@gmail.com [mailto:kamaji@gmail.com] On Behalf Of Keith Kyziva...

On Tue, Nov 8, 2011 at 8:42 AM, Don Williamson <don.williamson at yahoo.com> wrote: > 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. I don't know about VS support being deprecated, but I'm more curious as to what...

...c.h). So it looks like my build (using cmake) is not picking up the installed v7.0 SDK. This can be achieved by running a tool in the WSDK that makes your version "current" (it modifies the visual studio global include directories). However, that's kind of moot since you can install VS2005 and not update to the latest WSDK. In fact, I only updated it because I was after GPUView. Various MSDN documents say that if you want to compile for a minimum OS version then you need to define _WIN32_WINNT to be that version: http://msdn.microsoft.com/en-us/library/aa383745(v=vs.85).aspx Howev...

...ually maintained the Visual Studio project / solution files, which has always been a pain. Recently we've made a successful partial migration to a CMake driven environment. This lets us manage one set of quasi-make text files, and CMake does a surprisingly nice job of generating VS2003 and VS2005 project / solution files along with our Linux and other target make files. We've had some success adding other related automations like doxygen configs that get passed the per-library source file lists. CMake even lets us generate source / header folders within the Visual Studio projects...

...ind any recent discussion of this, so thought I'd post, and I'm not clear who maintains the Win32 build environment or I'd have contacted them directly. I've finally gotten around to turning voice back on in my project, and I'm having issues with obtaining a stable build in VS2005. I've checked out SVN trunk of obb (as libogg) and speex, built libogg with no problems in debug and release mode, but am having problems with the speex projects. I've reproduced these on three (multicore) machines, two XP and one Vista. Some of the strange intermittent errors (like...

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 prefer not to take discussions off the list. In my day-to-day development I use V...