[ros-users] [Discourse.ros.org] [Next Generation ROS] ROS2 application development in visual studio 2017 or 2015 (win 10 x64)

[Changsong Yu]

Hi everyone,

I want to start ROS2 development in visual studio 2017 or 2015. However, i encouner some problems so that I can't build my source code. 
1. First step: I create Helloworldexample in visual studio 2017.
2. Second step: I add paths C:\dev\ros2\include;  
                               C:\dev\ros2\Lib; in the properties --> C/C++ --> General --> Additional Include Directories
3. Third step: I add fies: C:\dev\ros2\Lib\libfastrtps-1.5.lib;
                                  C:\dev\ros2\Lib\libfastcdr-1.0.lib; in the properties --> Linker --> Input --> Additional Dependencies
4. Forth step:Build --> error info below

1>------ Rebuild All started: Project: Project1, Configuration: Debug x64 ------
1>HelloWorld_main.cpp
1>HelloWorldSubscriber.cpp
1>HelloWorldPubSubTypes.cxx
1>HelloWorldPublisher.cpp
1>HelloWorld.cxx
1>Generating Code...
1>libfastrtps-1.5.lib(ThroughputControllerDescriptor.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in HelloWorld.obj
1>libfastrtps-1.5.lib(ThroughputControllerDescriptor.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in HelloWorld.obj
1>libfastrtps-1.5.lib(Param![Error_Info|689x459](upload://rDsPzbc5gCb6U8EMyF8hr56vODh.PNG)eterTypes.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in HelloWorld.obj
1>libfastrtps-1.5.lib(ParameterTypes.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in HelloWorld.obj
1>libfastrtps-1.5.lib(QosPolicies.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in HelloWorld.obj





---
[Visit Topic](https://discourse.ros.org/t/ros2-application-development-in-visual-studio-2017-or-2015-win-10-x64/3464/1) or reply to this email to respond.