Where should I put sysroot for cross compiling toolchain? #6227
Unanswered
AlynxZhou
asked this question in
Writing Formulae/Casks
Replies: 1 comment
-
|
I think we need a standard to put cross compiling toolchain sysroot, because obviously we cannot install target libs into |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Output of
brew configOutput of
brew doctorDescription of issue
We already have formula for arm-none-eabi-gcc, however, there is no C library for it, so it's not able to cross compile binaries for that arch. And I am trying to package arm-none-eabi-newlib which is a C library for embedded systems.
Now I can correctly build and install arm-none-eabi-newlib. But the problem is arm-none-eabi-gcc cannot see it. Typically in Linux, we use sysroot for cross compiling toolchains, for example
/usr/arm-none-eabi, and put all headers, objects and libraries into that directory, so arm-none-eabi-gcc can find arm-none-eabi-newlib files here.However, Homebrew puts packages file into different Cellar dirs, so they cannot see each other. Where should I choose to make a sysroot, so cross compiling toolchain can put files into that dir and share them?
Beta Was this translation helpful? Give feedback.
All reactions