Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Swifty on August 10, 2007, 09:40:19 pm
-
It seems as though all the project files for the other IDE/compilers seem to be included. However, I find it rather peculiar that the MSVC2005 directory of the projects are missing, notably libjpeg, liblua, and fred2. Is there something wrong with this or should I just use VC6 to compile the source?
-
Each configuration is dependent upon different coders to keep it maintained. Since I have Visual C++ 6, I maintain the Visual C++ 6 project files. I don't (and can't) maintain the Visual C++ 2005 project files, and I can't speak for those who do.
Whoever added Visual C++ 2005 to CVS isn't maintaining it, which is rather inconvenient for the people who download it from CVS. I'm starting to wonder if I should remove it from CVS, considering how many people are being misled.
-
Each configuration is dependent upon different coders to keep it maintained. Since I have Visual C++ 6, I maintain the Visual C++ 6 project files. I don't (and can't) maintain the Visual C++ 2005 project files, and I can't speak for those who do.
Whoever added Visual C++ 2005 to CVS isn't maintaining it, which is rather inconvenient for the people who download it from CVS. I'm starting to wonder if I should remove it from CVS, considering how many people are being misled.
Well if that's the case, that's perfectly fine then. The Visual C++ 6 project files seem to compile perfectly and I guess I'll be sticking to that. :)
-
They were all there last I checked...
-
Well they weren't there when I last updated.
-
Each configuration is dependent upon different coders to keep it maintained. Since I have Visual C++ 6, I maintain the Visual C++ 6 project files. I don't (and can't) maintain the Visual C++ 2005 project files, and I can't speak for those who do.
Whoever added Visual C++ 2005 to CVS isn't maintaining it, which is rather inconvenient for the people who download it from CVS. I'm starting to wonder if I should remove it from CVS, considering how many people are being misled.
Even though I haven't actively participated in active development for a long time and only started reading the forums at all again recently, I know that there have been efforts to get the 2005 project files working since they were committed. IIRC phreak fixed them. Kazan addressed a thread to you a week ago because he discovered that one of your changes broke compatibility with MSVC2005, and you actually responded to that thread, so you should know that working project files exist. Backslash also uses MSVC2005, AFAIK.
However, AFAIK, Kazan doesn't have write access and nobody committed the fixes he posted in July. That is, at least in part, your decision. Obviously nobody can maintain the MSVC2005 project files if the people who want to maintain them are restricted from applying the changes, and nobody who can apply the changes does it for them.
OTOH, given that it's been about a month since Kazan posted those fixes, you'd probably want to ask him to see if he'd be willing to post an up-to-date set.
-
Kazan does have write access, as I restored it about a week or so after he began submitting patches. I know he's been committing things, since I've seen the commit logs.
I also know that he's been working on the MSVC 2005 project files, since he's asked me about those both on and off the forums. However, I don't know to what degree his changes in CVS reflect his fixes, nor do I know what percentage of the problems he's fixed.
-
Then I don't understand why the MSVC 2005 project file has been singled out for possible removal. The 2005 project files are for much more modern tools than the VC6 ones, that would be the most readily available for people to buy off of store shelves. The 2003 files seem to have even less reason of being there than the 2005 project files. If upgrading the MSVC6 project files is really so flawless, why have either set?
Although I've seen enough issues from people trying to get MSVC2005 to work that I don't think that pulling the project files and expecting everyone to upgrade the MSVC6 files is going to fix anything. At least if the 2005 files get stabilized, the most people will have to worry about is adding new files to the project, and the occasional #define (which should be rare).
-
It's been singled out because that's what the original poster was asking about. But the same goes for the MSVC 2003 files or any other files that are having similar problems. The point is that anything that's in CVS should be ready to use. There should be no compile errors, no missing files, and no project configuration problems.
Removing the non-working project files will allow people to 1) switch to another project file, such as XCode or GCC, that works; or 2) wait for an experienced coder to fix them a copy. Regardless of whether upgrading the MSVC6 files is easy or not, we shouldn't expect end-users to have to jump through hoops to fix the MSVC 2005 files that should already work. That's not a good use of their time.
-
Hear hear!
-
i forgot to commit some in 3.6.9