From: Frederic B. <fre...@fr...> - 2010-09-12 08:28:49
|
----- "James Turner" a écrit : > On 11 Sep 2010, at 22:38, Frederic Bouvier wrote: > > > saw that you updated MSVC project files and that's nice of you, but > it happens that for the MSVC100 (2010) files, things are a little bit > more complicated than for MSVC90 (2008). > > > > Basically, you added .hxx files in FlightGear.vcxproj file, with the > clause : > > > > <ClCompile Include="..\..\..\src\Environment\realwx_ctrl.hxx" /> > > > > Doing so, you asked MSVC to compile that header file, which led to > numerous strange compile errors, because that files are not self > complete, and depends on other header files that are not included. > > > > The right clause is : > > I think I made the same error recently - I've got into the habit of > updating the project files, but didn't even look at the structure when > I added some new files in. Thanks for the explanation, Fred. > > If we try to hand-edit the files, and make a mistake, is that a hassle > to fix? I.e, would you rather we *tried* to hand-edit the files, or > just not bothered? The problem is to spot a problem, because now we can compile files that do not appear in the solution tree, and it would be hard to remove or alter them then. When the problem is identified (when you realize you shouldn't bother with the compile errors because that file shouldn't be compiled, and you realize you can't remove it because it is not in the tree ;-), it's just a matter of loading the vcxproj file in vi and fix it. But when there are no errors, the problem stay hidden. Overall, it's less hassle to add the files by hand in the studio, so, don't bother. Do you remember which file you added to the MSVC100 project ? -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery - album photo http://www.youtube.com/user/fgfred64 Videos |