Is OpenFyde Build Instructions going to be updated?

Support & help
, , ,
1

Hello All,

I just completed going through the OpenFyde “Getting Started”

compile and although it compiled, the USB never did boot up.

In know that the Github repository is set for R102 of Chromium OS build but I think that the latest is Build release-R136-16238.B from the manifest list.

https://chromium.googlesource.com/chromiumos/manifest.git/+refs

I am wondering if the OpenFyde build instructions are going to be updated too the latest version since it seems (although I could be wrong) that the current instructions and scripts are matched for the R102 Chromium OS base.

I am heavily researching things as I would like to experiment with a web browser Kiosk based on OpenFyde, if possible.

Thanks and have a great day

2

Just use the latest version. It’s all on GitHub. The process is the same.

3

Will give it a try and see if it works. Thanks

4

I just tried it the steps with the r136 chromium sources and it gives an error but not when I use the r102 sources like in the Getting Start documentation:

$ repo sync -j8
error: in `sync -j8`: extend-project element specifies non-existent project: infra/luci/client-py

seems like something has changed.

5

Openfyde has not released r136 yet. You should check what’s the latest release of openfyde.

6

You may refer to this. How others did it before. OpenFyde r120-dev Compilation Notes: Examples with VMware and OrangePi5

7

Thanks for the reply and information on this, but the build from the “Getting Started” even with the “r102” as in those instructions also does not seem to work and there seems to be some discontinuity with the “depot_tools”. I have tried using an older version of the tools as well as set up Ubuntu 18.04 LTS which is mentioned on that build page and followed the instructions but things fall apart an crash out when I get to the “gclient sync” part when errors get thrown.

Even tried setting up a Docker container build environment for Ubuntu 18.04 LTS with the same problem errors.

Has anyone been able to successfully build OpenFyde OS with the “Getting Started” instructions?

Maybe a Fyde developer will chime in and let us know their build process which I am hopeful.

Thanks again

8

Why don’t you use a newer version? The topic I sent to you, he used r120 and successfully compiled an image.

9

Hello, Yea, I have been digging into using r120 which I plan to try today to see if that will work and will report back on the results.

BTW, have you been able to compile OpenFyde up from the source to a bootable version as well? Just wondering if anyone else has had success with those listed steps out of curiosity. Thanks again.

10

Yes, I did it before just not with the r120.

11

Just found out that r120 does not compile on Ubuntu 18.04 LTS with the default install of Python3 which is v3.6 and r120 needs v3.11+ so now I am going to recreate a new docker container based upon Ubuntu 20.04 and check that one.

12

Hi All,

I have had some luck with my Dockerfile now set up using Ubuntu 22.04 and installing Python 3.11 and made it through the download and sync of the source code.

Then I moved into the actual build step with the cros_sdk but came across an error:

:/home/builder/r120# cros_sdk
WARNING:root:Unable to locate a non-root user home, falling back to root's configs.
cros_sdk: Unhandled exception:

my guess is that cros_sdk needs to be run as non-root perhaps but wanted to ask if you had any ideas just to confirm and be sure. :slight_smile:

UPDATE: After some adjustments to the Dockerfile and docker-compose.yml, it now seems like the build is starting and we are making some progress so far. Thanks again.

13

Latest Info:

I made it to the " Setup board amd64-openfyde"

from:

(inside)
$ setup_board --board=amd64-openfyde

When I set up the board for amd64 then I get an error:

chromite.lib.portage_util.MissingOverlayError: archero was not found

Not sure what is causing this but I am using the latest repo at:

https://github.com/openFyde/overlay-amd64-openfyde

I do wonder if I need to match the r120-dev from this repo that I am using with the chromiumos r120 from the “Getting Started” pages.

Any thoughts on this?

14

Remove archero, no android support in openfyde now

1 Like
15

how is that done? Any documentation or suggestions on this type of step?

16

You should check the link I replied before.

17

Based upon the link that you gave me and the information in it, the idea was to remove the archhero reference in the parent file.

I have removed the line “archero:base” in the “parent” file

/r120/src/overlays/overlay-amd64-openfyde/profiles/base/parent

and the "parent" file just has:

reven:base
arch-amd64:base
openfyde:base

but still get:

chromite.lib.portage_util.MissingOverlayError: archero was not found

Are there any other files that might have this reference or is it perhaps cached somewhere and causing problems?

Any thoughts and I truly thank you for the help as we are getting really close to a build now, I think?

18

UPDATE: from a repo issue link:

Step1 of the fix:

/r120/src/overlays/overlay-amd64-openfyde/profiles/base/parent

remove "archero:base" from parent file

Step2 of the fix: https://github.com/openFyde/overlay-rock5b-openfyde/issues/19

diff --git a/metadata/layout.conf b/metadata/layout.conf
index 8170e7fbd248..49078249b06d 100644
--- a/metadata/layout.conf
+++ b/metadata/layout.conf
@@ -1,4 +1,4 @@
-masters = portage-stable chromiumos eclass-overlay rock5b-openfyde-base fyde-eclass archero
+masters = portage-stable chromiumos eclass-overlay rock5b-openfyde-base fyde-eclass
 profile-formats = portage-2 profile-default-eapi
 profile_eapi_when_unspecified = 5-progress
 repo-name = rock5b-openfyde
(END)
19

Did you click the GitHub link?

20

New problem in that I have made it a little further, from the Getting Started page, but now it seems that there is not “build_packages” script.

Build all packages
Now it is time to build all software packages for the amd64-openfyde board.

(inside)
$ ./build_packages --board=amd64-openfyde --nowithautotest --autosetgov --nouse_any_chrome
# Append "--nowithautotest" to speed up the build process by skipping some tests

Any thoughts?