cc269730a5
ExternalNet interface: - allows a much more closely coupled execution. A remote network FDM will run at it's own rate, and maybe a particular data packets will come, maybe it won't. This makes it very hard to control timing and keep the animation smooth. There are also cpu scheduling issues with running multiple processes on a single machine. The linux scheduler by default runs at 100hz. If an FDM process uses a sleep/alarm system to avoid wasting CPU, it will be forced to run at 100hz, 50hz, 25hz, 20hz, etc. This makes it *impossible* to serve a display system running at 60hz without dropping frames. - the downside is that the FDM process must now run on the same machine as the master flightgear process.
11 lines
262 B
Makefile
11 lines
262 B
Makefile
noinst_LIBRARIES = libExternalPipe.a
|
|
|
|
# noinst_PROGRAMS = demo_fdm
|
|
|
|
libExternalPipe_a_SOURCES = \
|
|
ExternalPipe.cxx ExternalPipe.hxx
|
|
|
|
# demo_fdm_SOURCES = demo_fdm.cxx demo_httpd.cxx demo_httpd.hxx
|
|
# demo_LDADD =
|
|
|
|
INCLUDES = -I$(top_srcdir) -I$(top_srcdir)/src
|