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

Displays error when I execute tools\setup-buildtools.cmd #2253

Closed
varasavelli opened this issue Aug 1, 2023 · 4 comments
Closed

Displays error when I execute tools\setup-buildtools.cmd #2253

varasavelli opened this issue Aug 1, 2023 · 4 comments
Assignees
Labels
bug Something isn't working triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@varasavelli
Copy link

I am installing the opentelemetry-cpp on windows 10 VM.

Steps to reproduce
I have just followed the steps from the document, got the error below.

PS C:\Venu\OTEL\OTLLibs\opentelemetry-cpp> tools\setup-buildtools.cmd

C:\Venu\OTEL\OTLLibs\opentelemetry-cpp>REM Copyright The OpenTelemetry Authors

C:\Venu\OTEL\OTLLibs\opentelemetry-cpp>REM SPDX-License-Identifier: Apache-2.0
Running with Administrative privilege...
Visual Studio installations detected:
C:\Program Files\Microsoft Visual Studio\2022\Professional
Building with vs2022 Professional...


** Visual Studio 2022 Developer Command Prompt v17.6.5
** Copyright (c) 2022 Microsoft Corporation


[vcvarsall.bat] Environment initialized for: 'x64'
Using existing vcpkg installation...
Computing installation plan...
error: Could not locate a manifest (vcpkg.json) above the current working directory.
This vcpkg distribution does not have a classic mode instance.
Computing installation plan...
error: Could not locate a manifest (vcpkg.json) above the current working directory.
This vcpkg distribution does not have a classic mode instance.
Computing installation plan...
error: Could not locate a manifest (vcpkg.json) above the current working directory.
This vcpkg distribution does not have a classic mode instance.
Computing installation plan...
error: Could not locate a manifest (vcpkg.json) above the current working directory.
This vcpkg distribution does not have a classic mode instance.
Computing installation plan...
error: Could not locate a manifest (vcpkg.json) above the current working directory.
This vcpkg distribution does not have a classic mode instance.
Computing installation plan...
error: Could not locate a manifest (vcpkg.json) above the current working directory.
This vcpkg distribution does not have a classic mode instance.
Computing installation plan...
error: Could not locate a manifest (vcpkg.json) above the current working directory.
This vcpkg distribution does not have a classic mode instance.
Computing installation plan...
error: Could not locate a manifest (vcpkg.json) above the current working directory.
This vcpkg distribution does not have a classic mode instance.
Computing installation plan...
error: Could not locate a manifest (vcpkg.json) above the current working directory.
This vcpkg distribution does not have a classic mode instance.
Computing installation plan...
error: Could not locate a manifest (vcpkg.json) above the current working directory.
This vcpkg distribution does not have a classic mode instance.

@varasavelli varasavelli added the bug Something isn't working label Aug 1, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 1, 2023
@lalitb
Copy link
Member

lalitb commented Aug 3, 2023

Doesn't look the issue with buildtool script. Can you check the vcpkg installation in you machine, if it is configured in classic mode ?

@vahw
Copy link

vahw commented Aug 4, 2023

I do have vcpkg. I am going use these libraries in C++ projects on windows environment (Visual studio 2022). Could you please share the steps to install the libraries ?

@ThomsonTan ThomsonTan self-assigned this Aug 9, 2023
@ThomsonTan
Copy link
Contributor

@vahw have you tried to to use your local vcpkg which is probably out-of-date. You can simply try remove the path of you local vcpkg.exe from %PATH% then rerun the script tools\setup-buildtools.cmd.

@marcalff marcalff added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 11, 2023
@ThomsonTan
Copy link
Contributor

Close it for now. Please reopen it if it happens again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

5 participants