search

bark-simulator / bark

Open-Source Framework for Development, Simulation and Benchmarking of Behavior Planning Algorithms for Autonomous Driving
https://bark-simulator.github.io/
MIT License
287 stars 69 forks source link

cannot open the source file #498

Closed tinmodeHuang closed 3 years ago

tinmodeHuang commented 3 years ago

In face of the errors, is there any advices to give me? thanks ahead of time. I tried to modify the includePath-es, but it didn't seem to work.

2021-03-22 22-05-49 的屏幕截图

patrickhart commented 3 years ago

These errors are "just" VS-Code specific that cannot find the includes.

tinmodeHuang commented 3 years ago

so VS code of specific version is to blame for these errors

patrickhart commented 3 years ago

Not a specific version, but VS-Code is unable to locate the, e.g., boost source files. You can try to install Bazel extensions for VS-Code, but I am not sure if this will fix these issues.

tinmodeHuang commented 3 years ago

there is still the errors after installing the Bazel 0.4 extension, did you developers also meet the same trouble that VS Code cannot locate these source files besides boost ?

2021-03-23 18-46-16 的屏幕截图

patrickhart commented 3 years ago

These problems are generated by cpplint as far as I know. Maybe you can try to find a fix somehow this way.

tinmodeHuang commented 3 years ago

it seems that the problems don't relate to cpplint, there are still the ones after installing successfully bark on another machine. the bark folder is opened by selecting file→open directory once VS Code is installed and configured with the extensions including bazel, cpplint, python and C++.

2021-03-24 14-00-40 的屏幕截图 I'm thinking about what's wrong in the configuring process.

patrickhart commented 3 years ago

Under macOS (latest Catalina) and using VS-Code 1.54, I do not get these error messages shown. Do you have similar problems? @klemense1 @juloberno

tinmodeHuang commented 3 years ago

besides, could you pay a little attention to #499? please

patrickhart commented 3 years ago

I close this issue then as resolved as it seems a VS-Code/Linux specific error. If you find a fix for it, feel free to share it with us!

tinmodeHuang commented 3 years ago

in fact, the problem isn't resolved.