Until now, we were publishing deps archives using the {OS}_{CONFIG} where OS is the name of the system we are building and CONFIG is how we are building (native/cross...; dyn/static).
Now, we are publishing deps using a name {TARGET_ARCH}_{dyn/static} so archives are now independent of the system/config we have used to compile dependencies.
(ie building natively on arm and cross compiling to arm from x86_64 is now using the same name)
On top of that, inside the archive, we were using build dir BUILD_{CONFIG}. We now have a option to use BUILD_{TARGET_ARCH}.
Note that this option should be used only on CI as we start a new build each time.
On a dev usage when we want to test different config (and especially native vs dyn), this option should not be used as different configs could use the same build directory.
Until now, we were publishing deps archives using the
{OS}_{CONFIG}where OS is the name of the system we are building and CONFIG is how we are building (native/cross...; dyn/static).Now, we are publishing deps using a name
{TARGET_ARCH}_{dyn/static}so archives are now independent of the system/config we have used to compile dependencies. (ie building natively on arm and cross compiling to arm from x86_64 is now using the same name)On top of that, inside the archive, we were using build dir
BUILD_{CONFIG}. We now have a option to useBUILD_{TARGET_ARCH}. Note that this option should be used only on CI as we start a new build each time. On a dev usage when we want to test different config (and especially native vs dyn), this option should not be used as different configs could use the same build directory.