Skip to content

Build error on Windows 10 with Visual Studio 2019 #113

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

Closed
mefoster opened this issue Jun 15, 2020 · 5 comments
Closed

Build error on Windows 10 with Visual Studio 2019 #113

mefoster opened this issue Jun 15, 2020 · 5 comments

Comments

@mefoster
Copy link

mefoster commented Jun 15, 2020

I have installed ROS 2 on my Windows 10 machine and have downloaded the latest ros2-java (checked out everything with vcs)

I am trying to build as follows:
C:\dev\ament_ws>python src/ament/ament_tools/scripts/ament.py build
I get the following error (horizontal lines removed because they mess with markdown):

Process package 'ament_cmake_core' with context:
 source_space => C:\dev\ament_ws\src\ament\ament_cmake\ament_cmake_core
  build_space => C:\dev\ament_ws\build\ament_cmake_core
install_space => C:\dev\ament_ws\install
   make_flags => -j8, -l8
  build_tests => False
+++ Building 'ament_cmake_core'
ament build: Unknown / unsupported VS version: 16.0

Any suggestions on where to fix this?

@mefoster
Copy link
Author

Have been trying to get this to work a bit more but I'm not an expert on Visual Studio or CMake so I'm heading down a rabbit hole. Has anyone actually ever built this successfully with Visual Studio 2019?

@esteve
Copy link
Member

esteve commented Jun 16, 2020

@mefoster thanks for trying out ros2-java. We're adding a CI workflow for Windows in #109 to make sure that ros2-java supports Windows. However, we're now targeting ROS 2 Dashing and Foxy in separately in non-master branches, and will soon update the master branch of ros2-java, which right now only supports ROS 2 Bouncy. What version of ROS 2 did you install?

@mefoster
Copy link
Author

Foxy ... ah yes, now I see what might have happened. I'll look for the Foxy branch and try again.

@mefoster
Copy link
Author

Right, I see that you opened a new request about describing how to build with colcon instead of ament. I was just in the process of discovering that ament is obsolete ... I'll stay tuned and try again when there are new instructions

@jacobperron
Copy link
Contributor

I'm going to close this since we have this ticket to track getting CI turning over on Windows #102

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

No branches or pull requests

3 participants