ctuning / ck-armnn

Collective Knowledge workflows for ArmNN
BSD 3-Clause "New" or "Revised" License
7 stars 10 forks source link

Dev-2-dev and stable-2-stable repository synchronization between ArmCL and ArmNN #8

Closed ens-lg4 closed 5 years ago

ens-lg4 commented 5 years ago

Currently both dev branches of ArmCL and ArmNN live on a different server and have to be somehow synchronized when we build our packages (in each branch, 12 basic variations or ArmNN have to be correctly matched against 3 or 4 variations of ArmCL).

My initial urge to represent dev as yet another variation seems to be a wrong one. dev is more of a "version" than a "feature".

ens-lg4 commented 5 years ago

It finally seems to work.

Whenever building an ArmNN package make sure to either require "release" or "dev" in the list of tags. Examples:

$ ck install package --tags=lib,armnn,neon,tflite,release

OR

$ ck install package --tags=lib,armnn,opencl,onnx,dev