Hi,
Summary of issues status:
external/ffmpeg: IIRC you said that ffmpeg is not much used in lollipop - but it is almost effortless to add the new file and be able to build multiarch
Copied /external/ffmpeg/android/config-x86.mak to /external/ffmpeg/android/config-x86_64.mak
and added this line
...
ARCH_X86_32:=yes
+ARCH_X86_64:=yes
!HAVE_ARMV5TE:=yes
...
external/mesa: OK - Just a check about ASM optimizations.
I kept building but with ASM optimization disabled, because I had build errors with 64bit ASM code - Did you overcome this problem with your Android.mk files "magic"?
external/drm: OK problem was solved in lollipop-x86 branch
external/libpciaccess: OK, it was added to lollipop-x86 branch
hardware/drm_gralloc: OK as in lollipop-x86 branch
bluetooth share crashing: OK as in lollipop-x86 branch
972 error at app install: Problem assessed EXT4 needed.
Problem should be solved by bringing EXT4 support with Gabriel's patch to installer - It could solve some problems in formatting ETX3 too, if I'm not wrong.
system.img+ too large when building with gapps: to be solved in lollipop-x86 branch.
Solution: Edit /home/utente/lollipop-x86/device/generic/common/BoardConfig.mk
BOARD_SYSTEMIMAGE_PARTITION_SIZE = $(if $(MKSQUASHFS),0,1207959552) #was 1073741824
wifi authentication problem: It was solved at some point, but I don't remember exactly when.
sign-in crashing due to OpenGL sync queries: Patch available.
Feasible alignments to kitkat-x86:
kernel: just a check- is kernel already 3.18.x for lollipop-x86 branch?
enable nouveau: enable nouveau in device/generic/common/BoardConfig.mk and update init.sh - init_hal_gralloc() to detect 0*nouveaufb|0*svgadrmfb
That should be all.
For the details, I have kept track on the attached file about all the changes up to Dec 28th, but there were not much changes after.
Mauro
PS: as an off-topic I am advancing in the build of mesa-git to keep the Android.mk files up to date.
I almost completed mesa 10.6.0-devel build for x86 - just i965_dri has building errors now.
I am far from being the "oibaf" for Android-x86 - always having the mesa-git build up and running - but this will become useful for new mesa releases integration (at the time when needed).
I have a problem with a dependency - I'll write you and pstglia a PM about this.
As an objective I'd like to write a little vademecum (me as first user needing it) for porting native C/C++ projects to Android-x86, trying to cover all scenarios with generated sources and "How to create/update an Android.mk looking at existing
makefile.am"