nxp-mcuxpresso / vscode-for-mcux

Support for NXP Visual Studio Code for MCUXpresso Extension project.
19 stars 1 forks source link

Installer Created two toolchain directories on Linux #48

Open sprhawk opened 2 months ago

sprhawk commented 2 months ago

Type: Bug

I used MCUXpresso installer to install all the toolchain software under Debian Linux. However it created two different directories for toolchain: arm-gnu-toolchain-13.2.Rel1-x86_64-arm-none-eabi and arm-gnu-toolchain-13.2.rel1-x86_64-arm-none-eabi The VSCode Extension only found arm-gnu-toolchain-13.2.Rel1-x86_64-arm-none-eabi as the available toolchain, but the installed standalone add-ons are installed inside arm-gnu-toolchain-13.2.rel1-x86_64-arm-none-eabi

So during buiding, it reported linker didn't find cr_newlib_nohost, I manually copied all contents under arm-gnu-toolchain-add-ons-13.2.1 to arm-gnu-toolchain-13.2.Rel1-x86_64-arm-none-eabi, then fixed the building

Extension version: 1.10.128 VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:08:12.169Z) OS version: Linux x64 6.1.0-18-amd64 Modes:

System Info |Item|Value| |---|---| |CPUs|11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 4200)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|2, 3, 2| |Memory (System)|62.53GB (6.85GB free)| |Process Argv|--crash-reporter-id 33bcdb7b-636c-4190-909e-a1252f236adc| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|i3-gnome| |XDG_CURRENT_DESKTOP|GNOME| |XDG_SESSION_DESKTOP|i3-gnome| |XDG_SESSION_TYPE|x11|
A/B Experiments ``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492:30256859 vscorecescf:30445987 vscod805cf:30301675 binariesv615:30325510 vsaa593:30376534 py29gd2263:31024239 c4g48928:30535728 azure-dev_surveyone:30548225 vscrpc:30673769 2i9eh265:30646982 962ge761:30959799 pythongtdpath:30769146 welcomedialogc:30910334 pythonnoceb:30805159 asynctok:30898717 pythonregdiag2:30936856 pythonmypyd1:30879173 h48ei257:31000450 pythontbext0:30879054 accentitlementst:30995554 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 cppperfnew:31000557 dsvsc020:30976470 pythonait:31006305 dsvsc021:30996838 724cj586:31013169 pythoncenvpt:31062603 a69g1124:31058053 dvdeprecation:31068756 dwnewjupytercf:31046870 impr_priority:31102340 refactorc:31101458 ccplc:31098109 wkspc-onlycs-c:31102393 ```
cristitep-nxp commented 2 months ago

Hi,

Thanks for reporting it, we plan a new release soon, integrating this error too.

Regards, Cristian

DragosMiloiuNXP commented 2 months ago

Hi @sprhawk,

We just released an updated version of the add-on (13.2.2) that fixes the incorrect paths, so now it should be added correctly on top of the ARM GCC. As you already have fixed it manually, you don't need to do anything else in this moment.

Thanks again for reporting the issue.

Dragos.