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

Failed to activate protocol version: "CMAKE_HOME_DIRECTORY" is set but incompatible... #508

Closed
JMLX42 opened this issue Aug 4, 2018 · 8 comments
Assignees
Labels
bug a bug in the product
Milestone

Comments

@JMLX42
Copy link

JMLX42 commented Aug 4, 2018

Brief Issue Summary

[rollbar] Unhandled exception: Unhandled Promise rejection: configure [cmake-server] Failed to activate protocol version: "CMAKE_HOME_DIRECTORY" is set but incompatible with configured source directory value. {}

The CMake Project outline panel is empty.

Expected:

No error.
The CMake Project outline panel is filled.

Apparent Behavior:

git clone https://github.com/facebook/rocksdb.git
code rocksdb

CMake Tools will then attempt to "configure" the project and fail with the aforementioned error in the "debug console".

Platform and Versions

  • Operating System: Ubuntu 18.04 64bit
  • CMake Version: 3.10.2
  • VSCode Version: 1.25.1
  • CMake Tools Extension Version: 1.1.1
  • Compiler/Toolchain: gcc 7.3.0
@pointerless
Copy link

I had this same issue, I believe it is due to changing the project directory name/path. Try deleting the build directory and rerunning as loads of the stuff in that directory has absolute paths that are reused.

@JMLX42
Copy link
Author

JMLX42 commented Aug 7, 2018

As you can see in the issue description, it happens also with a freshly cloned repository.

@yay
Copy link

yay commented Aug 8, 2018

All my C++ projects created with the previous version of the plugin now have this issue. Is it possible for the plugin to recognize and fix whatever is wrong automatically?

@yay
Copy link

yay commented Aug 8, 2018

Removing the build directory and doing the Clean reconfigure works.

@JMLX42
Copy link
Author

JMLX42 commented Aug 8, 2018

It does work when the build directory is removed.
In my case, it was a permission issue: build is created - and build are done - from within a Docker container. So all the files are owned by root.

@vector-of-bool
Copy link
Contributor

I've had this issue myself with Docker containers, as well as when you move the source/build directory. I know how it can be fixed, so I'll take a swing for 1.1.2.

@vector-of-bool vector-of-bool added the bug a bug in the product label Aug 14, 2018
@vector-of-bool vector-of-bool added this to the 1.1.2 milestone Aug 14, 2018
@vector-of-bool vector-of-bool self-assigned this Aug 14, 2018
@JMLX42
Copy link
Author

JMLX42 commented Aug 14, 2018

I'll try to create my container with the proper uid/gid to see if it fixes it.

@vector-of-bool
Copy link
Contributor

This will now display a useful error message and helpful action button when it occurs. Fix in 1.1.2

@github-actions github-actions bot locked and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug a bug in the product
Projects
None yet
Development

No branches or pull requests

4 participants