Want to use Visual Studio Community 2017 to move OpenPose

Asked 3 months ago, Updated 3 months ago, 7 views

Thank you for your help.

When I tried to install OpenPose using Visual Studio Community 2017,
LNK1181cannot open input file'..\x64\Release\OpenPose.lib'OpenPoseDemo
The error occurred.

Therefore, after referring to the page below, I found out that the error like above was caused by the linker.
Problem installing openpose on windows 10 using visual studio 17

However, if you read the part that describes how to deal with it (where uvas94 on the link above commented on 12 Nov 2017),

"""uvas94 commented on 12 Nov 2017""
" ...I looked in the.vcxproj and change the necessary paths from Cuda8 to Cuda9 and found out that works as intended without any other change.

and so on.
However, even after reading this, I don't know exactly what to do.
I understand that you are changing the path, but I opened OpenPose.vcxproj in a text editor and changed CUDA_PATH_V8_0 to CUDA_PATH_V9_1, but it also outputs LNK1181 cannot open input file'..\x64\Release\OpenPode.OpenPode>.

Please let me know what .vcxproj file you want to modify.
(If it's a rudimentary story, I'm very sorry...)

By the way, the configuration is
·Visual studio community 2017
·CUDA v9.1
·cuDN version: 5.1 (started and installed the GitHub batch file as it is)
·Caffe version: Default from OpenPose (I just started and installed the GitHub batch file)

By the way, the following link recommends Visual Studio 2015.However, when I installed Visual Studio Community 2015 and built it with Release, it said MSB8020 The build tools for v141 (Platform Toolset='v141) cannot be found. so I gave up.


2022-09-30 11:15

2 Answers

Is it a multi-post by any chance?

To begin with, OpenPose does not officially support VS2017 and CUDA 9.0/9.1 environments.* There is no guarantee that you can compile by modifying .vcxproj, and even if you can compile it, it doesn't always work.If you don't have the skills to solve the problem on your own, you should wait for an official response.

Note that *.vcxproj configures the platform toolset to use a specific version of the Visual C++ compiler.v141 (VC14.1) is VC2017.To build on VS2015 (VC2015), you must change the platform toolset to v140 (VC14.0) in the project configuration.The MSB8020 error is presumed to have been caused by an attempt to open and build a project file configured for VS2017.

2022-09-30 11:15

It may have already been resolved, but I was able to install it on Visual Studio 2017.
I have put them all together, so please refer to them if you like.

2022-09-30 11:15

If you have any answers or tips

© 2023 OneMinuteCode. All rights reserved.