I've been testing the FlightGear interface against FlightGear version 2020.3.6, and it's working well. I was getting compilation errors earlier due to the way Qt is changing its QtEndian handling, so I'm now using my own routines for endian operations.
Tested with Qt 5.15.2
QtJSBSim now assumes it is running on a little endian machine, and it also assumes a float is 4 bytes and a double is 8 bytes. If any of these assumptions don't work for you please let me know and I'll update the code accordingly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been testing the FlightGear interface against FlightGear version 2020.3.6, and it's working well. I was getting compilation errors earlier due to the way Qt is changing its QtEndian handling, so I'm now using my own routines for endian operations.
Tested with Qt 5.15.2
QtJSBSim now assumes it is running on a little endian machine, and it also assumes a float is 4 bytes and a double is 8 bytes. If any of these assumptions don't work for you please let me know and I'll update the code accordingly.
Update: The endianess issue is now fixed, however I can only test it on a Little Endian machine.
QtJSBSim should now be able to communicate to FlightGear from either a Little or Big Endian host.
The only file in the code which needs to worry about this is src/flightgear/packet.cpp
Note that communication between QtJSBSim and JSBSim is done via text, so no need to consider endianess there.