Yaml parsing & Static linkage

[durovsky]

• Yaml adopted to 14.04 API
• Static linkage of dk16xx library to resolve third party dependency problems
• updated .travis.yml

[shaun-edwards]

The "new" or "preferred" way of utilizing travis is to have travis clone the industrial_ci repo, instead of including it as a submodule. This ensures that the latest version of industrial_ci is always used. The sub-module approach still works though.

[shaun-edwards]

An example of the new travis ci usage can be found here: https://github.com/ros-industrial/industrial_core/blob/indigo-devel/.travis.yml

[durovsky]

Oh I didn't know that, I will try second approach next time

[shaun-edwards]

Is there a reason you chose to include the Siemens header files in our repo? Are we certain the license allows this? If it does, I would prefer we capture all the non-ROS-I headers in their own folder.

Since you have switched to 14.04 these changes will only apply to ROS Indigo. Let's address any issues in this PR, but then open a new one to a indigo-devel branch.

[durovsky]

Sorry do not merge this PR, I was just testing what needs to be done in order to get Travis build passed successfully - that is the reason for including all the headers etc. Keeping PR open seemed to be the easiest way to restart build after each iteration :) Now when build succeeded I finally understand what was missing I will try to organize all the code in proper manner. I was about to close this this evening but you were just faster.