similar to: [LLVMdev] Files to lib/System/Win32

>From: "Henrik Bach" <henrik_bach_llvm at hotmail.com> >Date: Tue, 14 Sep 2004 18:10:29 +0200 > >>From: Jeff Cohen <jeffc at jolt-lang.org> >>Date: Tue, 14 Sep 2004 07:25:11 -0700 >> >>On Tue, 14 Sep 2004 12:46:31 +0200 >>"Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: >> >> > >From: Jeff Cohen

On Tue, 14 Sep 2004 12:46:31 +0200 "Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: > >From: Jeff Cohen <jeffc at jolt-lang.org> > >Date: Mon, 13 Sep 2004 21:24:47 -0700 > > > > > >But there are some issues with System I'm going to have to take care of > >besides using Win32. There appears to be some Unix assumptions like the

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Tue, 14 Sep 2004 07:25:11 -0700 > >On Tue, 14 Sep 2004 12:46:31 +0200 >"Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: > > > >From: Jeff Cohen <jeffc at jolt-lang.org> > > >Date: Mon, 13 Sep 2004 21:24:47 -0700 > > > > > > > > >But there are some

I think the $HOME and /etc assumptions are very limited in nature. Most of us who use LLVM every day here at UIUC don't need to bother installing anything in $HOME or /etc, and so they shouldn't be considered a major stumbling block for building a version of LLVM that runs on Windows, no matter how it is done or what libraries it is linked with. Making it possible to build LLVM on

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

>From: Jeff Cohen <jeffc at jolt-lang.org> > >Uh... shouldn't a Win32 port use the Win32 API? > Well, as I see it LLVM contains only tools that are perfectably manageble through a shell. And in this respect, I see the win32/mingw port perfectably achieves this at the moment. >On Tue, 14 Sep 2004 02:11:51 +0200 >"Henrik Bach" <henrik_bach_llvm at

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Wed, 15 Sep 2004 10:35:36 -0700 > >What's a "compiling mesh?" What I meant, was that there are some implicit defines in mingw (like __GCC) and vcX (like _MVC) but possibly also other unsupported? internal structures. As I stated earlier mingw should be win32 api compliant, but not for complicating matters. But

Hi Here is my first patches to the Win32 platform. They compile on the mingw platform. I haven't test them yet, but I thought it will best to put them in the save, just in case... /Henrik _________________________________________________________________ F� alle de nye og sjove ikoner med MSN Messenger http://messenger.msn.dk/ -------------- next part -------------- An embedded and

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

Uh... shouldn't a Win32 port use the Win32 API? On Tue, 14 Sep 2004 02:11:51 +0200 "Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: > Hi > > Here is my first patches to the Win32 platform. > > They compile on the mingw platform. > > I haven't test them yet, but I thought it will best to put them in the save, > just in case... > >

> >> >>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 the win32 API. > To be exact, I use mingws own header

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

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Mon, 13 Sep 2004 21:29:34 -0700 > > >Actually, this is one thing that does not need to be done. Windows is >quite happy using forward slashes in Win32 APIs. Of course, any path >you get /back/ from Windows will have back slashes. I didn't notice this nice little feature :) > >But you do have to take drive

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Wed, 15 Sep 2004 10:44:08 -0700 > >It's not hard in the sense that MSDN has sample code that does this. >It's not much more than cut and paste. But I could make it compile >conditionally so that it will compile only with Microsoft's compiler. > Leave it open as an excise. I'll barf if it's necessary

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

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

Hi, Today I've succeded in compiling the llvm-tools, llvm-gcc and stacker frontend and in installing it. Uptill now I've followed the steps given in: http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html with modifications for the mingw platform. I'll return with step-by-step instructions how to do it on this platform. Cheers Henrik :)

Hi, I get this error: --------------- configure: configuring in projects/Stacker configure: running /bin/sh '/C/projects/src/llvm-2/llvm/projects/Stacker/configure' --prefix=/C/LLVM/tools/ '--prefix=/C/LLVM/tools/' 'CPPFLAGS=-D__MINGW -DLLVM_ON_WIN32=1' --cache-file=/dev/null --srcdir=/C/projects/src/llvm-2/llvm/projects/Stacker configure: error: invalid variable

Yes, it should. I haven't reviewed Henrik's change set yet but if it doesn't look like clean Win32 code then I will create a separate target named MingW and adjust the configure script accordingly. On the other hand, no one has submitted any Win32 patches yet, so first come first served :) Reid. On Mon, 2004-09-13 at 19:35, Jeff Cohen wrote: > Uh... shouldn't a Win32 port use

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