similar to: [LLVMdev] LLVM and Visual Studio 2003

On 17 May 2011 21:56, Philip Ritchey <pritchey at microsemi-wl.com> wrote: > Hi, > > > > I have what I think is a simple question: Is it at all possible to build > LLVM with Visual Studio 2003? > > > > The “Getting Started with the LLVM System using Microsoft Visual Studio” > document states that versions earlier than 2005 SP1 will not work because > they

Hi, I have Visual Studio 2008 which builds LLVM just fine. The problem is that I need to build it using Visual Studio 2003. I am trying to figure out what it is about LLVM that makes VS2k3 inadequate and then determine if those parts can be removed so that VS2k3 can build a subset of LLVM, and hopefully the subset of LLVM that I need (which is the code generator). Thanks, Philip From: Aaron

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: speex_vs2008.diff Type: application/octet-stream Size: 165590 bytes Desc: speex_vs2008.diff Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20071127/08917736/speex_vs2008-0001.obj

I pulled the test directory from 2003, but everything else from 2005. The 2005 files have more ?cross-compiling? targets than the 2003 ones. I fixed the various missing files in the new 2008 projects (misc.c and one other other are 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

OvermindDL1 <overminddl1 at gmail.com> writes: [snip] > On this first compile everything compiled except for llc and lli, > which did not link due to: > unresolved external symbol "class llvm::FunctionPass * __cdecl > llvm::createPBQPRegisterAllocator(void)" That is because the lib/CodeGen project file is missing PBQP.cpp. [snip] > On Fri, Oct 10, 2008 at 2:11

On 12/3/07, Stefan Reuther <streu@gmx.de> wrote: > John Miles wrote: > > What's wrong with a plain old .bat file, or even an NMAKE .mak file? > > Ship two files, debug.bat and release.bat, and call it good. > > > > It is best to leave project-file creation up to individual users, > > in my opinion. > > I second that. When I played around with Speex

Hello, I maintain audio processing part of code in sipXtapi -- open-source VoIP library. And when I engaged Speex library, I found that its Windows project files are not up to date and use strange settings. They miss several source files and use single-threaded static runtime libraries. I see no benefits of using static and moreover single-threaded libraries. In the modern world very small amount

On 11/28/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > I think the amount of Windows crap is getting a bit ridiculous. Does > anyone know of a solution to keep things manageable? I mean, the same > autotools files manage the build for Linux PCs, Blackfins and MacOS (and > others). Yet, we need one set of files for each MS compiler version > (good thing they

"Cory Nelson" <phrosty at gmail.com> writes: > On Mon, Nov 24, 2008 at 8:18 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: >> OvermindDL1 <overminddl1 at gmail.com> writes: >>> As long as instructions are supplied on how to pass in user defined >>> macros to the build system. I have to turn off a lot of the extra >>> safety crap that

On Oct 10, 2008, at 1:44 PM, Óscar Fuentes wrote: > OvermindDL1 <overminddl1 at gmail.com> writes: > > [snip] > >> On this first compile everything compiled except for llc and lli, >> which did not link due to: >> unresolved external symbol "class llvm::FunctionPass * __cdecl >> llvm::createPBQPRegisterAllocator(void)" > > That is because

I apologize for what's surely a common question, but the Xiph archive-searcher seems broken, and all my other searches have come up dry. Anyway, my question is: Are there any Theora binaries available for Visual Studio.NET? Alternatively, how do I build Theora using Visual Studio.NET? I tried using "\win32\theora_static.dsp", but VS.NET claimed it was corrupt and couldn't

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 >

_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

> On Sat, 3 Mar 2007, Aaron Gray wrote: >> Two things regarding the new subversion repository :- >> 1) Can you remove lib/CodeGen/ELF - which was a copy of the 'libelf' GNU >> library which got partially deleted. > > I just removed it from the CVS repo. > >> 2) Is there any way make the "Win32" Visual Studio 2003 a separate source >>

On a very specific subset of ThinkPad P50 SKUs, particularly ones that come with a Quadro M1000M chip instead of the M2000M variant, the BIOS seems to have a very nasty habit of not always resetting the secondary Nvidia GPU between full reboots if the laptop is configured in Hybrid Graphics mode. The reason for this happening is unknown, but the following steps and possibly a good bit of patience

Hi, Two things regarding the new subversion repository :- 1) Can you remove lib/CodeGen/ELF - which was a copy of the 'libelf' GNU library which got partially deleted. 2) Is there any way make the "Win32" Visual Studio 2003 a separate source repository, so we do not have the VS2003 code being distributed on every *nix platform. AND could we also have a Visual Studio 2005

I have a few pass managers, but only one of them has been initialized with addPassesToEmitCode, how do I find how many passes are added to a function pass manager ? Thank you, Xin On Fri, May 20, 2011 at 1:00 PM, <llvmdev-request at cs.uiuc.edu> wrote: > Send LLVMdev mailing list submissions to > llvmdev at cs.uiuc.edu > > To subscribe or unsubscribe via the World Wide

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

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

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