search for: e01a4321

It's not clear it offers any real benefits. The project files already exist. To use this, I would have to throw them away and create new XML files by hand. I would have to maintain them by hand also, whereas the project files are maintainable from within Visual Studio, i.e. via an integrated GUI interface. And to comment on supporting other targets: No reason it can't be done,

Might I suggest the following tool for setting-up/maintaining the Visual Studio project files. It makes setting them up with all the right build options and include paths much, much easier. =) http://sourceforge.net/projects/xpj -- Christopher Lamb christopher.lamb at gmail.com On Mar 28, 2007, at 3:06 AM, Morten Ofstad wrote: > Seung Jae Lee wrote: >> Is there any special reason

...t cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -- Christopher Lamb christopher.lamb at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070328/e01a4321/attachment.html>