search for: vs2k3

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 Gray [mailto:aaronngray.lists at gmail.com] Sent: Tuesday, May 17, 2011 7:42 PM To: Philip...

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 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 do not support the C++ standard well enough. Is it just some features of LLVM that require better C++ support and so building

On Fri, Dec 5, 2008 at 2:31 PM, Cédric Venet <cedric.venet at laposte.net> wrote: > OvermindDL1 a écrit : >> On Fri, Dec 5, 2008 at 1:58 PM, OvermindDL1 <overminddl1 at gmail.com> wrote: >> >>> On Fri, Dec 5, 2008 at 1:57 PM, OvermindDL1 <overminddl1 at gmail.com> wrote: >>> >>>> On Fri, Dec 5, 2008 at 1:52 PM, OvermindDL1

On Fri, Dec 5, 2008 at 2:38 PM, OvermindDL1 <overminddl1 at gmail.com> wrote: > /* snip */ I updated the svn to 60607. It still needed that const change. Added the const word on that member function. Tried building debug, debug still fails horrible. I am going to try to stop by that computer for an hour or so before my next work shift tonight, will completely get rid of every trace

...uses a corresponding dll file), s is a static lib, p means it has all my preprocessor defines from above, no p means it does not. A setup like this in cmake would be perfect I would have to say (well, minus the dynamic libs since they are not well supported). I really wish I could have stuck with VS2k3, regardless of the (surprisingly) few complience issues it had, it just ran as you would expect, no hidden gotchas and other crap like these definitions. And good god yes, when using the stl in some cases, without all of the above, it adds so freaking much bound checking code that, quite literally...

"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

I did some looking up on that const thing. Apparently that const is 'supposed' to be there, but it is not strictly required. However there is a bug in VS2k3 (VS7) through VS2k8 (VS9) (no clue if it has been fixed yet) that requires it to be there when the functor is being called through a const qualified interface, such as through stl containers. They state that a bug report has been filed, but regardless of if it is filled or not, in such functors yo...

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

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

...upport things like > testing on systems that almost nobody (wants to) use?. Well I use it, and I know of three other windows LLVM users that have contacted me for help with their own projects as well. The VC2k3 support is broken because of a "friend" declaration in LLVM in a way that VS2k3 does not support (2k3's fault, although the friend usage was also questionable...). Although I think the main lack of visible Windows users (there are definitely Windows llvm users) is because llvm feels so gcc oriented, rather then being a truly open code generator (I mean come on, you try to...