Re: [Flightgear-devel] Buildiing/running the ATC network test
John Wojnaroski wrote: - Original Message - From: Jon Stockill [EMAIL PROTECTED] To: FlightGear developers discussions [EMAIL PROTECTED] Sent: Tuesday, October 05, 2004 1:48 PM Subject: Re: [Flightgear-devel] Buildiing/running the ATC network test John Wojnaroski wrote: Build the TNL libraries first which should produce three static libraries (libtnl.a, libencrypt.a and libatcmaster.a) which will be installed in /usr/local/lib/ Built, although I had to build libencrypt.a by running make in its own directory rather than at the top level. Yes, my fault. Just grabbed what was already there... should have mention that in the build notes I'll add that to the build notes and/or redo the makefile to work with configure.in. Thanks. Next build the libraries, the configure.in file conatains a lot of cruft used for plib/SimGear. We might wind up using some of that but for now Boris is working on a simpler version. If plib and Simgear is on your system you can use the *big* version. All there already - I just pointed configure to the correct paths. Next go to the ATC directory /usr/local/src/ATC-0.1 and build and install. Again, depending on your system configurations you can try aclocal automake autoconf ./configure I think I'm a victim of some of that cruft - configure is failing here with: configure: error: conditional ENABLE_XMESA_FX was never defined. Usually this means the macro was only invoked conditionally. Yes, more and likely. ATM there is no need for any sort of opengl library or graphics capability or plib/Simgear. Odds are some of those libraries will be used but you can comment all that stuff out for now. Plus there may be some macros or other things that happen between aclocal_to_make that I (quite honestly) don't fully understand. So things work on my system and may fail on others. When and if this becomes a living, breathing project all those items need to be dealt with and cleaned up OK, I had chance to have a look at configure.in and removed the section causing the problem - I've got the binaries built now, all start up ok, but the master segfaults when a pilot or controller connects: Starting program: /archive/Mirror/flightgear/OpenATC/ATC-0.1/src/Master/master [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 11705)] Socket created - bound to address: IP:Any:29002 UDP receive buffer size set to 32768. UDP send buffer size set to 32768. UDP socket non-blocking IO set. UDP socket initialized. Master Server created - listening on port 29002 Then you start the client: Pilot started - master is at IP:192.168.127.5:29002. Socket created - bound to address: IP:Any:32770 UDP receive buffer size set to 32768. UDP send buffer size set to 32768. UDP socket non-blocking IO set. UDP socket initialized. Connecting to master server at IP:192.168.127.5:29002 Client puzzle solved in 147 ms. And the master falls over: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 11705)] 0x080a3e68 in ?? () (gdb) bt #0 0x080a3e68 in ?? () #1 0x400e0974 in __dynamic_cast (from=0x80a3e68, to=0x807b740 typeinfo for TNL::Object, require_public=134723644, address=0x0, sub=0xbfffefb8, subptr=0x4000a490) at ../../gcc-2.95.3/gcc/cp/tinfo2.cc:282 #2 0x08056613 in TNL::NetConnectionRep::create ( name=0xbfffeb80 MasterServerConnection) at netConnection.cpp:50 #3 0x0805c458 in TNL::NetInterface::handleConnectRequest (this=0x809a520, [EMAIL PROTECTED], stream=0xb030) at netInterface.cpp:762 #4 0x0805b11f in TNL::NetInterface::processPacket (this=0x809a520, [EMAIL PROTECTED], pStream=0xb030) at netInterface.cpp:462 #5 0x0805affb in TNL::NetInterface::checkIncomingPackets (this=0x809a520) at netInterface.cpp:422 #6 0x08049cc6 in main (argc=1, argv=0xb7f4) at main.cpp:667 (gdb) -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
- Original Message - From: Jon Stockill [EMAIL PROTECTED] To: FlightGear developers discussions [EMAIL PROTECTED] Sent: Saturday, October 09, 2004 3:41 AM Subject: Re: [Flightgear-devel] Buildiing/running the ATC network test OK, I had chance to have a look at configure.in and removed the section causing the problem - I've got the binaries built now, all start up ok, but the master segfaults when a pilot or controller connects: Starting program: /archive/Mirror/flightgear/OpenATC/ATC-0.1/src/Master/master [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 11705)] Socket created - bound to address: IP:Any:29002 UDP receive buffer size set to 32768. UDP send buffer size set to 32768. UDP socket non-blocking IO set. UDP socket initialized. Master Server created - listening on port 29002 Then you start the client: Pilot started - master is at IP:192.168.127.5:29002. Socket created - bound to address: IP:Any:32770 UDP receive buffer size set to 32768. UDP send buffer size set to 32768. UDP socket non-blocking IO set. UDP socket initialized. Connecting to master server at IP:192.168.127.5:29002 Client puzzle solved in 147 ms. And the master falls over: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 11705)] 0x080a3e68 in ?? () (gdb) bt #0 0x080a3e68 in ?? () #1 0x400e0974 in __dynamic_cast (from=0x80a3e68, to=0x807b740 typeinfo for TNL::Object, require_public=134723644, address=0x0, sub=0xbfffefb8, subptr=0x4000a490) at ../../gcc-2.95.3/gcc/cp/tinfo2.cc:282 #2 0x08056613 in TNL::NetConnectionRep::create ( name=0xbfffeb80 MasterServerConnection) at netConnection.cpp:50 #3 0x0805c458 in TNL::NetInterface::handleConnectRequest (this=0x809a520, [EMAIL PROTECTED], stream=0xb030) at netInterface.cpp:762 #4 0x0805b11f in TNL::NetInterface::processPacket (this=0x809a520, [EMAIL PROTECTED], pStream=0xb030) at netInterface.cpp:462 #5 0x0805affb in TNL::NetInterface::checkIncomingPackets (this=0x809a520) at netInterface.cpp:422 #6 0x08049cc6 in main (argc=1, argv=0xb7f4) at main.cpp:667 (gdb) Quite honestly, we ( I ) don't fully understand all the internals and detailed workings of the TNL libraries and protocols. Where it fails is clear, why is the question? I have had the master node running and have been able to connect in all four net configs --- internal on the same machine with 127.0.0.1, across a LAN with 192.168.xxx.xxx, across the Internet to 216.86.210.202, or on the same machine using either its LAN or internet IP address. ATM I don't have an answer for you and have been unable to duplicate the problem on my systems. Bummer... Once I get the server set up for the field test later today, I'll get back on this problem and try to find an answer for you. BTW, for those participating in the test later today, you can run multiple instance of the controllers and pilots which will help to increase the traffic load on the master server as nodes connect/disconnect and reconnect. The more, the merrier... Regards John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
John Wojnaroski wrote: BTW, for those participating in the test later today, you can run multiple instance of the controllers and pilots which will help to increase the traffic load on the master server as nodes connect/disconnect and reconnect. The more, the merrier... Well I'm hanging around in the irc channel - seems like that'll be the easiest way to coordinate things. I'll be able to run clients from several machines with various different connections to the rest of the world. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
Boris Koenig wrote: leave it alone, then it's NOT your business, but rather the folks from opentnl.org should take care of such issues ... With such an attitude you might be better off subscribing to fgfs-users and not fgfs-devel. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
Hi But even then it won't compile on Solaris/Sparc: Just upgraded to GCC-3.4.2 and it fumed and fussed trying to build the TNL library on my P4. So it's not all Solaris/Sparc... Don't have time left today to work it further, will have a go at it tommorrow Regards John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
John Wojnaroski wrote: Hi But even then it won't compile on Solaris/Sparc: Just upgraded to GCC-3.4.2 oh well :-) and it fumed and fussed trying to build the TNL library on my P4. So it's not all Solaris/Sparc... leave it alone, then it's NOT your business, but rather the folks from opentnl.org should take care of such issues ... Don't have time left today to work it further, will have a go at it tommorrow let's collect the error messages and file a bug report/feature request. They haven't yet replied to my inquiry about creating new platform-specific networking 'modules' either ... - Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
John Wojnaroski wrote: But even then it won't compile on Solaris/Sparc: Just upgraded to GCC-3.4.2 and it fumed and fussed trying to build the TNL library on my P4. So it's not all Solaris/Sparc... Yep. I already worked around some of the CGG-3.4.2 things and made appropriate OS/CPU settings for Solaris. Although this makes the compiler happy for a while I later ran into trouble when some platform- specific inline assembler code was requested. I don't think it's worth spending your time digging into it as long as there's no clear commitment from the TNL folks to _real_ multi- platform portability. I _assume_ the way to go is to find another network abstraction layer that 'does the work' (TM ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
John Wojnaroski wrote: Note: For now, you will have to install the TNL headers files by hand: the following script should work #!/bin/bash cd /usr/include mkdir tnl cd tnl [...] This could be easily solved by setting srcdir = .. in src/master/Makefile and, what you'll have to do in any case, fix the include statement in the source files, for example src/master/masterInterface.h, to #include tnl/tnlEventConnection.h #include tnl/tnlRPC.h But even then it won't compile on Solaris/Sparc: Making all in src make[1]: Entering directory `/usr/local/src/TNL-1.4/src' Making all in master make[2]: Entering directory `/usr/local/src/TNL-1.4/src/master' source='masterInterface.cpp' object='masterInterface.o' libtool=no \ depfile='.deps/masterInterface.Po' tmpdepfile='.deps/masterInterface.TPo' \ depmode=gcc /bin/sh ../../depcomp \ c++ -DPACKAGE=\TNL\ -DVERSION=\1.4\ -DHAVE_DAYLIGHT=1 -DHAVE_TIMEZONE=1 -DHAVE_LIBM=1 -DHAVE_LIBPTHREAD=1 -DHAVE_LIBX11=1 [...] -I. -I/opt/gnu/include -I/usr/local/include -I/opt/FlightGear/include -O3 -c -o masterInterface.o `test -f masterInterface.cpp || echo './'`masterInterface.cpp In file included from /usr/local/include/tnl/tnlNetBase.h:33, from /usr/local/include/tnl/tnlNetConnection.h:31, from /usr/local/include/tnl/tnlEventConnection.h:31, from masterInterface.h:30, from masterInterface.cpp:28: /usr/local/include/tnl/tnlTypes.h:271:4: #error TNL: Unsupported Operating System /usr/local/include/tnl/tnlTypes.h:307:4: #error TNL: Unsupported Target CPU [...] I wonder how they can claim cross-platform portability BTW, what is the relation between the files you placed on OpenATC and the OpenTNL project ? From there I could download only a '1.4.0rc4' source code package, the version on OpenATC carries the version 1.4 and the OpenTNL website claims they already reached version 1.4.3. All this doesn't fit together, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
Martin Spott wrote: John Wojnaroski wrote: Note: For now, you will have to install the TNL headers files by hand: the following script should work #!/bin/bash cd /usr/include mkdir tnl cd tnl [...] This could be easily solved by setting srcdir = .. in src/master/Makefile yes, even though a simple cp -R tnl /usr/include would have been okay, too ... But I think, we'll add a simple install target to that makefile and take of all that care within the makefile. and, what you'll have to do in any case, fix the include statement in the source files, for example src/master/masterInterface.h, to #include tnl/tnlEventConnection.h #include tnl/tnlRPC.h yes, right - I did change exactly that yesterday ... there are some other smaller changes, we'll upload a fixed set of files by tomorrow. But even then it won't compile on Solaris/Sparc: I wonder how they can claim cross-platform portability okay, that's indeed a bit weird ... BTW, what is the relation between the files you placed on OpenATC and the OpenTNL project ? From there I could download only a '1.4.0rc4' source code package, the version on OpenATC carries the version 1.4 and the OpenTNL website claims they already reached version 1.4.3. All this doesn't fit together, The openTNL headers/library sources on openatc.sf.net/test are merely a downstripped/reduced version of the actual sources, simply because John figured we wouldn't need most of the stuff ... -- Bori ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
Boris Koenig wrote: yes, right - I did change exactly that yesterday ... there are some other smaller changes, we'll upload a fixed set of files by tomorrow. Would you mind trying to compile with a recent version of GCC before you post new files ? I'm using 3.4.2 on Solaris and I have the impression that that one is pretty picky. If you tell me it 'survives' compiling with 3.4.2 on Linux it simplifies determining which changes are specifically necessary for Solaris, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
Martin Spott wrote: Boris Koenig wrote: yes, right - I did change exactly that yesterday ... there are some other smaller changes, we'll upload a fixed set of files by tomorrow. Would you mind trying to compile with a recent version of GCC before you post new files ? I'm using 3.4.2 on Solaris and I have the impression that that one is pretty picky. If you tell me it 'survives' compiling with 3.4.2 on Linux it simplifies determining which changes are specifically necessary for Solaris, Hmm, the latest version that I have access to locally is: gcc (GCC) 3.3 - and actually, I wasn't going to recompile GCC ;-) I am not sure where exactly the TNL (lib) is incompatible with Solaris, but I guess that can only be fixed directly within the lib itself ... So, maybe you can resolve some issues by directly trying to build the STANDARD package from opentnl.org - possibly, there's even some info available specific to Solaris. The sources itself should actually not be too non-standard, John simply used the shipped opentnl examples to put a basic test framework together, so there's not even that much 'new' code ... Actually, pretty much all of it is simply derived from those examples. Let's see if the official version builds on Solaris or where exactly it fails. -- Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
Boris Koenig wrote: So, maybe you can resolve some issues by directly trying to build the STANDARD package from opentnl.org - possibly, there's even some info available specific to Solaris. Huh ? I think: Features Multiple platform support * Windows 98, ME, NT, XP * Linux on x86 * Mac OS X says it all I'll try anyway but it might take some time (which I usually don't have available ). I think people usually say don't hold your breath :-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
Martin Spott wrote: Boris Koenig wrote: So, maybe you can resolve some issues by directly trying to build the STANDARD package from opentnl.org - possibly, there's even some info available specific to Solaris. Huh ? I think: Features Multiple platform support * Windows 98, ME, NT, XP * Linux on x86 * Mac OS X says it all lol, Martin - I've got good news for you: quote The Torque Network Library runs on the Microsoft Windows, Mac OS X and Linux platforms. *A Microsoft XBox version is available seperately from GarageGames.com* and future support is planned for Sony's Playstation 2 platform. /quote Which essentially means: get an X-Box or Playstation 2 - instead of a solaris machine :-) Anyway, the following sounds rather encouraging: quote TNL compiles under either either Microsoft Visual C++ 6.0 or Microsoft Visual C++ .NET 2003 on Windows, XCode on Mac OS X and with makefiles and GCC on Linux. In addition, TNL is designed to be easily portable, with all platform specific code contained in a single module. /quote So far it seems to be somewhat X86 specific, which would explain why opentnl doesn't like to run on Solaris :-) I'll try anyway but it might take some time (which I usually don't have available ). I think people usually say don't hold your breath :-) I think they're running a mailing list, too - I might send them a short questions as to whether it's possible to make the opentnl run on Solaris EASILY, or not ... http://sourceforge.net/projects/opentnl -- Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
BTW, what is the relation between the files you placed on OpenATC and the OpenTNL project ? From there I could download only a '1.4.0rc4' source code package, the version on OpenATC carries the version 1.4 and the OpenTNL website claims they already reached version 1.4.3. All this doesn't fit together, The openTNL headers/library sources on openatc.sf.net/test are merely a downstripped/reduced version of the actual sources, simply because John figured we wouldn't need most of the stuff ... There was an update to OpenTNL at the end of September. The version currently used by ATC-0.1 is the 1.4.0 version prior to that update. The latest tagged revision, identified as HEAD, is the 1.4.3 version and it appears there are some binary files of the demo game zap tagged as 1.4.3. Regards John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
Boris Koenig wrote: I am not sure where exactly the TNL (lib) is incompatible with Solaris, but I guess that can only be fixed directly within the lib itself ... For GCC-3.4.2 I got this one: make[1]: Entering directory `/usr/local/src/tnl/tnl' g++ -g -DTNL_DEBUG -DTNL_ENABLE_LOGGING -I../libtomcrypt -c assert.cpp In file included from tnlUDP.h:35, from tnl.h:51, from assert.cpp:27: tnlVector.h: In member function `T TNL::VectorT::front()': tnlVector.h:301: error: there are no arguments to `begin' that depend on a template parameter, so a declaration of `begin' must be available tnlVector.h:301: error: (if you use `-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated) tnlVector.h: In member function `const T TNL::VectorT::front() const': tnlVector.h:306: error: there are no arguments to `begin' that depend on a template parameter, so a declaration of `begin' must be available tnlVector.h: In member function `T TNL::VectorT::back()': tnlVector.h:311: error: there are no arguments to `end' that depend on a template parameter, so a declaration of `end' must be available tnlVector.h: In member function `const T TNL::VectorT::back() const': tnlVector.h:316: error: there are no arguments to `end' that depend on a template parameter, so a declaration of `end' must be available make[1]: *** [assert.o] Error 1 make[1]: Leaving directory `/usr/local/src/tnl/tnl' make: *** [default] Error 2 After dealing with that I got to this point: make[1]: Entering directory `/usr/local/src/tnl/tnl' g++ -g -DTNL_DEBUG -DTNL_ENABLE_LOGGING -fpermissive -I../libtomcrypt -c eventConnection.cpp In file included from tnlUDP.h:35, from tnl.h:51, from eventConnection.cpp:27: [...] In file included from tnlRPC.h:35, from tnlNetObject.h:39, from tnlNetInterface.h:41, from eventConnection.cpp:31: tnlMethodDispatch.h:194:2: #error Compiling RPC code without inline assembler support! You will need to implement RPCEvent::process() and co for your platform. In file included from tnlNetObject.h:39, from tnlNetInterface.h:41, from eventConnection.cpp:31: tnlRPC.h: At global scope: tnlRPC.h:167: error: expected `0' before tnlRPC.h:167: error: invalid initializer for virtual method `virtual bool TNL::RPCEvent::checkClassType(TNL::Object*)' tnlRPC.h:167: error: expected `;' before make[1]: *** [eventConnection.o] Error 1 make[1]: Leaving directory `/usr/local/src/tnl/tnl' make: *** [default] Error 2 Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
Boris Koenig wrote: So far it seems to be somewhat X86 specific, which would explain why opentnl doesn't like to run on Solaris :-) That would seem to indicate that nobody's bothered to make use of things like hton functions, which in turn indicates that they weren't being particularly platform neutral in the design, and that we can expect some horrible bodges in the platform specific code contained in a single module for any other platform. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
Boris Koenig wrote: Which essentially means: get an X-Box or Playstation 2 - instead of a solaris machine :-) Well, I'll ask our institute if they'd like to run their primary fileserver, EMail relay and the university's FTP-Server on a Playstation :-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Buildiing/running the ATC network test
Hi, For those who expressed an interest in participating in the network test this weekend: After downloading the two tiles from SF, untar them in /usr/local/src/ and that will create two directories as ATC-0.1 and TNL-1.4. Note: For now, you will have to install the TNL headers files by hand: the following script should work #!/bin/bash cd /usr/include mkdir tnl cd tnl mkdir encrypt mkdir master cd /usr/local/src/TNL-0.1/src/encrypt cp *.h /usr/include/tnl/encrypt/ cd ../master cp *.h /usr/include/tnl/master cd ../tnl cp *.h /usr/include/tnl/ ## end of script Build the TNL libraries first which should produce three static libraries (libtnl.a, libencrypt.a and libatcmaster.a) which will be installed in /usr/local/lib/ Next build the libraries, the configure.in file conatains a lot of cruft used for plib/SimGear. We might wind up using some of that but for now Boris is working on a simpler version. If plib and Simgear is on your system you can use the *big* version. Next go to the ATC directory /usr/local/src/ATC-0.1 and build and install. Again, depending on your system configurations you can try aclocal automake autoconf ./configure make make install This will produce three binary applications ( master, controller, node ) located in /usr/local/bin. To run as a master simply type master at the commad prompt after checking that there is a small master.cfg file located in the same directory as the binary. To run as a controller or pilot you can enter the following commad controller IP_ADDRESS_MASTER:PORT or pilot IP_ADDRESS_MASTER:PORT The address(s) fo the master nodes will be posted on the OpenATC site http://openatc.sourceforge.net/test/ Again, don't expect anything dramatic or earth-moving, but hope you can join use ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
John Wojnaroski wrote: Build the TNL libraries first which should produce three static libraries (libtnl.a, libencrypt.a and libatcmaster.a) which will be installed in /usr/local/lib/ Built, although I had to build libencrypt.a by running make in its own directory rather than at the top level. Next build the libraries, the configure.in file conatains a lot of cruft used for plib/SimGear. We might wind up using some of that but for now Boris is working on a simpler version. If plib and Simgear is on your system you can use the *big* version. All there already - I just pointed configure to the correct paths. Next go to the ATC directory /usr/local/src/ATC-0.1 and build and install. Again, depending on your system configurations you can try aclocal automake autoconf ./configure I think I'm a victim of some of that cruft - configure is failing here with: configure: error: conditional ENABLE_XMESA_FX was never defined. Usually this means the macro was only invoked conditionally. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
- Original Message - From: Jon Stockill [EMAIL PROTECTED] To: FlightGear developers discussions [EMAIL PROTECTED] Sent: Tuesday, October 05, 2004 1:48 PM Subject: Re: [Flightgear-devel] Buildiing/running the ATC network test John Wojnaroski wrote: Build the TNL libraries first which should produce three static libraries (libtnl.a, libencrypt.a and libatcmaster.a) which will be installed in /usr/local/lib/ Built, although I had to build libencrypt.a by running make in its own directory rather than at the top level. Yes, my fault. Just grabbed what was already there... should have mention that in the build notes I'll add that to the build notes and/or redo the makefile to work with configure.in. Thanks. Next build the libraries, the configure.in file conatains a lot of cruft used for plib/SimGear. We might wind up using some of that but for now Boris is working on a simpler version. If plib and Simgear is on your system you can use the *big* version. All there already - I just pointed configure to the correct paths. Next go to the ATC directory /usr/local/src/ATC-0.1 and build and install. Again, depending on your system configurations you can try aclocal automake autoconf ./configure I think I'm a victim of some of that cruft - configure is failing here with: configure: error: conditional ENABLE_XMESA_FX was never defined. Usually this means the macro was only invoked conditionally. Yes, more and likely. ATM there is no need for any sort of opengl library or graphics capability or plib/Simgear. Odds are some of those libraries will be used but you can comment all that stuff out for now. Plus there may be some macros or other things that happen between aclocal_to_make that I (quite honestly) don't fully understand. So things work on my system and may fail on others. When and if this becomes a living, breathing project all those items need to be dealt with and cleaned up Regards John W. P.S. Hope to have an update or two before the field test. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
