I've come over an open source script which should be able to convert unix (gnu?) like makefiles to nmake. However, It possible needs some changes to work with the llvm makefile framework. Until then, I strongly suggest a repository for the msvc project files until we'll come with a lasting solution. It is natural that we, msvc guys, should keep these files in shape. Henrik. ----Original Message Follows---- From: Reid Spencer <reid at x10sys.com> Reply-To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] Final Visual Studio Patches Date: Mon, 01 Nov 2004 12:33:29 -0800 We could add the MSVS project files to the repository but I too would like to see a single mechanism for building on all platforms. Someone mentioned using the Boost build system a few weeks ago but I haven't heard anything more on how that effort is going. I also think we can customize our existing makefiles to use the underlying (command oriented) tools under MSVS. We'd still need cygwin for this solution but at least we could compile with an MS compiler. Reid. Chris Lattner wrote:>On Mon, 1 Nov 2004, Morten Ofstad wrote: > >>with the patches you accepted last week, everything now works with two >>one-line modifications. > > >Great! > > >>One is a missing include in a windows specific >>platform file and > > >Okay, as Jeff pointed out, this isn't needed, so not applied. > > >>the other is a definition of a symbol I need to trick the linker (as >>discussed before)... The attached file is the complete diff between my > > >Applied: >http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/020124.html > > >>If you want to put my visual studio project files into the CVS, please >>tell me where to send them as they're too big to attach to this mail. > > >I'm not sure what the right thing is to do with these, I will defer to >other people more involved with the build to decide. > >For me, coming up with a way to support both unix-like and windows-like >systems in one framework seems best from the maintenance standpoint, but I >don't know what the right way is to do this. > >-Chris >_______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev _________________________________________________________________ Opret en gratis Hotmail-konto http://www.hotmail.com med udsigt til 250 MB lagerkapacitet
On Tue, 02 Nov 2004 10:25:39 +0100 "Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote:> I've come over an open source script which should be able to convert unix > (gnu?) like makefiles to nmake. However, It possible needs some changes to > work with the llvm makefile framework.I'm very doubtful this utility is of any use. nmake is useless compared to gnu make. I don't see how gnu makefiles can be converted to nmake makefiles except in the most trivial of cases.> Until then, I strongly suggest a repository for the msvc project files until > we'll come with a lasting solution. It is natural that we, msvc guys, should > keep these files in shape. > > Henrik.Like it or not, I suspect solution and projects files are the lasting solution. Makefiles are not normally used in the Windows world, because nmake is not usable for anything non-trivial. Microsoft doesn't make nmake truly useful, because no one uses it enough to care. Heck, I could never get nmake to work with the makefiles generated by Visual Studio! Instead of fixing nmake, Microsoft simply dropped from VS the option of generating makefiles.
Jeff Cohen wrote:> On Tue, 02 Nov 2004 10:25:39 +0100 > "Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: > > >>I've come over an open source script which should be able to convert unix >>(gnu?) like makefiles to nmake. However, It possible needs some changes to >>work with the llvm makefile framework. > > > I'm very doubtful this utility is of any use. nmake is useless compared > to gnu make. I don't see how gnu makefiles can be converted to nmake > makefiles except in the most trivial of cases.Yeah, that would be my take too. I've tried this before and given up. The current makefile system HEAVILY depends on GNU Makef features (unabashedly) and there are many GNU functions that just have no equivlanet in nmake.> >>Until then, I strongly suggest a repository for the msvc project files until >>we'll come with a lasting solution. It is natural that we, msvc guys, should >>keep these files in shape. >> >>Henrik. > > > Like it or not, I suspect solution and projects files are the lasting > solution. Makefiles are not normally used in the Windows world, because > nmake is not usable for anything non-trivial. Microsoft doesn't make > nmake truly useful, because no one uses it enough to care. Heck, I > could never get nmake to work with the makefiles generated by Visual > Studio! Instead of fixing nmake, Microsoft simply dropped from VS the > option of generating makefiles.Right. This is why I suggested we just put the project files in a simple place that Windows folks can keep up to date and that won't get in the way of the Unix folks. So, where's the patch? Reid.