It also generated the gcs. When I run it, I get the following error message:
E:/librepilot/next/build/librepilot-gcs_release/lib/librepilot-gcs/plugins/LibrePilot/PfdQml.dll: Cannot load library E:\librepilot\next\build\librepilot-gcs_release\lib\librepilot-gcs\plugins\LibrePilot\PfdQml.dll: The specified procedure could not be found.
3D OSGEarth PFD
I recall that you must either disable this, or you must do a special download or build and tell it to use that.
I recall there is an issue building the 3D OSGEarth PFD. It has to do with versions of the things it depends on which you may have worked around by using @jdl's msys stuff.
This command will show you some options how to handle this. Handling it involves storing your request in a file called "config" (you will use use mingw32-make):
make config_help
I would either disable all OSG stuff as described in config_help or I would use the instructions at:
make/3rdparty/osgearth/README.TXT
to build these libs and to tell the build to make a GCS that uses them.
I recall there is a way to download pre-built libs, but am not familiar with that way.
There is also a way to hack Makefile that has to do with these lines:
GCS_WITH_OSG := 1
GCS_WITH_OSGEARTH := 1
GCS_COPY_OSG := 1
On the Flight data tab, the upper left panel allows setting gadgets - I have never played with this before - there was always a default display there. Now I see that ALL my GCS versions display what is set there! (I have both 16.09 and next set up on my computer).
Running the GCS with the -help option shows you the possible command line options:
$ ./build/librepilot-gcs_release/bin/librepilot-gcs -help
Command line ("./build/librepilot-gcs_release/bin/librepilot-gcs", "-help")
Loading system settings from "/home/cliff/dev/librepilot/1609/build/librepilot-gcs_release/share/librepilot-gcs/"
Loading user settings from "/home/cliff/.config/LibrePilot/LibrePilot GCS.xml"
main - system locale: "en_US"
main - GCS locale: "en_US"
main - language: "en_US"
Usage: librepilot-gcs [OPTION]... [FILE]...
Options:
-help Display this help
-version Display application version
-no-splash Don't display splash screen
-log <file> Log to specified file
-client Attempt to connect to already running instance
-D <key>=<value> Permanently set a user setting, e.g: -D General/OverrideLanguage=de
-reset Reset user settings to factory defaults.
-config-file <file> Specify alternate factory defaults settings file (used with -reset)
-exit-after-config Exit after manipulating configuration settings
-noload <plugin> Do not load <plugin>
How do I get back the default "gadget"?
Use the -reset option to reset the GCS to defaults. If you want to use multiple versions of GCS on the same PC, you will have to supply some glue code to move the settings files around.
Not sure where to mention this - but on the next GCS version I'm using (not my code build), importing UAV files does not seem to load mixer settings. I checked the UAV file - the settings are there. But they never load. 16.09 seems to load ok. Only next. I can export, but not import.
UAV files are version specific in that if the firmware version does not match exactly, then there are things that don't import because the UAVO hash number is different, because the UAVO is different. The bigger the changes from one version to the next, the more things don't import.
The simple way is to just make screen shots of the source version and hand input them in the destination version.
There is another way, but it is technical. The .uav files are human readable text and so you can use diff tools to compare them. If you compare e.g. the erase settings default revo exports for 16.09 and next, you will see the differences. I use two editors at once so I can Alt-Tab from one to the other. When both are on the same page, you can use this "blink test" to make the differences pop out. Then in a 3rd editor, you make the changes that you see when blinking between the two default files. A uav file does not have to have all the lines in it. I often make uav files that have just the calibrations in it. There are a LOT of differences between 16.09 and the last next.