gen: Added error handling in case of wrong encodings inside the header file.

This commit adds some debug output why the parsing of an file raised an
error.
generate an error if one tries to deploy an abstract task
Disambiguate orogen generated ros package name from 'native' ros generated
packages

Previously, base/orogen/std would generated a std_msgs package which conflicts
will the existing ros package. Current scheme will now generate a package named
orogen_std_msgs.
Disambiguate orogen generated ros package name from 'native' ros generated
packages

Previously, base/orogen/std would generated a std_msgs package which conflicts
will the existing ros package. Current scheme will now generate a package named
orogen_std_msgs.
in smart pointer support, throw if toIntermediate is called on an unset smart pointer
fix generation in deployments
fix generation of deployments that specify static connections
Merge remote-tracking branch 'autobuild/stable' into next
Merge remote-tracking branch 'autobuild/next'

Conflicts:
	lib/orogen/templates/main.cpp
	lib/orogen/templates/typekit/ros/Convertions.hpp
bin: enable extensions before the file gets evaluated

The extension might add API calls to the Spec objects, and thus are required for
the file to be loaded successfully
re-enable default extensions at the end of installed oroGen files

The .orogen files that get installed have the default extensions disabled (so
that we apply only the extensions that were selected at the time of generation).
However, they were not re-enabled afterwards, which breaks code generation
scenarios
Merge commit 'refs/merge-requests/3' of git://gitorious.org/orocos-toolchain/rock-orogen
ignore std::vector<bool> (closes #187)
replace some direct calls to STDERR.puts by proper logger-based output
gen: remove unused variable
gen: complete test case for Generation::Typekit#filter_unsupported_types
main: initialize two internal RTT thread with the proper scheduler
Update Manifest.txt
Modified handling of dynamic-properties:

The old behaviour was that a dynamic property get called every time.
Now when the (renamed) __orogen_set<name> function get's called it checks
wether the task is already configured or not. If the task is not configured
then only the property get's updated. If the task was already configures
the set<name> function get's called. Therefore the user has to make sure
all properties (even the dynamic) one get's applied within the configureHook
Adapt to servicediscovery updates