Hello Matsuzawa,
It just upgrades the code to android 10. So please use clean folder for the latest code
fetching.
And pls notice it use
'lunch celadon_ivi-eng' for IVI
'lunch celadon_tablet-eng' for tablet
And you can use repo init -m xxxx to fetch the old stable release code. and lunch command
is the old one.
B.R
Bill
OTC 1A Infra
-----Original Message-----
From: Celadon <celadon-bounces(a)lists.01.org> On Behalf Of Takashi Matsuzawa
Sent: Friday, September 6, 2019 10:41 AM
To: celadon(a)lists.01.org
Subject: [
01.org Celadon] stable master build manifests?
Hello.
I could build Celadon with master branch configuration a couple of months ago, but today
if I tried rebuilding, it failed.
(Due to patch conflict errors, etc.)
I did the following to download source.
$ repo init -u
https://github.com/projectceladon/manifest.git
(meaning, default.xml of master branch is used.)
From its nature master branch may not be stable enough everyday.
I can see several stable branch configuratsion xmls and I want to try them (so that I can
rebuild without errors).
https://github.com/projectceladon/manifest/tree/master/stable-build
What exact repo init syntax to use one of these (e.g. ww201925_H.xml) manifest file?
I think repo init has -b and -m options to specify branch and manifest file name, but -m
will work if I specify sub directory?
And, what are "stable-build" manifests relashonships with the Celadon project
releases?
(I would like to pick latest stable master build version for my daily works.)
--
Celadon mailing list
Celadon(a)lists.01.org
https://lists.01.org/mailman/listinfo/celadon