Index: README.md =================================================================== diff -u -r710dd1a29e1dd4557222c3b789c571ed5c5c37a0 -rbc0dee44b5cc4f15c8a0f765058c07911965d4e3 --- README.md (.../README.md) (revision 710dd1a29e1dd4557222c3b789c571ed5c5c37a0) +++ README.md (.../README.md) (revision bc0dee44b5cc4f15c8a0f765058c07911965d4e3) @@ -95,47 +95,9 @@ Build Diality's Embedded Leahi Yocto (ELY) ------------------------------------------ ``` -time screen bitbake ely-image-qt +./ely-build-image.sh BETA ``` -1. *screen* command -Since the build is going to be on the server on the network, and any disconnection will lose the bitbake progress output. -To retrieve the lost connection use screen command to get back the running bitbake progress output. -1.1. list the active screen terminal -if the screen is attahced -``` -$ screen -ls -There is a screen on: - 5249.pts-0.dvm-linux03 (09/21/2024 08:48:20 PM) (Attached) -1 Socket in /run/screen/S-bruce. -``` - -if the screen session is not attached -``` -$ screen -ls -There is a screen on: - 5249.pts-0.dvm-linux03 (09/21/2024 08:48:21 PM) (Detached) -1 Socket in /run/screen/S-bruce. -``` - -1.2. attach to a lost connection -``` -$ screen -r 5249 -``` -then you should see the output you have lost. - -2. *time* command - -The time command will let you know that how long the process took. - -Restart the build in another terminal or after the build interrupted Diality's Embedded Leahi Yocto (ELY) -------------------------------------------- -On any changes has been made to the manifest tun the following to get the ELY update. -``` - -time screen bitbake ely-image-qt -``` - Update Diality's Embedded Leahi Yocto (ELY) ------------------------------------------- On any changes has been made to the manifest tun the following to get the ELY update. @@ -151,16 +113,24 @@ time bitbake dey-image-qt-swu -c cleansstate && time bitbake dey-image-qt-swu ``` +Quick Note +---------- +1. mkdir leahi-distro +2. cd leahi-distro +3. repo init -u git@bitbucket.org:diality-cloud/leahi-distro-manifest.git +4. repo sync +5. . ./mkproject.sh -m meta-leahi -p leahi +5. ./ely-build-image.sh BETA + DRAFT NOTE -manifest: the manifest repo tool uses to clone the required projects/recipes. - - -distro : repo that manifest brings in that include all the layesrs and recipes. - - -manufact: any updatet to the application need to be embedded in the ELY image. +---------- + - manifest: the manifest repo tool uses to clone the required projects/recipes. + - distro : repo that manifest brings in that include all the layesrs and recipes. + - manufact: any updatet to the application need to be embedded in the ELY image. - update.sh: updates the local repo from the local application Project ( for now ) - it may need to change when we use it on the build server -image : the final build of the ELY with scripts to flash the device manually. + - image : the final build of the ELY with scripts to flash the device manually. - download.sh: downloads the last built images from the build servers. - fasstboot 0: has to be run on the device to make the mmc available for the flashing. - ./install_linux_fw_uuu.sh: flashing the board.