[HOWTO] build eOS in old fashioned way with breakfast -- now with interactive script

eOSWiki HOWTOs
182

Sometimes characters that are not 100% compatible are entered. If this is the problem, it is solved in linux like this:

dos2unix file.sh

2 Likes
183

The solution is to give the link of the folder and not the file, this way you don’t have to care about links.

184

At the beginning, the line :
repo init https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
needs to be back to :
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo

If not it fails because repo command not found.

185

Ups, Do I have changed the wrong line … sorry, will change it back soon

1 Like
186

New goal : build for LineageOS supported devices (without docker).

I tried with “peach”, Nougat sources for LineageOS are available.

Here is the logs (I cut the repo sync part).

I don’t have roomservice and haven’t put vendor in “vendor/ark” (or something like this), because I don’t understand why nothing is required with docker and why something would be needed with this method.

Thank you :slight_smile: (whoever you are)

187

With old fashioned way method is easy to build LineageOS.
I made a little modifications into @harvey186 's script, and I can choose to build /e/Os or LineageOS:

read -p "Que sincronizo 1=/e/ ; 2=lineageOS ? " OS
if [ $OS -eq 1 ]; then
  echo "Sincronizando repositorio de /e/"
  repo init -u https://gitlab.e.foundation/e/os/releases.git -b v1-pie
else
  if [ $OS -eq 2 ]; then
    echo "Sincronizando repositorio de LineageOS"
    repo init -u https://github.com/LineageOS/android.git -b lineage-16.0
  else
    echo "Opcion incorrecta"
    exit
  fi
fi
1 Like
188

If the build script will find needed sources in LOS git, it will downloaded them automatically. But there is no vendor sources in OS git, so you have to add it by your own. You can try this: Clone it manually to you sources. Than you don’t need the created a roomservice.xml

By the way, I think you are using eOS sources, or not ?

And you should have a look in device/ ineage.dependencies if all needed sources are available, incl. all kernel sources

189

Indeed looks like it’s not, I thought the vendor was automatically downloaded from TheMuppets :
https://github.com/TheMuppets/proprietary_vendor_ark

I clicked on Clone, then I unzipped it and save the “peach” directory in /home/android/e/vendor

And now the build has started successfully, thanks !
Edit : it just failed at 685/34033 grrrr Let’s see…

Yes I use /e/ source since I want to build /e/.

190

only with docker. On old fashioned way, you have to ensure for your own, that all sources are available

1 Like
191

I think it has to be
/home/android/e/vendor/ark/

the peach folder must be in /home/android/e/vendor/ark/
than it is OK

192

Yes everything seems to be here.

Looks like stupid mistakes will always be nearby, thanks.

Sadly it keeps failing, always at the same point.

193

your locale is wrong.

:weary: I#m always forget the right way to set. Must search for

194

try this: export LC_ALL=C you can put it in script, or cmd line.

195

Indeed it worked.
(I wasn’t pasting the right set of keywords on my search engine…)
Thank you for your constant big help !

1 Like
196

Has anyone attempted a build using @harvey186 instructions for galaxy sm-t580?

197

I see no problem building it. Sources you can find here if it is the same as A6+ https://forum.xda-developers.com/galaxy-a6/development/rom-lineageos-16-0-galaxy-a6-plus-t4019619

EDIT: The device seems to be treble supporting. Than you can try the eOS PIE-GSI. Example/HowTo here [HOWTO] install eOS GSI on a Treble device - new GSI added June 14th

198

The t580 is a Tab A so would need different source. I was able to build a lineage17.1 rom this week with help from more experienced guys

199

downgrading from 10 to 9 could be difficult, especially on Samsung devices. But if you will find the needed Los16 sources, you can try building.

200

By the way, save your los17 device sources.you will need them for eOS-Q :wink:

201

Hi, after 4 builds, my storage space is almost full. What can I do, delete and optimize to build for an infinity of devices ?
Note : I only need to build for a device one time (so ne need to keep data about a device for a futur build)
But since I will build for dozens of devices, some of them share the same kernel and other things.

First, I guess I can delete the full “device” directory in out/target/product/“device” right ? But will it be enough ?

Do you have other tips in order not to have full storage issues ans save storage please ? :slight_smile: