We can not use -buildArch and -RuntimeOS for armel when building managed code, because armel host packages are not yet available.
For example, we can build managed code for ubuntu.16.04-arm with following options.
./build-managed.sh -Release -buildArch=arm -RuntimeOS=ubuntu.16.04
But we can't build for tizen.4.0.0-armel yet, so we build managed code with following workaround command witch restore x64 host packages instead of armel host packages.
./build-managed.sh -Release
We use the workaround command for arm32 CI for armel too. (in PR dotnet/corefx#15900)
Therefore when armel host packages are published, we have to update arm32 CI script for armel to use standard options.
Related issue is tracked at #20225.
@gkhanna79 @jyoungyun
We can not use
-buildArchand-RuntimeOSfor armel when building managed code, because armel host packages are not yet available.For example, we can build managed code for ubuntu.16.04-arm with following options.
./build-managed.sh -Release -buildArch=arm -RuntimeOS=ubuntu.16.04But we can't build for tizen.4.0.0-armel yet, so we build managed code with following workaround command witch restore x64 host packages instead of armel host packages.
./build-managed.sh -ReleaseWe use the workaround command for arm32 CI for armel too. (in PR dotnet/corefx#15900)
Therefore when armel host packages are published, we have to update arm32 CI script for armel to use standard options.
Related issue is tracked at #20225.
@gkhanna79 @jyoungyun