Re: [bagder/curl] 0e66d5: vc: remove explicit MSVC6 IDE project file and doc...
On Wed, Feb 6, 2013 at 11:30 PM, GitHub nore...@github.com wrote: Commit: 0e66d5878edc3d7ffc445116d194b58bbc7504b9 https://github.com/bagder/curl/commit/0e66d5878edc3d7ffc445116d194b58bbc7504b9 Author: Daniel Stenberg dan...@haxx.se Date: 2013-02-06 (Wed, 06 Feb 2013) Changed paths: M Makefile.am M docs/INSTALL R vc6curl.dsw Log Message: --- vc: remove explicit MSVC6 IDE project file and documentation VC6 is _very_ old and we provide working makefiles even for that compiler. Users who build with the IDE never use that method and project file anyway and it was just lingering in the root dir. Please don't. File 'vc6curl.dsw' in the top subdirectory isn't a lingering file, it is the parent workspace file of the ones present in lib and src subdirectories, all are needed in their specific location. Ancianity of VC6 is no reason to drop it. We have build stuff for much more ancient systems and I would be equally surprised if they were removed. Comment relative to users not using it is inexact. Home page mentions 500 million users. Even if it is a small percentage of users using it, it is a big number of users. ;-) Workspace files for _any_ other MS visual studio can be generated from the VC6 ones. The other way round is impossible. Forward portability from the VC6 workspace and project files into later visual studio versions is possible, the contrary not. The possibility of building by other means is no reason to drop this. Sometimes the best way of debugging something is using the IDE, even when it is possible to build using makefiles. Please, at least reinstate the 'vc6curl.dsw' file in its previous location. I can perfectly live without the docs, although I really see no reason for it to get removed. -- -=[Yang]=- --- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
Re: [bagder/curl] 0e66d5: vc: remove explicit MSVC6 IDE project file and doc...
Yang Tse yangs...@gmail.com wrote: The possibility of building by other means is no reason to drop this. Sometimes the best way of debugging something is using the IDE, even when it is possible to build using makefiles. Also. MSVC6 IDE can generate makefiles from project files. Not sure if later MSVC IDEs can do that. --gv --- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
Re: [bagder/curl] 0e66d5: vc: remove explicit MSVC6 IDE project file and doc...
On Thu, 7 Feb 2013, Yang Tse wrote: vc: remove explicit MSVC6 IDE project file and documentation VC6 is _very_ old and we provide working makefiles even for that compiler. Users who build with the IDE never use that method and project file anyway and it was just lingering in the root dir. Please don't. File 'vc6curl.dsw' in the top subdirectory isn't a lingering file, it is the parent workspace file of the ones present in lib and src subdirectories, all are needed in their specific location. Okay. I grepped around for references to vc6curl.dsw in files but I found none. I'm listening and if you really think it should be left where it was then I'll revert. Also, it wouldn't mean that we drop support for building with that environment. Ancianity of VC6 is no reason to drop it. We have build stuff for much more ancient systems and I would be equally surprised if they were removed. This would be in the same spirit I removed the emacs files. They're virtually unused and only linger there in the root dir year in and year out and aren't ever used. I don't mind keeping files for ancient build systems but I rather not have them in the root dir. Workspace files for _any_ other MS visual studio can be generated from the VC6 ones. Yes, but no users I ever read comments from do their MSVC development based on this file. They typically either use makefiles or they just manually import all the source files into their project. But okay, if you use it I'll reinstate it. -- / daniel.haxx.se --- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
Re: [bagder/curl] 0e66d5: vc: remove explicit MSVC6 IDE project file and doc...
Just thinking out loud, but is it an option to keep the project files etc in a separate subdir, to be moved to root dir by the packager if needed? That seems to be an intersection between both needs? Brgds, Sent from my BlackBerry® smartphone on Telenor -Original Message- From: Daniel Stenberg dan...@haxx.se Sender: curl-library curl-library-boun...@cool.haxx.seDate: Thu, 7 Feb 2013 14:58:42 To: libcurl developmentcurl-library@cool.haxx.se Reply-To: libcurl development curl-library@cool.haxx.se Subject: Re: [bagder/curl] 0e66d5: vc: remove explicit MSVC6 IDE project file and doc... On Thu, 7 Feb 2013, Yang Tse wrote: vc: remove explicit MSVC6 IDE project file and documentation VC6 is _very_ old and we provide working makefiles even for that compiler. Users who build with the IDE never use that method and project file anyway and it was just lingering in the root dir. Please don't. File 'vc6curl.dsw' in the top subdirectory isn't a lingering file, it is the parent workspace file of the ones present in lib and src subdirectories, all are needed in their specific location. Okay. I grepped around for references to vc6curl.dsw in files but I found none. I'm listening and if you really think it should be left where it was then I'll revert. Also, it wouldn't mean that we drop support for building with that environment. Ancianity of VC6 is no reason to drop it. We have build stuff for much more ancient systems and I would be equally surprised if they were removed. This would be in the same spirit I removed the emacs files. They're virtually unused and only linger there in the root dir year in and year out and aren't ever used. I don't mind keeping files for ancient build systems but I rather not have them in the root dir. Workspace files for _any_ other MS visual studio can be generated from the VC6 ones. Yes, but no users I ever read comments from do their MSVC development based on this file. They typically either use makefiles or they just manually import all the source files into their project. But okay, if you use it I'll reinstate it. -- / daniel.haxx.se --- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html --- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
Re: [bagder/curl] 0e66d5: vc: remove explicit MSVC6 IDE project file and doc...
On Thu, Feb 7, 2013, Daniel Stenberg wrote: Okay. I grepped around for references to vc6curl.dsw in files but I found none. I'm listening and if you really think it should be left where it was then I'll revert. Also, it wouldn't mean that we drop support for building with that environment. Thanks, This would be in the same spirit I removed the emacs files. They're virtually unused and only linger there in the root dir year in and year out and aren't ever used. I don't mind keeping files for ancient build systems but I rather not have them in the root dir. We certainly know someone is using'em when we listen them crying when removed. Yes, but no users I ever read comments from do their MSVC development based on this file. They typically either use makefiles or they just manually import all the source files into their project. Maybe because it works and does what it is intended to do? But okay, if you use it I'll reinstate it. Thanks again -- -=[Yang]=- --- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
Re: [bagder/curl] 0e66d5: vc: remove explicit MSVC6 IDE project file and doc...
Daniel Stenberg wrote: On Thu, 7 Feb 2013, Yang Tse wrote: vc: remove explicit MSVC6 IDE project file and documentation VC6 is _very_ old and we provide working makefiles even for that compiler. Users who build with the IDE never use that method and project file anyway and it was just lingering in the root dir. Please don't. ... Ancianity of VC6 is no reason to drop it. We have build stuff for much more ancient systems and I would be equally surprised if they were removed. This would be in the same spirit I removed the emacs files. They're virtually unused and only linger there in the root dir year in and year out and aren't ever used. I don't mind keeping files for ancient build systems but I rather not have them in the root dir. Workspace files for _any_ other MS visual studio can be generated from the VC6 ones. Yes, but no users I ever read comments from do their MSVC development based on this file. They typically either use makefiles or they just manually import all the source files into their project. But okay, if you use it I'll reinstate it. FWIW, we have used the vc6curl.dsw with the 2010 VS as well as a project we still have kicking around in VS6. - Rich --- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
Re: [bagder/curl] 0e66d5: vc: remove explicit MSVC6 IDE project file and doc...
On Thu, 7 Feb 2013, Yang Tse wrote: Would it be fine with you then if I move, and adapt, the VC6 IDE stuff into a subdirectory tree named 'vc' (lowercase) which hangs directly from the root subdirectory? Sounds perfect! -- / daniel.haxx.se --- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
