similar to: [LLVMdev] ThisCall / Compilation problems

Displaying 20 results from an estimated 100000 matches similar to: "[LLVMdev] ThisCall / Compilation problems"

2004 Dec 26
1
[LLVMdev] VC++: Cannot open include file:'windows.h':No suchfileor directory
I agree completely with you, Jeff. However, I think it somehow would be nice, if you guys could tell comming users that the win32 solution is geared toward VC++ 7.1 (and hence use of other tools are at their own risk). And, I think it also would be really cool, if you guys come up with a solution how to handle multiple VC++ x solutions/projects from the same source, possibly ranging from VC
2004 Dec 26
0
[LLVMdev] VC++: Cannot open include file: 'windows.h':No suchfileor directory
It's a possibility, though it would be better to create whole separate trees for different versions of VS. It's not just the project and solutions that need to be kept separate; the object files themselves cannot be mixed between different versions of VS. There's no rush though. Trust me, C/C++ programmers will not rush to adopt Whidbey once it's released. You'd be
2004 Dec 25
2
[LLVMdev] VC++: Cannot open include file: 'windows.h':No suchfileor directory
Hi Jeff and Morten, I was just wondering if below wisdom is true, why not prefix every solution and project file with VC71 in front of the file name to signal the case that it is only designed for that specific IDE/tool? This gives us room for comming up with other solution and project files for another MS specific IDE/tool independt of each other. Henrik. ----Original Message Follows----
2004 Dec 23
3
[LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfileor directory
----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfileor directory Date: Thu, 23 Dec 2004 08:05:39 -0800 >Yes, it
2004 Dec 23
0
[LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfile or directory
Yes, it should find windows.h with the default configuration. But you have to be suspicious of beta code that Microsoft gives out for free. It might just be very buggy, or it might be deliberately crippled. Considering the price tag on Visual Studio, it's one or the other (and probably both). Out of curiosity, did it accept the solution and project files as is, or did it want to
2004 Dec 23
0
[LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfileor directory
Henrik Bach wrote: > ----Original Message Follows---- > From: Jeff Cohen <jeffc at jolt-lang.org> > Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List > <llvmdev at cs.uiuc.edu> > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': > No suchfileor
2006 Dec 15
0
[LLVMdev] ThisCall / Compilation problems
Hello, David. > A few things. > Firstly, I've got a working implementation of the X86ThisCall calling > convention, but I'm unsure how to go about submitting it. > (I'm not really sure how to go about creating patch files etc, but > would like to contribute to the project). I suppose, you've changed X86ISelLowering.cpp, X86*AsmPrinter.cpp, CallingConv.h. Right?
2004 Dec 23
2
[LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfile or directory
----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfile or directory Date: Tue, 21 Dec 2004 16:29:47 -0800
2006 Dec 14
3
[LLVMdev] ThisCall / Compilation problems
Hi all, A few things. Firstly, I've got a working implementation of the X86ThisCall calling convention, but I'm unsure how to go about submitting it. (I'm not really sure how to go about creating patch files etc, but would like to contribute to the project). Also, I'm using MS Visual C++ Express, and there are a few things that stop llvm1.9 (and the current CVS release) from
2004 Dec 24
0
[LLVMdev] win32 broken again
Hi Jeff, Typically, I've found out that these missing functions are placed beneath lib/System/Unix in some of *.cpp files. These function can be copied to their respectively lib/System/Win32 *.cpp files. Henrik. ----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at
2004 Dec 24
3
[LLVMdev] win32 broken again
Well... that didn't take long. I'm not sure what you did, Reid, with Path.cpp, but it broke VC++: Bytecode.lib(ReaderWrappers.obj) : error LNK2001: unresolved external symbol "public: __thiscall llvm::sys::Path::Path(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0Path at sys@llvm@@QAE at
2004 Dec 22
0
[LLVMdev] VC++: Cannot open include file: 'windows.h': No such file or directory
Windows.h is part of Microsoft's Platform SDK that's bundled with Visual Studio. It should never have been in the llvm source tree. Why don't you have it? You have VC++, right? Henrik Bach wrote: > Hi, > > I cannot find windows either... In previous llvm sources windows.h was > found in: 'include/llvm/Config'. > > ------ Build started: Project:
2004 Sep 15
0
[LLVMdev] Files to lib/System/Win32
>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Wed, 15 Sep 2004 09:35:51 -0700 > >I did successfully compile all those files with VC++ 7.1. Does mingw >come with it's own version of windows.h or are you using the official >Microsoft header files? > Due to legal issues with Microsoft, they (mingw development team) have supplied their own header files to support
2007 Mar 10
5
[LLVMdev] LLVM with Microsoft Visual Studio
On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: > It is, if only because it's the version I use, but 2005 is supposed to > work also. That being said, I wouldn't be surprised to learn that it > doesn't due to recent STL issues. Versions prior to 2003 won't work. I'm using the basic stuff (just libraries, 1.9) with 2005, although we had to fix a few
2007 Mar 10
1
[LLVMdev] LLVM with Microsoft Visual Studio
I successfully build llvm from cvs using vs2005 and stlport. I also had a couple of issues, but most were due to outdated project files. I also had to implement code for the alloca instruction. On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: > > The recent issues concern the head revision, post 1.9. As no one has > ever submitted patches to fix 2005 problems with the 1.9
2004 Sep 15
1
[LLVMdev] Files to lib/System/Win32
>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Tue, 14 Sep 2004 19:43:34 -0700 > >OK, I stand corrected: mingw can be used to create honest-to-goodness >Windows applications using Win32. But you're still using it as a Unix >emulator :) > OK, if POSIX.1 is unix emulation then we have that all *nix emulates all *nix and that's fine with me :) OK, I admit,
2005 Nov 01
4
[LLVMdev] Re: Still can't compile backend or frontend on, Windows
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 Web, visit > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >or, via email, send a message with subject or body 'help' to > llvmdev-request at cs.uiuc.edu > >You can reach the person managing the list at
2004 Sep 19
2
[LLVMdev] Files to lib/System/Win32
Patch committed. Thanks for cleaning up some of the coding standards issues. Reid. On Sat, 2004-09-18 at 22:18, Jeff Cohen wrote: > Patch for Signals.cpp attached. > > On Sat, 18 Sep 2004 21:30:12 -0700 > Jeff Cohen <jeffc at jolt-lang.org> wrote: > > > On Sat, 18 Sep 2004 12:30:41 -0700 > > Reid Spencer <reid at x10sys.com> wrote: > > > >
2005 Jan 14
1
[LLVMdev] Building the CFE I get this error: there are no arguments to `lrand48'
This sounds suspiciously like the problem I ran into with VC++, whose std implementation also includes _Distance. Could mingw have copied VC++ too closely? The fix with VC++ was to add a "using std::_Distance" line (or just "using namespace std". Chris Lattner wrote: > On Fri, 14 Jan 2005, Henrik Bach wrote: > >> when building the llvm cfe (3.4 derivative), for
2007 Mar 10
0
[LLVMdev] LLVM with Microsoft Visual Studio
The recent issues concern the head revision, post 1.9. As no one has ever submitted patches to fix 2005 problems with the 1.9 release, it is safe to say they still exist. Andreas Fredriksson wrote: > On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: >> It is, if only because it's the version I use, but 2005 is supposed to >> work also. That being said, I