| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
cc: @dotnet/samsung for review |
Sorry, something went wrong.
|
@am11 should this go to arcade first? Upd: don't mind, I missed another PR to arcade |
Sorry, something went wrong.
|
@gbalykov another approach is to make it dynamic for all of these: eng/common/cross/toolchain.cmake: set(TIZEN_TOOLCHAIN "armv7hl-tizen-linux-gnueabihf/9.2.0") eng/common/cross/toolchain.cmake: set(TIZEN_TOOLCHAIN "aarch64-tizen-linux-gnu/9.2.0") eng/common/cross/toolchain.cmake: set(TIZEN_TOOLCHAIN "armv7l-tizen-linux-gnueabi/9.2.0") eng/common/cross/toolchain.cmake: set(TIZEN_TOOLCHAIN "riscv64-tizen-linux-gnu/13.1.0") eng/common/cross/toolchain.cmake: set(TIZEN_TOOLCHAIN "x86_64-tizen-linux-gnu/9.2.0") eng/common/cross/toolchain.cmake: set(TIZEN_TOOLCHAIN "i586-tizen-linux-gnu/9.2.0") For other platforms, we don't have version at that location. In Tizen containers, there is always a single versioned directory there. So we can search it using cmake's GLOB_DIRECTORY. WDYT? |
Sorry, something went wrong.
I think it's a good thing to do since it simplifies things |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
/ba-g failures are unrelated infrastructure issues |
Sorry, something went wrong.
|
Thank you! |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
/backport to release/9.0-staging |
Sorry, something went wrong.
|
Started backporting to release/9.0-staging: https://github.com/dotnet/runtime/actions/runs/12278369811 |
Sorry, something went wrong.
This syncs the gcc version in toolchian file with what's in the newest container build. Fixes dotnet#110517
| Back | FazBrowse Home | New Git URL |
This syncs the gcc version in toolchian file with what's in the newest container build.
Fixes #110517