sorry for the delay....
I second that config.h-msvc6.in (having cygwin to compile MSVC) is plain si=
You may have noticed that the Version in CVS has a config.h-msvc8
without the @VERSION@ madness.
> >* They don't even work for newer Visual Studios
> >(Dependencies are broken: Microsofts Fault, not
> Not sure how this is related to removing the
> DSW/DSP file, or what is exactly refered to here.
> If it is refer to the fact that MSVC7.1, and perhaps 8,
> no longer seem to keep as good a automatic track of
> dependencies as good old MSVC6, then, as a
> 'developer' you get used to using 'remake all' ;=3D))
> actually, I more frequently use the 'batch mode' ...
> But why is this any reason for removing this set of
> DSW/DSP files, automatically generated?
The point is: If you generate Project files from scratch, dependencies
work. But somehow dependencies do not work when importing the *dsp/dsw
from FlightGear. On the other side: SimGear does work. I tried to fix
this behaviour but didn't succeeeded. It is a lot easier to support
new files than the automagic conversion process using undocumented
file formats which work, sometimes.
> These DSW/DSP files can be automatically generated
> by am2dsp.pl, enhanced fractionally a few months
> ago by Fred, using am2dsp.cfg, thus can be the
I suggested one of the fixes applied, but realised later that the
files are broken more severely, and gave up.
... do not know about MSVC8, since
> I have yet to BUY, and use this extensively ... I
There is almost no difference between the express and the professional
version. (It has MFC, ATL and masm included, and offline help)
> I too have MSVC7.1 *AND* MSVC6 build file on my
> site - http://www.geoffmclane.com/fg/ - this is
> purely a factor of how frequently you 'update'
> your site ... or the cvs, if put in cvs.
I would be happy to get something more useable into FlightGear. I am
only insisting to get something usable into FlightGear.
> So what am I suggesting? Simply, that a
> config.h-msvc file be returned to cvs, so
> the current custom step in am2dsp.cfg works!
> And that, that file NOT contain an automake
> macro - @VERSION@ ...
> Should we abandon MSVC6? That is up to the
> community ... we have already, in a way, in
> that some of the code syntax no longer can
> not be compiled with MSVC6 ... but I, and
> perhaps others, ARE willing to help people
> with this ... IT IS POSSIBLE ...
Yes, it is possible, but IMHO it does not make sense.
> Recently, with the addition of mk_viii.cxx,
> which was the first file to include "version.h",
> adds to this complexity. This file is generated
> by 'automake', using "version.h.in", which ALSO
> includes an automake macro @VERSION@ ...
IMHO The version.h file is plain silly. Please remove from CVS and
include the info back into the config.h.
> Simply, to move on - yes!
> * Abandon the very good, efficient, 'autogen'
> of DSW/DSP files - no!
Efficient? The converted vcproj file is over 300kb large. The hand
crafted is 8 kb. VC8 is dead slow using the converted one.