Comments (7)
@borjamunozf Sorry for misunderstanding your question, for your issue we tried to use open-source projects that didn‘t reproduce it, in order for us to investigate this issue further, could you please provide a sample project and detailed steps to reproduce it (a video of the reproduction would be great)? We are looking forward to your reply. Thank you.
from vscode-cmake-tools.
Seems related or exactly the same scenario we're facing...
from vscode-cmake-tools.
@borjamunozf Thanks for the feedback, we use bullet3 project then 'CMake: Compile Active File' doesn't work properly and shows 'Unable ro find compilation information for this file' error, does this reproduce your issue? If it doesn't reproduce your issue is it possible to provide demo project & exact steps?
ENV:
- System info: Ubuntu 22.04.4 LTS
- VS code version: 1.88.1
- CMake Tools: v1.17.17
- CMake: 3.19.2
Repro Steps:
- Download bullet3 project and open with VS Code.
- Run command ‘CMake: Compile Active File’
from vscode-cmake-tools.
Not sure what you mean. Has this any relationship with my error? In my case, the problem is about truncating (the compile active file does not complain, it just logs to terminal console but the cmd looks truncated, not about unable to find compilation information for this file
I cloned the repo and did that and yes, if I go to any file of the bullet3 and select Compile Active file I got that error. But I guess this is the expected behaviour, there is not compile_commands.json ?
I tried to build bullet3 with the provided script with this:
- Modified CMakeLists root file with CMAKE_EXPORT_COMPILE_COMMANDS ON
- Executed
./build_cmake_pybullet_double.sh
- Same error: Unable to find compilation information for this file.
@borjamunozf Thanks for the feedback, we use bullet3 project then 'CMake: Compile Active File' doesn't work properly and shows 'Unable ro find compilation information for this file' error, does this reproduce your issue? If it doesn't reproduce your issue is it possible to provide demo project & exact steps?
ENV:
1. System info: Ubuntu 22.04.4 LTS 2. VS code version: 1.88.1 3. CMake Tools: v1.17.17 4. CMake: 3.19.2
Repro Steps:
1. Download [bullet3](https://github.com/bulletphysics/bullet3) project and open with VS Code. 2. Run command ‘CMake: Compile Active File’
from vscode-cmake-tools.
Hi again.
It seems that the length is not the root cause of this issue, because I was able to reproduce (after spending more time that it was required) the error with a short length. It just simply not working at all.
Here is the repo:
https://github.com/borjamunozf/vscode-cmd-truncated
- Build with CMakePresets.
- Try to remove build/Debug/CMakeFiles/vscode-cmd-truncated.dir/main.cpp.o
- Run Compile Active file for main.cpp and it wont compile anything, just show the message.
/usr/bin/g++ -I/home/borjamf/workspace/vscode-cmd-truncated/quefacemos/Include -I/home/borjamf/workspace/vscode-cmd-truncated/quefacemos2/Include -I/home/borjamf/workspace/vscode-cmd-truncated/quefacemos3/Include -I/home/borjamf/workspace/vscode-cmd-truncated/quefacemos4/Include -I/home/borjamf/workspace/vscode-cmd-truncated/quefacemos5/Include -o CMakeFiles/vscode-cmd-truncated.dir/main.cpp.o -c /home/borjamf/workspace/vscode-cmd-truncated/main.cpp
- However, copying & pasting the same compile command in the terminal will work.
from vscode-cmake-tools.
@borjamunozf @gcampbell-msft Thank you for investigating! We will be able to reproduce the issue using the following steps and will continue to follow up on this issue:
ENV:
System info: Ubuntu 22.04.4 LTS
VS code version: 1.88.1
CMake Tools: v1.17.17
C/C++ extension: 1.20.2(pre-release)
Repro Steps:
- Clone and open project with VS Code: https://github.com/borjamunozf/vscode-cmd-truncated
- Run 'CMake: Build' command after successfully configuring the project using CMakePreset.
- Remove build/Debug/CMakeFiles/vscode-cmd-truncated.dir/main.cpp.o
- Run 'CMake: Compile Active File' command for main.cpp.
Actual Result: The 'CMake: Compile Active File' VSCode command doesn't compile anything, it just displays the message:
/usr/bin/g++ -I/home/test/Desktop/EricaTest/vscode-cmd-truncated/quefacemos/Include -I/home/test/Desktop/EricaTest/vscode-cmd-truncated/quefacemos2/Include -I/home/test/Desktop/EricaTest/vscode-cmd-truncated/quefacemos3/Include -I/home/test/Desktop/EricaTest/vscode-cmd-truncated/quefacemos4/Include -I/home/test/Desktop/EricaTest/vscode-cmd-truncated/quefacemos5/Include -g -o CMakeFiles/vscode-cmd-truncated.dir/main.cpp.o -c /home/test/Desktop/EricaTest/vscode-cmd-truncated/main.cpp
More Info: Using the compile command in the terminal will work fine
Command: g++ -o main main.cpp
from vscode-cmake-tools.
Is there any way we could help with this? I have not too much exposure to Typescript and so, but if there's any info to help debugging this and accelerate would be ok for us
from vscode-cmake-tools.
Related Issues (20)
- VSCODE reports symbols not found, while jump to declaration works correctly. HOT 8
- Extension display language not right HOT 2
- How to set the default ``cmake_minimum_required`` version in QuickStart command HOT 2
- Customer request: Add a setting for hierarchy delimiter to Test Explorer HOT 1
- CTest as the run-layer
- Broken API usage of latest WSL "No cache object found" HOT 6
- "Test results not found" for successful CTests from a CMakeLists file HOT 24
- Add setting to toggle Project Outline View
- Quick Start: Does not work with WSL on Windows HOT 3
- [loc] The content of the prompt box is not translated when hovering over the default value in the project status
- [loc] The custom configure preset is not translated in the VS Code Command Palette drop-down options
- Regression on running CTest with v1.18.41 update HOT 24
- XDG_SESSION_ID and XDG_SESSION_TYPE environment in debugConfig.environment or console's environment are overrided by getConfigureEnvironment HOT 3
- The build configurations generated do not contain the active build configuration. Using 'DEBUG' for CMAKE_BUILD_TYPE instead of 'Debug' to ensure that IntelliSense configurations can be found. HOT 6
- Presets not working when using version 8 with $schema HOT 1
- Installing cmake after launching VS Code results in claims of a cmake invalid location, forcing user to restart VS Code to proceed HOT 3
- Unable to run CTest in parallel HOT 3
- Project Outline Does Not Show Source Group or Headers HOT 1
- [regression] TypeError when running CTests with debugging HOT 3
- CMake presets not used correctly? HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vscode-cmake-tools.