Christian Mayer wrote:
Off course. As I wrote in my mail it's no problem to add additional
include/library directories. But I don't see a reason to add
K:\Projekte\SimGear\simgear\zlib or ..\SimGear\simgear\zlib to the
include directory. The include directory should have only intuitive
Christian Mayer writes:
PS: So there's just the #include zlib.h issue left to be
fully MSVC friendly...
Typically in the unix world, you would install packages like zlib into
a place where the compiler expects to see them, or some other place
and inform the compiler where to look.
In the
Curtis L. Olson writes:
Christian Mayer writes:
PS: So there's just the #include zlib.h issue left to be
fully MSVC friendly...
Typically in the unix world, you would install packages like zlib into
a place where the compiler expects to see them, or some other place
and inform the
Curtis L. Olson wrote:
Christian Mayer writes:
PS: So there's just the #include zlib.h issue left to be
fully MSVC friendly...
Typically in the unix world, you would install packages like zlib into
a place where the compiler expects to see them, or some other place
and inform the
I committed a fix to the FGInitialCondition problem this morning.
If the MSVC folks could give it a shot without your fixes (either
from JSBSim CVS or wait for FG CVS to be updated) I'd really appreciate
it.
The problem did exist on linux, as well, but somehow never surfaced.
It was only after
