Olaf Flebbe wrote :
> Hi,
>
> sorry for the delay
>
> I second that config.h-msvc6.in (having cygwin to compile MSVC) is plain
> silly.
>
> You may have noticed that the Version in CVS has a config.h-msvc8
> without the @VERSION@ madness.
>
Call it silly or madness if you want. In the mean
Hi,
sorry for the delay
I second that config.h-msvc6.in (having cygwin to compile MSVC) is plain silly.
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: Micr
As you know, the file NEEDED to compile FG is config.h.
Several years back this was COPIED from config.h-msvc6,
like what is done in many other open projects ...
this is common ... people get used to this ...
Of course, they can be very puzzled why, unless they are
also quite familiar with the *
Please delete the dsw/dsp files for four reasons:* They don't work as is.* The dsw files are for VC6. Visual C 6 does not compile FlightGear (any more). * They don't even work for newer Visual Studios (Dependencies are broken: Microsofts Fault, not our's)
* IMHO No developer uses them.I would vote
Geoff Air a écrit :
>
> Just a small point, but it could bother
> some new people ... when you load MSVC7.1
> using the FlightGear.dsw (and dsp), you
> can be blocked from a compile by a
> custom step, which presently fails ...
>
> The am2dsp.cfg file contains a custom -
> # Rule to create config.h
Just a small point, but it could bother
some new people ... when you load MSVC7.1
using the FlightGear.dsw (and dsp), you
can be blocked from a compile by a
custom step, which presently fails ...
The am2dsp.cfg file contains a custom -
# Rule to create config.h
which gets included when am2dsp.pl
Curtis L. Olson wrote :
> Currently whenever I run "make dist" to roll up a new tarball release
> of FlightGear or SimGear the am2dsp.pl and new dsp/dsw files are
> generated. Now that we have a couple active MSVC developers who track
> the cvs changes and maintain their own version of these files
Currently whenever I run "make dist" to roll up a new tarball release of
FlightGear or SimGear the am2dsp.pl and new dsp/dsw files are
generated. Now that we have a couple active MSVC developers who track
the cvs changes and maintain their own version of these files, does it
make sense to keep
8 matches
Mail list logo