Hi,
Going through a Cygwin FG build, notice that
SimGear configure.in checks for the plib files, but plib is not required
to
build SimGear just FlightGear. Should that test be
removed from SimGear or is this just a early heads up? Of course
simgear could be used for other sims not using
John Wojnaroski writes:
Hi,
Going through a Cygwin FG build, notice that SimGear configure.in
checks for the plib files, but plib is not required to
build SimGear just FlightGear. Should that test be removed from
SimGear or is this just a early heads up? Of course
simgear could be used
Mac OS X developers, Curt, (et. al.):
I've built the current CVS repository of SimGear FlightGear on
Mac OS X (v10.1.2). The file fgdev.tar.gz is README.MacOSX which
contains the particulars about how to compile (this file should be added
to docs-mini). There are still a few
cygwin should come with all the opengl libs and headers you need to
build plib right out of the box. Perhaps there is an opengl cygwin
package you need to install?
Otherwise, check the contents of the config.log ... sometimes
configure failures aren't quite what they seem. Failing that, you
Actually if you grep through the simgear source for plib includes you
will find several, so simgear does indeed depend on plib in order to
build.
Ooops, that's weird, I turned off the plib directory and SimGear still
built. I think I best check my make files and
include paths and
John Check writes:
Kind of OT: On the matter of blender I was going to take a
shot at painting the DC3 model (which was AFAIK done in blender and
exported as VRML). Something gets lost in the translation, parts
are rotated, sized wrong, etc. Anyway blender does work as a
modeling
The command-line time options appear to be broken in the latest CVS
(Cygwin/Win2k). When I specify --start-date-gmt, --start-date-lat,
or --time-offset, the time is still set to the current GMT.
They worked in
FGFS 0.7.8 and I'm not sure exactly where along the line they stopped
Hi,
Running FG under cygwin allows the socket output to
be set to the broadcast address, 192.xxx.xxx.255. But under linux Fg returns an
error
that make_client_socket failed for the broadcast
address. Looks like cygwin is faking it.
there are socket options with the system call
of 'int
Here's my list of things that have been changed, fixed, or added for
0.7.9. It's rather long, but if anyone sees any major ommissions or
errors in this list, please let me know. Thanks.
New for 0.7.9:
* MSVC fixes.
* IRIX fixes.
* FreeBSD fixes.
* Mac OS X fixes.
* Better cygwin and mingwin
All I did was remove the following from config.h-msvc6 and everything
still built (main.cxx also includes version.h). I noticed the CVS
comment for the creation of version.h was to move the flightgear version
into its own file.
deleted symbols:
/* Define to package version - use in main.cxx
On Mon, Feb 11, 2002 at 04:45:16PM -0600, Curtis L. Olson wrote:
Wow ... when it broke, it broke ... interesting test. I wonder if the
'rate' of flex is important, not just the amount of flex? They were
bending the wing pretty slowly ...
They would run the test slowly for a number of
Running FG under cygwin allows the socket output to be set to the broadcast address,
192.xxx.xxx.255. But under linux Fg returns an error
that make_client_socket failed for the broadcast address. Looks like cygwin is
faking it.
Not necessarily. Did you declare that to be the broadcast
Running FG under cygwin allows the socket output to be set to the
broadcast address, 192.xxx.xxx.255. But under linux Fg returns an error
that make_client_socket failed for the broadcast address. Looks like
cygwin is faking it.
Not necessarily. Did you declare that to be the broadcast
Jon S. Berndt wrote:
Also, flex wings are surprisingly robust, even slow beginner
nice-weather-only gliders are specified to +6 gs.
IIRC the Vari-EZ composite is spec'ed at +12 -6 and Ruttan refuses to divulge
the actual limits. (Not that you're going to be awake after pulling +12
14 matches
Mail list logo
