On Thu, Dec 23, 2010 at 2:48 PM, Vincent Torri <[email protected]> wrote: > > Hey, > > On Thu, Dec 23, 2010 at 2:24 PM, Pierre Joye <[email protected]> wrote: >> >> The main issue with sln is that they are versions specific. It would >> be possible to generate dsw for VC6 but for VC8/7/9/10 it is trickier, >> while possible. However you can use cmake instead, it will generate >> sln if desired. > > Visual Studio IDE upgrades automatically older solutions/projects.
I would not call that upgrade, more a conversion. Many flags are not ported correctly, version speicific flags can't be added,etc. However yes, it does convert them, why I mentioned the automatic generation for VC6 :) > So just > write one. For me, just drop everything below Visual Studio 2008. They > indeed provide too old compilers without good standard support. You can > still support VS 2005. but VC6 and VC7 are just crappy compilers. That's > what I do for the dozen of libraries I maintain on Windows. > > cmake is not an option for me: horrible syntax, no 'help' option like > configure, cross compilation is a real pain. I can't understand why people > like it. It's a matter of taster though and I just give my point of view > about cmake. Others like it, it seems. There is a help as far as I remember (anyone maintaining the cmake files can answer? :), but I don't understand how the cmake syntax affects its usage (to build curl or libcurl). >> About the debugger, if you use a non express version of Visual Studio, >> you can enable the JIT debugger (what I do), which provides everything >> you may need. Express editions sadly do not support JIT debugging. >> WinDBG is an alternative as well. > > It's not a matter of what you use and do, it's a matter of most of Windows > developers use. And most of them will not use a Makefile. On the contrary, > most of them will use Visual Studio. Actually it is more a matter what you do. As a curl user (developer using libcurl), how libcurl is built does not matter too much. You fetch the development files, put it in your lib/include paths (be via the IDE, makefile or whatever else you prefer) and that's it. If you are a curl developer, then I can understand the need, however being a windows developer as well (along other OSes), I don't care too much but I find makefiles more flexible and version/setup independent. But as you said, a taste matter :) Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
