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

>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: 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 >presence of /etc or the HOME environment variable. Neither have any >true equivalent in Windows. > Will be fixed in a working

>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

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

>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

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

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

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

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

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

============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ =============================================================

Hi Jeff, _HEAPOK is unknown to mingw 1.0 (which is the official release). Henrik. ============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/

Hi, This minor patch clarify matters in the CFEBuildInstrs.html file in my view. Henrik. ============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/

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

Sorry, I forgot to give all you guys my credit, too. Without your help - especially from Jeff, Morten, Reid and Chris, to name a few, this wouldn't have succeded. Just for fun, I ran from a windows command prompt the fibinacci.exe with the argument of 10 and it returned 55. All in all, something lives. Great! :) >From: "Henrik Bach" Date: Fri, 28 Jan 2005 23:26:02 +0100

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

Well, Henrik has a point. As of now, the only thing LLVM is good for when built with VS is the JIT engine, and then only if you're willing to write your own front end--or be satisfied computing fibonacci numbers :) That doesn't make it useless, of course, as Morten will testify, but the market for this level of functionality can't be big. I do plan on creating projects to build llc

Henrik, The patches you submitted will not work (at all) for the Win32 platform because they (still) use Unix system calls. Win32 doesn't have mkdtemp, fork, execve, etc. Furthermore in Path.cpp forward slashes are still used. These need to be changed to back slashes. So, I'm not familiar with mingw platform. Since you've stated they compile on your mingw platform, I'm assuming

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