Mmm permettimi di dissentire
make -jobs va dato con n+1 core!
Dual core --> make -j3
quad core --> make -j5

:D

Te lo permetto eccome! Il fatto è che la regola generale del "core fisici +1" certe volte non è del tutto affidabile. In fase di compilazione del kernel linux con hyperthreading attivato un quadcore i7 ottiene addirittura i migliori risultati con -j10, fatti conto....

come siete messi con i lavori?

Maluccio, direi: aspettavo qualcuno che si mettesse in pari per proseguire ma si vede che la cosa ormai è sfumata. D'altra parte, con la nuova .bin di Eclair, molti problemi si sono risolti da sè.

però spero non rinunciate!
questo forum sta crescendo anche a livello di developer, o comunque gente che in programmazione sta iniziando a dilettarsi, e sarebbe un peccato mollare tutto.

già purtroppo non saprei da dove cominciare per darvi 1 mano nn ho assolutamente idea da dove partire per darvi 1 mano....

io per ora sono troppo impegnato con gli esami (meledetta ingegneria areospaziale ihihihihih) quindi sono un po a corto di tempo lol...(infatti mi si vede un po meno del solito sul forum)

Io potrei rendermi utile...dipende da una cosa: se sarò preso come developer Archlinux

ecco non si finisce mai di imparare :D

Sto vendendo il liquid e sto già maneggiando un milestone....direi che per me l'avventura finisce qui. Spero di contribuire al meglio nel forum Motosola, arrivederci a tutti!

grazie ad aux ora possiamo provare a compilare un rom AOSP


So, technical details.

Google decided to use prelinking technique to speed everything up and to waste as little RAM as possible. Great! So they took prelink utility and modified it to fit their needs. Two tools were born: apriori and soslim. They are run on every build to produce optimized and prelinked system libs. Almost every .so file you see in /system/lib is prelinked via soslim/apriori.

Prelinking works by loading libs at known base addresses which are defined in a special file . This file contains a list of libs with their predefined base addresses. What Acer did is that they modified this file and did not share it with us. So every AOSP attemp failed. If you compile any lib from Android sources and put it on your Liquid boom happens and nothing works. Studying Android sources I've found a small utility which is called isprelinked. It checks binary library if it is prelinked and if it is, then base address is shown.

So yesterday I ran isprelinked on Acer libs and recreated prelink-linux-arm.map for Liquid. Then I built test version of webkit (libwebcore.so), put it into /system/lib replacing version from Acer and rebooted the phone - it worked! I can not share prelink map at the moment - it is at my home PC and I don't have remote access. I will share this file in the evening, but you can make it yourself, actually.

How to make prelink map? Quite simple. First of all you need to create isprelinked binary. cd to your Android source (cd ~/mydroid as in docs) and run "make isprelinked" (without quotes, of course). You will get app binary in a while, it will be somewhere in ~/mydroid/out/host/bla-bla-bla. The correct path will be shown in console once compilation is done.

Next step is run isprelinked over Acer binaries. It is quite simple, but will take some time. Copy all libs from your Liquid to some folder, for example to ~/acer-libs. Now open original prelink map (make a backup!), copy its contents to empty text file, in this new text file remove comments and base addresses, leave only lib names. Put a new line at top with full path to isprelinked and merge all lib names into single line with spaces between. You should have text file with one line looking like this:

CODE
~/mydroid/out/host/tools/isprelinked libdl.so libc.so libstdc++.so


This line will be very long (: Now go back into console, cd ~/acer-libs and run this BIG line. It will fail (: Because this list has some libs which Acer does not have. It will fail WITHOUT telling which lib is missing. But you will see base addr of previous lib. So find all unneeded libs and remove them from command line. Hell of a work, actually. But once again - I'm not at home, I can not paste correct line at the moment. Sorry.

Once isprelinked runs clean without errors you will see a list of all libs and their base addresses. Remove ":" character between lib name and address, paste it into prelink-linux-arm.map replacing all previous contents (you made a backup, right?) and this part is finished - now you have all base addresses needed for successful compilation of system binaries.

But if you run compilation now it will fail - apriori will tell you that lib addresses are out of bound. You need to modify prelinkmap.c. There is a line:

CODE
#define PRELINK_MIN 0x90000000


Change it to:

CODE
#define PRELINK_MIN 0x50000000


And recompile apriori tool with "make apriori" from your ~/mydroid. Now you have a 100% Acer compatible build environment!

Now if you wish to compile any component just run "make SOMETHING" where SOMETHING is what you need to compile. For example, "make libwebcore" compiles WebKit (: This is the simplest way of compilation, but you also want to make Snapdragon optimizations generated. So you need to compile with additional option TARGET_ARCH_VARIANT to target Snapdragon. SD has armv7-a CPU inside. So final string for WebKit is "make TARGET_ARCH_VARIANT=armv7-a libwebcore". That will make default WebKit with all CPU dependent optimizations. Compilation result can be found in ~/mydroid/out/target/system/lib - full and correct path will be shown in console after compilation.

What does it all mean? Well, AOSP is finally possible! This will also be helpful for porting binaries from other non-acer ROMs - now you can easily rebase libs to Acer standard and everything will work.

Today I will put map file I've generated from Acer libs and will continue working on Flash support for 2.1. I also think I will compile Flash supporting WebKit with V8 JavaScript engine (like in Froyo), SVG support and I will look into animated GIFs issue. There will be two libwebcores from me: stock with Flash and full-blown (which may eat your RAM and kill CPU).

ci stai provando con il metodo appena descritto? io ci sto facendo più di un pensierino già per Eclair.

thon sono un po incasinato con gli esami..e probabilmente forse mi chiamano per un partime 30 a settimana da fnac hihiihhi quindi non so se riuscirò a provarci..speriamo che qualcuno (dato che ormai si può) compili una bella AOSP per il liquid lol