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: 
  NOTE: It's all based on Windows & QtCreator 3.4, but this will work for Linux & OSX as well.
  
  NOTE: We are assuming that you can build and delpoy a native app already _(if not, you can read our previous article on link:https://fw4spl-org.github.io/fw4spl-blog/2015/04/13/Fw4spl-and-Android.html[FW4SPL and Android])_.
  
  
  This article is a bit long, but it's mostly setup & explanations.
  
negative.code: 
  ===== 2.1. Sysroot
  
  . To get a copy of the sysroot of your device, first make sure you plugged it to your computer, and that it's recognized when you launch the command :
  
  [source,bash]
  adb devices
  
  [start = 2]
  . Then, 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 MyNexus C:/Tmp
  
  NOTE: Of course you specify the name you want, and the path you want... just remember that you will use them later (cf. 2.3 and 3.)
  
  
  As a result, you will have the sysroot of your device copied to "C:/Tmp/MyNexus/"
  
  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/*.
  
  Now, for your information  :
  
  [horizontal]
  * *app_process* : _entry point for the debugger, since it is responsible for starting any Activity on Android_
  