Hi ,I want to compile chromium os for arm64 , so I choose board=arm64-generic on setup_board, howerver , some of the packages would fail during build_packages , such as tlsdate and autotest-tests-security , anyone could help ,please? Log of tlsdata is attached.
--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
image_to_vm and cros_start_vm are not specific to x86_64. Vincent made them work for non-native targets and i thought he landed those CLs.
On Nov 29, 2016 12:14 PM, "Mike Frysinger" <vap...@chromium.org> wrote:
>
> patches welcome ! :)
> -mike
Mike,
It's been some time since I've done any dev with repo (although I'm already good to go with Portage obviously).
What is the typical build / debug / push for review cycle again?
Something like
1) ./build_packages --board=arm64-generic
2) if build fails, do
repo start [arm64-generic-fix-problem-foo]
3) finish building package via
ebuild-arm64-generic
4) Commit changes via
git commit
5) Submit changes for review via
repo upload
6) Go To 1
Is there anything I'm missing?
I'm going to mess around with the Qemu build first (hopefully that builds fine), and then will likely throw together something for Pine64.
I do have a bit of a deadline for this, because it's going to Mini-Me as an Xmas gift :-)
©
Sent from my Android