Updated markdown documents.

Reordered 'Readme' paragraphs and rephrased 'Features' section.
Updated 'Authors'
Updated 'Changelog' to match all 0.6 changes

Author: MrPointer

AUTHORS.md

@@ -2,8 +2,11 @@
 
 This files lists all the authors of this project that helped it grow by adding code, fixing bugs, etc.
 
-- Tomasz Bogdal ([queezythegreat - Original author of **Arduino-CMake**)
-- Timor Gruber ([MrPointer](https://github.com/MrPointer) - Author of **Arduino-CMake 3**, Current Maintainer)
+- [Tomasz Bogdal](https://github.com/queezythegreat) - Original author of **Arduino-CMake**
+- [Timor Gruber](https://github.com/MrPointer) - Author of **Arduino-CMake-NG**, Current Maintainer
+- [Tao Yuan](https://github.com/taoyuan)
+- [Mike Machado](https://github.com/machadolab)
+- [ooxi](https://github.com/ooxi)
 
 There are many other authors who have contributed to the various forks and versions, work which couldn't be done without them.
 

CHANGELOG.md

@@ -1,9 +1,56 @@
 # Change Log
 
+## Version 0.6
+
+This is a **BIG** version including numerous bug fixes, changes and even some new features.  
+It mostly addressed *3rd Party Libraries*.
+
+### New Features
+
+* 3rd Party Arduino libraries can now be manually added from any path using the `add_arduino_library` function or automatically found using the `find_arduino_library` function.  
+  To use the *find API*, the `3RD_PARTY` argument option should be passed to the function.
+
+* Header-only Arduino libraries are now supported - They can be manually added using the `add_arduino_header_only_library` function or automatically found using the `find_arduino_library` function.  
+  To use the *find API*, the`HEADER_ONLY` argument option should be pass to the function.
+
+* Full Arduino IDE *Sketchbook* support - Libraries, examples and sketches can be optionally searched there as well.  
+  The framework can also automatically find the *Sketchbook Location*, however, this is disabled by default, what also means that unless set otherwise, the framework ***doesn't search the sketchbook*** - This policy is set due to the unwanted dependency on the Arduino IDE for this feature to fully work.  
+  Further information can be found in the documentation.
+* Many improvements to the CI platforms **AppVeyor** and **Travis CI**, including:
+  * Cached builds - Decreased build time significantly
+  * Improved control-flow and readability
+
+### Bug Fixes
+
+* The `Linux-Dist-Detection` module didn't check whether the required dependencies for the detection are installed.
+* 3rd Party libraries that don't include a **library.properties** file couldn't be used.
+* 3rd Party libraries have been renamed to an "Arduino-Compliant" name when attempting to find them using the `find_arduino_library` function, which renamed them to an invalid name.
+* 3rd Party libraries that have been added using custom CMake logic (Calls to `add_library`) didn't get any of the build flags that every Arduino library has to have.
+* The framework couldn't automatically find the Arduino SDK on OS X images.
+
+### Changes
+
+* The `Find-SDK` module now searches for the **version.txt** file under a sub-directory named **lib**, which resides directly under SDK's root path. This file's path is common across all OSs, unlike the previously searched **arduino** program.
+
+* The `find_arduino_library` function now searches under the following paths:
+
+  * `ARDUINO_SDK_LIBRARIES_PATH` - Usually the **libraries** directory under the SDK's root directory
+  * *Sketchbook Location* - **Arduino IDE**'s *Sketchbook* path, storing all user-downloaded libraries
+  * `CMAKE_CURRENT_SOURCE_DIRECTORY` - The directory in which the executed **CMakeLists.txt** file resides, i.e. Project's source directory
+  * `PROJECT_SOURCE_DIR` - The directory in which the **CMakeLists.txt** file that sets the `project` resides.
+
+  Besides,  the following sub-directories are searched under every path mentioned above:
+
+  - **libraries**
+  - **dependencies**
+
+* 3rd Party Arduino Libraries do not longer have to include the **library.properties** file in their root directory - Their root directory is searched instead.  
+  Nevertheless including the file is still ***recommended***, because when the file isn't present, the framework can't infer potentially required metadata from it.
+
 ## Version 0.5.2
 
-This version adds case-insensitive support for examples, forgotten in the last version.
-Fixes a bug in Core-Lib target creation on Debian/Ubuntu systems, and adds support for **AppVeyor** CI.
+This version adds case-insensitive support for examples, forgotten in the last version.  
+Fixes a bug in Core-Lib target creation on Debian/Ubuntu systems, and adds support for **AppVeyor** CI.  
 
 But most importantly - It changes the way users should supply a custom SDK location.
 
@@ -23,7 +70,7 @@ But most importantly - It changes the way users should supply a custom SDK locat
 
 ## Version 0.5.1
 
-This version fixes some "invisible" bugs from previous versions, along with general design improvements.
+This version fixes some "invisible" bugs from previous versions, along with general design improvements.  
 Moreover, there are even some new minor features.
 
 ### New Features
@@ -48,7 +95,7 @@ This version refactored the Sketch API entirely to enhance support for missing f
 
 - Headers included in a sketch file are now resolved to provide better insight
   - Arduino/Platform libraries that are resolved from a sketch's headers are linked to the target
-- Option/Policy to "forcefully" convert a sketch to a source file when adding it to a target, even if the source file already exists (Usually means that sketch has already been converted). 
+- Option/Policy to "forcefully" convert a sketch to a source file when adding it to a target, even if the source file already exists (Usually means that sketch has already been converted).   
   By default it's set to **OFF**.
 
 ### Changes
@@ -74,15 +121,15 @@ This version mostly added support for examples and sketches.
 
 * Arduino examples such as **Blink** can now be used by calling the `add_arduino_example` function
 * Arduino library examples, each being part of an Arduino library, can also be used by calling the `add_arduino_library_example` function
-* Arduino Sketches can be converted into source files under the project's source directory.
+* Arduino Sketches can be converted into source files under the project's source directory.  
   The API to use them seamlessly as using examples is still missing, however.
-* During platform initialization the main header of the platform gets selected.
-  This is useful for sketch conversion, as sketches usually don't include the header in their source files but depend on the **Arduino IDE** to do so instead.
+* During platform initialization the main header of the platform gets selected.  
+  This is useful for sketch conversion, as sketches usually don't include the header in their source files but depend on the **Arduino IDE** to do so instead.  
   The header is selected based on the number of `#include` lines it has - The header with most includes is selected as platform's main header, as it probably includes many other platform headers.
 
 ### Changes
 
-* The API of the utility function `list_replace` now resembles CMake's List API.
+* The API of the utility function `list_replace` now resembles CMake's List API.  
   It's also a macro now instead of a function.
 * Improved logic and performance of utility `increment` and `decrement` math functions
 
@@ -102,17 +149,17 @@ This version added support for Arduino libraries and platform libraries.
 
 * Arduino libraries can be found by calling `find_arduino_library` and then linked to another target by calling `link_arduino_library`
   * The library search process is architecture-aware, meaning that only sources that match the platform's architecture will be included in the library target
-* Arduino platform libraries can be simply linked to another target by calling `link_platform_library`.
+* Arduino platform libraries can be simply linked to another target by calling `link_platform_library`.  
   There's no special search process for platform libraries as there is for Arduino libraries.
 
 ## Version 0.2
 
-This version added support for the **Core Library** - A static library built from the platform's core sources that must be linked to every single target in the Arduino build system, including libraries in the future.
+This version added support for the **Core Library** - A static library built from the platform's core sources that must be linked to every single target in the Arduino build system, including libraries in the future.  
 This library is also the missing piece for getting correct program sizes, which hasn't been the case up until now.
 
 ### New Features
 
-* The Core Library is added once per board (As a board has a single associated core) and linked against every created target.
+* The Core Library is added once per board (As a board has a single associated core) and linked against every created target.  
   This behavior is internal and not up to the control of the user, much like a Kernel.
 
 ### Changes
@@ -128,13 +175,13 @@ This version added support for displaying a program's size upon build completion
 
 ### New Features
 
-* Program size output for every executable target at the end of each successful build.
-  This is done using Arduino's **avr-size** tool.
+* Program size output for every executable target at the end of each successful build.  
+  This is done using Arduino's **avr-size** tool.  
   The tool's output is then reformatted to match the format of Arduino IDE.
 
 ## Version 0.1
 
-This is the bare metal version of the framework, adding support for the very basic stuff.
+This is the bare metal version of the framework, adding support for the very basic stuff.  
 Although basic, there's a lot that had to be done in order to reach a somewhat "stable" version that can be burned to the board and actually work.
 
 ### Features

README.md

@@ -5,7 +5,53 @@
 **Arduino-CMake** is a framework which allows developers to write Arduino-based programs using any tool that supports cmake. *Arduino-based*? There are many other frameworks out there built upon Arduino's base, such as ESP32, and **we support that**.
 In other words, developers can use their favorite IDEs or text editors on their favorite OS to develop Arduino programs!
 
-Wait - Hasn't it been possible all this time? Apparently not, as you'll find out by reading further.
+Wait - Hasn't it been possible all this time? Apparently not. You can read more about it in the [Motivation](#Motivation) section.
+
+## Features
+
+**Arduino-CMake** should<sup id="fl1">[1](#f1)</sup> do almost<sup id="fl2">[2](#f2)</sup> <u>anything</u> that the **Arduino IDE** does!
+Here's a list of features **already supported** by **Arduino-CMake**:
+
+- Creating Arduino "Executables"/Programs
+- Uploading programs to hardware boards
+- Adding/Finding and using Arduino Libraries
+  - 3rd Party libraries are fully supported
+  - User libraries which are not Arduino Libraries are also supported
+- Using Arduino example programs
+  - Using Arduino library example programs
+- Attaching Arduino sketches (`.ino` files) to programs
+
+Moreover, **Arduino-CMake** allows some things that **Arduino IDE** *doesn't*:
+
+- Developing Arduino programs in any IDE or text editor
+- Completely customizing the build process per user's requirements
+
+It's also worth mentioning that **Arduino-CMake** is **<u>cross platform</u>** and works out-of-the-box on every OS that support **CMake** and **Arduino**.
+
+<b id="f1">1</b> The framework is still a WIP, meaning there are some missing features. [↩](#fl1)
+<b id="f2">2</b> The **Arduino IDE** supports several concepts which make writing code easier but are completely unprofessional. Our framework is not willing to encourage such poor coding standards, and thus doesn't support them. These will be mentioned throughout the documentation. [↩](#fl2)
+
+## Usage
+
+A very basic example of how **Arduino-CMake** can be used is listed below:
+
+```cmake
+# Define CMake's minimum version (must-do) and the project's name and supported languages
+cmake_minimum_required(VERSION 3.8.2)
+project(Hello_World LANGUAGES C CXX ASM)
+
+# Call a framework utility function, passing it information about the hardware board that will be used - This function returns a structure known only to the framework
+get_board_id(board_id nano atmega328)
+
+# Create an executable suitable for Arduino using CMake-style target-creation
+add_arduino_executable(Hello_World ${board_id} helloWorld.cpp)
+# Upload the created target through a connected Serial Port (Where your board is connected to)
+upload_arduino_target(Hello_World "${board_id}" COM3)
+```
+
+You should then call **CMake** (either through *cmd*, *cmake-gui* or an *IDE* if it supports that) passing it the argument `-DCMAKE_TOOLCHAIN_FILE=[project_path]/cmake/Arduino-Toolchain.cmake` where `[project_path]` is substituted by the project's full path. This is what allows cmake to use our framework.
+
+That's it! It's super simple, yet super extensible :)
 
 ## Motivation
 
@@ -43,27 +89,6 @@ NG stands for "New Generation".
 Inferred from the written above, it can easily be understood why the project has this name.
 However, if you don't think this name is good enough or it confuses you - Feel free to propose a name of your own, we're open for offers :)
 
-## Features
-
-**Arduino-CMake** should do <u>anything</u> that the **Arduino IDE** can!
-Why should? Because currently it's still WIP, meaning there are still some missing features.
-Here's a list of features **already supported** by **Arduino-CMake**:
-
-* Creating Arduino "Executables"/Programs
-* Uploading programs to hardware boards
-* Linking/Using Arduino libraries to programs
-  * Linking/Using custom libraries to programs
-* Creating Arduino example programs
-  * Creating Arduino library example programs
-* Attaching Arduino sketches to programs
-
-Moreover, **Arduino-CMake** allows some things that **Arduino IDE** *doesn't*:
-
-- Developing Arduino programs in any IDE or text editor
-- Completely customizing the build process per user's requirements
-
-It also worth mentioning that **Arduino-CMake** is **entirely <u>cross platform</u>**.
-
 ## Requirements
 
 The following list is the basic requirements of the framework in order to use it:
@@ -74,29 +99,6 @@ The following list is the basic requirements of the framework in order to use it
   * 1.8.2 or Higher on **Microsoft Windows**
   * 1.6.10 or Higher on **Linux** and **Apple OS X**
 
-## Usage
-
-A very basic example of how **Arduino-CMake** can be used is listed below:
-
-```cmake
-# Define CMake's minimum version (must-do) and the project's name and supported languages
-cmake_minimum_required(VERSION 3.8)
-project(Hello_World LANGUAGES C CXX ASM)
-
-# Call a framework utility function, passing it information about the hardware board that will
-# be used - This function returns a structure known only to the framework
-get_board_id(board_id nano atmega328)
-
-# Create an executable suitable for the Arduino firmware using CMake-style target-creation
-add_arduino_executable(Hello_World ${board_id} helloWorld.cpp)
-# Upload the created target through a connected Serial Port (Where your board is connected to)
-upload_arduino_target(Hello_World "${board_id}" COM3)
-```
-
-You should then call **CMake** (either through cmd, cmake-gui or an IDE if it supports that) passing it the argument `-DCMAKE_TOOLCHAIN_FILE=[project_path]/cmake/Arduino-Toolchain.cmake` where `[project_path]` is substituted by the project's full path. This is what allows cmake to use our framework.
-
-That's it! It's super simple, yet super extensible :)
-
 ## Installation
 
 A complete installation guide can be found in the [Installation](https://github.com/arduino-cmake/arduino-cmake/wiki/Installation) Wiki page.