Getting Started Guide for Ubuntu 16.04

[isarota]

I've tried to build QGC on my Ubuntu based computer and I faced lots of guidance problems. Then I decided to prepare a stable guide that any developer can easily build QGC on an Ubuntu based computer.

[hamishwillee]

Thanks @isaimadoglu - appreciated.

I'll leave it to @DonLakeFlyer to decide on what he wants to do. I just have a few points:

1. I've run the official instructions lots of times and they work fine. That said, I wrote them, so not surprising I can follow them.
2. Having duplicate docs is a maintenance burden. Not opposed to splitting out instructions for different OS, but should be agreed that is the plan for all OS. i.e. one set of docs for installation, not multiples.
3. If we aren't splitting out, would be good to understand what the pain points of current instructions are.

[isarota]

Thank you @hamishwillee for your response, I can say that the document which is current is good and it works. As I am a starter of QGC, everything is blurry for me and I need a clear document with sorted instructions so as to I can be sure that I am on the right way.

I just want to point out some problems here:

• I saw a suggestion that we should use Ubuntu 16.04 or higher version somewhere, but I couldn't see that in the guide page. I could build QGC on the Ubuntu systems other than Ubuntu 16.04, but when it comes to run Gstreamer 1.0 on Ubuntu 14.04 and Ubuntu 18.04 I got errors.
• I tried to build QGC on Ubuntu for Android, I got an error about GCC compiler of Android NDK, because Android NDK 19 doesn't use GCC, instead it uses CLANG.
• I tried to build QGC on Windows 10 in reference to the guide page, but I couldn't build it.

So, in any case QGC is dependent on some specific versions of programs, it makes things harder int the starting point. I think that we can make guidance simpler.

[DonLakeFlyer]

If there is something missing from the existing docs then they should just be updated. I don't see a need for another completely separate set of instructions.

[isarota]

Okay, if it's proper to do like that for the presentation of guide, I'm closing this Pull Request. @hamishwillee and @DonLakeFlyer thank you for your quick responses.

[hamishwillee]

Hi @isaimadoglu

In summary, we're consciously sacrificing ease-of-use for an approach we know can be maintained and kept up to date more easily.

If we had more time and fewer updates we'd probably have gone with something what you did. Thanks again for your contribution!