anchor.diff:  
   ===== 2.3. QtCreator
   
  -To make things easier for everyone, I provide here a complete set of screenshots. +
  -=> use them to setup your QtCreator.
  +_To make things easier for everyone, I provide here a complete set of screenshots. +
  +=> use them to setup your QtCreator._
   
   . First, make sure QtCreator knows the paths to your android sdk & ndk (cf. Tools > Android).
   
  
positive.code: 
  ===== 2.1. Sysroot
  
  
  For ease of use, we provide the script https://raw.githubusercontent.com/fw4spl-org/android-cmake/master/pull_sysroot.py.
  It does the whole sysroot pulling in one command, and goes something like :
  
  [source,bash]
  pull_sysroot.py Nexus C:/Tmp
  
  :: _Of course you specify the name you want, and the path you want... just remember that you will you them later (cf. 2.3 and 3.)_
  
  
  That's it !
  
  Not only will it *"adb pull"* the most important files /system/bin/*app_process* and /system/bin/*linker*, but also the libraries in */system/lib/* and */vendor/lib/*.
  
  For your information  :
  
  [horizontal]
  * *app_process* : _entry point for the debugger, since it is responsible for starting any Activity on Android_
  
negative.code: That's what we have done, and that's pretty neat !
  
  
  [start = 2]
  . Then get a copy of the script https://raw.githubusercontent.com/fw4spl-org/android-cmake/master/start_gdbserver.py, and modify its vars *ANDROID_APK_PACKAGE* and *ACTIVITY_NAME* to match your app. 
  
  TIP: This script will be in charge of launching the app to debug on the device, and attaching the *gdbserver* packaged with it to this app, leaving it waiting for a connection from gdb (on the port 5039).
  
  