-
Notifications
You must be signed in to change notification settings - Fork 48
vcpkg: Vcpkg is not installed #203
Comments
@seanyen @ooeygui |
Attached is my chocolatey log, I had the same problem. |
Hi all, a version of |
Hi - new ROS user installing for the first time ever on Windows 10; I'm running into this issue even after specifically running a "choco upgrade ros-vcpkg" first. Still seeing "ERROR: the following rosdeps failed to install" vcpkg: Vcpkg is not installed". This is with ros-melodic-desktop_full V20200409.2. This is on Windows 10 1909 (OS Build 18363.752) and Visual Studio Community Edition 2019; fresh install. |
@dweekly Thanks for reporting, can you check if |
Ah, it was not. My issue was caused by #153 |
Closing it since the fixed release is out. |
I'm having exactly the same issue. |
Hi @andyworkingholiday , |
Hi, I also have the same trouble. I have installed VC2019 community (because I do not want to mess with my 2017 work license) just today and added the desktop C++ package, so that should be there. I followed this "http://wiki.ros.org/Installation/Windows" until 5.1 and ran into the problem. Then, I upgraded "ros-vcpkg": C:\Windows\System32>choco upgrade ros-vcpkg -y --execution-timeout=0 I guess there is nothing to update. I also have a "C:\opt\vcpkg" folder with lots of stuff, so there is something. Then I again called "choco upgrade ros-melodic-desktop_full -y --execution-timeout=0" and now my error messages for the ros installation changed to this: I don't understand that. I upgraded vcpkg which says I have the latest version and then the next call now says I do not have any version ? What should I do? Delete some folders and start over? regards |
@lwoffice, I have a hypothesis. To confirm, is there If not, can you:
and post the output? |
Well, I am currently figuring it out and it has to do with messed up Path variables. This is what I have right now: I partly solved the issue by starting from scratch. I found that my Windows settings missed an entry in the PATH variable for Powershell (%SYSTEMROOT%\System32\WindowsPowerShell\v1.0) As a result, the installation of the vcpkg outputs a message which can be quickly overlooked and says that the command "Powershell" can not be found. Nevertheless there will be a green message that the installation of vcpkg was successful ! I looked up thread #153 where I found that their is a build script after the download procedure which outputs message "Building vcpkg.exe ...". Without powershell, that build script does not work obviously. I looked up the windows features, but Powershell was installed. Whatever, I removed and reinstalled it, but it still did not work. I manually added the path from above and I was able now to call Powershell from the x64 Dev Console. Additionally, I also had to completely delete the c:\opt folder, otherwise the build process was also not started correctly. After that, it worked fine and a "vcpkg.exe" was created in C:\opt\vcpkg. Nevertheless, the installation of ros-melodic afterwards still fails: C:\Windows\System32> choco upgrade ros-melodic-desktop_full -y --execution-timeout=0 ros-melodic-desktop_full v20200409.2 Chocolatey upgraded 0/1 packages. 1 packages failed. Failures
I looked up "chocolateyInstall.ps1" and "rosdepInstall.bat" and I guess it now has something to do with a messed Python variable too. Trying to figure that out now ... |
Thank you for investigating. The vcpkg bootstrap script does not use a full path to powershell: (the ROS install is explicit about calling powershell by full path to install chocolatey) Can you run |
That was not successful, but I recognized some (probably) strange folder issues. In the c:\opt\chocolatey\lib" I only have the "ros-vcpkg" folder. There are no further subfolders. Whenever I use the install procedure for ros (choco upgrade ros-melodic-desktop_full ... ), this "ros_melodic..." folder is created in "C:\ProgramData\chocolatey\lib" and after it fails it is automatically moved into the "lib-bad" folder. So ... I can find that rosdepInstall.bat here "C:\ProgramData\chocolatey\lib-bad\ros-melodic-desktop_full\tools". Running this manually immediately crashes the whole x64 console, so I can not see anything. I am really wondering, why I have this chocolatey folder in "C:\ProgrammData", although I installed chocolatey according to "http://wiki.ros.org/Installation/Windows" section 4. Looking at that installation string it might have something to do with the "PATH" variable as well? I made a screenshot with all the folders and you I found a "c:\ProgramData\chocolatey\bin" in the System Path variable. I do not know if that is supposed to be there and why it is there. |
Thank you for working with us on this, I really do appreciate it. The console window crashing is quite ominous. What version of Windows are you using? (I can't tell from the screen shot). I noticed that you have mingw32 in your path, I'm a bit worried that the inherited environment is causing compatibility problems. ROS is quite sensitive to the host environment, which is why we've tried to isolate it as much as possible. However, environment from the host can 'leak' into the ROS environment in strange ways. When you create the shortcut to the console window, we recommended adding a chocolatey bypass, so that it too is isolated:
When the console is launched with that command line, chocolatey will reference the packages from the |
Version is Win 10 Pro 1809 (Build 17763.1098). After all, I figured it out. I completely removed the c:\opt and the c:\ProgramData\chocolately folders to get rid of the crappy installations before. I restarted all steps from section 4, but I used a cmd with the "bypass" option. Move section 6 inbetween 3 and 4 and modify it slightly: I removed the last statement (&& c:\opt\ros\melodic\x64\setup.bat), because I did not want the setup.bat to be executed in the steps 4 and 5 already, I just wanted the console with the bypass which worked fine (maybe it would not harm to have setup.bat here already, I do no know). I used that modified cmd for steps in section 4 and 5 and when I reached section 6, I added the "...\setup.bat" part to the link. Honestly, I do not know why there is a difference between setting "set ChocolateyInstall=..." in the link instead of calling it in the console itself, but on my system that made the difference. Maybe that is a Windows secret :) You could add the workaround for vcpkg to section 5.1 (and probably 5.2), so people do no longer need to search this thread. At least it does not harm I think, although it might not be necessary in all cases: It might also be good to add the hint with regard to Powershell path issues that I had. Users should check their User Path variables and add "%SYSTEMROOT%\System32\WindowsPowerShell\v1.0" if it does not exist. That solved my build issues with regard to vcpkg. That's it for me ... Chocolatey upgraded 10/10 packages. Done :D |
I'm glad you figured it out!
We had put it in this order because setup.bat won't exist the first time around which causes an error launching the script.
I'll add some clarity to the doc. We decided to move the chocolatey install into the c:\opt directory so that it was self-contained. you can reinstall ROS by removing c:\opt or move the install to another machine by copying c:\opt. That said, we are looking at alternative environment management solutions for future deployments. (Including CondaForge)
I added a troubleshooting section.
I really appreciate you working with us on this! |
Hi, I'm having issues.
which created Also, there is no path to the python 2.7, that the install downloads, in the path variable. I don't know if there should be. |
@David-milne Is it possible to provide a screenshot of what error you saw? And the From the logs it said it failed at |
@seanyen After I posted last I rebuilt Here is my path environment variables: I built the |
Yes that's it |
Hi, I noticed that for your console outputs it still says that vcpkg.exe is not installed. I guess you have called installation part, but it still did not successfully build that executable. Please have a look into C:\opt\vcpkg and if there is really an executable. The only other things I have in mind are starting the Dev Console as an Administrator and using a link to the console with the path and options that were described above. Also, I had to remove everything in C:\opt and start over completely again with it. regards |
Thanks for the suggestion, but I have started with a clean |
Chocolatey upgraded 10/12 packages. 2 packages failed. Upgraded:
Failures
Attached is my chocolatey log and env.log.Thank you fou helping me with the problem. |
sorry,I don't quite understand your requirements.What network configuration is required? @seanyen |
ERROR: The remote name could not be resolved: 'raw.githubusercontent.com' |
@jiaodaxiaoli: are you behind a (corporate) firewall or proxy? What is the output of If you are behind a firewall, additional configuration may be needed to allow |
|
@jiaodaxiaoli You are experiencing multiple separate issues:
|
@ooeygui hi, I installed it according to the instructions on this website--http://roswiki.autolabor.com.cn/Installation(2f)Windows.html |
I don't know how to set up ros, because I am a beginner. I hope you can explain it carefully. |
@jiaodaxiaoli Thank you for the pointer. That appears to be a copy of the official documentation, and is missing steps. The official documentation is located: https://wiki.ros.org/Installation/Windows. Please follow the steps from top to bottom. The distribution of ROS2 in that document is designed to work within ROS1. If you are interested in ROS2 only, the official documentation is here: https://index.ros.org/doc/ros2/. At this point, I recommend removing |
@ooeygui Thank you very much for your help, I have installed ROS.I have installed ROS, but now I have a new problem. My RVIZ starts normally, but gazebo doesn't. It shows that 'gazebo' is not an internal or external command, nor is it a runnable program or batch file.Here are my system variables. |
@jiaodaxiaoli It is best to file a new issue as this is not vcpkg related. Gazebo is provided in the gazebo_ros package, and is from roslaunch. |
Hi
Chocolatey upgraded 11/12 packages. 1 packages failed. Upgraded:
Failures
I have try to install in two computers but the error is the same, i have trying with the solve 20200409.2.0 but it not change nothing, the file vcpkg.exe is created in the folder "C:\opt\vcpkg" , I have "%SYSTEMROOT%\System32\WindowsPowerShell\v1.0" in path variables, i follow the recomendation of lwoffice commented on 29 Apr, but the result is the same. What i can do it? |
vcpkg is the canary in the coalmine. It is the first time that ROS attempts to build in a prompt. If it fails, it means that the environment has not been set up correctly. Can you do the following:
Paste the output? |
@940222JESUS in your shortcut, did you include the setup.bat for the Window? If not, can you run |
Thank you for digging in with us. The English language pack is requirement within vcpkg itself: microsoft/vcpkg#3842. I'll update the document on the ros install page. |
@940222JESUS I'm glad we could get you past that. The vxpkg install happens early in the ROS install process, so ROS isn't complete installed. to complete the install upgrade
This will resume where it left off. Afterward, reopen the ROS prompt. (Make sure that setup.bat is called), then you can check out ROS repos. Thanks again! |
@Wal1082 It seems that it cannot reach out to the powershell URL. Are you behind a proxy? Are you able to change the network or disable proxy to retry again? |
I am not using behind a proxy. I tried on other network and still no luck. |
That's kind of odd - why is Powershell x86 being installed? Are you using a 32bit command prompt? or running on a 32bit OS? |
@Wal1082 By checking Vcpkg issues, your symptom is very alike to many issues reported in Vcpkg side: I would recommend to also cross-post your issue in Vcpkg repo and I believe the Vcpkg team has better insight on the network issues. |
Thanks for the help. I disabled the firewall and it works but then I Have trouble in installing the rviz. So, I scrap the windows 10 installation, I went through virtualbox which no issue at all.
rgds, Warby
… On Jun 10, 2020, at 4:38 PM, Sean Yen ***@***.***> wrote:
@Wal1082 By checking Vcpkg issues, your symptom is very alike to many issues reported in Vcpkg side:
microsoft/vcpkg#4729
microsoft/vcpkg#9064
I would recommend to also cross-post your issue in Vcpkg repo and I believe the Vcpkg team has better insight on the network issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I'm closing this bug as it is generally not the root cause of new issues. vcpkg is the first time in the environment where code is built - anything wrong upstream manifests here. |
Hello, I am still having issues with the vcpkg, can somebody please advise. Please refer to the error message I am receiving Chocolatey v0.10.15 Chocolatey upgraded 0/1 packages. 1 packages failed. Failures
|
This is a cross-post for the issues reported here:
We are investigating this issue. For whoever lands here because of hitting this issue, please kindly share yourc:\opt\chocolatey\logs\chocolatey.log
. That would help us better understand what's happening.UPDATED: We are working on a release for the fix. Meanwhile, you can use the following workaround while waiting for the new release.UPDATED: A version of
20200409.2.0
is released and this problem should be addressed.Workaround:
Following the normal instructions, and when it comes to do
Binary Package Installation
, please do the steps instead:The text was updated successfully, but these errors were encountered: