Fix build system to find libraries on OSX and Linux (still not perfect)
Define different toolchain subdirs for Mac, Windows and Linux
workaround fix for library problems with build rootfs

Conflicts:

	CMakeLists.txt
Fix Eclipse CMake generator name (use Unix Makefiles on Linux/OSX)
cmake: generate Eclipse projects by default (make/nmake still work)
Fix .gitignore to ignore symlinked downloads/tools/build directories
Merge remote-tracking branch 'origin/vrubel/gcs' into os/wip

Conflicts:
	CMakeLists.txt
	configure.sh
	targets/beaglebone/CMakeLists.txt
Remove unused 'gcs' library
Add threads to the link (didn't link on Windows without it)
Link with few extra libraries (dl, rt) required for Mac toolchain
fix detect path to binary
remove base class CModuleMetainfo
CModule: disable period value is -1
Shut up the compiler. Maybe some structure could be used here for options?
Merge remote-tracking branch 'origin/voha/fwsdk' into os/wip
cmake: install module configurations (*.def.js) with 'make install'
Normalize line endings
add simple matrix 4f
Merge commit 'vrubel/gcs-bootstrap' into voha/fwsdk
Add project directory find module to keep tools globally accessible

It is possible to set LINUXDRONE_TOOLS_DIR environment variable to override
local tools directory. So the same toolchains can be used for all working
copies. Particularly useful for CI server build agents, but also for local
installations. If no such variable defined, cmake will use directory
${PROJECT_SOURCE_DIR}/tools/ under the source tree.

Similarly, LINUXDRONE_DOWNLOADS_DIR can be defined instead of default
${PROJECT_SOURCE_DIR}/downloads/ directory to download tools distribution
tarballs or binary archives to install them into TOOLS_DIR.

Finally, LINUXDRONE_ROOTFS_DIR can be defined as an alternative to default
${TOOLS_DIR}/rootfs/ which must contain (parts of) the target board root
filesystem with headers and libraries used for cross compilation.