microsoft / vscode-embedded-tools

Official issue tracking repository for Microsoft's Embedded Tools VS Code extension.
MIT License
43 stars 3 forks source link

Extension can't find static library #40

Closed MatTab3335 closed 1 year ago

MatTab3335 commented 1 year ago

Type: Bug Report

Describe the bug

Hello! At the final make step: [build] [50/50] Linking C executable prj_upm_01.elf

I get an error:

[build] FAILED: prj_upm_01.elf
....
[build] arm-none-eabi-gcc.exe: error: ../../libSTM32F4XX.a: No such file or directory
[build] arm-none-eabi-gcc.exe: error: ../../libkernel_m4f.a: No such file or directory
[build] arm-none-eabi-gcc.exe: error: ../../libmodbus_rtu_m4f.a: No such file or directory
[build] arm-none-eabi-gcc.exe: error: ../../libuip_m4f.a: No such file or directory
[build] arm-none-eabi-gcc.exe: error: ../../libIQmathLib-cm4f.a: No such file or directory
[proc] The command: c:\Users\Ivan\AppData\Roaming\Code\User\globalStorage\ms-vscode.vscode-embedded-tools\vcpkg\root\downloads\artifacts\vcpkg-ce-default\tools.kitware.cmake\3.20.1\bin\cmake.EXE --build C:/mexbiosdevelopmentstudio_ll_stm32cubeide/.../Libraries/STM32F4XX/prj_upm_01/build/debug/build --target prj_upm_01 exited with code: 1
[build] ninja: build stopped: subcommand failed.
[build] Build finished with exit code 1

Project in Cube IDE makes fine, somehow extension can't find those static libs. Any ideas?

Cproject file in attachments (I couldn't download .cproject, so it in txt format)

cproject.txt

benmcmorran commented 1 year ago

Thanks for the report. In the .cproject file the paths are simply specified as "other flags" for the linker, which is why the importer isn't attempting to do any special path translation.

Are the static libraries still being built in VS Code (probably to some other directory), or are they missing completely? If they're still being built, then it should be possible to modify the generated CMake script to point at the correct location.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has been inactive for 30 days. To reactivate the issue, simply post a comment with the requested information to help us diagnose this issue. If this issue remains inactive for another 7 days, it will be automatically closed.

github-actions[bot] commented 1 year ago

This issue has been automatically closed due to inactivity. If you are still experiencing problems, please open a new issue.