Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

windwos ros2-eloquent-debug std::regex re(regex) running error #170

Open
cjsJack opened this issue Dec 4, 2019 · 3 comments
Open

windwos ros2-eloquent-debug std::regex re(regex) running error #170

cjsJack opened this issue Dec 4, 2019 · 3 comments
Labels

Comments

@cjsJack
Copy link

cjsJack commented Dec 4, 2019

Hi, I am using ros2-eloquent-debug in windows, using visual studio 2015,
and I am building image_common package from https://github.com/ros-perception/image_common , and when I run list_transport project of image_common package, it failed when running list_transports.exe
So, I debug and find the reason is from pluginlib package from https://github.com/ros/pluginlib ,there is a syntax error about std::regex re(regex); in split.hpp from C:\dev\ros2-eloquent-debug\include\pluginlib\impl\split.hpp 45 line, and the parameter regex of std::regex re(regex) will become "\\" in windows system, because C:\dev\ros2-eloquent-debug\include\pluginlib\impl\filesystem_helper.hpp already define #define CLASS_LOADER_IMPL_OS_DIRSEP '\\'
so std::regex re("\\") will fail when running project. It is running error, I already test in vs2015, vs2017, vs2019, they all run error std::regex re("\\")
Because give me some advice, thanks,
jack

@dirk-thomas
Copy link
Member

dirk-thomas commented Dec 4, 2019

ROS 2 Eloquent officially only supports Visual Studio 2019 (see https://index.ros.org/doc/ros2/Releases/Release-Eloquent-Elusor/).

The C++ compiler in VS 2015 might just be too old to understand the used syntax. Therefore I will go ahead and close this ticket.

@dirk-thomas
Copy link
Member

Reopening - I missed that you are describing a runtime error in the regex and that you see the same problem with VS 2019.

@dirk-thomas dirk-thomas reopened this Dec 4, 2019
@cjsJack
Copy link
Author

cjsJack commented Dec 5, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants