yanghhhhhhh

Thanks for the comment. If there is progress on this issue, we will update here. Thanks!

@TSonono Thank you for your suggestion. We will update you if there is any progress on this issue. Thank you.

Hi @josephgarnier, thank you for reporting this issue. We tried to check this issue in Visual Studio Code v1.105.1 + CMake Tools v1.21.36. Could you please help us check if...

Hi @josephgarnier , thanks for reporting issue here! We can reproduce this issue on VS Code 1.105.1 + CMake tools 1.21.36 version. **Repro Steps:** 1. Download the attached project([Test4601.zip](https://github.com/user-attachments/files/23176909/Test4601.zip)) and...

@debugee Thanks for reporting this issue. In order for us to investigate this further, could you share this sample project with us? Thank you.

@debugee Thanks for checking this issue. We verified this issue in a Mac OS darwin environment with CMake version 4.1.0 + VS Code 1.105.1 + CMake tools 1.22.16. When we...

@debugee Thank you for the detailed information. We have rechecked this issue on our side. The build information displays as "/A, /B (framework directory), /C, /D, /E, /build (framework directory)"....

@debugee Thank you for your reply. As you say, it is ‘/A, /C, /E, /B, /build /D’. We can reproduce the issue now. Thank you.

We can reproduce this issue in a Mac OS darwin environment with VS Code 1.105.1 + CMake tools 1.22.16 version. **Repro Steps:** 1. Clone the project from https://github.com/debugee/bug-sample.git or download...

@david-fong Thank you for reporting this issue. We have verified this issue using this sample project([demo_project.zip](https://github.com/user-attachments/files/22459440/demo_project.zip)) in VS Code 1.104.1 + CMake tools 1.22.9 and we can reproduce it. So...