Replies: 1 comment 2 replies
-
I just realized it did do the correct thing in the \xpacks@xpack-dev-tools\arm-none-eabi-gcc\bin directory. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was setting up a new project using the xpm where I wanted the local xpacks directory to contain the compiler. So as I understood from "xpm --help" the "--copy" option should install the compiler to the local directory rather than the "... AppData\Roaming\xPacks" directory. However it still installs in the roaming directory and tries to the symbolic type links.
What I was trying to do is setup cortex-debug in VSCode which requires the toolchain path for running the gdb server:
"interface": "swd",
"svdFile": "${workspaceFolder}/CMSIS/ATSAML21J18BU.svd",
"armToolchainPath": "${workspaceFolder}/xpacks/.bin"
The issue is that the cortex-debug is trying to run "xpacks.bin\arm-none-eabi-gdb.exe" which does not exist. Is there a way to force xpm to install in the local directory, so specify the path where to install?
Beta Was this translation helpful? Give feedback.
All reactions